Obyte: Totally new consensus algorithm + private untraceable payments

[tonych]

Thank you. Syncing is starting. I hope all my data is on the old backup from 2017. My newer full backup from 2020 always had a syntax error (I have more backups with this error). If I have a problem with the old backup, is it possible to restore or repack one of the full backups with a syntax error?

No idea where the syntax error comes from, maybe the backup is corrupt. You can install an older version of the wallet from https://github.com/byteball/obyte-gui-wallet/releases released at about the same time when the backup was made, and try to restore into that version. Before installing an old version, make sure you uninstall the current one and rename the data folder to get it out of the way.

[tonych]

Obyte’s community is currently at its weakest point in 8 years. Our social channels often go quiet for days and almost nobody seems to be interested — all that despite strong underlying technology.

We must fix that and build a community Obyte deserves.

Meet Obyte City, a community engagement space for Obyte. It is designed to strengthen our community by encouraging closer connections, and more connections between community members. We believe that such horizontal ties, and a dense network of them, will make our community stronger, more cooperative, more capable of effective collective action, more resilient, and more independent of the team — who, otherwise, would be a central point of failure and has already demonstrated its poor performance in community building.

Read the intro blog: https://blog.obyte.org/introducing-obyte-city-a-community-engagement-space-for-obyte-8401470d790d

Try it out: https://city.obyte.org

CITY presale runs until June 30.

[Buchi-88]

I see why the new witness list is not saved, it'll be fixed in the next version.

In the meantime, I updated the main hub to enable catchup with old witness lists. Your wallet should start syncing if you open it again.

No new version of the wallet available yet? The wallet is being updated and I can already see some Obytes in the wallet, as well as other tokens such as Silentnotary and Titan Coin, but unfortunately I don't see any Blackbytes yet.

However, the wallet synchronises very slowly despite a fast fibre optic connection and when the CPU is not under load, could it be that I am not connected to all witnesses?

No idea where the syntax error comes from, maybe the backup is corrupt. You can install an older version of the wallet from https://github.com/byteball/obyte-gui-wallet/releases released at about the same time when the backup was made, and try to restore into that version. Before installing an old version, make sure you uninstall the current one and rename the data folder to get it out of the way.

I will only try if I have no more Blackbytes, but after successful synchronisation I will immediately create a full backup again.

[tonych]

I see why the new witness list is not saved, it'll be fixed in the next version.

In the meantime, I updated the main hub to enable catchup with old witness lists. Your wallet should start syncing if you open it again.

No new version of the wallet available yet? The wallet is being updated and I can already see some Obytes in the wallet, as well as other tokens such as Silentnotary and Titan Coin, but unfortunately I don't see any Blackbytes yet.

No new version, but your sync issue appears to be already resolved.
You won't see Blackbytes by continuing the sync. By their nature, they are a private asset and are stored only in your backup.

However, the wallet synchronises very slowly despite a fast fibre optic connection and when the CPU is not under load, could it be that I am not connected to all witnesses?

The bottleneck is usually in CPU or disk speed, not in network connection.
You don't need to be connected to witnesses. In fact none of the witnesses accepts connections.

No idea where the syntax error comes from, maybe the backup is corrupt. You can install an older version of the wallet from https://github.com/byteball/obyte-gui-wallet/releases released at about the same time when the backup was made, and try to restore into that version. Before installing an old version, make sure you uninstall the current one and rename the data folder to get it out of the way.

I will only try if I have no more Blackbytes, but after successful synchronisation I will immediately create a full backup again.

As I said, sync won't recover them. They are only in your backups.

[Buchi-88]

No new version, but your sync issue appears to be already resolved.
You won't see Blackbytes by continuing the sync. By their nature, they are a private asset and are stored only in your backup.

I have a full backup from 2017, when was the first time the black bytes were created/distributed? The synch is still hanging in 2018... the other assets have also only come with time...

The bottleneck is usually in CPU or disk speed, not in network connection.
You don't need to be connected to witnesses. In fact none of the witnesses accepts connections.

The sync takes about one day per day, Obyte runs on an i7 of the 7th generation with a CPU utilisation of about 10%.

As I said, sync won't recover them. They are only in your backups.

Currently the Blackbytes balance is still at zero in 2018, and it's a Full Backup from 2017.

[tonych]

I have a full backup from 2017, when was the first time the black bytes were created/distributed?

On 25 December 2016.
However I don't know when you started participating in distributions.
If you created the backup later than you first received blackbytes, they should be there.

The bottleneck is usually in CPU or disk speed, not in network connection.
You don't need to be connected to witnesses. In fact none of the witnesses accepts connections.

The sync takes about one day per day, Obyte runs on an i7 of the 7th generation with a CPU utilisation of about 10%.

That's terribly slow. Do you have a SSD or a magnetic HDD on this computer?

[Buchi-88]

On 25 December 2016.
However I don't know when you started participating in distributions.
If you created the backup later than you first received blackbytes, they should be there.

My three backups from this date:

- Byteball-Full-18032017
- ByteballBackup-2017-12-17-10-02-58
- ObyteBackup-2020-07-25-16-28-58

However, there is always an error with the two newer backups, as explained above.

That's terribly slow. Do you have a SSD or a magnetic HDD on this computer?

The synch files are on a SSHD Seagate FireCuda ST2000LX001, and i benchmark the SSHD with AS SSD Benchmark, and all OK. 

[tonych]

On 25 December 2016.
However I don't know when you started participating in distributions.
If you created the backup later than you first received blackbytes, they should be there.

My three backups from this date:

- Byteball-Full-18032017
- ByteballBackup-2017-12-17-10-02-58
- ObyteBackup-2020-07-25-16-28-58

However, there is always an error with the two newer backups, as explained above.

When was your first airdrop? Check the date of the first transaction in Bytes if you don't remember.

That's terribly slow. Do you have a SSD or a magnetic HDD on this computer?

The synch files are on a SSHD Seagate FireCuda ST2000LX001, and i benchmark the SSHD with AS SSD Benchmark, and all OK. 

I googled this name and looks like it is a hybrid HDD+SSD drive from 2016... I don't expect high performance from it for the type of work a syncing node does. Do you have anything else?

[Buchi-88]

When was your first airdrop? Check the date of the first transaction in Bytes if you don't remember.

Ok, I'll see when I had the first transaction from Obytes.

I googled this name and looks like it is a hybrid HDD+SSD drive from 2016... I don't expect high performance from it for the type of work a syncing node does. Do you have anything else?

I have also tested it with an Intel NVMe, and the synchronisation was not faster there either, the wallet always wants to update Witnesses addresses, but unfortunately the wallet does not save the addresses... Could this be the problem?

[tonych]

the wallet always wants to update Witnesses addresses, but unfortunately the wallet does not save the addresses... Could this be the problem?

No, this can't affect the speed.

One way to accelerate sync is to enable the bFaster option in your conf.json.  This file either already exists or needs to be created in your data folder (the same folder that contains byteball.sqlite).  The file should look like:

Code:

{
	"bFaster": true
}

[Eddyc]

Article 1



https://www.publish0x.com/crypto-bits/obyte-city-a-space-for-community-connection-and-going-beyond-xnjevdn

A space for community connection and going beyond engagement

[Eddyc]

Article 2



https://www.publish0x.com/crypto-bits/obyte-city-buying-a-plot-in-a-simple-and-formidable-way-xzrylep

Buying a Plot in a Simple and Formidable Way

Note* This article is a tutorial

[tonych]

We are excited to announce a collaboration between Obyte and 3DPass around the upcoming deployment of the Counterstake Bridge on 3DPass. They forked it and made a few modifications to accommodate the EVM compatibility layer of their Substrate-based system. It's open-source and decentralized like the original bridge.

To mark this milestone, 3DPass will host an AMA session on X with:
Tony, the founder of Obyte and Inventor of the Counterstake Bridge.

Date & Time: Monday, September 1, 2025 at 18:00 CEST
Location: X page of @3dpass_genesis

During this AMA, we'll discuss:
- The Counterstake Bridge technology and its upcoming integration with 3DPass
- How this technology has been used so far
- Cross-chain functionality and real use cases
- What this means for the 3DPass and Obyte

This is a great opportunity to ask questions directly and learn more about how 3DPass and Obyte are working together to expand cross-chain possibilities for RWA assets.