Topic: [BTB] The BitBar Information Thread - page 39. (Read 180272 times)

To let the community know.

I have sponsored the node and block explorer @ Cryptocoinexplorer for the next year in hope that it can be continued to be used as a tool for the bitbar community. The Explorer is run by Dreamwatcher, a respected member of the crypto community whos dedication and experience speak for itself.

Through my correspondences with Dreamwatcher, I shared updates on the status of Bitbar...

The Bitbardev going offline (leaving the project?)

Mullicks involvement I'm early 2015,

The lack of any dedicated Developer/coder on the project at this time.

I reached out to Dreamwatcher about potentially working on Bitbar after hearing the outcry for development from the community. I figured he would be a logical choice in heading up the project after his original coding of CCE,  his work on multiple types of crypto-currencies of the star trek theme, and the online exchange of said cryptos.

I feel like we are at a stage where with the proper Coding Developer, and the dedication of community involvement, we can turn the tide on Bitbar, and be proud of having taken part in doing so.

With the renewal of CCE for 2016, Dreamwatcher has expressed interest in further development of bitbar, as a Dev . We need a proper developer.

I'm sure he will weigh in here, as he has in the past. But the prospect of this becoming a reality drove me to inform the community now.

I welcome any opinions and support for this move forward.

I want to reassure people about their wallets during this chain fork.

The wallet.dat files' primary purpose is to store the private keys to the addresses you own.

It does contain a mini ledger of sorts so that the client/daemon does not have to re-scan the entire blockchain every time you start it.

The transaction/balance information in the wallet.dat file is not "canon" so to speak. It is really just there for display purposes.

The true balance/transaction information is in the block chain itself. When the Client/daemon detects that the blockchain might not match the ledger in the wallet file, it will re-scan the blockchain and correct the balance/transaction information in the wallet.dat. This normally happens when a chain reorganization takes place, or a new/different wallet.dat file is presented.

When the resolution of a fork occurs, all transactions on the rejected fork no longer exist. If person A sent 10 coins to person B and they were on the rejected fork, person A would have the 10 coins back in his wallet and person B would have never received those coins because the transaction no longer exists.

The people that have the potential to lose coins are those who mined POW blocks on the rejected chain. Those will be lost.
Although the coins gained on the rejected chain through POS would disappear, the coins that were used to stake a block would still have the same maturity as if the fork did not happen and will stake new blocks on the correct chain.

Take all the precautions you wish, whatever makes you comfortable. When the correct chain is decided, your client/daemon will automatically adjust your wallets ledger.


ETA: This only applies to transactions after the fork. Any transactions before the fork are unaffected.

Spiderboxes advise is a good way to go. I would say keep your wallet up, when you sync if your bars are still unconfirmed copy the received address and go to the console, dumpprivkey and save it. Back up the wallet and save it to some sort of digital medium (the private key can be saved on paper)

Depending on what chain the exchanges sync to, the bars may confirm or turn to orphan blocks.

I would then make a fresh wallet knowing that I have those potential bars backed up, for the fact that I would not want that constant reminder when I look at the qt client.

Ultimately the decision is yours, but having a wallet online and synced is a big help to everyone in terms of connectivity.

When I messing with my wallets, I close the wallet if it is running, I copy and paste the Bitbar directory - that way everything is backed up - including the chain you were on.
Once that is done, you can mess with whatever you want, because if you screw it up, you can just delete the Bitbar directory, rename 'copy of Bitbar' back to bitbar, and you are back to where you started.

If you want to start fresh (once you have a backup copy) you can delete everything in the Bitbar folder except the wallet.dat, and bitbar.conf files, start up the bitbar-qt.exe and it will start syncing the chain.


To start out, you can do as Luke suggested and put:
connect=68.191.93.33
in your bitbar.conf file.

After you are caught  up, change the 'connect=' to 'addnode=' and add some of the nodes listed at http://btb.cryptocoinexplorer.com/peerinfo

also remember to add:
irc=0
listen=1

Should I take the wallet offline the one with the unconfirmed coins? Just keep it as back up?

The safest answer I can give you is to backup the addresses you received coins to, perhaps a paper wallet or of the wallet.dat file and come back to it in the future after everyone is on the same chain.

I am on the longest chain, connected to the oldest node but things are not certain even for that.

It sucks, but thus isn't the first time anyone has lost due to split chains.

I myself have been a victim of pools going rouge in the past (anyone remember diggers pool?)

until there is more infrastructure surrounding bitbar all we can do is try to help eachother out by spreading information.

Speaking of, I am excited to share some information concerning possible future developments....

more to come

My wallet is syncing now, but I get the feeling my coins are going to be unconfirmed. The million dollar question is have I lost them or not?

I have now used the connect command in my conf file, many thanks

I received a message from Mastermining that he would be syncing his pool to the explorer at Cryptocoinexplorer.

It looks like he failed to sync, as I saw a message on the site about it. I have isolated my node and will transmit it to him again to hopefully get things straight over there.

Another thing is when syncing, one can use the command

connect=68.191.93.33 in the bitbar conf file to lock onto my node and sync.

I am already running with them nodes thanks anyway

I've decided to download the chain from scratch see if that helps it was originally stuck on 141002

I am running a full node synced with Cryptocoinexplorer, Block count 142596

addnode=68.191.93.33

CCE runs a dedicated node @

addnode=btb.altcointech.net

Hope this helps

http://btb.cryptocoinexplorer.com/ is at block 142593, same as I have.
Mastermining is at 142141
I can't get to ispace now but I'm sure they are way of the mark.

What block are you stuck on ??

Wallet not syncing,,,,,,again! 

Looks like Mastermining is re-syncing his wallet.
Noticed a few minutes ago a block on the chain for about 22 BTB had 127 transactions - maybe another pool payout??

That's because they are on a different fork than us.
Things will become clearer once Cryptsy gets done with their BTB wallet maintenance.

There info is incorrect when you click on the block explorer link it says the blocks not found. The info I am after is how to download the blockchain they are on. That's where I mined my coins and the blockchain I have is saying my coins are unconfirmed.

Don't know what info you want, but here is a link to thier site that shows what block they are on:
http://ispace.co.uk/coindetails/?coin=btb

Does anyone have the info for the ispace blockchain?

Yeah I agree hopefully without loss of coins to anyone