Topic: Obyte: Totally new consensus algorithm + private untraceable payments - page 1111. (Read 1233994 times)
September 14, 2016, 02:24:38 AM
did follow the twitter account and install the wallet!!
September 14, 2016, 02:24:06 AM
It is definitely a clone of IOTA because of the copy of IOTA's concept.
Too many differences to be a clone:
- differrent codebase, different language (javascript vs. java)
- byteball uses no POW, iota does
- byteball charges fees for transactions, iota does not
- byteball uses concept of "witnesses"
- byteball has different features and use cases (multi-signature, assets, voting, chat, etc.)
- byteball has mobile wallets for iOS and android
September 14, 2016, 02:04:25 AM
any wallet for win 32 dev?
I have already download but win 64.
its not compatibel for 32bits.
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.
September 14, 2016, 12:37:43 AM
It is definitely a clone of IOTA because of the copy of IOTA's concept.
Define clone. An entirely new codebase and you call it a clone?
September 13, 2016, 10:01:05 PM
It is definitely a clone of IOTA because of the copy of IOTA's concept.
same concept ≠ clone
September 13, 2016, 09:29:57 PM
It is definitely a clone of IOTA because of the copy of IOTA's concept.
September 13, 2016, 03:58:15 PM
Who are you tonych? What have you done in crypto so far?
Read the whitepaper
Cryptographers are a rare breed.
Many spend their life on research and even philosophical thought.
September 13, 2016, 03:46:44 PM
Who are you tonych? What have you done in crypto so far?
September 13, 2016, 01:58:31 PM
Version 0.3.0 is released https://github.com/byteball/byteball/releases/tag/v0.3.0.
Several bugs were fixed, in particular:
- receiving long chains of private payments in light wallets (thank you Bitsharesuser1234 and CryptKeeper for help in discovering the issue)
- opening byteball: links when the wallet is encrypted by password
- receiving private payments sometimes was not displayed in chat window
Please upgrade your desktop clients. Android should have already updated automatically by this time (although I still receive crash reports from someone who is using the original version on Android, please update).
There are still some bugs whose cause is unclear to me, I need more data because the bugs are rare. Please actively use the wallet, use it in the least evident way you can think of, trying to cause the bugs to surface. If you see something unexpected, please report.
Several bugs were fixed, in particular:
- receiving long chains of private payments in light wallets (thank you Bitsharesuser1234 and CryptKeeper for help in discovering the issue)
- opening byteball: links when the wallet is encrypted by password
- receiving private payments sometimes was not displayed in chat window
Please upgrade your desktop clients. Android should have already updated automatically by this time (although I still receive crash reports from someone who is using the original version on Android, please update).
There are still some bugs whose cause is unclear to me, I need more data because the bugs are rare. Please actively use the wallet, use it in the least evident way you can think of, trying to cause the bugs to surface. If you see something unexpected, please report.
September 13, 2016, 01:28:24 PM
whether android wallet can be used when the coin is official and not a test ? because I prefer to use android wallet that does not consume a lot of space in my computer files .
Of course, it will be used on livenet too.
September 13, 2016, 12:43:27 PM
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.
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.
September 13, 2016, 10:38:05 AM
follow is done , keep work
September 13, 2016, 10:25:08 AM
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.
A good way would be some kind of newsletter to keep people informed so they don`t miss everything.
Follow the project's twitter https://twitter.com/ByteballOrg.
September 13, 2016, 09:53:08 AM
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.
A good way would be some kind of newsletter to keep people informed so they don`t miss everything.
Follow the project's twitter https://twitter.com/ByteballOrg.
Done. searched it before but didnt´find it.
That´s great to keep everyone updated.
September 13, 2016, 09:45:25 AM
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.
A good way would be some kind of newsletter to keep people informed so they don`t miss everything.
Follow the project's twitter https://twitter.com/ByteballOrg.
September 13, 2016, 08:11:04 AM
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).
September 13, 2016, 07:47:45 AM
No IPO scam.
The distribution make this altcoin "legit".
I am fine with the 1% for the developers.
Are you planing to hire a team ?
This was my sentiment, exactly. I have no clue how well Byteball is going to work since it's so new and I've not had the time to dig into the software. However, when the dev is willing to offer the distribution 100% to supporters AND the code is 100% new, it's worth giving it a look and a little support.
Thanks, Tonych! I'm looking forward to finding out more details soon.
September 13, 2016, 07:08:48 AM
No IPO scam.
The distribution make this altcoin "legit".
I am fine with the 1% for the developers.
Are you planing to hire a team ?
Yes, I'll add more people as soon as I see the need.
September 13, 2016, 05:57:54 AM
No IPO scam.
The distribution make this altcoin "legit".
I am fine with the 1% for the developers.
Are you planing to hire a team ?
September 13, 2016, 05:47:24 AM
whether android wallet can be used when the coin is official and not a test ? because I prefer to use android wallet that does not consume a lot of space in my computer files .
Jump to: