harnorno2
Jr. Member
 Offline
Activity: 72
Merit: 1
|
 |
April 25, 2017, 02:16:13 PM |
|
Great Tech, great community, huge potential
|
|
|
|
|
|
|
|
Bitcoin mining is now a specialized and very risky industry, just like gold mining. Amateur miners are unlikely to make much money, and may even lose money. Bitcoin is much more than just mining, though!
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
avs001
Newbie
Offline
Activity: 58
Merit: 0
|
|
April 25, 2017, 02:20:11 PM |
|
i'm noob, how exactly to buy blackbytes? any how to?  |
|
|
|
|
testnet.worker1
Newbie
Offline
Activity: 37
Merit: 0
|
|
April 25, 2017, 02:43:03 PM |
|
Edit
I am reading every post in this ANN right now ha
|
|
|
|
|
galaxiekyl
Legendary
Offline
Activity: 2002
Merit: 1113
|
|
April 25, 2017, 02:50:29 PM |
|
i sell my GBB if someone is interested pm me.
|
|
|
|
|
|
kaicrypzen
|
|
April 25, 2017, 03:12:19 PM |
|
today latest full wallet stopped syncing and it gives me this error, Uncaught exception: Error: known bad WRc/Ylyr5wKYozWO+RpVf330NRLCSU0VjKfmUrRUaKI=: WRc/Ylyr5wKYozWO+RpVf330NRLCSU0VjKfmUrRUaKI=: last ball unit LGFzduLJNQNzEqJqUXdkXr58wDYx77V8WurDF3+GIws= is not stable in view of your parents 6O4t3j8kW0/Lo7n2nuS8ITDv2UbOhlL9fF1M6j/PrJ4= what to do ? Also after this bug is resolved can I switch to light wallet from full while keeping the address or I need to install light wallet on another machine and send my balance there and relink BTC addresses ? As you said, this is a bug and it is being worked on currently. If you have a backup of your data folder before the install, then you can try downgrading to 1.8.0 and using that backup. Switching from full to light and vice-versa is not possible. Maybe you can use the seed on a light wallet to recover addresses and bytes (but not blackbytes), but that's just a maybe  . |
|
|
|
|
pwpwpw
|
|
April 25, 2017, 03:16:02 PM |
|
today latest full wallet stopped syncing and it gives me this error, Uncaught exception: Error: known bad WRc/Ylyr5wKYozWO+RpVf330NRLCSU0VjKfmUrRUaKI=: WRc/Ylyr5wKYozWO+RpVf330NRLCSU0VjKfmUrRUaKI=: last ball unit LGFzduLJNQNzEqJqUXdkXr58wDYx77V8WurDF3+GIws= is not stable in view of your parents 6O4t3j8kW0/Lo7n2nuS8ITDv2UbOhlL9fF1M6j/PrJ4= what to do ? Also after this bug is resolved can I switch to light wallet from full while keeping the address or I need to install light wallet on another machine and send my balance there and relink BTC addresses ? As you said, this is a bug and it is being worked on currently. If you have a backup of your data folder before the install, then you can try downgrading to 1.8.0 and using that backup. Switching from full to light and vice-versa is not possible. Maybe you can use the seed on a light wallet to recover addresses and bytes (but not blackbytes), but that's just a maybe . So the switch from full to light wallet must be done via sending all balance to another machine with a light wallet and then copying that light wallet back to the main machine. About this bug, is it known what's causing it ? |
|
|
|
|
kaicrypzen
|
|
April 25, 2017, 03:27:44 PM |
|
I want to relink my BTC address to different byteball address  You can still do this, but move your Bitcoins to a different Bitcoin address, and link that new address to your new Byteball address. But the wallet is same despite the different payment address. I mean, I made the micropayment-for-linking to different byteball address from the single hardware BTC wallet (Ledger nano) but chatbot told me it was paid from different address. There's no problem if, as you said, previous link become invalid, but worried if the later linking is also invalid without any notifications. Sorry for my bad English from Japan, but I want to get involved in this exciting coin. Best regards I think both links will be invalidated, and the BTC address blacklisted, it might be perceived as a cheating attempt (linking the same BTC address to several BB addresses). When you do a micropayent, the remaining balance is transferred to another address, that's probably why the linked address and the one that holds your funds are different. if you link by a micropayment you'll have to move your funds back to the original address. Here is a tutorial to link by signing a message using Ledger Nano S + Electrum https://bitcointalk.org/index.php?topic=1608859.msg17160291#msg17160291, I hope it helps. |
|
|
|
megashira1
Legendary
Offline
Activity: 1146
Merit: 1000
|
|
April 25, 2017, 04:58:58 PM |
|
At this rate ByteBall should get added to Poloniex in no time.
|
|
|
|
|
pwpwpw
|
|
April 25, 2017, 05:08:34 PM |
|
I want to relink my BTC address to different byteball address You can still do this, but move your Bitcoins to a different Bitcoin address, and link that new address to your new Byteball address. But the wallet is same despite the different payment address. I mean, I made the micropayment-for-linking to different byteball address from the single hardware BTC wallet (Ledger nano) but chatbot told me it was paid from different address. There's no problem if, as you said, previous link become invalid, but worried if the later linking is also invalid without any notifications. Sorry for my bad English from Japan, but I want to get involved in this exciting coin. Best regards I think both links will be invalidated, and the BTC address blacklisted, it might be perceived as a cheating attempt (linking the same BTC address to several BB addresses). When you do a micropayent, the remaining balance is transferred to another address, that's probably why the linked address and the one that holds your funds are different. if you link by a micropayment you'll have to move your funds back to the original address. Here is a tutorial to link by signing a message using Ledger Nano S + Electrum https://bitcointalk.org/index.php?topic=1608859.msg17160291#msg17160291, I hope it helps. If you send all your balance to a new wallet address (switch from full to light for example), you need to relink your btc but if how do you unlink them at the first BB address ? or you need to move all your BTC to another address and link the new one? |
|
|
|
|
taurados
|
|
April 25, 2017, 05:10:06 PM |
|
At this rate ByteBall should get added to Poloniex in no time.
Hope so then 0.5 possible |
|
|
|
|
|
the artful bodger
|
|
April 25, 2017, 05:22:38 PM |
|
I want to relink my BTC address to different byteball address You can still do this, but move your Bitcoins to a different Bitcoin address, and link that new address to your new Byteball address. But the wallet is same despite the different payment address. I mean, I made the micropayment-for-linking to different byteball address from the single hardware BTC wallet (Ledger nano) but chatbot told me it was paid from different address. There's no problem if, as you said, previous link become invalid, but worried if the later linking is also invalid without any notifications. Sorry for my bad English from Japan, but I want to get involved in this exciting coin. Best regards I think both links will be invalidated, and the BTC address blacklisted, it might be perceived as a cheating attempt (linking the same BTC address to several BB addresses). When you do a micropayent, the remaining balance is transferred to another address, that's probably why the linked address and the one that holds your funds are different. if you link by a micropayment you'll have to move your funds back to the original address. Here is a tutorial to link by signing a message using Ledger Nano S + Electrum https://bitcointalk.org/index.php?topic=1608859.msg17160291#msg17160291, I hope it helps. If you send all your balance to a new wallet address (switch from full to light for example), you need to relink your btc but if how do you unlink them at the first BB address ? or you need to move all your BTC to another address and link the new one? I don't think you need to unlink your bitcoins, the bot automatically detects when you move them. Just link them to a byteball address and check if the bot shows they are linked on the website. |
|
|
|
|
|
|
CryptKeeper
Legendary
Offline
Activity: 2044
Merit: 1055
|
|
April 25, 2017, 07:24:03 PM |
|
200 dollars a price, I do not believe in it)))
party is not over yet. and don't forget this is one ball man game. Tony, the chief developer, has two colleagues involved and there are already community members developing for byteball. Currently there are 15 contributors listed on github: https://github.com/byteball/byteball/graphs/contributors |
Follow me on twitter! I'm a private Bitcoin and altcoin hodler. Giving away crypto for free on my Twitter feed!
|
|
|
|
bustedsynx
|
|
April 25, 2017, 07:26:10 PM |
|
200 dollars a price, I do not believe in it)))
party is not over yet. and don't forget this is one ball man game. Tony, the chief developer, has two colleagues involved and there are already community members developing for byteball. Currently there are 15 contributors listed on github: https://github.com/byteball/byteball/graphs/contributorsNice! 15 devs. I like where this is going. How many is ETH and BTC's dev pool? |
|
|
|
tonych (OP)
Legendary
Offline
Activity: 964
Merit: 1008
|
|
April 25, 2017, 07:29:15 PM |
|
Sorry for frequent upgrades, a new bug popped up yesterday and is fixed now, please update if you are running a full client https://github.com/byteball/byteball/releases. It was a validation error that needs to be fixed in two steps to minimize disruption. This is step 1, step 2 will follow after most full nodes upgrade. Also since this release, the node automatically clears old log data to save some space (thanks @portabella!). The update is mandatory for all full nodes (both GUI and headless). |
Simplicity is beauty
|
|
|
|
kaicrypzen
|
|
April 25, 2017, 07:53:46 PM |
|
So the switch from full to light wallet must be done via sending all balance to another machine with a light wallet and then copying that light wallet back to the main machine.
Yes. You can also transfer (instead of copy) your blackbytes (first) and bytes to the new light wallet on your main machine (from the other machine). |
|
|
|
|
SatoNatomato
|
|
April 25, 2017, 08:39:32 PM |
|
Sorry for frequent upgrades, a new bug popped up yesterday and is fixed now, please update if you are running a full client https://github.com/byteball/byteball/releases. It was a validation error that needs to be fixed in two steps to minimize disruption. This is step 1, step 2 will follow after most full nodes upgrade. Also since this release, the node automatically clears old log data to save some space (thanks @portabella!). The update is mandatory for all full nodes (both GUI and headless). Thanks for the frequent upgrades, better those than crickets and promises.  Remember to take rest, do not overwork, chill and relax. |
|
|
|
|
|
zanzibar
|
|
April 25, 2017, 08:55:34 PM |
|
Sorry for frequent upgrades, a new bug popped up yesterday and is fixed now, please update if you are running a full client https://github.com/byteball/byteball/releases. It was a validation error that needs to be fixed in two steps to minimize disruption. This is step 1, step 2 will follow after most full nodes upgrade. Also since this release, the node automatically clears old log data to save some space (thanks @portabella!). The update is mandatory for all full nodes (both GUI and headless). Thanks, upgraded, runs good. |
|
|
|
|
|
pwpwpw
|
|
April 25, 2017, 11:11:55 PM |
|
Sorry for frequent upgrades, a new bug popped up yesterday and is fixed now, please update if you are running a full client https://github.com/byteball/byteball/releases. It was a validation error that needs to be fixed in two steps to minimize disruption. This is step 1, step 2 will follow after most full nodes upgrade. Also since this release, the node automatically clears old log data to save some space (thanks @portabella!). The update is mandatory for all full nodes (both GUI and headless). fixed my bug in less than 8hours of reporting it...that's what I'm talking about, all praise tonych! |
|
|
|
|
onetwo12
|
|
April 26, 2017, 01:05:29 AM |
|
Sorry for frequent upgrades, a new bug popped up yesterday and is fixed now, please update if you are running a full client https://github.com/byteball/byteball/releases. It was a validation error that needs to be fixed in two steps to minimize disruption. This is step 1, step 2 will follow after most full nodes upgrade. Also since this release, the node automatically clears old log data to save some space (thanks @portabella!). The update is mandatory for all full nodes (both GUI and headless). thanks for the updates that's great! |
|
|
|
|
