Peck by twetch#2432

19YN95…8BB9 Key · twetch

Wonder why #BSV does not showcase any truly big blocks?

We barely broke 100MB, miles away from the 512MB soft cap of 2019 and galaxies away from 2GB+, which - in theory - should work now.
The answer:
The network cant handle it (yet).

What the chain says

Transaction: e5f2262e75d68d3ee9dc14cd14c25f585651c42201fc4971bac9482d51ad9f40
Block: 626 443
Time: 2020-03-16T08:59:25Z
Signer: 19YN95JqM59DQSsojsMnNvAQK9WEoc8BB9
App: twetch
Type: post
Content type: text/plain
Name in tx: twetch#2432

Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.

Signed by 19YN95JqM59DQSsojsMnNvAQK9WEoc8BB9 Verified

Replies (2)

twetch#2432 6.6y

19YN95…8BB9 Key · twetch

Replying to@19YN95…8BB9

Even if the code can handle it (and it most likely can, which could be seen on the test net), it doesnt mean the main net can handle it.
Most miners & related business-nodes & services are not capable of propagating and compute such big blocks right now.

twetch#2432 6.6y

19YN95…8BB9 Key · twetch

Replying to@19YN95…8BB9

This will hopefully change gradually over time.
But for now, the promise of "unlimited scaling" is just a marketing slogan, a vague future promise - instead of an actual reality.
You think i am wrong?
Too bad.. you cant prove me wrong.
Only big blocks can!

Post by twetch#2432

Replies (2)