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?
Topic: Obyte: Totally new consensus algorithm + private untraceable payments - page 1065. (Read 1234271 times)
November 21, 2016, 03:32:00 PM
November 21, 2016, 03:01:38 PM
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.
yes sent a new one and seems working, not sure what happened last time.
November 21, 2016, 08:04:04 AM
so I need a testnet bitcoin address with my funds? I have my funds in my real address, how it can check if I give another address?
For the time being, Byteball is in a test phase, using testnet Bitcoin and testnet Byteball addresses. For now, you can link testnet Bitcoin addresses to participate in the late November distribution of test bytes. The linking of your real address will start in early December and will last until December the 25th, when the first distribution of real bytes will happen.
So, for now, you can test by using a funded testnet Bitcoin address.
November 21, 2016, 05:54:53 AM
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"?
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.
Thank you for clarifying. Seemed too obvious to miss, however I wanted to check for sure.
November 21, 2016, 05:36:44 AM
"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."
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.
November 21, 2016, 05:24:49 AM
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.
November 21, 2016, 05:23:18 AM
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"?
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.
November 21, 2016, 05:11:00 AM
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"?
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"?
November 21, 2016, 03:22:25 AM
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?
November 21, 2016, 12:27:28 AM
1. For the first byteball distribution, is there only one snapshot at the btc address balance linked to byteball address (on 25th december)?
2. Is it possible to claim byteballs for instance for each device in which you have installed byteball wallets? for example PC, laptop and mobile phone? or one BTC deposit is only allowed to claim byteballs for just one device once? I do understand that there are more distribution hopefully every 2-3 months after.
2. Is it possible to claim byteballs for instance for each device in which you have installed byteball wallets? for example PC, laptop and mobile phone? or one BTC deposit is only allowed to claim byteballs for just one device once? I do understand that there are more distribution hopefully every 2-3 months after.
From the first post:
Since early December you'll be able to link your livenet bitcoin and byteball addresses. Livenet launches on December 25, snapshot will be taken from the first block of this day, and the distribution will be proportional to BTC balances on the linked Bitcoin addresses in this block. 10% of bytes and blackbytes will be distributed on this date, the remaining 88% will be distributed in subsequent rounds, see https://bitcointalksearch.org/topic/m.16569906.
So:
1. Yes there will be only one snapshot for the first distribution.
2. If you link another BTC address to another Byteball address (on another device) then there shouldn't be an issue, maybe you are talking about linking the same BTC address to multiple devices, this would make a good testcase
. See the quote above, for details about the distribution.how i can get byteball coin , follow distribution
only deposit use bitcoin in wallet dekstop byteball coin,
iam not understand about link another BTC addres to annother byteball address
you can explain for me step by step link btc addres to byteball address
read the first page, all explained there,
some details at
https://bitcointalksearch.org/topic/m.16837694
November 20, 2016, 09:56:03 PM
1. For the first byteball distribution, is there only one snapshot at the btc address balance linked to byteball address (on 25th december)?
2. Is it possible to claim byteballs for instance for each device in which you have installed byteball wallets? for example PC, laptop and mobile phone? or one BTC deposit is only allowed to claim byteballs for just one device once? I do understand that there are more distribution hopefully every 2-3 months after.
2. Is it possible to claim byteballs for instance for each device in which you have installed byteball wallets? for example PC, laptop and mobile phone? or one BTC deposit is only allowed to claim byteballs for just one device once? I do understand that there are more distribution hopefully every 2-3 months after.
From the first post:
Since early December you'll be able to link your livenet bitcoin and byteball addresses. Livenet launches on December 25, snapshot will be taken from the first block of this day, and the distribution will be proportional to BTC balances on the linked Bitcoin addresses in this block. 10% of bytes and blackbytes will be distributed on this date, the remaining 88% will be distributed in subsequent rounds, see https://bitcointalksearch.org/topic/m.16569906.
So:
1. Yes there will be only one snapshot for the first distribution.
2. If you link another BTC address to another Byteball address (on another device) then there shouldn't be an issue, maybe you are talking about linking the same BTC address to multiple devices, this would make a good testcase
. See the quote above, for details about the distribution.how i can get byteball coin , follow distribution
only deposit use bitcoin in wallet dekstop byteball coin,
iam not understand about link another BTC addres to annother byteball address
you can explain for me step by step link btc addres to byteball address
November 20, 2016, 07:29:44 PM
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.
November 20, 2016, 07:23:35 PM
"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."
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.
November 20, 2016, 06:40:52 PM
Could you clarify the relationship between the Byteball wallet and Copay and their respective codebases?
November 20, 2016, 06:10:21 PM
"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."
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."
November 20, 2016, 04:08:28 PM
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.
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.
That could almost solve the claiming exchange addresses problem.
November 20, 2016, 04:04:03 PM
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.
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.
Quote
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.
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.
November 20, 2016, 02:23:34 PM
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.
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.
November 20, 2016, 01:05:59 PM
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.
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.
November 20, 2016, 11:17:58 AM
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.
Jump to: