Quote from: freezal on December 20, 2016, 01:44:33 PM

Quote from: freezal on December 20, 2016, 12:29:02 PM

Quote from: tonych on December 19, 2016, 07:54:51 PM

Quote from: freezal on December 19, 2016, 02:03:51 PM

So I cloned master again, run build steps leaving only the final "grunt" to be run.
Then find byteball/node_modules/byteballcore renamed it to get ride of it.
Put in its place the content of your unfinished byteballcore, and run grunt and tried to run byteball as before.
But after chose full wallet it shows and exclamation icon with message:
An exception occurred: TypeError: Wallet.readBalance is not a function: cause: undefined
And after click OK button it closes.
it seems I'm doing it the wrong way.
If you still want me to test this sock5 thing, could you please point me to some instruction on how to make it works.

Besides of this, I think I'm afraid I could not use this new version of byteball with sock5 to link and participate on byteball first round of distribution, as it probably won't be ready soon enough;
I still want to use TOR and so my only option seems to be whonix building livenet myself.

You did everything right, but the versions appeared to be incompatible (the fork was lagging a few commits), so forget it, better wait that we merge, or given the time constraints, the whonix ways seems safer.

Quote from: freezal on December 19, 2016, 02:03:51 PM

If by doing: git clone https://github.com/byteball/byteball.git I get "new testnet", how can I clone live 0.7.1 (with I assume is the version everybody linking their bitcoins is using) to build it to proceed with live wallet generation and linking process via TOR?
Thanks.

Switch to "livenet" branch, it corresponds to live 0.7.1.

OK, that works and I've successfully build and run livenet. Thank you.
Now, my security model imply, as a way to link byteball to bitcoins, that I sign byteball addresses offline.
So I've tried to generate a certain number of byteball address in order to create a file to take it offline to another computer and while there I would sign each byteball address with a bitcoin address and save the signed text.
Then I would bring that file back to the online computer start byteball again and inform to the linking bot those addresses and signed results and have everything linked.
So, to generate the byteball addresses I went to receive and press generate address button several times and then went to Preferences > Advanced > Wallet Information and at button copied the generated byteball addresses.
First thing I noticed was that it seems to only show the last about 6 generated addresses.
Never mind, I come back to receive and generate some more and go back to Walled Information and copy the new ones from there,
Then I noticed that after some time receive stop generating new addresses and every time that I press generate button it generates one of those already generated.
I tried to close and run again the wallet and the same thing happened
Is there a way around this?
Even thou I'm not being able to see all addresses can I be sure to have all them registered inside the wallet?
Thanks again

Complementing....

I've also noticed that when I press insert address button on transition bot it place there one of the previouslly generated ađresses and not a newly generated one.

thanks

BIP44 recommends to avoid having more than 20 unused addresses in a row, that's why we stop generating new addresses at this point and give a random unused one. However, you can hack this around by editing MAX_BIP44_GAP constant at https://github.com/byteball/byteballcore/blob/master/wallet_defined_by_keys.js#L25.

Note that signed message is expected to sign the last BB address that you told the bot. So if you want to avoid all your Bitcoin addresses being associated with the same BB address, your dialog with the bot should consist of repeated series of these 3 steps:
- BB address
- Bitcoin address
- signed message