Bitcoin Forum
October 22, 2017, 06:50:58 AM *
News: Latest stable version of Bitcoin Core: 0.15.0.1  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 [11] 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 »
  Print  
Author Topic: [BTB] The BitBar Information Thread  (Read 148000 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
A L I E N
Hero Member
*****
Offline Offline

Activity: 756

Better now than never.


View Profile
September 28, 2013, 10:26:08 PM
 #201

All problems: checkpoint to old and fork, are due to dynamic checkpointing off - I stopped  vps for BTB zero-client and redirected dns-lookup to some pool.

I synced my home client to longest chain and i suggest doing the same :
connect=btb.ltcoin.net, or at least addnode=btb.ltcoin.net

DNS first node search has been redirected to some pool ,soon dns will be updated to btb.ltcoin.net as it proves to be the fastest one.

I run dyn-checkpointing on my private PC now, until I get my hands on some VPS.


WRONG!!!!!
btb.ltcoin.net is NOT on the correct chain!  All the exchanges and other pools are on the same as the block explorer.

The following are all on the same as the block explorer and NOT diggers chain:
Here: http://btb.cryptocoinexplorer.com/chain/BitBar
Here: http://btb.pnwminer.com/index.php?page=statistics
Here: http://www.coinchoose.com/
Here: http://www.coinwarz.com/cryptocurrency
Here: https://www.cryptsy.com/markets/view/23
Here: https://bter.com/trade/btb_btc

Here are some nodes for the correct chain:
Code:
addnode=23.92.25.46
addnode=37.229.117.57
addnode=84.200.4.218
addnode=88.198.184.231
addnode=176.28.55.230
addnode=85.228.195.71
addnode=204.10.105.113
addnode=82.137.114.220

Here is a longer list of peers:

[
{
"addr" : "24.11.75.124:65012",
"services" : "00000001",
"lastsend" : 1380381072,
"lastrecv" : 1380381072,
"conntime" : 1380332832,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 25838,
"banscore" : 0
},
{
"addr" : "196.221.149.93:22607",
"services" : "00000001",
"lastsend" : 1380381072,
"lastrecv" : 1380381073,
"conntime" : 1380338647,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 26063,
"banscore" : 0
},
{
"addr" : "96.127.225.253:60617",
"services" : "00000001",
"lastsend" : 1380381072,
"lastrecv" : 1380381072,
"conntime" : 1380352927,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 26085,
"banscore" : 0
},
{
"addr" : "85.228.195.71:48949",
"services" : "00000001",
"lastsend" : 1380379977,
"lastrecv" : 1380381072,
"conntime" : 1380363208,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 26094,
"banscore" : 0
},
{
"addr" : "24.210.41.92:8777",
"services" : "00000001",
"lastsend" : 1380381073,
"lastrecv" : 1380381073,
"conntime" : 1380371932,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 26097,
"banscore" : 0
},
{
"addr" : "37.229.117.57:8777",
"services" : "00000001",
"lastsend" : 1380381072,
"lastrecv" : 1380381072,
"conntime" : 1380372102,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 26100,
"banscore" : 0
},
{
"addr" : "88.198.184.231:8777",
"services" : "00000001",
"lastsend" : 1380381072,
"lastrecv" : 1380379976,
"conntime" : 1380372103,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 26100,
"banscore" : 0
},
{
"addr" : "74.90.3.175:61050",
"services" : "00000001",
"lastsend" : 1380381072,
"lastrecv" : 1380381072,
"conntime" : 1380372188,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 26100,
"banscore" : 0
},
{
"addr" : "23.92.25.46:8777",
"services" : "00000001",
"lastsend" : 1380381072,
"lastrecv" : 1380381072,
"conntime" : 1380372231,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 26100,
"banscore" : 0
},
{
"addr" : "84.200.4.218:8777",
"services" : "00000001",
"lastsend" : 1380381073,
"lastrecv" : 1380381073,
"conntime" : 1380372232,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 26100,
"banscore" : 0
},
{
"addr" : "176.28.55.230:8777",
"services" : "00000001",
"lastsend" : 1380380515,
"lastrecv" : 1380381071,
"conntime" : 1380372236,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 26100,
"banscore" : 0
},
{
"addr" : "184.73.75.111:55368",
"services" : "00000001",
"lastsend" : 1380380420,
"lastrecv" : 1380381071,
"conntime" : 1380372369,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 26100,
"banscore" : 0
},
{
"addr" : "204.10.105.113:40491",
"services" : "00000001",
"lastsend" : 1380381072,
"lastrecv" : 1380381072,
"conntime" : 1380372561,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 26100,
"banscore" : 0
},
{
"addr" : "190.19.238.43:34539",
"services" : "00000001",
"lastsend" : 1380381072,
"lastrecv" : 1380381072,
"conntime" : 1380373657,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 26102,
"banscore" : 0
},
{
"addr" : "83.85.50.164:53039",
"services" : "00000001",
"lastsend" : 1380381072,
"lastrecv" : 1380380427,
"conntime" : 1380373932,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 26102,
"banscore" : 0
},
{
"addr" : "74.208.170.71:53276",
"services" : "00000001",
"lastsend" : 1380381072,
"lastrecv" : 1380381072,
"conntime" : 1380374860,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 26106,
"banscore" : 0
},
{
"addr" : "94.192.246.249:54171",
"services" : "00000001",
"lastsend" : 1380381072,
"lastrecv" : 1380381072,
"conntime" : 1380374964,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 26107,
"banscore" : 0
},
{
"addr" : "97.89.210.5:49203",
"services" : "00000001",
"lastsend" : 1380381072,
"lastrecv" : 1380379977,
"conntime" : 1380375894,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 26113,
"banscore" : 0
},
{
"addr" : "109.190.159.190:17840",
"services" : "00000001",
"lastsend" : 1380381072,
"lastrecv" : 1380379977,
"conntime" : 1380377073,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 26115,
"banscore" : 0
},
{
"addr" : "82.181.61.90:8777",
"services" : "00000001",
"lastsend" : 1380380424,
"lastrecv" : 1380381071,
"conntime" : 1380377391,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 26116,
"banscore" : 0
},
{
"addr" : "66.97.52.150:45328",
"services" : "00000001",
"lastsend" : 1380380937,
"lastrecv" : 1380381071,
"conntime" : 1380380936,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 26120,
"banscore" : 0
},
{
"addr" : "91.197.6.153:11002",
"services" : "00000001",
"lastsend" : 1380381175,
"lastrecv" : 1380381175,
"conntime" : 1380381174,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 26121,
"banscore" : 0
},
{
"addr" : "78.155.216.107:59116",
"services" : "00000001",
"lastsend" : 1380381245,
"lastrecv" : 1380381245,
"conntime" : 1380381244,
"version" : 60005,
"subver" : "/Satoshi:0.7.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 13255,
"banscore" : 0
}
]
Be very wary of relying on JavaScript for security on sites such as blockchain.info and brainwallet.org. The site can change the JavaScript at any time unless you take unusual precautions, and browsers are not generally known for their airtight security.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
rbdrbd
Sr. Member
****
Offline Offline

Activity: 350



View Profile
September 29, 2013, 09:42:09 PM
 #202

Hey guys, I've thrown the OP source up at pastebin: http://pastebin.com/6e8kdGNt

Unfortunately, I don't have the time to read through all the posts and make any relevant updates. If anyone wants to do this and give me the updated post (via pastebin, etc) then I can update the OP from that, just send me a PM when you do this to make sure I get it.
lukemarshall
Full Member
***
Offline Offline

Activity: 183



View Profile
September 29, 2013, 10:05:56 PM
 #203

Anyone else have the bitbar wallet lose connections and seem to always be behind:

Catching up...

"last block received 77 days ago "

https://bitcointalk.org/index.php?topic=196125.msg2662000#msg2662000

Try using this node... the one from CCE

tried this but can't even get the thing to sync or find any connections....

The new node for the CCE is this:

Code:
connect=84.200.4.218

Make sure to change 'connect' back to 'addnode' once you are synced
Also add these nodes:

Code:
addnode=23.92.25.46
addnode=37.229.117.57
addnode=84.200.4.218
addnode=88.198.184.231
addnode=176.28.55.230
addnode=85.228.195.71
addnode=204.10.105.113
addnode=82.137.114.220



Here are some nodes for the correct chain:

WRONG!!!!!
btb.ltcoin.net is NOT on the correct chain!  All the exchanges and other pools are on the same as the block explorer.

The following are all on the same as the block explorer and NOT diggers chain:
Here: http://btb.cryptocoinexplorer.com/chain/BitBar
Here: http://btb.pnwminer.com/index.php?page=statistics
Here: http://www.coinchoose.com/
Here: http://www.coinwarz.com/cryptocurrency
Here: https://www.cryptsy.com/markets/view/23
Here: https://bter.com/trade/btb_btc


Thank you Mr. A L I E N, for the good information.


Its all about what the people want...
lukemarshall
Full Member
***
Offline Offline

Activity: 183



View Profile
September 29, 2013, 10:37:19 PM
 #204

I have send an email to Digger, https://bitcointalk.org/index.php?action=profile;u=32194

The owner opperator of the pool, ( btb.ltcoin ) and have yet to get a responce.

He need to know what is going on with his forked pool, and take the appropriate measures.


Its all about what the people want...
dreamwatcher
Legendary
*
Offline Offline

Activity: 1064


View Profile WWW
September 29, 2013, 10:43:23 PM
 #205

Quick Note:

I need to get people used to using the official cryptocoinexplorer.com address without the suffix. When CCE3 goes live, the ABE "/chain/BitBar" suffix will be invalid.

Please use:

btb.cryptocoinexplorer.com

or

www.btb.cryptocoinexplorer.com

darksoft
Sr. Member
****
Offline Offline

Activity: 275


View Profile
September 30, 2013, 12:22:55 AM
 #206

I have send an email to Digger, https://bitcointalk.org/index.php?action=profile;u=32194

The owner opperator of the pool, ( btb.ltcoin ) and have yet to get a responce.

He need to know what is going on with his forked pool, and take the appropriate measures.



I wouldn't hold my breath... just saying...
A L I E N
Hero Member
*****
Offline Offline

Activity: 756

Better now than never.


View Profile
September 30, 2013, 01:08:29 AM
 #207

I have send an email to Digger, https://bitcointalk.org/index.php?action=profile;u=32194

The owner opperator of the pool, ( btb.ltcoin ) and have yet to get a responce.

He need to know what is going on with his forked pool, and take the appropriate measures.



I wouldn't hold my breath... just saying...

Yes, about half a dozen of his pools are forked and he hasn't taken any action thus far.
BitBardev
Newbie
*
Offline Offline

Activity: 27


View Profile
September 30, 2013, 03:57:46 AM
 #208

Looks like Alien is right, the longest chain was not the one than main exchanges was on, I resynced checkpointing client to CCE and everybody should see checkpoint to old warning disappear soon.

connect=btb.cryptocoinexplorer.com
A L I E N
Hero Member
*****
Offline Offline

Activity: 756

Better now than never.


View Profile
September 30, 2013, 05:35:39 PM
 #209

Looks like Alien is right, the longest chain was not the one than main exchanges was on, I resynced checkpointing client to CCE and everybody should see checkpoint to old warning disappear soon.

connect=btb.cryptocoinexplorer.com

This is great news, the checkpoint warning is gone and I have over 35 connections on the client!
I can confirm that transactions in and out of Cryptsy are working great.
rbdrbd
Sr. Member
****
Offline Offline

Activity: 350



View Profile
October 08, 2013, 10:01:37 AM
 #210

Thanks to CaptainAK for submitting an update to the OP!
Garz
Jr. Member
*
Offline Offline

Activity: 32


View Profile
October 17, 2013, 10:45:13 PM
 #211

I have send an email to Digger, https://bitcointalk.org/index.php?action=profile;u=32194

The owner opperator of the pool, ( btb.ltcoin ) and have yet to get a responce.

He need to know what is going on with his forked pool, and take the appropriate measures.


Hi - I sent an email too only to get a reply of 'check the coins by selling/trading them' to see if they are mined. Terrible I say, very annoyed about no communication and to let people still mine something on the wrong fork.  Angry
miffman
Legendary
*
Offline Offline

Activity: 1624


PGP ID: 78B7B84D


View Profile
October 29, 2013, 05:34:55 PM
 #212

Bitbar has officially died. The market cap is now ~600$. It can literally all be bought with about 3 BTC














 

 

█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
BitBlender 

 













 















 












 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
A L I E N
Hero Member
*****
Offline Offline

Activity: 756

Better now than never.


View Profile
October 29, 2013, 06:16:23 PM
 #213

Bitbar has officially died. The market cap is now ~600$. It can literally all be bought with about 3 BTC

Actually the market cap is between 7-24 BTC depending if you are basing your calculation on the Bid or Ask price.  Good thing you have no authority to officially declare a coins death lol.  A coin only dies when transactions cannot be completed. This will not happen with BTB since it could continue POS blocks even if there was no POW hash.  There are still plenty of POW miners hashing on BTB though.  A savvy trader could easily double up trading BTB at these levels.
ANiceJewishBoy
Jr. Member
*
Offline Offline

Activity: 42

Oy Vey!!


View Profile
October 29, 2013, 10:34:59 PM
 #214

I have a feeling Bitbar will survive based on it's status as the "consolidated Bitcoin" but I thought I would share this with you guys:
https://bitcointalk.org/index.php?topic=321086

and subbed

My Negative Rating is For Bringing a Dead Thread Back to Life, Just BTW. Click The Link To See For Yourself.
https://bitcointalk.org/index.php?action=trust;u=155011
plutuswd
Jr. Member
*
Offline Offline

Activity: 30


View Profile WWW
November 11, 2013, 03:45:50 AM
 #215

I have something that will determine whether the coin has any chance of proceeding.

I have some btb. I mined it many moons ago. I was going through old wallets and found it. I tried to send the coin out and it has remained stalled without any confirmations. The block chain cannot be updated because the check point is too old. I downloaded the latest client and that did not resolve it. I searched my computer and cound not find a .conf to manually update the server used to rebuild the block chain.

Is there a solution for this?
CaptainAK
Full Member
***
Offline Offline

Activity: 142


View Profile WWW
November 11, 2013, 06:05:54 PM
 #216

Try deleting your blockchain (blk*.dat and the database/ folder) and peers.dat, but NOT your wallet.dat (that would be bad). Then use a conf file similar to this:

server=1
gen=0
daemon=1
rpcuser=yourrpcusername
rpcpassword=yourpassword
rpcport=8100
port=8099
rpcallowip=127.0.0.1
addnode=btb.cryptocoinexplorer.com

Connecting directly to the block explorer should get you up to the current block. From there you should start getting additional peers connecting.

I repeat.. you can delete everything from your profile folder, but DO NOT delete your wallet.dat. Before you start the client you should only have wallet.dat and bitbar.conf in the folder
A L I E N
Hero Member
*****
Offline Offline

Activity: 756

Better now than never.


View Profile
November 11, 2013, 06:46:56 PM
 #217

Try deleting your blockchain (blk*.dat and the database/ folder) and peers.dat, but NOT your wallet.dat (that would be bad). Then use a conf file similar to this:

server=1
gen=0
daemon=1
rpcuser=yourrpcusername
rpcpassword=yourpassword
rpcport=8100
port=8099
rpcallowip=127.0.0.1
addnode=btb.cryptocoinexplorer.com

Connecting directly to the block explorer should get you up to the current block. From there you should start getting additional peers connecting.

I repeat.. you can delete everything from your profile folder, but DO NOT delete your wallet.dat. Before you start the client you should only have wallet.dat and bitbar.conf in the folder


Yes deleting the block chain and re-downloading should get you back up to speed. I have the following ports instead of what was posted above:
Code:
rpcport=9344
port=8777
lukemarshall
Full Member
***
Offline Offline

Activity: 183



View Profile
November 23, 2013, 04:39:35 PM
 #218

Quick Note:

I need to get people used to using the official cryptocoinexplorer.com address without the suffix. When CCE3 goes live, the ABE "/chain/BitBar" suffix will be invalid.

Please use:

btb.cryptocoinexplorer.com

or

www.btb.cryptocoinexplorer.com



Block Explorer Stuck on block #34012 whilst client is @ 34238 and counting.

Its all about what the people want...
dreamwatcher
Legendary
*
Offline Offline

Activity: 1064


View Profile WWW
November 23, 2013, 06:31:14 PM
 #219

Quick Note:

I need to get people used to using the official cryptocoinexplorer.com address without the suffix. When CCE3 goes live, the ABE "/chain/BitBar" suffix will be invalid.

Please use:

btb.cryptocoinexplorer.com

or

www.btb.cryptocoinexplorer.com



Block Explorer Stuck on block #34012 whilst client is @ 34238 and counting.


Coin daemon crash. The explorer is now back in sync.
lukemarshall
Full Member
***
Offline Offline

Activity: 183



View Profile
November 23, 2013, 08:47:30 PM
 #220

Thank you for addressing this so quickly Dreamwatcher, the community thanks you for your services.

Its all about what the people want...
Pages: « 1 2 3 4 5 6 7 8 9 10 [11] 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!