Pages:
Author

Topic: Hello BCH: 2.26 MB & we keep 1MB - page 2. (Read 368 times)

legendary
Activity: 4410
Merit: 4766
September 19, 2018, 06:04:35 AM
#14
development still required me thinks

That's correct. I've read somewhere that Schnorr signatures could reduce the transaction sizes by some 25% (average) and would also add more privacy.
I don't know yet if there are unwanted side effects in that though... We'll live and see...

But Segwit is in the right direction in my opinion. Because with it will come other inclusive soft forks like Schnorr that would improve on-chain scalability.

ok heres a lesson for you both
the 1mb limit still exists in the bitcoin core network.
transaction data needs to sit in the 1mb limit. but Segwit lets signatures sit outside.
the reason the block in this topics example is what it is.. is because alot of signature data sits outside the 1mb area. but.. that leaves space inside the 1mb are.. hense why the OP's example only has a few hundred transactions as oppose to a couple thousand

schnorr will reduce the amount of signatures thus bring down only the witness area weight. but it still does not sort out the limitation of the 1mb area

what needs to happen is completely remove the 1mb limit so all the legacy transaction data can utilise the entire 4mb weight. which then means we actually get more transaction capacity per mb (4x with a true no hidden sublimit, 4mb block)

the math was already done and the consensus is if EVERY transaction was a LEAN SEGWIT. the best hope would be 2.1x increase of transactions.

but at the moment it still sits at only 10% segwit utility.
(i know people will say its 40%. but thats not the case. the graph showing such treats a mixed tx of legacy and segwit as a full segwit which misleads the reality of real statistics)

in short. if schnorr was used the OP's example would still only be a couple hundred transactions but the weight outside the 1mb limit would be less.
meaning schnorr is not scaling. is unbloating the bloat of the 'witness' area

legendary
Activity: 2898
Merit: 1823
September 19, 2018, 02:40:29 AM
#13

development still required me thinks

That is true. I believe that the development on the network's latency, block propagation, and "time-locked, off-chain" transactions should be first explored before making a development roadmap for increasing block sizes.

But Segwit is in the right direction in my opinion. Because with it will come other inclusive soft forks like Schnorr that would improve on-chain scalability.
sr. member
Activity: 365
Merit: 250
September 19, 2018, 12:55:41 AM
#12
I don't know how anyone could fall for that BCH propaganda they are pushing.
hero member
Activity: 3150
Merit: 937
September 19, 2018, 12:49:55 AM
#11
I don't think that Roger Ver cares about the BCH block size.It's all about the money,not about the technology.
BCH can still make him a few millions worth of USD,despite the fact that bitcoin cash is a shitty altcoin.
The "scaling" debate is now over and bitcoin core won. Grin
legendary
Activity: 3668
Merit: 6382
Looking for campaign manager? Contact icopress!
September 19, 2018, 12:00:23 AM
#10
development still required me thinks

That's correct. I've read somewhere that Schnorr signatures could reduce the transaction sizes by some 25% (average) and would also add more privacy.
I don't know yet if there are unwanted side effects in that though... We'll live and see...
legendary
Activity: 4410
Merit: 4766
September 18, 2018, 03:18:38 PM
#9
a 2.26mb block..
but such a shame it doesnt amount to 5000 transactions on such a big block.
such a waste of space. only a couple hundred transactions for over 2mb of space.

development still required me thinks
hero member
Activity: 782
Merit: 500
September 18, 2018, 03:15:50 PM
#8
BCH average block size is 50 KB and although is only 3% of Bitcoin beside this Bitcoin has average 1.3 MB block size. But I believe BCH has the potentialities to go forward for its unique features.


Changing block size is unique? Been there done that.
hero member
Activity: 1470
Merit: 655
September 17, 2018, 04:25:20 AM
#7
Congratulations... We can have huge blocks and our 0 confirm transaction system is not less secure because of segwit.

0 confirmations were NEVER secure, only an idiot would think otherwise.

The fact that you have huge blocks and the usage is even less than Dogecoin should really make you think twice. How can you not see that huge block space is a big target for anyone with enough funds to start a spam attack and clutter the network? (I mean, someone serious, unlike the Bitpico scammers)

there is no point spam attacking something that is not used. a spam attack requires incentive so that the attacker gains something out of that attack. it is never done for trolling or having fun! LOL
for example the spam attack against bitcoin had multiple possible reasons: altcoin pumpers pumping their altcoins with the premise that bitcoin is slow and they will replace it. big blockers spamming bitcoin to say we need bigger blocks. the miners spamming bitcoin to earn more fees as the fees went to the moon. government agents wanting to destroy bitcoin or at least slow down its adoption.

but what would you gain by spamming BCH?!!!
legendary
Activity: 3668
Merit: 6382
Looking for campaign manager? Contact icopress!
September 17, 2018, 04:15:21 AM
#6
The fact that you have huge blocks and the usage is even less than Dogecoin should really make you think twice. How can you not see that huge block space is a big target for anyone with enough funds to start a spam attack and clutter the network? (I mean, someone serious, unlike the Bitpico scammers)

After millions were spend in a hype attempt for Bcash, it's hard for them to understand they are continuously pissing against the wind.
In truth I also don't understand why would somebody buy an over-hyped altcoin with no real use nor special functionality at 450$ a piece.
Your Dogecoin example is pretty good, although Dogecoin still has a nice community which I am not sure Bcash has.
legendary
Activity: 1372
Merit: 1252
September 16, 2018, 06:15:59 PM
#5
Congratulations... We can have huge blocks and our 0 confirm transaction system is not less secure because of segwit.

0 confirmations were NEVER secure, only an idiot would think otherwise.

The fact that you have huge blocks and the usage is even less than Dogecoin should really make you think twice. How can you not see that huge block space is a big target for anyone with enough funds to start a spam attack and clutter the network? (I mean, someone serious, unlike the Bitpico scammers)
newbie
Activity: 70
Merit: 0
September 16, 2018, 04:17:14 PM
#4
We might have huge barrier and our zero ascertain transaction system is much secured because of segwit. Bitcoin has 4 megabytes of block and 32 MB of BCH but Bitcoin blockchain is larger than 45.4 GB.
hero member
Activity: 1470
Merit: 655
September 11, 2018, 05:01:33 AM
#3
we have had at least 50x  2MB+ blocks already. check blocks such as 505253, 508116, 531885, 505225,...

here is the funny part! bitcoin has 4 MB blocks and BCH has 32 MB blocks but bitcoin blockchain is currently 45.4 GB bigger than BCH blockchain despite BCH being about 7000 blocks ahead of bitcoin Cheesy

the fund doesn't stop there.
bitcoin average block size is about 1.3 MB while BCH average block size is 50 kB which is only 3% of bitcoin Grin
sr. member
Activity: 378
Merit: 260
Bitcoin SV is Bitcoin
September 11, 2018, 04:15:20 AM
#2
Congratulations... We can have huge blocks and our 0 confirm transaction system is not less secure because of segwit.
legendary
Activity: 2702
Merit: 4002
September 11, 2018, 04:13:56 AM
#1
Hello Roger Ver:
Did you know that we were able to achieve 2.26MB block size "on-chain transactions" without changing 1 MB block size limit?. Thanks, #segwit.
Hash: 00000000000000000021868c2cefc52a480d173c849412fe81c4e5ab806f94ab
https://www.blockchain.com/btc/block/00000000000000000021868c2cefc52a480d173c849412fe81c4e5ab806f94ab
This is a whole without the need for lightning network, more low fees.
*** I do not know if anyone has posted this, please let me know to lock it.

Pages:
Jump to: