Obyte: Totally new consensus algorithm + private untraceable payments

[Xeelee]

Are there any figures available what amount was distributed overall?

[1714300813]

1714300813

[1714300813]

1714300813

[1714300813]

1714300813

[piiper]

I have a BIG problem , v. 1.70 on win 10 x64 last update no have backup :

https://s15.postimg.org/av3uykcjv/Cattura.jpg

Any help ? .

I have the exact same problem. Didn't have a chance to backup since receiving the black bytes from round 4...

[D3m0nKinGx]

Are there any figures available what amount was distributed overall?

Total balance linked: 145164.13818055 BTC
Transition rate: 0.0625 gigabyte/BTC

For linked BTC:  9072 Gbytes were distributed

Not sure how many were distributed for the wallets that already have bytes in them which the calculation is 0.1 byte per 1 byte.

[innergy]

This doesn't answer my question about why I didn't receive any airdropped blackbytes.

You are supposed to receive blackbytes according to the bytes you receive depending on bitcoins on your linked BTC address and/or bytes on your linked Byteball address.

In that case I should have received blackbytes too.

Do you have the Transition bot as paired device in the chat?

[LoyceV]

This doesn't answer my question about why I didn't receive any airdropped blackbytes.

You are supposed to receive blackbytes according to the bytes you receive depending on bitcoins on your linked BTC address and/or bytes on your linked Byteball address.

In that case I should have received blackbytes too.

Do you have the Transition bot as paired device in the chat?

I have the Transition Bot in my chat, I'm not sure what "paired device" means exactly.

[Vita1ico]

I have a BIG problem , v. 1.70 on win 10 x64 last update no have backup :



Any help ? .

I have the exact same problem. Didn't have a chance to backup since receiving the black bytes from round 4...

Too such problem ..

[kola-schaar]

This doesn't answer my question about why I didn't receive any airdropped blackbytes.

You are supposed to receive blackbytes according to the bytes you receive depending on bitcoins on your linked BTC address and/or bytes on your linked Byteball address.

Did you have positive balances on your linked BTC address(es) and/or you Byteball linked address(es)?

On a side note, there has been cases where Tony had to re-send blackbytes to some addresses that didn't receive them during the distribution, before you contact him, let's make sure that everything was set up as it should have.

My view on the subject (@ kaicrypzen Is this view correct?)

The Bytes Balance  is “visible” for tony (address <-> Byte-Balance). It’s similar to the Bitcoin-network – low privacy and easy to trace.
Tony distribute (Byte to Byte ratio 1:0.1) “simple” to every Byte address with a balance in the BB-network.
So, you can buy bytes and get new bytes with each distribution round - without any further action.
It is not mandatory to have a linked pair (BB Address <-> BTC address) to receive Bytes.

Blackbytes are invisible for the BB-network (private currency).
See OP:.. Payments in private assets (like Blackbytes) are not published to the public database.  Instead, only the hash of the transaction is stored to the database, ..” … and with Tor they become untraceable. It is therefore not technically possible to distribute them like bytes.
To receive blackbytes, you must have at least one connected address pair  (BB address <-> BTC address). It does not matter if the BTC address has no balance.  

This address (BB address <-> BTC address) is your linked BB address (bot tells you), where you have to consolidate your bytes. You can link different BTC-addresses to different BB addresses:
Pair 1 (BB address 1 <-> BTC address 1) you will receive Blackbytes for the Balance at BB address 1
Pair 2 (BB address 2 <-> BTC address 2) you will receive Blackbytes for the Balance at BB address 2
Pair 3 (BB address 3 <-> BTC address 3) you will receive Blackbytes for the Balance at BB address 3
….

Or you can link different BTC-addresses to one BB addresse:
Pair 1  (BB address  0 <-> BTC address 1 ) you will receive Blackbytes for the Balance at BB address 0
Pair 2  (BB address  0 <-> BTC address 2 ) you will receive Blackbytes for the Balance at BB address 0
Pair 3  (BB address  0 <-> BTC address 3 ) you will receive Blackbytes for the Balance at BB address 0
…
BB address XXXX (no linked BTC address) you will receive Byte but no Blackbytes

Note: If you consolidate your bytes to a linked BB-address, make sure you are not running any transactions after that.
In this case the Bytes will jump to another (maybe) not linked address...( similar  BTC-wallet see: https://en.bitcoin.it/wiki/Change ).

[kaicrypzen]

My view on the subject (@ kaicrypzen Is this view correct?)

The Bytes Balance  is “visible” for tony (address <-> Byte-Balance). It’s similar to the Bitcoin-network – low privacy and easy to trace.
Tony distribute (Byte to Byte ratio 1:0.1) “simple” to every Byte address with a balance in the BB-network.
So, you can buy bytes and get new bytes with each distribution round - without any further action.
It is not mandatory to have a linked pair (BB Address <-> BTC address) to receive Bytes.

Yes.

Blackbytes are invisible for the BB-network (private currency).
See OP:.. Payments in private assets (like Blackbytes) are not published to the public database.  Instead, only the hash of the transaction is stored to the database, ..” … and with Tor they become untraceable. It is therefore not technically possible to distribute them like bytes.
To receive blackbytes, you must have at least one connected address pair  (BB address <-> BTC address). It does not matter if the BTC address has no balance.

Yes. By linking a Byteball address, one exposes their device address which is needed to send the blackbytes.  

This address (BB address <-> BTC address) is your linked BB address (bot tells you), where you have to consolidate your bytes. You can link different BTC-addresses to different BB addresses:
Pair 1 (BB address 1 <-> BTC address 1) you will receive Blackbytes for the Balance at BB address 1
Pair 2 (BB address 2 <-> BTC address 2) you will receive Blackbytes for the Balance at BB address 2
Pair 3 (BB address 3 <-> BTC address 3) you will receive Blackbytes for the Balance at BB address 3
….

Yes.

Or you can link different BTC-addresses to one BB addresse:
Pair 1  (BB address  0 <-> BTC address 1 ) you will receive Blackbytes for the Balance at BB address 0
Pair 2  (BB address  0 <-> BTC address 2 ) you will receive Blackbytes for the Balance at BB address 0
Pair 3  (BB address  0 <-> BTC address 3 ) you will receive Blackbytes for the Balance at BB address 0
…
BB address XXXX (no linked BTC address) you will receive Byte but no Blackbytes

Yes.

Note: If you consolidate your bytes to a linked BB-address, make sure you are not running any transactions after that.
In this case the Bytes will jump to another (maybe) not linked address...( similar  BTC-wallet see: https://en.bitcoin.it/wiki/Change ).

And yes .

[kaicrypzen]

You are supposed to receive blackbytes according to the bytes you receive depending on bitcoins on your linked BTC address and/or bytes on your linked Byteball address.

In that case I should have received blackbytes too.

Did you have positive balances on your linked BTC address(es) and/or you Byteball linked address(es)?

Yes. That's why I did receive Bytes, but no Blackbytes.

On a side note, there has been cases where Tony had to re-send blackbytes to some addresses that didn't receive them during the distribution, before you contact him, let's make sure that everything was set up as it should have.

In this case, I think something went wrong.

Okay, so if I understand correctly the bytes you got are according to BTC and/or bytes you have on linked addresses (you should normally find them here http://transition.byteball.org by the way). In that case, you should send a private message to Tony, explaining the situation, and he will re-send the blackbytes to you.

[LoyceV]

You are supposed to receive blackbytes according to the bytes you receive depending on bitcoins on your linked BTC address and/or bytes on your linked Byteball address.

In that case I should have received blackbytes too.

Did you have positive balances on your linked BTC address(es) and/or you Byteball linked address(es)?

Yes. That's why I did receive Bytes, but no Blackbytes.

On a side note, there has been cases where Tony had to re-send blackbytes to some addresses that didn't receive them during the distribution, before you contact him, let's make sure that everything was set up as it should have.

In this case, I think something went wrong.

Okay, so if I understand correctly the bytes you got are according to BTC and/or bytes you have on linked addresses (you should normally find them here http://transition.byteball.org by the way). In that case, you should send a private message to Tony, explaining the situation, and he will re-send the blackbytes to you.

I never had "bytes" before, so it came from my Bitcoin connection. I'll send Tony a message to continue my ride in altcoins
Thanks!

[bitcoinerik]

Hello!
I would like to buy some byteball coins. Is it possible to cold storage them? Like a paper wallet, only containing the private key?

[Lercker]

I have a BIG problem , v. 1.70 on win 10 x64 last update no have backup :



Any help ? .

I have the exact same problem. Didn't have a chance to backup since receiving the black bytes from round 4...

Too such problem ..

I have the same problem too...

[Odrak]

Hello!
I would like to buy some byteball coins. Is it possible to cold storage them? Like a paper wallet, only containing the private key?

You could store them in a wallet, write down the seed and then never look at it again until you need it. However, in order to preserve Blacbytes you need to save a Full Backup, and put that on a USB or something similar.

[bitcoinerik]

Hello!
I would like to buy some byteball coins. Is it possible to cold storage them? Like a paper wallet, only containing the private key?

You could store them in a wallet, write down the seed and then never look at it again until you need it. However, in order to preserve Blacbytes you need to save a Full Backup, and put that on a USB or something similar.

Thanx!

[Xmr fan]

I have a BIG problem , v. 1.70 on win 10 x64 last update no have backup :

https://s15.postimg.org/av3uykcjv/Cattura.jpg

Any help ? .

I have the exact same problem. Didn't have a chance to backup since receiving the black bytes from round 4...

Too such problem ..

I have the same problem too...

I have the exact same problem with 16.04 Ubuntu 64bit. The wallet was stuck at 60% syncing this morning, so I rebooted ky PC and that message came up. Wat gives?

[bcmine]

I have a BIG problem , v. 1.70 on win 10 x64 last update no have backup :



Any help ? .

I have the exact same problem. Didn't have a chance to backup since receiving the black bytes from round 4...

Too such problem ..

I have the same problem too...

I have the exact same problem with 16.04 Ubuntu 64bit. The wallet was stuck at 60% syncing this morning, so I rebooted ky PC and that message came up. Wat gives?

we seem all to have the same problem. when can we expect a fix release?

[giagge]

I have a BIG problem , v. 1.70 on win 10 x64 last update no have backup :



Any help ? .

I have the exact same problem. Didn't have a chance to backup since receiving the black bytes from round 4...

Too such problem ..

I have the same problem too...

This wallet is really crap , i try to new full wallet , and stuck a 99% sync after 5 hours , WTF , fix this shit .

[hannusolo]

I have a BIG problem , v. 1.70 on win 10 x64 last update no have backup :



Any help ? .

You still can back up your wallet. Just disconnect the internet before opening it, and than you can use it offline to back it up.

[zanzibar]

I keep getting errors when trying to reinstall, malware detected, will wait for new release.

[kola-schaar]

...
I have the Transition Bot in my chat, I'm not sure what "paired device" means exactly.

May be also interesting for other people:

see white paper page 1:
..Users can also issue assets whose transfers are not published to
the database, and therefore not visible to third parties. Instead, the information about the
transfer is exchanged privately between users (…. and their paired devices), and only a hash of the transaction and a spend proof (to prevent double-spends) are published to the database…

To use any privacy feature in Byteball (i.e. the chat function or blackbyte transfer / blackbyte trading), you have to pair the involved devices.

You need also to pair your own devices if you like to build a multisig / multidevice wallet.
Such a wallet (i.e. 2 of 3) is in Byteball very easy to build.
And it’s very recommended to do this in relation of security / backup and redundancy.

•   Paired Devices -> Add new Device
•   Use QR Code and Cam or send pairing Code by mail
•   Make the devices known to each other (pairing):

Invite Device 1 -> Accept Device 2
Invite Device 1 -> Accept Device 3
Invite Device 2 -> Accept Device 1
Invite Device 2 -> Accept Device 3
Invite Device 3 -> Accept Device 1
Invite Device 3 -> Accept Device 2

Test: Chat between the devices (both directions) -> O.K.

•   use new wallet -> Multidevice wallet -> total number of co-signers: 3
•   Required number of signatures: 2
•   select your paired devices 1-3 as co-signers

Done - 10 minutes and  very secure in any case..