After introducing Sabu protocol as a solution for Bitcoin scaling (
https://raymo-49157.medium.com/time-to-boost-bitcoin-circulation-million-transactions-per-second-and-privacy-1eef8568d180), I shared this idea with Bitcoin developers through the bitcoin-dev mailing list.
I got some constructive feedbacks and critiques leading me to add this part to the proposal which I was skipped due to brevity of proposal introduction.
Here I will investigate on more real live scenarios, general usages and corner cases, and the consequences of some attacks or buggy implementation of protocol, as well as different actors (malicious, irrational, profit seeker, griefer, stupid, reckless, incompetent, etc.) activity effects.
In proposal introduction (previous post), I did not talk about Lightning deliberately, although it seems that this solution is an alternative to Lightning.
Most of readers misunderstood Sabu and asking what differs it from Lightning?
Indeed, Sabu has nothing with Lightning. It has totally different design, network architecture, security model and implementation. The only thing in common with Lightning is both are intended to cover micro payments.
The good thing about Bitcoin is that it does not require any kind of permission. Consequently, related products do not need to ask permission too. We are in a permission-less free market. I think Sabu will work perfectly and if a group of users think like me, we are done. Sabu will work parallel the other scaling solutions without need to drive them out.
However, I have made a comparison between Sabu, on-chain and Lightning transactions to get a clearer understanding of the advantages and disadvantages of Sabu and answer to “why we should implement and use Sabu in our day-to-day deals”.
Most probably this paper is not comprehensive document, therefore this article will be updated.
read here for complete post:
https://raymo-49157.medium.com/scaling-bitcoin-by-sabu-protocol-risks-and-benefits-62157f8a664e