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.

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:

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


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?

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.


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

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.


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.



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

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.

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 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.

Yes, the right tab, thanks.

This error message gives the clue that your witness list might be too old:

catchup request got error response: your witness list might be too much off, too few witness authored units

Please click the burger menu > Settings > Witnesses and enable auto-update of the witness list from the hub.

It displays the dollar amounts, so apparently it is connected to the hub. Could you press Ctrl+i and look for errors in the console log? Copy the last few lines here if you can't see any clues.

You don't need to sync anything. If you are going to restore from backup, select "light" when starting the wallet for the first time, then immediately proceed to restoring.

See my previous messages, I told you the (approximate) location of the data folder a couple of times before.

Windows stores programs and their data in separate locations.

No, I mean just removing the data folder. You don't need to uninstall or do anything with the program folder.



Of course, the wallet will become what the backup was. The previous wallet is fully overwritten and it doesn't matter whether it was full or light.

As I said above, remove the data folder.

As I said before:

No, I see no point in such options for Obyte wallet.

I'm not aware of any detailed comparison. The technologies are different. Regarding use options, perhaps the main difference is that Blackbytes can be sent as textcoins, without any trace on the ledger at all, like cash. Blackbyte textcoins are sent as files over any digital medium (such as email, whatsapp, etc), see details here https://blog.obyte.org/private-textcoins-6a2288d80757.


This article answers the question https://blog.obyte.org/byteball-rebrand-the-next-step-to-real-world-adoption-6a0a924390de

This is your program folder. It's small, you don't need to bother about moving it to another partition.


The data folder.
However, I'm not sure what would be your next step after re-syncing. If you restore from backup, all data will be overwritten.

Are you sure AppData\Local\Programs\obyte is the data folder?
It might be the program folder. Please check its contents.

The data folder name should be like AppData\Roaming\obyte (not sure, writing from memory, I don't have an easily accessible Windows machine now).

Obviously, you need to copy the entire data folder to its new location before creating a symink to it.

Copying would be easier if on the same OS, otherwise backup/restore.

On Linux, I use symlinks in such cases. As far as I know, Windows has symlinks too, you can try to symlink the data folder to a location in another partition.