Obyte: Totally new consensus algorithm + private untraceable payments

[110110101]

.....

Follow the project's twitter https://twitter.com/ByteballOrg.

Started following, looks like a neat concept!

[1714114743]

1714114743

[1714114743]

1714114743

[1714114743]

1714114743

[Jerry S]

interesting, will follow this

[tonych]

any wallet for win 32 dev?
I have already download but win 64.
its not compatibel for 32bits.  

Try this: https://byteball.org/downloads/Byteball-test-win32.exe.
This 32bit version works on my win64, you will be the first to try it in win32.

Has this been proven to work?
Tried installing it and seem not. It prompts for awhile then just disappears after. If anyone experienced such do let us know how it works.

Do you say the _installer_ fails?  Please PM me with as many details as possible.

[traumschiff]

Following the project, seems very interesting and congrats Tonych for choosing a non ICO distribution method. This will probably be well greeted within the crypto community when going live.

[doktor1897]

follow already and want to join byteball bounty

[tamara163]

I got 62000 bytes.what's next?what's the point of testnet?

[CryptKeeper]

I got 62000 bytes.what's next?what's the point of testnet?

You can send some Bytes to me: MBACPRCMAYRWFVHZQHZZYQRN3XEUECVR
and if you post your address I'll send you some back! 

[penniless1]

What I've found so far with the windows binary is that the installer appears to work, but launching the wallet fails after that. Going to try the following:
1. backup my C:\Users\...\AppData\Local\byteball-test
2. Delete the folder above
3. Reinstall using the binary
4. Attempt to reload my wallet from the backup.

[cryptonikus]

This project looks good, kind of fresh air.

[str4wm4n]

Then the number of bytes and blackbytes you receive on the launch date will be proportional to the BTC amount on your linked address in a specific bitcoin block (e.g. in block 437000 which is expected late October - early November)

It'll probably be a good time to short alts as well depending on how much hype this project gets

[btcmerich]

sorry can some one explain.this sounds great but if transactions are not stored on blockchain , does that mean both sender and reciever need to be online at the same time???

[xtester]

A good idea if you want to maximize distribution would be to not only extend the period, but find a way to make linking accounts available as soon as possible. This way, people don't have to wait another 1 - 2 months until they can link their accounts and potentially forget or miss byteball.

We'll enter the linking phase long before the launch date.
Even before that, I plan to test flight the distribution on the Bitcoin testnet (i.e. Bitcoin testnet to Byteball testnet).

Thanks for the info. I still wonder what effect this kind of distribution model will have on the price. Indeed, it could well be that, counter-intuitively, one will observe precisely the opposite effect one would expect, thanks to the low perceived risk - possibly high reward option offered, which distorts the natural order of things. Though I suspect that, depending on a few variables, over the longer term market forces could offset this kind of distortion.

[golfhuso]

.....

Follow the project's twitter https://twitter.com/ByteballOrg.

Started following, looks like a neat concept!

Followed and keep watch.

[tonych]

sorry can some one explain.this sounds great but if transactions are not stored on blockchain , does that mean both sender and reciever need to be online at the same time???

They don't need that.  Private information is delivered through a hub, which stores it while the recipient is offline (similar to email).  The information is end-to-end encrypted, so even the hub can't see it.

[davide72]

sorry can some one explain.this sounds great but if transactions are not stored on blockchain , does that mean both sender and reciever need to be online at the same time???

They don't need that.  Private information is delivered through a hub, which stores it while the recipient is offline (similar to email).  The information is end-to-end encrypted, so even the hub can't see it.

very good for the privacy!

[wahyu5]

What I've found so far with the windows binary is that the installer appears to work, but launching the wallet fails after that. Going to try the following:
1. backup my C:\Users\...\AppData\Local\byteball-test
2. Delete the folder above
3. Reinstall using the binary
4. Attempt to reload my wallet from the backup.

And how step to backup via android device?

[kaicrypzen]

Having both options adds complexity on both technical and usability sides:
1.  More code that needs to be written, debugged, and tested.  Despite all the testing, more code is always more complexity and greater probability of errors, including security errors.  Complexity is the enemy of security.
2.  More options for users means more options for attackers too.  This needs to be analyzed, and with growing complexity the chances of missing something increase.
3.  Longer instructions for users.  They are scared off by the abundance of text or unfamiliar words, like "signing a message".
4.  Users have to evaluate both options and make their choices.  Choice is difficult when the difference between the choices is not immediately clear.

All this is fine as long as there is a real tangible benefit in adding more options that overweights the negatives.  In this particular case, there isn't.

Thx for clarifying these points. Points 3 and 4 are okay but as I said earlier they do not apply to all users, I think we won't reach an agreement on that and that's okay .

What I find negative about this, is the lack of options ... (I want to send a signed message to claim, I can't. I want to see the transaction id and/or fees before sending, I can't. I don't want to use Google Play , I can't).

Looks like you want more control than an average user (well, as I perceive an average user).  That's OK, there is no one size that fits all.  I envisage that we'll have multiple wallets in Byteball ecosystem that fit different preferences, like we already have in Bitcoin.

Nice to hear that , I can accommodate with the current wallet though .

You can send some Bytes to me: MBACPRCMAYRWFVHZQHZZYQRN3XEUECVR
and if you post your address I'll send you some back!  

Here you go, just sent you 100 000 bytes.

- My DEVICE ADDRESS is 0CGP3QJM2ZUGYO6TYLG4KAGYWNWW6BLDV.
- The address that displays when I click on INSERT MY ADDRESS (it changes every time) in the chat window with Testnet Faucet is KRMI2HTBIML3CB3KEG3LB4QP75QQHDQ5.

If you are interested in pairing devices, here is my pairing code:

Code:

AmOIR5s+WxMyYUhUbEUwvr4lSP68ftSd9My8vJ1Esz2/@byteball.org/bb#gnSZxT7d0S2R

I actually tried pairing two of my devices by adding the pairing code from one to the other but this doesn't seem to be enough (I chatted from one device to another but never received messages), maybe I need to perform the operation on both devices? or maybe both must be online?

Some observations:
- 0 is considered as a valid amount, I mean when I type 0, Not valid does not appear (whereas it appears for -1 for instance), however 0 does not trigger the SEND button (which is normal), so maybe 0 should be considered not valid.
- When writing a very long number the digits overlap on bytes.
- I tried sending very large numbers and it resulted in sending 1 or 2 bytes.
- Why is it compulsory to backup the wallet keys before receiving a payment?

[CryptKeeper]

Here you go, just sent you 100 000 bytes.

- My DEVICE ADDRESS is 0CGP3QJM2ZUGYO6TYLG4KAGYWNWW6BLDV.
- The address that displays when I click on INSERT MY ADDRESS (it changes every time) in the chat window with Testnet Faucet is KRMI2HTBIML3CB3KEG3LB4QP75QQHDQ5.

If you are interested in pairing devices, here is my pairing code:

Code:

AmOIR5s+WxMyYUhUbEUwvr4lSP68ftSd9My8vJ1Esz2/@byteball.org/bb#gnSZxT7d0S2R

Received! I've paired and sent you back! 

[tonych]

What I've found so far with the windows binary is that the installer appears to work, but launching the wallet fails after that. Going to try the following:
1. backup my C:\Users\...\AppData\Local\byteball-test
2. Delete the folder above
3. Reinstall using the binary
4. Attempt to reload my wallet from the backup.

And how step to backup via android device?

Unfortunately, the usual methods of backup don't work for Byteball.  This is because of private payments, which are stored only in your local database and cannot be restored from a seed.  Desktop users can backup the entire app data folder C:\Users\...\AppData\Local\byteball-test but you have to do it every time you send or receive blackbytes (or any other private asset), which is not something I would recommend.

The right way to protect your funds against loss is to create a multisig wallet.  Any wallet with redundancy will do, e.g. 1-of-2, 2-of-3, 1-of-3.  With multisig, if any of your devices is lost or fails, you'll be able to use the remaining devices to move the funds to a new wallet.

[tonych]

If you are interested in pairing devices, here is my pairing code:

Code:

AmOIR5s+WxMyYUhUbEUwvr4lSP68ftSd9My8vJ1Esz2/@byteball.org/bb#gnSZxT7d0S2R

Remember, this is for one-time use, the code won't work for the second person.

I actually tried pairing two of my devices by adding the pairing code from one to the other but this doesn't seem to be enough (I chatted from one device to another but never received messages), maybe I need to perform the operation on both devices? or maybe both must be online?

It is enough.  If the devices are listed in each other's list of paired devices, they should be able to chat.

Some observations:
- 0 is considered as a valid amount, I mean when I type 0, Not valid does not appear (whereas it appears for -1 for instance), however 0 does not trigger the SEND button (which is normal), so maybe 0 should be considered not valid.

Agreed, a minor glitch.

- When writing a very long number the digits overlap on bytes.

That's a really long number, are you a whale?

- I tried sending very large numbers and it resulted in sending 1 or 2 bytes.

Thank you for spotting, will investigate.

- Why is it compulsory to backup the wallet keys before receiving a payment?

Actually, it shouldn't be compulsory, I copied it from Copay and didn't change.  Will fix.