Obyte: Totally new consensus algorithm + private untraceable payments

[bspus]

‘the graph is very complex now, which makes validation very slow, and it is still performed in sql. So large complex graph became possible after we allowed spending unconfirmed funds. Trying to do urgent performance improvements now’

Wasn't the scalability of DAG supposed to be much, much better than blockchain? I thought that was the selling point of Byteball and other cryptocurrencies based on DAG. But if validation becomes slower as the graph becomes more complex, then we really don't have a competitive advantage in using DAG,.

That’s a valid concern but please mind that we have mostly unoptimised code here. IMO the underlying SQL server is the bottleneck here, there’s no flaw in the DAG scalability. This was already discussed several times but the optimization of the database functions was postponed because other improvements seemed to be more urgent.

Since most people are encouraged to run the wallet in light mode anyway, would it make sense for the full nodes to use a full capability DBMS? Assuming the performance benefits would be that significant and thinking about long term future.

[1555939963]

1555939963

[1555939963]

1555939963

[1555939963]

1555939963

[1555939963]

1555939963

[1555939963]

1555939963

[CryptoRobert]

‘the graph is very complex now, which makes validation very slow, and it is still performed in sql. So large complex graph became possible after we allowed spending unconfirmed funds. Trying to do urgent performance improvements now’

Wasn't the scalability of DAG supposed to be much, much better than blockchain? I thought that was the selling point of Byteball and other cryptocurrencies based on DAG. But if validation becomes slower as the graph becomes more complex, then we really don't have a competitive advantage in using DAG,.

That’s a valid concern but please mind that we have mostly unoptimised code here. IMO the underlying SQL server is the bottleneck here, there’s no flaw in the DAG scalability. This was already discussed several times but the optimization of the database functions was postponed because other improvements seemed to be more urgent.

As long as it is a choice and not a flaw, I see no problem there. However, it would be nice if the wallet would have the capability to display a message of maintainence status.

[muleroaa]

‘the graph is very complex now, which makes validation very slow, and it is still performed in sql. So large complex graph became possible after we allowed spending unconfirmed funds. Trying to do urgent performance improvements now’

Wasn't the scalability of DAG supposed to be much, much better than blockchain? I thought that was the selling point of Byteball and other cryptocurrencies based on DAG. But if validation becomes slower as the graph becomes more complex, then we really don't have a competitive advantage in using DAG,.

That’s a valid concern but please mind that we have mostly unoptimised code here. IMO the underlying SQL server is the bottleneck here, there’s no flaw in the DAG scalability. This was already discussed several times but the optimization of the database functions was postponed because other improvements seemed to be more urgent.

What about now though, will more emphasis be placed towards optimizing database functions? It appears to have quite some impact.

[CryptKeeper]

Hi guys! Network is working fine for ya?

No, the Byteball network is in maintenance mode. The chief developer posted this on our Slack:

‘the graph is very complex now, which makes validation very slow, and it is still performed in sql. So large complex graph became possible after we allowed spending unconfirmed funds. Trying to do urgent performance improvements now’

The chief developer posted an update:

most of the network is back online, steem attestations will resume after 12pm CET, will prepare a new release for full wallets

[funcho]

trying to send a 1 byte payment to ZLJY3IYWL6BA6WSS5IZYTR3AUF37DE6N

in android
error message / syncing for 1minute then internal connection closed regardless of qr code or manual enter

windows wallet same / timeout

 

[alyssa85]

‘the graph is very complex now, which makes validation very slow, and it is still performed in sql. So large complex graph became possible after we allowed spending unconfirmed funds. Trying to do urgent performance improvements now’

Wasn't the scalability of DAG supposed to be much, much better than blockchain? I thought that was the selling point of Byteball and other cryptocurrencies based on DAG. But if validation becomes slower as the graph becomes more complex, then we really don't have a competitive advantage in using DAG,.

That’s a valid concern but please mind that we have mostly unoptimised code here. IMO the underlying SQL server is the bottleneck here, there’s no flaw in the DAG scalability. This was already discussed several times but the optimization of the database functions was postponed because other improvements seemed to be more urgent.

What about now though, will more emphasis be placed towards optimizing database functions? It appears to have quite some impact.

They'll have to - this latest episode has exposed that they can't handle large volumes of transactions yet.

[Random-String-Symphony]

‘the graph is very complex now, which makes validation very slow, and it is still performed in sql. So large complex graph became possible after we allowed spending unconfirmed funds. Trying to do urgent performance improvements now’

Wasn't the scalability of DAG supposed to be much, much better than blockchain? I thought that was the selling point of Byteball and other cryptocurrencies based on DAG. But if validation becomes slower as the graph becomes more complex, then we really don't have a competitive advantage in using DAG,.

That’s a valid concern but please mind that we have mostly unoptimised code here. IMO the underlying SQL server is the bottleneck here, there’s no flaw in the DAG scalability. This was already discussed several times but the optimization of the database functions was postponed because other improvements seemed to be more urgent.

What about now though, will more emphasis be placed towards optimizing database functions? It appears to have quite some impact.

They'll have to - this latest episode has exposed that they can't handle large volumes of transactions yet.

Byteball might not be able to handle large volumes of tx yet, but that's not what this latest episode was about. See this statement from Tony on Slack:

tonych [2:32 PM]what happened:
- on Friday (the 13th) 10 out of 12 witnesses crashed due to a bug. The 2 surviving were recently updated and didn't have the bug
- among the 2 surviving witnesses, was the steem attestation bot which continued to post transactions very fast, and since it didn't have to wait for confirmations, nothing could stop it and the unconfirmed tail of the DAG has grown very large
- the 10 witnesses updated and restarted but they started adding their units to the old part of the DAG they last witnessed, which caused massive rebuilds of the main chain each time a new unit was added.  This made validation of new units very slow.
- I had to urgently find and apply a few optimizations that matter only when the DAG takes such unusual form.  They made validation faster but still way slower than usual
- when the optimizations were ready, another issue popped up: calculation of stability point gave unexpected result.  I had to investigate the new issue, which took another day, and found a mistake in the algo. The fix breaks compatibility with the old (flawed) algo, and makes the update mandatory for all full nodes.

tonych [2:43 PM]
there were other performance improvements we've ben working on for the past several months, they affect a lot of code and any small mistake could cause a consensus split, and i didn't feel it is right to roll them out in such unprepared manner.

[slovakia]

any news about to resume the Byte distribution for WCG?

[Freefactomizer]

any news about to resume the Byte distribution for WCG?

It will happen very soon.

[Nippel66]

Joined Airdrop yesterday with my Steemit account. That was a good airdrop since i am over 60 in Rep

[weird123]

What is going on with cryptox.pl ? I know that admin is not anonymous person. What he say?

[Random-String-Symphony]

What is going on with cryptox.pl ? I know that admin is not anonymous person. What he say?

From Slack, yesterday evening:

grzem [10:38 PM]
Cryptox is down, problem is known, not conected to the Byteball. Probable up tomorrow at 10:00 CET. Too many registrations, just need to solve it with dev.

[CryptKeeper]

What is going on with cryptox.pl ? I know that admin is not anonymous person. What he say?

From Slack, yesterday evening:

grzem [10:38 PM]
Cryptox is down, problem is known, not conected to the Byteball. Probable up tomorrow at 10:00 CET. Too many registrations, just need to solve it with dev.

Update:

Cryptox suspended new registrations for about 1 week. Not in elegant way but - holiday.

cryptox service shouldn't interrupt.

[langnhangvl]

Hello Is there anyone encountered the same problem ? I downloaded Byteball wallet ages ago, and I deleted it and reinstall it lately, but it just keep syncing every single day

[CryptKeeper]

Hello Is there anyone encountered the same problem ? I downloaded Byteball wallet ages ago, and I deleted it and reinstall it lately, but it just keep syncing every single day

I guess you once had the full wallet installed, which needs a very long time to sync. If you have no coins in your wallet, you can do a fresh install of a 'light' wallet by deleting your Byteball folder in userdata:

Windows: %LOCALAPPDATA%\byteball
MacOS: ~/Library/Application Support/byteball
Linux: ~/.config/byteball

[CryptKeeper]

-blank-

[publiccoin57]

Chat is encrypted client side and shared with the peer through the hub. It can be decrypted only by the recipient so the hub merely relays the message which isn't stored on the DAG. Blackbytes works in pretty much the same way, only a hash of the transaction is posted to the DAG. As of version 2.3, a blackbytes transaction can be sent including the entire coin history in an encrypted file, too.

[elitecstrike]

Network issues over the weekend and questions about Steem attestations
https://medium.com/byteball/network-issues-over-the-weekend-and-questions-about-steem-attestations-99935d9a3efd

As you may know the Byteball network experienced issues July 13–15. Clearly the timing was not great given the surge in new users following the Steem release made on July 12.
The good news is these have been fixed. Technical details on what happened can be found towards the bottom of this article. But first, here are some resources for the many new users we have attracted from the Steem community.

[StandingTall]

Why are you all using medium.com instead of steemit.com for writing blog posts? It's high time to switch.

It's like appealing to Linux users and publicly demonstrating the use of Windows.

[jwinterm]

Why are you all using medium.com instead of steemit.com for writing blog posts? It's high time to switch.

It's like appealing to Linux users and publicly demonstrating the use of Windows.

Steem is hot garbage. Fuck that shitcoin/token/whatever.