Hi tonych,
Today, I was preparing to byteball lunch and linking some bitcoin.
I'll use whonix, that same environment that, with your help, I had built and tested successfully byteball before.
I decided to build Byteball-TN first to test a little more.
I first cloned Byteball-TN branch only with:
> git clone -b tn --single-branch
https://github.com/byteball/byteball.git> cd byteball
Then followed build process and resolved same issues as before, and then run byteball wallet with:
> nw .
Everything seems ok. I choose full wallet.
The wallet shows "[NEW TESTNET]."
It's run for hours but it still shows "syncing... 0%" (even after changing window focus and changing focus back to byteball window).
The file byteball.sqlite has only 345 kib.
Is the new testnet supposed to sync until 100% as before?
Can you imagine what is wrong?
Next I'll do the same thing with master branch (live) in other go generate a wallet and do the linking, but before I'd like to be sure everything is working.
Thanks again.
Please clone from master branch, master is now testnet.
BTW, we are adding TOR support (or rather support for socks5 proxy), almost done, should be merged in a few days, but if you are ok to experiment with unfinished software, you can clone from our developer's fork https[Suspicious link removed]y/byteballcore.
Please clone from master branch, master is now testnet.
Yes, it works now, Wrong assumptions of me...
BTW, we are adding TOR support (or rather support for socks5 proxy), almost done, should be merged in a few days, but if you are ok to experiment with unfinished software, you can clone from our developer's fork https[Suspicious link removed]y/byteballcore.
Really great news, congratulations!
Ok, I can test.
First I tried to integrate this byteballcore lib into "new testnet", build it and run as before inside whonix 32 bits without configuring sock5, just to see if it works with defaults.
If it would have worked, I had planned to build it again in another box with a Linux 64 bits and TOR service started and configuring it to listen on sock5 port 9050.
I couldn't find instruction on how to use this byteball core lib.
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.
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.