Obyte: Totally new consensus algorithm + private untraceable payments

[altcoinnxt]

Now,is it must update to the latest version?
i open the wallet,it also minde me and i select later,then got error

[ByteFan]

Now,is it must update to the latest version?
i open the wallet,it also minde me and i select later,then got error

latest wallet is mandatory 1.7.1

[ParmaBTC]

Now,is it must update to the latest version?
i open the wallet,it also minde me and i select later,then got error

latest wallet is mandatory 1.7.1

YES it is mandatory for full old version wallet, instead if you have lightwallet you can wait next release

[kaene]

Can anybody help me pls?  

First everything worked well, but the syncing needed 15+ hours so meanwhile i tried to install a second time to start the lightwallet. After that, suddenly nothing worked anymore. I tried to install and uninstall several times, but suddenly i always get this error after a few seconds:

Uncaught exception: Error: known bad
...... (many letters and numbers)
authentifier verification failed

I use:
macOS Sierra 10.12.4

Thanks!

Schnidl

Try pointing your wallet to byteball.fr/bb (in wallet settings/hub)

is that better than default hub?

It is an alternative hub (peered to default). The error means your default hub is down or too busy.

I'm having the same error (using 1.7.1), even after I changed the hub, any idea?

[ByteFan]

Can anybody help me pls?  

First everything worked well, but the syncing needed 15+ hours so meanwhile i tried to install a second time to start the lightwallet. After that, suddenly nothing worked anymore. I tried to install and uninstall several times, but suddenly i always get this error after a few seconds:

Uncaught exception: Error: known bad
...... (many letters and numbers)
authentifier verification failed

I use:
macOS Sierra 10.12.4

Thanks!

Schnidl

Try pointing your wallet to byteball.fr/bb (in wallet settings/hub)

is that better than default hub?

It is an alternative hub (peered to default). The error means your default hub is down or too busy.

I'm having the same error (using 1.7.1), even after I changed the hub, any idea?

Sorry no. You may contact @tonych on slack to report the problem.

[schnidl]

Thanks for reply, will try this

[schnidl]

Can anybody help me pls?  

First everything worked well, but the syncing needed 15+ hours so meanwhile i tried to install a second time to start the lightwallet. After that, suddenly nothing worked anymore. I tried to install and uninstall several times, but suddenly i always get this error after a few seconds:

Uncaught exception: Error: known bad
...... (many letters and numbers)
authentifier verification failed

I use:
macOS Sierra 10.12.4

Thanks!

Schnidl

Try pointing your wallet to byteball.fr/bb (in wallet settings/hub)

is that better than default hub?

It is an alternative hub (peered to default). The error means your default hub is down or too busy.

I'm having the same error (using 1.7.1), even after I changed the hub, any idea?

Sorry no. You may contact @tonych on slack to report the problem.

Doesnt work for me too. Error comes before i'm able to change the hub and closes the programm automatically

[garthkiser]

I'm migrating from Windows 10 to Ubuntu 16.04. My Byteball data files from Windows won't work with Byteball on Ubuntu. I can import my seed on Ubuntu to access my Bytes, but without importing the data file I cannot access my BlackBytes.

[tonych]

Hello
I have this message when i try to send blackbytes through chat to another wallet:

"Impossible to send payment
conflicting spend proof in inner unit"

Even with version 1.7, the problem still exist.

Thank you if you have somme help!
I will reward the first who will help me to solve this issue with 24 GBB (~ $100).

The error means you were trying to double-spend.
This might happen if you are running the same wallet (same seed) on more than one device.

Here it is: I have made a copy of the wallet on another device and deleted this wallet everywhere else.
But I still get the same message.

Thank you

If you deleted the clones _after_ this error, it shouldn't help.  You can spend blackbytes only from the device that was most recent to send a blackbytes transaction.

[tonych]

Can anybody help me pls?  

First everything worked well, but the syncing needed 15+ hours so meanwhile i tried to install a second time to start the lightwallet. After that, suddenly nothing worked anymore. I tried to install and uninstall several times, but suddenly i always get this error after a few seconds:

Uncaught exception: Error: known bad
...... (many letters and numbers)
authentifier verification failed

I use:
macOS Sierra 10.12.4

Thanks!

Schnidl

Try pointing your wallet to byteball.fr/bb (in wallet settings/hub)

is that better than default hub?

It is an alternative hub (peered to default). The error means your default hub is down or too busy.

I'm having the same error (using 1.7.1), even after I changed the hub, any idea?

1.8.0 is coming soon, it'll fix the issue.

[schnidl]

perfect! 

[ttookk]

I'm migrating from Windows 10 to Ubuntu 16.04. My Byteball data files from Windows won't work with Byteball on Ubuntu. I can import my seed on Ubuntu to access my Bytes, but without importing the data file I cannot access my BlackBytes.

The stupid dirty-hack solution would be to send them from one device to another. If it's the same computer you're using, maybe use some old smartphone or whatever as a relay?

I'm pretty sure, there is a better way, though, so use this only if you are in a hurry

[hannusolo]

Can anybody help me pls?  

First everything worked well, but the syncing needed 15+ hours so meanwhile i tried to install a second time to start the lightwallet. After that, suddenly nothing worked anymore. I tried to install and uninstall several times, but suddenly i always get this error after a few seconds:

Uncaught exception: Error: known bad
...... (many letters and numbers)
authentifier verification failed

I use:
macOS Sierra 10.12.4

Thanks!

Schnidl

Try pointing your wallet to byteball.fr/bb (in wallet settings/hub)

is that better than default hub?

It is an alternative hub (peered to default). The error means your default hub is down or too busy.

I'm having the same error (using 1.7.1), even after I changed the hub, any idea?

1.8.0 is coming soon, it'll fix the issue.

Thank god, this error gave me headaches! How ssoon can we expect it?

[synthgauge]

I'm migrating from Windows 10 to Ubuntu 16.04. My Byteball data files from Windows won't work with Byteball on Ubuntu. I can import my seed on Ubuntu to access my Bytes, but without importing the data file I cannot access my BlackBytes.

The stupid dirty-hack solution would be to send them from one device to another. If it's the same computer you're using, maybe use some old smartphone or whatever as a relay?

I'm pretty sure, there is a better way, though, so use this only if you are in a hurry

It's not a dirty hack solution it's what I would do the first when migrating to another OS. Go to ur ubuntu wallet, generate an address, write it on ur forehead, go to ur windows wallet and send coins to that address. Use mirror to read the address from ur forehead. Why on earth would u choose ubuntu? Unity and ubuntu do suck ass. Havent ever in my life seen an OS uglier than fucking ubuntu.

[tonych]

Version 1.8.0 released https://github.com/byteball/byteball/releases

In this release:

1. Option to save chat history. It is done in the most privacy-centric way: chat history is saved only if both parties agree, and the setting can be changed in the middle of the conversation.  If at least one of the parties doesn't want the history to be saved, it is discarded when the app is closed (of course it can still be saved manually by copying and pasting).


2. Push notifications for chats / received payments on Android.  What's important, even alternative hubs can send push notifications, which makes us even better decentralized than Signal.  Alternative hub operators, please follow instructions at https://github.com/byteball/byteball-hub#push-notifications-for-android to enable push for your clients.



3. Ability to remove chat correspondents unless they are part of a multisig address or smart contract (thanks @vakar!)

4. Improved French and Portuguese translations

5. Fixed a validation bug that caused crashes while syncing for many users.

Because of the above bugfix, upgrade is mandatory for all full clients.

I am happy to say that 2 of 5 above items were contributed by community members.

[D3m0nKinGx]

New version working great !  Don't forget to do your backups !

[ruptan]

When will be blackbytes be lusted in the exchange?

[altcoinrich]

Byteball will be huge because this technology is the newest one without blockchain, a big boom of innovation. Yeah, moon time.

[D3m0nKinGx]

Byteball will be huge because this technology is the newest one without blockchain, a big boom of innovation. Yeah, moon time.

And without the problems Bitcoin is having

[ByteFan]

Version 1.8.0 released https://github.com/byteball/byteball/releases

https://byteball.fr hub has been updated to support 1.8.0 (including new Android push notification service).

To get the feature point your wallet to our hub. Go in your wallet settings → hub and set byteball.fr/bb as your default hub.