Bitcoin has proven time and time again to be a giant ponzi scheme

https://www.reddit.com/r/buttcoin contains good reading

See Moldbug's excellent essay "Bitcoin is money, Bitcoin is a bubble" [1]

[1] http://unqualified-reservations.blogspot.com/2013/04/bitcoin...

good overview of Bitcoin

Pretty good Bitcoin guide, not so technical and easy to read.

Very good read. Too bad, when the author talks about power of algorithms, he doesn't mention Bitcoin and Ethereum.

Matt Mullenweg did alright. Whoever wrote Bitcoin probably did ok too.

Of Reamde by Neal Stephenson:

> The hero is an aging tech entrepreneur who owns a game that's a combination of World of Warcraft and Bitcoin (yes, this book predicts Bitcoin).

Reamde - published 20 September 2011

Bitcoin - initial release 9 January 2009

Why would a book payment processor use Bitcoin when the average Bitcoin transaction fee is about the same price as many new books? With Bitcoin, you're looking at spending about $50 if you buy a $25 book.

The author clearly doesn’t know what he’s talking about. Bitcoin is an attempt to establish hard money.

The paper introducing Bitcoin (https://bitcoin.org/bitcoin.pdf) is well-written and easy to read. Understanding _how_ it works should be simple.

On the other hand, understanding _why_ it works is difficult, as it requires understanding the hard math underlying the system. In fact, nobody knows _why_ it works, because, AFAIK, we do not know whether the hash functions used have the necessary properties (in fact, it is worse: we do not even know whether one-way functions exist, let alone that we can point to one)

Well it could in theory be that the author of Bitcoin had previously written and released software under their real name but without ever providing the source code for said software, in which case comparing the first binary release of Bitcoin to such executables could give a hint as to who Satoshi is/was.

If I'm reading you, the idea is to essentially to negotiate out-of-band? I remember reading something like this in Bitcoin and Cryptocurrency Technologies with a note saying nobody had tried it in practice.

> (Your analogy to a ledger with account balances is precisely correct for Ethereum, but Bitcoin actually has a somewhat different model.)

My understanding is that in bitcoin it's a log of transactions -- a ledger. Ethereum is instead addresses holding totals -- more like an account statement.

Bitcoin will be a multi-decade artifact at minimum. A novel collectable.

Bitcoin Paper Wallets (2015) | https://news.ycombinator.com/item?id=15302500

would you write Bitcoin in python?

The configuration is the same as Bitcoin.

Basically, the Dogecoin wallet is going to attempt to punch a hole in your firewall with UPnP and any other NAT-busting techniques the author (of Bitcoin) has contrived to enable you to help new nodes to come to sync by sending them blocks from the winning blockchain.

The daemon mode (which listens on an RPC/HTTP port for commands like "send money here") is not going to attempt to run unless you enable a password in your .doge/config (just like bitcoind). RPC clients will need this password to be able to issue commands. If you have one node, then both the client and server will have the same .doge/config and it's secure, assuming they don't guess your password. If you have multiple nodes, this is the way to have a lightweight client that sends commands to your "heavyweight" wallet. If the client doesn't have your RPC password, the client can't do anything that any 'nobody' new node on the network should be able to do.

You can run Dogecoin on public networks, or the Dogecoin wallet has a bug that you should report. Whether it's wise to be in a position to be the first to discover such a bug (by losing all the coins in your wallet), that's another matter, but if there are such bugs in the wallet then it's really not viable, and you should therefore probably sell all your doges immediately.

It's the famous Bitcoin white paper by Satoshi. The linked Ontier press release* quotes Wright's legal team:

>“Dr Wright does not wish to restrict access to his White Paper. However, he does not agree that it should be used by supporters and developers of alternative assets, such as Bitcoin Core, to promote or otherwise misrepresent those assets as being Bitcoin given that they do not support or align with the vision for Bitcoin as he set out in his White Paper.”

They're saying the project bitcoin.org promotes is using the whitepaper dishonestly to promote itself. Which resembles to me a trademark dispute, instead. And usually the trademark or copyright owner has solid proof of ownership.

* https://www.ontier.digital/post/uk-court-awards-bitcoin-crea...

Years ago, there was a presentation [1] by Peter Rizun of Bitcoin Unlimited at Stanford that demonstrated ~100TPS on Bitcoin, and the potential for 1000+ TPS if certain bottlenecks were removed. People said the same thing you're saying back then, but it served to motivate the big block community, and now today BSV routinely does 300+ MB blocks (1000+ tps). This Teranode software is the future of BSV and will become the common node configuration within a few years, so it's worth taking seriously. Also, I left a comment in this thread explaining why this test is more representative than you may think [2].

[1] https://www.youtube.com/watch?v=5SJm2ep3X_M

[2] https://news.ycombinator.com/item?id=27597510

I recently published an intermediate-level e-book on Bitcoin:

http://bitzuma.com/owning-bitcoin/

This is the book I wish had existed when I started learning about Bitcoin in 2011. It's a technical deep-dive for a non-expert audience. Only knowledge of high school algebra and a willingness to learn are assumed. Every technical term comes with a definition. Over 300 figures help visual learners understand complex technical topics. Hundreds of footnotes provide jumping-off points and links to online demos. Cross-links allow you to quickly review prior material in later chapters.

There are eight chapters:

1. Bitcoin from Scratch (the view from 20,000 feet of Bitcoin and its subsystems)

2. Authentication (elliptic curve cryptography)

3. Authorization (Script, transactions, and contracts)

4. Network (block chain, consensus, hard/soft forks, governance, segwit, Lightning Network)

5. Privacy (what can and can't be discovered about users of a public block chain)

6. Security (what to protect and why)

7. Wallets (software for using Bitcoin)

8. Bitcoin in Practice (a complete system for using Bitcoin based on the content in the first seven chapters)