Thanks for the updates. This is the content of that file (seams ok?):
[MIME Cache]
x-scheme-handler/byteball-test=byteball-test.desktop;
This seems ok, but your desktop file has references to nw: Exec=/home/user/byteball/test-whonix/software/nwjs-v0.14.7-linux-ia32/nw %u
Did you run the last build steps? grunt desktop
copy node_modules into the app bundle ../byteballbuilds/Byteball/linux64, except those that are important only for development (karma, grunt, jasmine)
grunt linux
After you first run "Byteball test" from byteballbuilds folder, your desktop file will be rewritten and the links should work. |
|
|
|
Description for whoever is interested in how to run byteball throw TOR:
.......
Thank you for very detailed description, it'll be helpful for anybody who wants to run Byteball through TOR too! I could see that there isn't any /home/user/byteball/test-whonix/byteball/node_modules/sqlite3/lib/binding/node-webkit-v0.14.7-linux-ia32
The directory there is named /home/user/byteball/test-whonix/byteball/node_modules/sqlite3/lib/binding/node-v47-linux-ia32
So, I renamed the directory there from node-v47-linux-ia32 to node-webkit-v0.14.7-linux-ia32
This is how node-sqlite under nw.js is to be installed, I had to do similar step on all platforms. I could determined that the '/home/user/.local/share/applications' directory were missing.
Do you remember what parts of the path were missing? It should be a problem on fresh installs, my ubuntu already had the path when I first tried. It took me 2 hours yesterday to sync to completion which seemed very good if as it seems we are going throw TOR, afaik.
Last week it took about 8 hours to fully synchronizing running your 64 bit binary on a 64 bit ubuntu virtualbox guest on the same host (so, clear internet).
Since you were building from sources, you used the latest version. We did a few optimizations in the last few days that improved performance about 10x (and still doing more optimizations). 2 hours still looks too good, I guess you are on SSD drive? Using Tor Browser (firefox) I get the following messagem when I click on "After installing, click this link to receive free bytes to play with" link.
"The address wasn't understood"
The information on address bar was: byteball-test:<meaningless-string-here>@byteball.org/bb#0000
Please can you check mimeinfo.cache in your ~/.local/share/applications? It should list protocol handler for byteball-test: links. As a workaround, you can copy the link from the website and paste it into the wallet at Menu -> Paired devices -> Add new -> Accept Invitation. |
|
|
|
Can somebody help me, after I click the link to chat with the Transition Bot there is nothing happens?
I though it's only on firefox but when I try it on chrome it's still nothing happens?
I open the byteball wallet but it's still nothing happens?
Did you install the TN version of the wallet? https://github.com/byteball/byteball/releasesThere are two testnets now, and two separate wallets. |
|
|
|
Hi tonych,
Is there a way to run byteball client throw TOR (ex: a proxy settings, as bitcoin core has, to point network traffic locally to TOR)?
I understand that byteball encrypts communications with its network (does this include communications to your servers during link bitcoin process?) but any byteball node could save user's ip (see how bitcoin explorers, ex: blockchain.info, shows originating ip for each transaction even knowing bitcoin doesn't save ip on its blockchain) and also byteball could save it during the link bitcoin process (not saying that you will, or even that if you would that you'd share it, but we all know that restricting access to malicious parties is very, very hard).
Privacy and even anonymity is very important specially when money is involved because evil parties can do incredible harmful things with information like ip, amounts, address and etc. Byteball may become very valuable in the future and every cautionary measure is advisable from now on.
In order to test byteball with TOR I tried to run byteball inside whonix (it comes as two virtualbox debian linux guests with a scheme where all network communication goes only throw TOR without any special configuration) but unfortunately whonix is only available for debian 32 bits and byteball binaries for linux are only available on 64 bits (could you please think in offering it in 32 bits for linux too?).
I also tried to run byteball inside whonix by not using your 64 bit binaries and but instead getting sources from github and installing as per yours instructions there, but after fixing some problem and have it finally installed, it didn't run ok. But I think the problem were unrelated to TOR (I will try again the whole process and come back later with more details if needed. For now could you please tell which specific version of NW is advisable to this intent as I found instructions somewhat cryptic?).
Unfortunately I have little experience with TOR and can't help much here, but it will be interesting if you update about your efforts to run Byteball through TOR. All communications are end-to-end encrypted but the IPs are visible of course. Note that during linking process you do not communicate with the Transition Bot directly, you communicate through a hub, so the bot doesn't see your IP while the hub sees the IP but doesn't see the communication as it is encrypted. Since I run both the bot and the only hub in the network, I can still match their data to determine your IP (which I'm not going to do). Asking you to run your own hub would be too much I'm afraid. Yes, you can build for linux32 yourself with very little tweaking, I recommend NW.js version 0.14.7. |
|
|
|
wow this is a nice coin, will follow...
i don't understand why the exchange wallet not working, as long as I send you the required verification amount, even my total amount is not accurate, you have no way to detect it, right?
If you send your micropayment from an exchange, we'll receive it from one of hot wallet addresses that belong to the exchange. That won't prove your balance. But how do you know it is an exchange hot wallet address? do you keep a list of all exchange addresses? They may generate new ones all the time? Just curious how you can detect them for sure. We don't know if it's an exchange address. We'll assume the address is yours. |
|
|
|
wow this is a nice coin, will follow...
i don't understand why the exchange wallet not working, as long as I send you the required verification amount, even my total amount is not accurate, you have no way to detect it, right?
If you send your micropayment from an exchange, we'll receive it from one of hot wallet addresses that belong to the exchange. That won't prove your balance. |
|
|
|
 anyone experienced something like this?not enough funds Keep trying. Somebody is siphoning bytes off the testnet faucet, I have no idea what for. |
|
|
|
Can we associate exchange address? Or only with pc wallet?  Good question, I will appreciate answer to this question. If we can with exchange addresses it will be fine and a job well done by Byteball team Exchange wallets don't work. You need a wallet where you control your private key(s). |
|
|
|
This is a nice coin, looking forward to the formal version.
Just did some tests with sending /receiving blackbytes, working fine. A minor question: when I sent 2222 blackbytes, the balance says 63,879 blackbytes - Including pending confirmation: 3,229. Why the pending confirmation is not 2222 that I just sent?
3,229 was most likely your change. Some existing outputs were split into the outgoing payment (2,222) and the change that remains in your wallet (3,229), you have to wait that the change is confirmed before you can use it again. |
|
|
|
when I try to send some blackbytes to my friend, I got this error... I have enough blackbytes in my account, and account is synchronized, I paired with my friend's device, any help on why this is not working?  Is the amount fully confirmed? Try again. |
|
|
|
I must be blind, I cannot find in the whitepaper an explanation how private keys are generated.
I may be naive in asking this, but I suppose if I should acquire someones used phone that used to have Byteball on it and reinstall Byteball, I would get issued different private keys?
This is the line from the whitepaper that got me confused: "Each device has a permanent private key that is
unique to the device."
What exactly constitutes the "device"?
On mobile phones, when an app is uninstalled, its data is wiped. So, if you reinstall, you'll have a new "device" with new keys. |
|
|
|
Could you clarify the relationship between the Byteball wallet and Copay and their respective codebases?
Byteball GUI is based on Copay, which was chosen for its ease of use and support of multiple platforms. |
|
|
|
"If your Bitcoin wallet has "Sign message" function. In this case, let me know your Bitcoin address first."
I say my Btc address and the transition bot still ask me to pay:
"Please just pay 0.000534 BTC to Bitcoin address XXXXX (this address is valid only for you), I'll give you further instructions as soon as we see your payment."
The bot expects a testnet Bitcoin address. I guess you are giving a livenet one. |
|
|
|
You have two options to prove your Bitcoin balance:
a. By making a micropayment. The bot will see your address the payment came from, will know that it is your address, and will instruct you to move your Bitcoins to this address. By making several micropayments, you can link several Bitcoin addresses to the same Byteball address.
@tonych: not sure if this was discussed before, but don't you think there is a possible door for cheating here? One could send bitcoins from an exchange address just before the mainnet launch, hoping that address will have many BTC at the coin launch date. I am not sure how exchanges work, but I suppose some of them do not always zero the address they used to complete their users' withdrawals, so the withdrawal address could contain big funds, not actually belonging to the person who withdrew the funds from it. This way someone could imitate he has big funds, while not having them in reality. Not sure I explained my point the best way... I hope the main idea is understandable though. That's a valid concern, and most likely there will be more than one user trying to profit from exchanges that reuse addresses. Probably we'll have to blacklist BTC addresses that sent more than one micropayment, unless it negatively affects other legitimate use cases. Some exchanges have minimum withdrawal amounts, and they refuse any withdrawals below them. You could check the amounts all the big exchanges use and blacklist micropayments above them. That might help mitigate the problem, but it wouldn't solve it completely if some exchanges don't have minimum withdrawal limits. This site analyses bitcoin addresses and works out if they belong to an exchange. https://www.walletexplorer.com/I gave it a cursory test, and it does quite a good job. It could be useful to work out if a micropayment is from an exchange, alhough it's probably not perfect. Thanks, this is useful information. |
|
|
|
Has anyone been able to transfer blackbytes? I have not. Any blackbytes for testing are strongly appreciated if sent to the following byteball address: KJXCTA4X7UPBGLPNW4MPQMTGYNV52LLV
You should pair the payer and payee devices to be able to send blackbytes. See Menu -> Paired devices. After pairing, exchange the addresses in chat. If you have Byteball on two or more your devices, you can already send blackbytes between them. |
|
|
|
Hi devs!
one question: i'm a xapo user(they have multisig), will i have any problem to link my address and receive byteball?
Maybe other xapo users know more, but if you control your private keys, you should be able to link. |
|
|
|
You have two options to prove your Bitcoin balance:
a. By making a micropayment. The bot will see your address the payment came from, will know that it is your address, and will instruct you to move your Bitcoins to this address. By making several micropayments, you can link several Bitcoin addresses to the same Byteball address.
@tonych: not sure if this was discussed before, but don't you think there is a possible door for cheating here? One could send bitcoins from an exchange address just before the mainnet launch, hoping that address will have many BTC at the coin launch date. I am not sure how exchanges work, but I suppose some of them do not always zero the address they used to complete their users' withdrawals, so the withdrawal address could contain big funds, not actually belonging to the person who withdrew the funds from it. This way someone could imitate he has big funds, while not having them in reality. Not sure I explained my point the best way... I hope the main idea is understandable though. That's a valid concern, and most likely there will be more than one user trying to profit from exchanges that reuse addresses. Probably we'll have to blacklist BTC addresses that sent more than one micropayment, unless it negatively affects other legitimate use cases. |
|
|
|
In Byteball client, the receive tab shows only the latest receiving address. Is there a way to see all my receiving addresses and the number of coins associated with each? Basically some feature similar to "coin control" in most alt coins.
To some extent. Click gear icon -> Advanced -> Wallet information, scroll to Last wallet addresses. |
|
|
|
I have trouble to send blackbytes too. See below screenshot:  Was the balance fully confirmed at that time? |
|
|
|
Trying to send 3000 blackbytes, after pairing, but I got an exception and the client exit. Any info?  Is your blackbytes balance confirmed? Yes, it is. Did one more test, same thing. BTW, I am using a mac client. I see the bug that causes this error message, it'll be fixed in the next release. Meanwhile, as a workaround, you can receive more bytes (not blackbytes) from the faucet and after the newly received bytes are confirmed the error message should go away. |
|
|
|
|
Show Posts
