Obyte: Totally new consensus algorithm + private untraceable payments

[kaicrypzen]

I checked both on my phone and on the GP web page https://play.google.com/store/apps/details?id=org.byteball.wallet, neither lists the mic.  I'm guessing you see some broad groups of permissions rather than individual ones.

I think your guess is right.

If you found this line https://github.com/byteball/byteball/blob/e1e29620587d4a8744777af3e713c53940e1773a/src/js/directives/qrScanner.js#L13, this where we call the cordova plugin that works with the camera.

Yep, found this one .

I googled for "byteball apk" and "google play apk" and found a few.  Not sure how trustworthy they are, and some list the old version that was replaced yesterday.

Ok. If you're not sure how trustworthy they are then I prefer sticking with the GP version.

Just curious, what are you so averse of google play?

Just not a fan of the we-gather-your-info-and-habits and synchronize-your-device-without-telling-you and other-anti-privacy-stuff attitude of Goolge .

If you can't include the apk on the website, then maybe you could try submitting your app to be listed on F-droid https://f-droid.org/wiki/page/FAQ_-_App_Developers#How_do_I_get_my_app_included.3F.

[1713964238]

1713964238

[1713964238]

1713964238

[1713964238]

1713964238

[1713964238]

1713964238

[1713964238]

1713964238

[1713964238]

1713964238

[tonych]

I see 65,000 bytes and 53,923 of ... why two please: Is it one for Bytes and the other for ByteBalls?

The other is for blackbytes.  The "of JY4R..." part is about the asset you are holding, JY4R... is blackbytes.  You can have even more than two assets.

How to link my byteball to the bitcoin addresses please

The linking phase will start later, watch this thread for announcements.

[cryptospreader]

Nice project. Linux client seems to work well, but after clicking some buttons, I feel myself lost. Some user guide on what to do with those blackbytes, devices, bots, seeds etc would be nice to have.

I do suggest the same. A video presentation or a walk-through to all of the features available in the client is advisable at this point.

[CryptKeeper]

Thanks.
Another question: there are many app types listed in the whitepaper. I'm wondering how many of them are already available in the current release? How many devs are working on this?

All the app types are implemented in the core library https://github.com/byteball/byteballcore but only payments are available through the GUI wallet.  The rest can be invoked directly in javascript, see samples at https://github.com/byteball/headless-byteball/tree/master/play.
One dev so far (me).

Jesus, you need a team! 

Quite an achievement for only one person, you can be proud! I've got the feeling that this could be really huge. Do you have a vision how the project should go forward?

[tonych]

Thanks.
Another question: there are many app types listed in the whitepaper. I'm wondering how many of them are already available in the current release? How many devs are working on this?

All the app types are implemented in the core library https://github.com/byteball/byteballcore but only payments are available through the GUI wallet.  The rest can be invoked directly in javascript, see samples at https://github.com/byteball/headless-byteball/tree/master/play.
One dev so far (me).

Jesus, you need a team! 

Quite an achievement for only one person, you can be proud! I've got the feeling that this could be really huge. Do you have a vision how the project should go forward?

Like many open-source projects it should be supported by the community, which will hopefully emerge.
If you are a developer, you are welcome to contribute to our github repos.

[tonych]

Just curious, what are you so averse of google play?

Just not a fan of the we-gather-your-info-and-habits and synchronize-your-device-without-telling-you and other-anti-privacy-stuff attitude of Goolge .

If you can't include the apk on the website, then maybe you could try submitting your app to be listed on F-droid https://f-droid.org/wiki/page/FAQ_-_App_Developers#How_do_I_get_my_app_included.3F.

I agree they are becoming too intrusive with their data mining.
I checked F-droid but didn't change my decision to distribute APKs through google play exclusively.  The biggest merit of google play is auto-updates, which is absolutely required for security apps like this.  While you say you are prepared to go through the trouble of manual updating, most people aren't, and I don't want to encourage use of outdated software that might have critical security bugs.  Moxie Marlinspike had some fair criticisms about f-droid, which I totally agree with, and I believe, for this kind of apps, google is a lesser evil.

Since you are rightfully concerned about privacy, I want you to be aware that Byteball wallet sends crash reports to me whenever it detects any abnormal condition.  These reports have already helped me fix some bugs in the latest release and identify others that need further investigation.

[CryptKeeper]

Thanks.
Another question: there are many app types listed in the whitepaper. I'm wondering how many of them are already available in the current release? How many devs are working on this?

All the app types are implemented in the core library https://github.com/byteball/byteballcore but only payments are available through the GUI wallet.  The rest can be invoked directly in javascript, see samples at https://github.com/byteball/headless-byteball/tree/master/play.
One dev so far (me).

Jesus, you need a team! 

Quite an achievement for only one person, you can be proud! I've got the feeling that this could be really huge. Do you have a vision how the project should go forward?

Like many open-source projects it should be supported by the community, which will hopefully emerge.
If you are a developer, you are welcome to contribute to our github repos.

I cannot help you with the development but I can help you finding a community (and maybe there are some good devs among them).

I'll try to make this project popular using my twitter account (3000 followers) and my contacts from other crypto projects.
IMHO some bounties for community tasks like beta testing, documentation, translations, end user support, marketing, fighting the trolls etc. etc. could be really helpful.
You should consider to set aside another percentage of bytes for these things.

[spartacusrex]

Back to the tech..

With the private fixed denominations, what happens if I have a single 1000 output,  and i need to pay someone 523..?

Do I need to get change from someone?

[tonych]

Like many open-source projects it should be supported by the community, which will hopefully emerge.
If you are a developer, you are welcome to contribute to our github repos.

I cannot help you with the development but I can help you finding a community (and maybe there are some good devs among them).

I'll try to make this project popular using my twitter account (3000 followers) and my contacts from other crypto projects.
IMHO some bounties for community tasks like beta testing, documentation, translations, end user support, marketing, fighting the trolls etc. etc. could be really helpful.
You should consider to set aside another percentage of bytes for these things.

Thank you for your help, we do need active community members.
While I expect most community effort, including development, to be voluntary, I'll consider funding some clearly defined tasks without impacting the distribution percentages.

[tonych]

Back to the tech..

With the private fixed denominations, what happens if I have a single 1000 output,  and i need to pay someone 523..?

Do I need to get change from someone?

Depends on the denomination of your 1000 output.  Consider it like cash.
In code, we have tolerances that allow to round the transfer amount if you are short of small-denomination outputs required to compose the exact desired amount.

[spartacusrex]

Back to the tech..

With the private fixed denominations, what happens if I have a single 1000 output,  and i need to pay someone 523..?

Do I need to get change from someone?

Depends on the denomination of your 1000 output.  Consider it like cash.
In code, we have tolerances that allow to round the transfer amount if you are short of small-denomination outputs required to compose the exact desired amount.

And so if it is just 1 1000 note ?

To pay 523, I would need to change it with someone ?

[tonych]

And so if it is just 1 1000 note ?

To pay 523, I would need to change it with someone ?

Yes, same as cash.

[Sam123]

How  to see the all the previous addresses generated please

[spartacusrex]

And so if it is just 1 1000 note ?

To pay 523, I would need to change it with someone ?

Yes, same as cash.

Why not have a special 'split' txn ?

So I can split my 1000, into a subset of smaller denominations that allow payment of any amount. Say.. 500, 100x4, 50, 10x4, 5, 1x5.. etc

This would not increase the proof size as all the unused coins would just be outputs in the txn, that wouldn't need tracking.

So you would have one extra txn with the single 1000 input and the above outputs. All controlled by you. You would need to post that.

The payment final proof would only be one step longer, and in fact in this case all the outputs used would link back through the same proof tree?

Then you could use those outputs to make 523.

I know your system keeps track of amounts of the individual coins, but the spli txn could be designed specifically to sort all that out.

[tonych]

How  to see the all the previous addresses generated please

Gear icon -> Advanced -> Wallet information -> scroll to Last wallet addresses

[tonych]

And so if it is just 1 1000 note ?

To pay 523, I would need to change it with someone ?

Yes, same as cash.

Why not have a special 'split' txn ?

So I can split my 1000, into a subset of smaller denominations that allow payment of any amount. Say.. 500, 100x4, 50, 10x4, 5, 1x5.. etc

That's what smaller denominations are for.  If we allow unlimited splitting (remember, there is no merging), all large-denomination coins will be split and large-value payments will become inconvenient.

[kaicrypzen]

I checked F-droid but didn't change my decision to distribute APKs through google play exclusively.  The biggest merit of google play is auto-updates, which is absolutely required for security apps like this.  While you say you are prepared to go through the trouble of manual updating, most people aren't, and I don't want to encourage use of outdated software that might have critical security bugs.

I see your point. I do however believe that all the solutions can co-exist, Google Play + auto-upates for those who activate them, Google Play without auto-updates for those who deactivate them, F-droid and apk. I don't think this will penalize users from a given group. People who do not use auto-updates (GP or F-droid) and people who use apks are generally aware that they should keep an eye on potential updates and that they should untick allow 3rd party apks once an app is installed .

Moxie Marlinspike had some fair criticisms about f-droid, which I totally agree with, and I believe, for this kind of apps, google is a lesser evil.

Didn't know about that, so I searched and found this discussion https://github.com/WhisperSystems/Signal-Android/issues/127 between @moxie and users pushing for providing his app outside Google Play. Some of the concerns he raised back in 2013 were no more in 2015 (Yep the discussion lasted 2 years ).

Since you are rightfully concerned about privacy, I want you to be aware that Byteball wallet sends crash reports to me whenever it detects any abnormal condition.  These reports have already helped me fix some bugs in the latest release and identify others that need further investigation.

Thanks for pointing that out. Do you mean that it is hard-coded or the user can choose not to send the reports?

My opinion on the matter in general, is that the user should have the choice and assume the consequences that come with their choice.

[tonych]

Since you are rightfully concerned about privacy, I want you to be aware that Byteball wallet sends crash reports to me whenever it detects any abnormal condition.  These reports have already helped me fix some bugs in the latest release and identify others that need further investigation.

Thanks for pointing that out. Do you mean that it is hard-coded or the user can choose not to send the reports?

My opinion on the matter in general, is that the user should have the choice and assume the consequences that come with their choice.

In the current version, it is hard-coded.
One way to get rid of the reports is by connecting to another hub (change hub address in global settings) that doesn't process bug reports.  I'm not aware of any other hubs except the one I run, but you can run your own https://github.com/byteball/byteball-hub.

This is one of recent bug reports to see what information it contains:

Javascript error: Uncaught TypeError: Object [object Object] has no method 'retrieveJsMessages'

TypeError: Object [object Object] has no method 'retrieveJsMessages'
   at pollOnce (file:///android_asset/www/cordova.js:969:40)
   at pollOnceFromOnlineEvent (file:///android_asset/www/cordova.js:960:5)

Breadcrumbs:
Sat Sep 10 2016 17:17:52 GMT+0200 (CEST): index.js
Sat Sep 10 2016 17:17:56 GMT+0200 (CEST): already connecting to wss://byteball.org/bb
Sat Sep 10 2016 17:17:59 GMT+0200 (CEST): already connecting to wss://byteball.org/bb
Sat Sep 10 2016 17:18:00 GMT+0200 (CEST): connected to wss://byteball.org/bb
Sat Sep 10 2016 17:47:18 GMT+0200 (CEST): already connecting to wss://byteball.org/bb
Sat Sep 10 2016 17:47:18 GMT+0200 (CEST): already connecting to wss://byteball.org/bb
Sat Sep 10 2016 17:47:20 GMT+0200 (CEST): connected to wss://byteball.org/bb
Sat Sep 10 2016 17:55:58 GMT+0200 (CEST): already connecting to wss://byteball.org/bb
Sat Sep 10 2016 17:55:58 GMT+0200 (CEST): already connecting to wss://byteball.org/bb
Sat Sep 10 2016 17:55:59 GMT+0200 (CEST): connected to wss://byteball.org/bb
Sat Sep 10 2016 17:56:08 GMT+0200 (CEST): bugreport

UA: Mozilla/5.0 (Linux; Android 4.4.4; GT-I9000 Build/KTU84Q) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/33.0.0.0 Mobile Safari/537.36
Program: byteball-test android 0.2

[Sam123]

How  to see the all the previous addresses generated please

Gear icon -> Advanced -> Wallet information -> scroll to Last wallet addresses

Great thanks

[animalroam]

So when distribution happens, would we need to consolidate all bitcoins to a certain address before a certain block? How would sending from a coinbase wallet work - if a user sent maybe 0.0001 BTC from an address to your address and the Coinbase address contains 100 BTC, would he/she have a weight of 100 BTC during distribution?