I'm unsubbing from this topic cause BitcoinHoarder is just offtopic shitposting 24/7. We really need that block feature yesterday.
We really need that "block" functionality in Memo... Spam is getting out of hand.
BU is a separate team and I think they have a good chunk of the nodes that run their client. No? And what mass censorship? I see SVs viewpoints everywhere just fine.
cockblockstream can you please stop shitposting and answer me for a moment?
Or is it about the ticker name?
Is it hard for BSV users to understand that some of us that like BCH don't care if regulators won't like out coin etc?
It's not hard for me to understand why some people prefer BSV. I have no idea why people like CSW but as far as the ideas of BSV go, it's a legit position even if I think it's inferior to BCH.
I'm really not sure why we're fighting anymore about the two coins. We both got what we wanted, so what's the problem now?
Yes I like their roadmap. Although I prefer BU when it comes to keeping better PR.
How is Avalanche PoS? Why do people say it is?? Isn't it based on the last 100 mined blocks therefore an extension of PoW? What's the "stake" in Avalanche?
Maybe HL3 will need a QC to run it. They always released every time with new tech.
Sell stuff you don't need on OpenBazzar. Or offer your services on OpenBazzar.
It happened again. Can't post something from the main site, I switch to abc and I can post it, but I see the tx on the SV chain as well. wtf.
Actually no... This one is on both chains! Argh not sure what is going on. :-D
I think I run out of something, then switched to the abc site and I'm able to post again. But I have split protection and broadcast to both... Blockexplorers show txs only on abc now for me.
In other words, does the main website show only messages that exist on both chains? Or on either?
I'm wondering, if I run out of unsplit coins, and charge my wallet with coins only on the bch(abc) side, and disable the split protection in order to be able to use them, will my msgs be seen here?
So they would calculate more than 2.2MB of ordering info in the VISA example I gave above.
The mention n*log2(n) bits of info for ordering n transactions. This is the same as log2(n^n). I believe that's an overestimate, I think that you need log2(n!) which is always lower.
I'm not an expert or anything so it would be great if someone could doublecheck me btw. :-) Also I noticed that the Graphene whitepaper mentions a formula which would give even higher numbers.
So for VISA level of txs per second (1000200txs/block), CTOR will cut down about 2.2MB of ordering info from graphene if I get this right.
bytes! not bits, sorry. 2.5 bytes.
Nah I think I'm right. If you have about 1mil txs in a block, each extra tx will be adding 2.5bits of info to graphene.So the ordering info is quite linear in the block sizes that we have now.
Or maybe I have some mistake in my calculations. I'll double check later.
