Oh ya, stay away from Bter!
Are they on the wrong chain?
I submitted 3 tickets, and two emails - none were answered - I haven't heard a thing from them.
Topic: [BTB] The BitBar Information Thread - page 31. (Read 180446 times)
Are they on the wrong chain?
I submitted 3 tickets, and two emails - none were answered - I haven't heard a thing from them.
I have pics of both of those Bitbar transactions with 10,000 confirmations on each. Doesn't that mean they were good?
They are "good" on the forked chain only.They never existed on the good chain. - kind of like my 325.1 BTB on Cryptsy.
Oh ya, stay away from Bter!
Are they on the wrong chain?
Oh ya, stay away from Bter!
Could someone possibly help me with something. I've been a big buyer of altcoins since 2011 but am not tech savvy one bit. I sent two transactions of Bitbar to my wallet on 10/03/15 and 10/10/15 neither of which registered on the blockchain but did show up in my wallet until I resynced it and now they are missing. One was for 52.123839 and the other 67.715018 it shows 119.883857 as unconfirmed. My address is B8Z8UBnZofYjMuxpMh4mFMTANsFYFpGxGD I have pictures to show all of this. Thanks for any help you can offer.
My guess is the bitbar transactions were done on a forked chain. Both you and the sender where on the same fork, which is why the transactions were confirmed in your wallet.When you re-synced your wallet, it's like the transactions never happened.
If the sender was to re-sync their wallet (and repairwallet) the missing 119.88 BTB would (in theory) re-appear, and they could make a new transfer.
"in theory" was stated because it depends where the original Bitbars came from.
If the Bitbars were mined/minted from a chain fork, (like a pool was on a wrong fork), they only exist on that fork.
This is where it gets REAL confusing:
Cryptsy and several pools where on a fork for about a month. Before the fork, they had x amount of BTB (call them good)
During the fork, pools and miners that were on the same fork as Cryptsy deposited y amount of BTB (call them bad).
So for a month or so, the BTB payouts were added to the forked chain.
People on the fork got bitbars in their wallet.
People not on the fork got nothing.
(people not on the fork - who send btb to cryptsy - lost their bitbars (probably). the btb went out on the good chain - but never showed up at cryptsy)
It could -technically, be straightened out. But you would have to get everybody who received bitbars to give them back. you would have to get 'money' back from the persons that deposited 'bad' bitbars.
In your case, and not knowing where your BTB were sourced from, I would contact the source, and ask them to check their wallet block count.
If it doesn't match our official block explorer http://btb.cryptocoinexplorer.com/, they need to fix it.
Then maybe, you might have a chance of regaining your lost Bitbars.
In the end, you might end up taking it in the end.
I've got a couple hundred Bitbars that got cast away, and is now floating in the ether, never to be seen again.
(maybe...I have dreams...)
Is there any chance there is going to be a Bitbar coin swap? I also have 734 Bitbar stuck on cryptsy. I was paying $200 each for Bitbar in Jan. 2014 that is true. It was on EBay for $200 each at that time.
WoW,I have only ever owned 12 bitbar so I cant imagine your pain in loosing so many,sad to say I am going to guess the coins on cryptsy are no good as the chain has forked several times since cryptsy BTB wallet last worked.
Ok thx. I'm going to try and figure this out. I don't know how to add nodes but will try. Those 120 Btb were confirmed in my wallet but it was stuck at dec 08 so I resynced it and now they won't confirm. I had transaction id for both before I resynced.
Sent you a pm with easy instruction M8, and you are most welcome
The wallet I have on my computer works fine and shows all coins even new ones purchased the last few days from Cryptopia. Does that mean I'm on the correct chain?
Yes,the correct chain is the one Cryptopia is on,to make sure you stay on it, add the nodes they are in sync with to a conf file and place it in your AppData/Roaming/BitBar folder.
A couple of post back I put info for solo mining and you can find a copy of the .conf file you need there.
This is the link to that post https://bitcointalksearch.org/topic/m.13634188
Could someone possibly help me with something. I've been a big buyer of altcoins since 2011 but am not tech savvy one bit. I sent two transactions of Bitbar to my wallet on 10/03/15 and 10/10/15 neither of which registered on the blockchain but did show up in my wallet until I resynced it and now they are missing. One was for 52.123839 and the other 67.715018 it shows 119.883857 as unconfirmed. My address is B8Z8UBnZofYjMuxpMh4mFMTANsFYFpGxGD I have pictures to show all of this. Thanks for any help you can offer.
It is most likely that those coins where from the incorrect block chain and are invalid coins,if you have resynced to the proper chain now and they are gone then that is probably the case and I am sorry to say they where never real coins and as such you never had them and wont get them back.
This is the problem that occurs when a blockchain forks.
This is not the only possible reason though and there may be hope for them but I wouldnt count on it,sorry and good luck M8.
Cool - I'm in sync with CCE
Note to self:
I think it's time to add a block explorer to the wallet.
I think it's time to add a block explorer to the wallet.
Good and bad news 
Good news - I finished coding the markets module of CCE for the Cryptopia API. The BTB explorer on CCE now has Cryptopia in the market header.
Bad news:
I believe we are looking at a hard fork due to a client update.
After a complete fresh chain download with addnodes that were given to me on the longer chain, the daemon on CCE ended up on the same block (150545).
It appears the clients responding with the subversion "/Bitbar:0.7.4/" are on the chain that is about block 150882.
The clients (including CCE) that are on subversion "/Satoshi:0.7.4/" are on the chain that is on block 150545.
So now the question is, which client version is going to become the official client?
The newer version is the Bitbar version.Good news - I finished coding the markets module of CCE for the Cryptopia API. The BTB explorer on CCE now has Cryptopia in the market header.
Bad news:
I believe we are looking at a hard fork due to a client update.
After a complete fresh chain download with addnodes that were given to me on the longer chain, the daemon on CCE ended up on the same block (150545).
It appears the clients responding with the subversion "/Bitbar:0.7.4/" are on the chain that is about block 150882.
The clients (including CCE) that are on subversion "/Satoshi:0.7.4/" are on the chain that is on block 150545.
So now the question is, which client version is going to become the official client?
It has been updated with btb.altcointech.net as the seednode, where as the older versions have bitbar.biz as the seed node.
last checkpoint is ( 141550, uint256("0x0000000014b26064d91f70baed8561e6642d71fcbac3b38bf24f6fe262212792"))
Good and bad news
Good news - I finished coding the markets module of CCE for the Cryptopia API. The BTB explorer on CCE now has Cryptopia in the market header.
Bad news:
I believe we are looking at a hard fork due to a client update.
After a complete fresh chain download with addnodes that were given to me on the longer chain, the daemon on CCE ended up on the same block (150545).
CCE peer list:
It appears the clients responding with the subversion "/Bitbar:0.7.4/" are on the chain that is about block 150882.
The clients (including CCE) that are on subversion "/Satoshi:0.7.4/" are on the chain that is on block 150545.
So now the question is, which client version is going to become the official client?
Good news - I finished coding the markets module of CCE for the Cryptopia API. The BTB explorer on CCE now has Cryptopia in the market header.
Bad news:
I believe we are looking at a hard fork due to a client update.
After a complete fresh chain download with addnodes that were given to me on the longer chain, the daemon on CCE ended up on the same block (150545).
CCE peer list:
Code:
{
"addr" : "172.127.121.113:59629",
"services" : "00000001",
"lastsend" : 1453576812,
"lastrecv" : 1453576812,
"conntime" : 1453573183,
"version" : 60006,
"subver" : "/Bitbar:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 150882,
"banscore" : 0
},
{
"addr" : "173.65.129.85:8777",
"services" : "00000001",
"lastsend" : 1453576812,
"lastrecv" : 1453576812,
"conntime" : 1453573189,
"version" : 60006,
"subver" : "/Bitbar:0.7.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 150882,
"banscore" : 0
},
{
"addr" : "109.228.4.100:8777",
"services" : "00000001",
"lastsend" : 1453576812,
"lastrecv" : 1453576812,
"conntime" : 1453573191,
"version" : 60006,
"subver" : "/Bitbar:0.7.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 150882,
"banscore" : 0
},
{
"addr" : "108.61.10.90:8777",
"services" : "00000001",
"lastsend" : 1453576812,
"lastrecv" : 1453576813,
"conntime" : 1453573191,
"version" : 60006,
"subver" : "/Bitbar:0.7.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 150882,
"banscore" : 0
},
{
"addr" : "89.27.70.48:8777",
"services" : "00000001",
"lastsend" : 1453577099,
"lastrecv" : 1453576812,
"conntime" : 1453573192,
"version" : 60006,
"subver" : "/Bitbar:0.7.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 150882,
"banscore" : 0
},
{
"addr" : "94.23.54.195:49148",
"services" : "00000001",
"lastsend" : 1453576812,
"lastrecv" : 1453576812,
"conntime" : 1453573226,
"version" : 60006,
"subver" : "/Bitbar:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 150882,
"banscore" : 0
},
{
"addr" : "144.76.91.109:8777",
"services" : "00000001",
"lastsend" : 1453576812,
"lastrecv" : 1453576812,
"conntime" : 1453573243,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 150545,
"banscore" : 0
},
{
"addr" : "198.0.43.101:58716",
"services" : "00000001",
"lastsend" : 1453577101,
"lastrecv" : 1453576812,
"conntime" : 1453573245,
"version" : 60006,
"subver" : "/Satoshi:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 150545,
"banscore" : 0
},
{
"addr" : "148.251.19.213:62161",
"services" : "00000001",
"lastsend" : 1453576812,
"lastrecv" : 1453576812,
"conntime" : 1453573272,
"version" : 60006,
"subver" : "/Bitbar:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 150882,
"banscore" : 0
},
{
"addr" : "81.230.143.200:46978",
"services" : "00000001",
"lastsend" : 1453576813,
"lastrecv" : 1453576812,
"conntime" : 1453573291,
"version" : 60006,
"subver" : "/Bitbar:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 150882,
"banscore" : 0
},
{
"addr" : "91.121.120.218:54756",
"services" : "00000001",
"lastsend" : 1453576812,
"lastrecv" : 1453576812,
"conntime" : 1453573291,
"version" : 60006,
"subver" : "/Bitbar:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 150882,
"banscore" : 0
},
{
"addr" : "159.205.246.59:58248",
"services" : "00000001",
"lastsend" : 1453576812,
"lastrecv" : 1453577091,
"conntime" : 1453573692,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 150545,
"banscore" : 0
},
{
"addr" : "87.182.80.119:43986",
"services" : "00000001",
"lastsend" : 1453576783,
"lastrecv" : 1453577099,
"conntime" : 1453573970,
"version" : 60006,
"subver" : "/Satoshi:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 150239,
"banscore" : 0
},
{
"addr" : "68.191.93.33:49519",
"services" : "00000001",
"lastsend" : 1453576812,
"lastrecv" : 1453576812,
"conntime" : 1453575612,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 150545,
"banscore" : 0
}
]
It appears the clients responding with the subversion "/Bitbar:0.7.4/" are on the chain that is about block 150882.
The clients (including CCE) that are on subversion "/Satoshi:0.7.4/" are on the chain that is on block 150545.
So now the question is, which client version is going to become the official client?
The community should go with the fork that BTER and Cryptopia hopefully are both on. Default to the exchanges, and always addnode the exchanges in your wallet.
agree
and get a new thread going so you can up date OP
anyone sent from BTER to crytopia? just to test if they are on the same chain;)
luke says above no go, but last i recall BTER wallet looked open to me
The OP was updated last month and most everything is current with he exception of cryptsy, and I haven't given up hope on them yet.
I do need to get Cryptopia added though, thanks for the reminder.
The community should go with the fork that BTER and Cryptopia hopefully are both on. Default to the exchanges, and always addnode the exchanges in your wallet.
agree
and get a new thread going so you can up date OP
anyone sent from BTER to crytopia? just to test if they are on the same chain;)
luke says above no go, but last i recall BTER wallet looked open to me
maybe we can get Bitbar listed on https://safecex.com/coin/add?q=BTB ??
We only have two votes, mine and a guy from DMD that I traded votes with.
We only have two votes, mine and a guy from DMD that I traded votes with.
The community should go with the fork that BTER and Cryptopia hopefully are both on. Default to the exchanges, and always addnode the exchanges in your wallet.
I don't think BTER even has their Bitbar clients running. I attempted a test withdrawal nearly a month ago, submitted a support ticket and got a simple "thanks"
The two big hashing pools and Cryptopia seem to be running the show right now
for now, I think bter bites.
If you recall BTER was hacked for quite a large amount a year or ago. It is very well possible they are operating in the same manner as Cryptsy had.
Sound s like everybody agrees that CCE should re-sync to the chain that Cryptopia is on.
I'll send him a PM and let him know.
I'll send him a PM and let him know.
The community should go with the fork that BTER and Cryptopia hopefully are both on. Default to the exchanges, and always addnode the exchanges in your wallet.
I don't think BTER even has their Bitbar clients running. I attempted a test withdrawal nearly a month ago, submitted a support ticket and got a simple "thanks"
The two big hashing pools and Cryptopia seem to be running the show right now
for now, I think bter bites.
Jump to: