Quote from: Fallenkeith75 on Today at 01:40:48 AM

Quote from: tarmo888 on September 10, 2020, 12:46:41 PM

Quote from: Artifex on September 10, 2020, 12:06:25 PM

just remembering the predecessor of Obyte, namely Byteball, you can see that the latter had serious problems with bandwidth in the working network. I wonder how the situation is at the moment with Obyte. Therefore, I am interested in this question

Obyte is Byteball, it was just a rebranded, rest of the project is same, just improved a lot since mainnet launch (works now even on IoT devices).
It didn't have and still doesn't have problems with bandwidth, it hardly ever reached even 1% of bandwidth that it could actually do.

The difference between then and now is that now Obyte has Autonomous Agents and thanks to that can do Payment Channels, which decreases the need to have small payments on mainnet even more and it even makes these streaming payments almost free (only paying fees for opening/closing the channel).
https://github.com/byteball/aa-channels-lib

Not sure where do you get this bandwidth problem, do you mean the stress test that spammed mainnet in 2018 with hundreds of transactions that all got confirmed at once or you mean the incorrectly done DAGbench test with IOTA and Nano that couldn't even get 1TPS out of Obyte because they were using light obyte.js library for web?

Aha, so that's what happened to Byteball. Byteball / Obyte is a pretty old and good project. I hope the developers keep on working on the project into the future.

https://medium.com/obyte/byteball-rebrand-the-next-step-to-real-world-adoption-6a0a924390de