hi all. Long time reader, new account holder, first time poster
I'm not a miner or a serious investor but I love buying into new projects that get me excited. The current ~10 hypers on this thread seem (mostly) legit from watching your total forum activity, not just shillers, and dev has been a total legend over the last 1.5 years, all of which has got me SUPER interested in WBB. The thing I can't wrap my head around is where the real long term value in use cases is for WBB over any other crypto.
I've seen many posts talking about the project making waves but is there somewhere where I can go for a detailed explanation of how this whole project works and where this thing is actually going; not just the business plan.
This isn't about making a quick buck - I'm really interested in any disruptive tech or systems and want to understand the power of the WBB project so I can get behind it fully and become a local advocate. I've downloaded the chat client and am trying to get my friends to use just to intro them to WBB, but I need to understand this project better overall. My guess is that I'm not the only noob out there who is excited by the wildbeast but doesn't fully understand it.
Any help would be greatly appreciated. Keep up the great work dev!
HI,
In a nutshell it is about speed, security, stability and scale-ability.
If we take lets say the grandfather of all (Bitcoin) as a base plus the fact that is local to to each client (user) we could do the following
- We assume there are 6500 to 7000 nodes out there on BTC (lets round this to 8000 nodes)
- We assume as BTC is in fact slow it has a TPS of 1 to 7 max (lets round this to 10TPS for the sake of it)
- Each 8 nodes (hard coded in BTC) for a cluster and therefore we could say there are 1000 clusters and 8 nodes each, each of the cluster is also in sync
- That means that in a sense of backup (lets say like a raid) you have 8000 copies of the blockchain flying out there somewhere which needs to stay in sync. That is a major over head but also a nearly foolproof way of having copies as it is unlikely 8000 nodes are gone
Then we have the round times of 10 min ish ( its a little less in calculation but lets keep it simple) so we could say the latency is 10 minutes which is very bad. If lets say the network grows 3 times to what it is now the network load would be extreme and no improvement on speed , storage and so on.
With only 10 TPS (Transaction per second) it is very slow and in business terms not usable. The fact also that there are 8000 copies floating around is good in a perspective of backup but not the best way on security and efficiency.
In time as the usage grows on BTC the issue that clients need to hold bigger chain becomes unrealistic and it take days already to get in sync. Even now people working on it / talking how they could increase the storage/speed and so on.
If lets say a business (lets take a bank) they can not use it due the TPS limitation and that there are to many nodes floading around. If we lets say they have just 1000TPS (a slow day with them) and a peak of 5000TPS (also very low) then
a.) they will never get the throughput
b.) network may crash/overload
c.) the storage of clients will be full before they can say "bah". This means the end-user (like you) and you have a local BTC wallet will fill your 1TB HDD in no time. And here i am not talking in months , here we are talking in hrs/days.
d.) only a few in the end will be able to hold the amount of data in the chain if they get it in it
So WBB is moving the otherway but still keeping a decentralized part.
The latest test on the WBB V5 test coin we use and the new setup we are using we done the following.
- a small 3 server setup inclusive regulator, replicator
- automated doc insertions tests to it with a size of 900kb with no payload (config test and insertion)
- load balance automatically
On these test we already reached speeds of 800TPS stable and load was only 50%
Here is a graph from the tests
At this point test was running already stable for some time and 790000 doc inserted at a stable rate of 790 to 800 TPS
About 24 min later another 400000 doc been inserted and tps still steady and stable at 790 to 800TPS
Now this is still not fast enough and this weekend we 10 fold the setup and configure it to real time setup.
The we run a new benchmark and load tests on it
After this is done the V5 will start inserting to this test setup. But before we need to configure all correct and correct the code as needed. This part is time consuming but we get closer every day.
- Now once WBB is complete then the example with the business above could use this and has no issue on speed.
- Also there want be 8000 nodes floating around out there
- if a node fails others take automatically over
- clients don't need to use their private storage
- latency is in milli seconds not minutes
- much more but we leave this for later
edit: BTC as per this calculation would take 100 times longer so about 40hrs plus (compared to 24 min on WBB) if it can manage it and most of the normal nodes (clients ) probably have already a storage issue taking this small test we done.
Thanks
Peter
Poll
