Any fully decentralized crypto at the scale of use that the Web Monetization API would need would have enormous tx prices. There are ways to scale this, ie the lightning network, but those are essentially centralized solutions to scale.
Any fully decentralized crypto at the scale of use that the Web Monetization API would need would have enormous tx prices. There are ways to scale this, ie the lightning network, but those are essentially centralized solutions to scale.
There is however no technical reason we should limit the blocksize to 1mb. We could have 10mb or even 100mb blocksizes easily. Realistically a 100mb block would be large enough to handle all transaction data our species currently generates.
The transaction fee is a considerable portion of miner's revenue. Miners ultimately are responsibility for making changes to the bitcoin protocol. I think it's unlikely bitcoin miners will vote for a higher blocksize because it will cause short term decreases in revenue. However, they are missing a potential boon from the Jevons paradox -- the cheaper a resource becomes to use the more of the resource we use.
So in summary, it's not really a technical limit to have a high transaction volume but we aren't likely to see it from the current big coins.
Edit: The problem is not 100mb is too small for the future. The problem is that just like we cannot go from 1mb to 100mb today, we would have no ability to go from 100mb to 1000mb when needed.
Otherwise it would've been long superseded by other chains.
Bitcoiners still arguing about the solidity of the network guaranteed by so much mining, yet virtually all the mining is in the hands of few specialized operations all knowing each other (so it's not really decentralized) and despite Ethereum proving new protocol to be a valid and safe alternative.
None of Bitcoin cultists at the end of the day understood that it wasn't about algorithms nor computers, but consensus among people.
And that consensus voted to have Bitcoin, the oldest and least technologically developed chain to be the "store of value" of cryptocurrencies.
Nonsense.
With the current block size and average transaction size, the bitcoin network processes ~7 transactions per second. A 100X increase in block size gets you to 700 transactions per second. A quick google says global credit card transactions currently average more than 21,000 per second.
You're still almost two orders of magnitude off, and that's just existing credit card transactions.
The complete blockchain is currently about half a TB.
According to bitcoin technology experts, a network of Full Nodes is more secure than a network of Partial Nodes. Right now almost anyone can run a Full Node. If you make the blockchain grow by 1.5 TB per day, only big corporations will be able to run Full Nodes.
So no, existing storage and network transfer is not sufficient for large block sizes, at least not for the current way we validate BTC transactions. I assume if there was a good technology fix for the full/partial node issue, it would have been implemented already.
Other networks were designed for speed and others are working on it (etherum with layer 2 networks, and more speed focused networks, for instance as was mentioned Nano was doing 1200-1500tps years ago, with plans for increases not sure if thtey eer went further.
The problem is crypto has a few solid real projects and a billion loud useless scam/spam projects that make the idea of "crypto" look like its all trash, finding the networks that actually have something to really give to the world is hard.
Your claim is opposed to the contents of the original Bitcoin whitepaper
The bitcoin white paper clearly describes the goal as a digital cash with and low fee transactions without the used of a trusted third party. We have none of those today in bitcoin.
I was using the term "speed" as a concept, and you were using it as a constant. I referred to "speed" as "fast" or "slow." Which is to say, the subjective judgement on what is fast. Which is a decent way to default to judging speed unless the white paper specifies a threshold of transactions per second to be considered "fast." You thought of speed as a constant unit of measurement for speed, which makes no sense unless they have a target for their transactions per second. The problem with that is, the number of transactions per second that a payment solution needs to process is pretty much only going to increase over time, and thus, the goal to be considered "fast" does actually change over time. You're just potentially thinking in too short of a time range to see much drift in that subjective judgement.
I think you're mistaking my intention too. My intention is to say that Bitcoin's perceived speed with handling transactions then, is perhaps slow by today's standards. The goal you gave:
> digital cash with and low fee transactions without the used of a trusted third party.
is at least 2/3rd of the way complete. You have digital cash, with high transaction fees, and no trusted third party. The solution that blockchain designers/engineers seem to have come up with is referred to as "layer 2 rollups" where a bunch of transactions are processed quickly by a trusted third party, bundled together, and then enforced in one big transaction on the actual network in intervals. This promises to be faster, and possibly cost less in transaction fees, but then under-delivers on the third goal of not using a trusted third party. But it is apparently the best way that blockchain engineers have thought up to compete with the transaction processing speed of entities like VISA, at least today. While it's not ideal to trust that third party, presumably you have a choice to opt in or out of the layer 2 network, and enforce your transaction on the slower, more traditional blockchain layer 1. And at least with the layer 2 network, it eventually gets trued up on the blockchain with each of the rollup intervals. It's maybe up for an argument on whether trusting the layer 2 third party is better than, or the same as, trusting VISA. I would potentially argue that it's better, with the caveat of admitting that I am not a blockchain expert. I just potentially know more than the average crypto enthusiast that trades BTC and Doge on institutions like Coinbase.
I will note that the goal you gave said absolutely nothing about speed though.
>> The problem is crypto has a few solid real projects and a billion loud useless scam/spam projects that make the idea of "crypto" look like its all trash, finding the networks that actually have something to really give to the world is hard
Congrats to the OP who sent money to Vietnam. It's a fantastic use case. But as a non-crypto user I can't do that with crypto because I don't know which site to trust and which is a scam.
And -reputationally- they are -all scams-, some just haven't been caught yet.
(I know, I know, there are honest players, but even the -big names I recognise- get caught with their hands in the cookie jar, that taints everyone)
Incompetents like MtGox and FTX lasted only a few years. OP claims the service they used has been operating for a decade already.
Same for the underlying tech : Bitcoin, Etherium and even Monero have also been around for a decent amount of time. (Of course you might refuse to use them for other reasons, like the wasteful power usage of Bitcoin or the money laundering enabled by Monero.)
(Note that this can generally be applied to anything money-related...)
Some nodes are more popular than others for open a channel to, but there are still several thousands, so calling it centralized is misleading.
The reason adoption has been so low is that with current hardware you cannot run a full node in a phone, so you either get a server to run a full node or you trade-off some control/security of your coins
There are still other theoretical problems, mostly things like denial-of-services, but adoption has been what has stagnated it.
The hardware/control tradeoff is a real PITA, we need a phone with like 50x more battery or efficient to be able to run lightning in a completely self-custodial manner
And there are still some people advocating for blocksize increase, which will make the problems of lightning even worse