209 похожих чатов

I think that's 8MB, and we technically have a 32MB

limit (until some future hardfork), but 8 is the configured default limit for all nodes, so bigger blocks than 8MB might have trouble propagating atm regardless of the protocol limit. So what does theoretical mean? Because I know much bigger blocks than even 32MB have been tested on testnets with bigger limits.

11 ответов

9 просмотров

oh i mean the transactions per second (tps), not the block size.

Dustin 🪐- Автор вопроса
Joemar Taganna
oh i mean the transactions per second (tps), not t...

Right, and I think 300 tps is the limit of 8MB blocks. So depending on how that scales, maybe it's technically 1200 (basic math, maybe not that simple), but that's depending on who you ask and how you define technical. With a hard fork, it can theoretically go much higher, but it also theoretically only be 800 now because of the default node config.

i see. since we have 32mb max block size limit, max tps is a lot higher than 300tps.

Dustin 🪐- Автор вопроса
Joemar Taganna
i see. since we have 32mb max block size limit, ma...

I believe so, but I could be super wrong, and 300 could be 32mb

Joemar Taganna
i see. since we have 32mb max block size limit, ma...

Roughed out the math. 32,000,000 bytes divided by average transaction size of around 250 bytes, equals 128,000 transactions per 10-minute block, divided by 600 seconds, equals 213 tps.

Powell Quesne
Roughed out the math. 32,000,000 bytes divided by ...

thanks. this then sets the theoretical tps. i wonder if there are other factors that can influence tps other than block size. speed of tx propagation in mempool perhaps?

Joemar Taganna
thanks. this then sets the theoretical tps. i wond...

There are all sorts of attacks possible, so it's really ideally.

Dustin 🪐- Автор вопроса
Joemar Taganna
thanks. this then sets the theoretical tps. i wond...

That's the average confirmed TPS, mempool can likely accept several thousand transactions in a given second, but once the number of transactions in mempool over a given time under 10 minutes exceeds the number of transactions that fit in a block, some transactions will have to wait for the next block. This doesn't matter for most transactions until/unless the volume is sustained for a longer time. Put another way, TPS is only relevant when it is consistently exceeded, because this leads to a tx fee market as has been seen on BTC. However, it arguably also matters in the interest of being prepared for adoption without the negative repercussions of a fee market. Would suck to have bigger blocks 9 months away while needed today.

Dustin 🪐
That's the average confirmed TPS, mempool can like...

What is the best resource published so far about BCH max TPS?

Joemar Taganna
thanks. this then sets the theoretical tps. i wond...

Propagation speed can limit things further, but modern networks are pretty good, except.... I heard there was a problem specifically with all the miners behind the Great Firewall of China, which imposes huge amounts of packet loss on anything trying to go through. Because most SHA256 mining was based in China until recently, this was a big problem but could be changing now that miners are going international. I'm not aware of any insurmountable obstacles to BCH going to 256mb blocks as soon as the usage get anywhere near that, say if it exceeds 8mb, that would a good time to backport the 256mb limit from scalenet, so that gets it to the 1800-2400tps range. And by then scalenet will probably be doing 1gb blocks.

Cheapy 🪐🌭
What is the best resource published so far about B...

I know Peter boasted about viability of 1GB blocks years ago already https://twitter.com/PeterRizun/status/1257698192721801217

Похожие вопросы

Обсуждают сегодня

Карта сайта