📅 Original date posted:2015-01-30
📝 Original message:On the Chinese "Single's Day" (sort of like the american Black Friday)
according to MIT's Tech Review
<http://www.technologyreview.com/news/534001/alipay-leads-a-digital-finance-revolution-in-china/>;
magazine
"Alipay handled up to 2.85 million transactions per minute, and 54 percent
of its transactions are made via mobile device."
For a few weeks I've been reading the conversations about block sizes and
the experiments being done on the subject with larger blocks.
On the day with the most transactions, the Bitcoin block chain averages
about 73 transactions per minute. I kept wondering what blocksize we'd need
for handling 100,000 transactions per minute, and estimated that roughly
we'd need a blocksize of about 1300x times larger than what we have now, so
bigger than 1Gb block... but seeing the numbers Alipay gets to handle just
in China make me wonder how scalable is Bitcoin if it were to truly compete
with worldwide financial services.
If you were to include double the number Alipay can handle, you'd be
shooting about 6 million transactions per minute, or roughly 60 million
transactions per block.
If you average every transaction around 250 bytes, then you'd need ~15
Gigabytes per block to be broadcast and hashed by all the full nodes every
10 minutes, eating good 2Tb of storage daily... do miners have enough
bandwidth and CPU power to handle this?
are my scalability concerns absurd?
http://twitter.com/gubatron
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150131/3b354179/attachment.html>;
Angel Leon [ARCHIVE] /
npub1c8…zgzt8
2023-06-07 15:29:07
in reply to nevent1q…0nqs
Author Public Key
npub1c8flqlwmkh5vehm7rfcacurk9x5ggv36vtra2p97thynzfq0vxus5zgzt8Published at
2023-06-07 15:29:07Event JSON
{
"id": "899e0a1170d94788e5a952150ccfdd47b4bc86c1298618a60caeb0fdb04196b9",
"pubkey": "c1d3f07ddbb5e8ccdf7e1a71dc707629a884323a62c7d504be5dc931240f61b9",
"created_at": 1686151747,
"kind": 1,
"tags": [
[
"e",
"80b2849bae4f1d58112b12e74d6c62714729bcd70f146bc9248c7e90e134db34",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2015-01-30\n📝 Original message:On the Chinese \"Single's Day\" (sort of like the american Black Friday)\naccording to MIT's Tech Review\n\u003chttp://www.technologyreview.com/news/534001/alipay-leads-a-digital-finance-revolution-in-china/\u003e\nmagazine\n\n\"Alipay handled up to 2.85 million transactions per minute, and 54 percent\nof its transactions are made via mobile device.\"\n\nFor a few weeks I've been reading the conversations about block sizes and\nthe experiments being done on the subject with larger blocks.\n\nOn the day with the most transactions, the Bitcoin block chain averages\nabout 73 transactions per minute. I kept wondering what blocksize we'd need\nfor handling 100,000 transactions per minute, and estimated that roughly\nwe'd need a blocksize of about 1300x times larger than what we have now, so\nbigger than 1Gb block... but seeing the numbers Alipay gets to handle just\nin China make me wonder how scalable is Bitcoin if it were to truly compete\nwith worldwide financial services.\n\nIf you were to include double the number Alipay can handle, you'd be\nshooting about 6 million transactions per minute, or roughly 60 million\ntransactions per block.\n\nIf you average every transaction around 250 bytes, then you'd need ~15\nGigabytes per block to be broadcast and hashed by all the full nodes every\n10 minutes, eating good 2Tb of storage daily... do miners have enough\nbandwidth and CPU power to handle this?\n\nare my scalability concerns absurd?\n\nhttp://twitter.com/gubatron\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150131/3b354179/attachment.html\u003e",
"sig": "d4b3d84110a0f5fbbb390db763ddca2dc8ed2c20d69aed4ebc68bd7265a86eeea696b9f84c62c9e2442ce7f3b8cefc7027c0e401b81aebcc8efba9b6ca7bda08"
}