Windows and Mac wallets have been compiled by TronREX. A huge thanks for this service to our community.
Version 1.1.0.1 - Maintenance release with checkpoints
rabbitcoin-qt-win.zip
https://mega.nz/#!7Il3HbyY!UiDYsMmExUhEhAeDWC1ymMneEMi5TAjJprhsZzUeEWU
rabbitcoin-qt-mac.zip
https://mega.nz/#!TctCjQLb!cpk_Cr1iE5GCghnFZEbVn3BtfMAW7VdyYQXNj6jyJnY
I've also place these on BitBucket repo.
https://bitbucket.org/Hobbyistpool/rabbitcoin/downloads/rabbitcoin-qt-win.zip
https://bitbucket.org/Hobbyistpool/rabbitcoin/downloads/rabbitcoin-qt-mac.zip
Topic: [ANN]🐰 RabbitCoin [RBBT] [Scrypt KGW] - page 18. (Read 182371 times)
cryptsy wallet off ((( now exnage ?
Updated source available at https://bitbucket.org/Hobbyistpool/rabbitcoin
Added Checkpoints, Updated client name, Updated CLIENT_VERSION_MINOR.
Differences can be found here https://bitbucket.org/Hobbyistpool/rabbitcoin/commits/839e7b5538821553dbc7b627ffd078ccbb647d5f?at=master
Hope to have Windows/Mac wallets soon.
Added Checkpoints, Updated client name, Updated CLIENT_VERSION_MINOR.
Differences can be found here https://bitbucket.org/Hobbyistpool/rabbitcoin/commits/839e7b5538821553dbc7b627ffd078ccbb647d5f?at=master
Hope to have Windows/Mac wallets soon.
widows client??
Same fork or a new coin?
Added checkpoints to stop this forking and get the chain accepted at exchanges.
Changed the client name from 'Satoshi' to 'RabbitCoin' to help identify other chains connecting to ours.
Changed CLIENT_VERSION_MINOR from 0 to 1 to help identify this version.
Added a ADDNODE to the release/rabbitcoin.conf file (Don't know if this is even used)
Same RabbitCoin as belore ... Just updated / minor revisions.
looks like you've already had experience in developing wallets )))
Great news!
Looking forward to the new wallet. Let's end this fork already and get back to normal.
Looking forward to the new wallet. Let's end this fork already and get back to normal.
Same fork or a new coin?
Added checkpoints to stop this forking and get the chain accepted at exchanges.
Changed the client name from 'Satoshi' to 'RabbitCoin' to help identify other chains connecting to ours.
Changed CLIENT_VERSION_MINOR from 0 to 1 to help identify this version.
Added a ADDNODE to the release/rabbitcoin.conf file (Don't know if this is even used)
Same RabbitCoin as belore ... Just updated / minor revisions.
Updated source available at https://bitbucket.org/Hobbyistpool/rabbitcoin
Added Checkpoints, Updated client name, Updated CLIENT_VERSION_MINOR.
Differences can be found here https://bitbucket.org/Hobbyistpool/rabbitcoin/commits/839e7b5538821553dbc7b627ffd078ccbb647d5f?at=master
Hope to have Windows/Mac wallets soon.
Added Checkpoints, Updated client name, Updated CLIENT_VERSION_MINOR.
Differences can be found here https://bitbucket.org/Hobbyistpool/rabbitcoin/commits/839e7b5538821553dbc7b627ffd078ccbb647d5f?at=master
Hope to have Windows/Mac wallets soon.
Same fork or a new coin?
Updated source available at https://bitbucket.org/Hobbyistpool/rabbitcoin
Added Checkpoints, Updated client name, Updated CLIENT_VERSION_MINOR.
Differences can be found here https://bitbucket.org/Hobbyistpool/rabbitcoin/commits/839e7b5538821553dbc7b627ffd078ccbb647d5f?at=master
Hope to have Windows/Mac wallets soon.
Added Checkpoints, Updated client name, Updated CLIENT_VERSION_MINOR.
Differences can be found here https://bitbucket.org/Hobbyistpool/rabbitcoin/commits/839e7b5538821553dbc7b627ffd078ccbb647d5f?at=master
Hope to have Windows/Mac wallets soon.
Now Cryptsy should fix the chain nodes.
My wallet is synced and on the 1st chain (the official chain if we are voting)
https://hobbyistpool.ddns.net/rabbit/
new, correct link
I found when the old start to come on the rest of the primitive list
new, correct link
I found when the old start to come on the rest of the primitive list
Pool Available and on the 1st chain.
well, let's say that all went back to the new blockchain.
a month later again this error and the pool will go to the other - the third chain?
if you want to cryptsy resumed replenishment rbbt-coins she needed a stable pool and not one that jumps every month on different chains at the first error
a month later again this error and the pool will go to the other - the third chain?
if you want to cryptsy resumed replenishment rbbt-coins she needed a stable pool and not one that jumps every month on different chains at the first error
That is the risk we all take without a DEV and a properly checkpointed client. I'm in the process of switching back to the old chain.
Appears Doge had a similar problem https://github.com/dogecoin/dogecoin/issues/250
Is there a block explorer for the old chain? it appears https://prohashing.com/explorer/Rabbitcoin is on the new chain.
The community needs to agree on what is the official chain.
1st chain
(1400000, uint256("0xe7330bf983cebb0f921079f774e22af2032b367162427bda37c9dba9acfa41ce"))
(1420000, uint256("0xadea4fc3a47702cc7a109047ca76054875e54d06b5e5876094d9e0ead73c5fac"))
2nd chain
(1400000, uint256("0x33b81cf2473bfb10ee6b0defb3bb68971dafef7249cb97985036fcfff6136074"))
(1420000, uint256("0x5f1dac3cbbc606053cf44d7cf762d26c1c0cbfddb7b337ba70bc1e5ea8ec0bb6"))
have synced with 2nd chain
Code:
addnode=76.95.178.229:17040
addnode=99.63.193.158:17020
addnode=99.63.193.158:17020
The above nodes are back online and accepting connections.
The newyorkcoin chain is just that, NewYorkCoin. Both coins use C0C0C0 as their peermagic. The clients will connect to each other.
If we ever hard-fork, get this changed... We also share port 17020.
If we ever hard-fork, get this changed... We also share port 17020.
another blockchain
"startingheight" : 1529646
"subver" : "/NewYorkCoin:1.1.0/",
"subver" : "/Satoshi:1.0.1.1/",
getpeerinfo (8 connections)
"startingheight" : 1529646
"subver" : "/NewYorkCoin:1.1.0/",
"subver" : "/Satoshi:1.0.1.1/",
getpeerinfo (8 connections)
Code:

[
{
"addr" : "117.6.130.233:17020",
"services" : "00000001",
"lastsend" : 1441169111,
"lastrecv" : 1441169266,
"conntime" : 1441168722,
"version" : 60003,
"subver" : "/Satoshi:1.0.1.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1529646,
"banscore" : 0
},
{
"addr" : "67.80.46.211:22556",
"services" : "00000003",
"lastsend" : 1441169217,
"lastrecv" : 1441168730,
"conntime" : 1441168728,
"version" : 70001,
"subver" : "/Shibetoshi:1.5.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 145119,
"banscore" : 0
},
{
"addr" : "37.233.101.127:17020",
"services" : "00000003",
"lastsend" : 1441169262,
"lastrecv" : 1441169263,
"conntime" : 1441168729,
"version" : 70002,
"subver" : "/NewYorkCoin:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1529646,
"banscore" : 0
},
{
"addr" : "96.255.60.31:22556",
"services" : "00000001",
"lastsend" : 1441169251,
"lastrecv" : 1441169159,
"conntime" : 1441168730,
"version" : 60003,
"subver" : "/Satoshi:0.6.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 104738,
"banscore" : 0
},
{
"addr" : "98.115.147.74:17020",
"services" : "00000001",
"lastsend" : 1441169275,
"lastrecv" : 1441169277,
"conntime" : 1441168731,
"version" : 60003,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1451496,
"banscore" : 0
},
{
"addr" : "115.236.88.86:17020",
"services" : "00000001",
"lastsend" : 1441169275,
"lastrecv" : 1441169275,
"conntime" : 1441168733,
"version" : 60003,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1451496,
"banscore" : 0
},
{
"addr" : "188.165.2.147:17020",
"services" : "00000001",
"lastsend" : 1441169118,
"lastrecv" : 1441169271,
"conntime" : 1441168810,
"version" : 60003,
"subver" : "/Satoshi:1.0.1.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1529646,
"banscore" : 0
},
{
"addr" : "203.20.114.252:17020",
"services" : "00000001",
"lastsend" : 1441169117,
"lastrecv" : 1441169264,
"conntime" : 1441168876,
"version" : 60003,
"subver" : "/Satoshi:1.0.1.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1529646,
"banscore" : 0
}
]
[
{
"addr" : "117.6.130.233:17020",
"services" : "00000001",
"lastsend" : 1441169111,
"lastrecv" : 1441169266,
"conntime" : 1441168722,
"version" : 60003,
"subver" : "/Satoshi:1.0.1.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1529646,
"banscore" : 0
},
{
"addr" : "67.80.46.211:22556",
"services" : "00000003",
"lastsend" : 1441169217,
"lastrecv" : 1441168730,
"conntime" : 1441168728,
"version" : 70001,
"subver" : "/Shibetoshi:1.5.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 145119,
"banscore" : 0
},
{
"addr" : "37.233.101.127:17020",
"services" : "00000003",
"lastsend" : 1441169262,
"lastrecv" : 1441169263,
"conntime" : 1441168729,
"version" : 70002,
"subver" : "/NewYorkCoin:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1529646,
"banscore" : 0
},
{
"addr" : "96.255.60.31:22556",
"services" : "00000001",
"lastsend" : 1441169251,
"lastrecv" : 1441169159,
"conntime" : 1441168730,
"version" : 60003,
"subver" : "/Satoshi:0.6.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 104738,
"banscore" : 0
},
{
"addr" : "98.115.147.74:17020",
"services" : "00000001",
"lastsend" : 1441169275,
"lastrecv" : 1441169277,
"conntime" : 1441168731,
"version" : 60003,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1451496,
"banscore" : 0
},
{
"addr" : "115.236.88.86:17020",
"services" : "00000001",
"lastsend" : 1441169275,
"lastrecv" : 1441169275,
"conntime" : 1441168733,
"version" : 60003,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1451496,
"banscore" : 0
},
{
"addr" : "188.165.2.147:17020",
"services" : "00000001",
"lastsend" : 1441169118,
"lastrecv" : 1441169271,
"conntime" : 1441168810,
"version" : 60003,
"subver" : "/Satoshi:1.0.1.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1529646,
"banscore" : 0
},
{
"addr" : "203.20.114.252:17020",
"services" : "00000001",
"lastsend" : 1441169117,
"lastrecv" : 1441169264,
"conntime" : 1441168876,
"version" : 60003,
"subver" : "/Satoshi:1.0.1.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1529646,
"banscore" : 0
}
]
well, let's say that all went back to the new blockchain.
a month later again this error and the pool will go to the other - the third chain?
if you want to cryptsy resumed replenishment rbbt-coins she needed a stable pool and not one that jumps every month on different chains at the first error
a month later again this error and the pool will go to the other - the third chain?
if you want to cryptsy resumed replenishment rbbt-coins she needed a stable pool and not one that jumps every month on different chains at the first error
That is the risk we all take without a DEV and a properly checkpointed client. I'm in the process of switching back to the old chain.
Appears Doge had a similar problem https://github.com/dogecoin/dogecoin/issues/250
Is there a block explorer for the old chain? it appears https://prohashing.com/explorer/Rabbitcoin is on the new chain.
The community needs to agree on what is the official chain.
1st chain
(1400000, uint256("0xe7330bf983cebb0f921079f774e22af2032b367162427bda37c9dba9acfa41ce"))
(1420000, uint256("0xadea4fc3a47702cc7a109047ca76054875e54d06b5e5876094d9e0ead73c5fac"))
2nd chain
(1400000, uint256("0x33b81cf2473bfb10ee6b0defb3bb68971dafef7249cb97985036fcfff6136074"))
(1420000, uint256("0x5f1dac3cbbc606053cf44d7cf762d26c1c0cbfddb7b337ba70bc1e5ea8ec0bb6"))
Yes, The pool was on another fork and behind in block count. I re-synced it last night/today and it's joined the other nodes below at Current height 1450594.
"addr" : "115.236.88.86:17020",
"addr" : "204.11.237.233:38721",
"addr" : "98.115.147.74:17020",
"addr" : "122.233.243.196:17020",
The chain I was on was causing DB exceptions during reorgs. This chain appears stable.
My apologies for any lost coins caused by the other chain.
Can someone sanity check the following block hashes?
rabbitcoind getblockhash 1400000
33b81cf2473bfb10ee6b0defb3bb68971dafef7249cb97985036fcfff6136074
rabbitcoind getblockhash 1420000
5f1dac3cbbc606053cf44d7cf762d26c1c0cbfddb7b337ba70bc1e5ea8ec0bb6
rabbitcoind getblockhash 1450594
b0f6550c9bde9b7b8e2c8a045a500b8cf9d3334166313ebf4db9853c27f35b06
"addr" : "115.236.88.86:17020",
"addr" : "204.11.237.233:38721",
"addr" : "98.115.147.74:17020",
"addr" : "122.233.243.196:17020",
The chain I was on was causing DB exceptions during reorgs. This chain appears stable.
My apologies for any lost coins caused by the other chain.
Can someone sanity check the following block hashes?
rabbitcoind getblockhash 1400000
33b81cf2473bfb10ee6b0defb3bb68971dafef7249cb97985036fcfff6136074
rabbitcoind getblockhash 1420000
5f1dac3cbbc606053cf44d7cf762d26c1c0cbfddb7b337ba70bc1e5ea8ec0bb6
rabbitcoind getblockhash 1450594
b0f6550c9bde9b7b8e2c8a045a500b8cf9d3334166313ebf4db9853c27f35b06
i have connected these nodes,thanks!
well, let's say that all went back to the new blockchain.
a month later again this error and the pool will go to the other - the third chain?
if you want to cryptsy resumed replenishment rbbt-coins she needed a stable pool and not one that jumps every month on different chains at the first error
a month later again this error and the pool will go to the other - the third chain?
if you want to cryptsy resumed replenishment rbbt-coins she needed a stable pool and not one that jumps every month on different chains at the first error
About 3 weeks ago, I also had this error, resync with your IP and more have not seen her.
Your pool started checking with block 14292** finished 135**** (-100 000) which was 28 July, all who mining on hobbypool last month lost their coins/
Rabbitcoin mining for the last month several people (acckkiller, miner, ariesteam and me) + someone else solo sometimes connected, and probably 90% of the blocks were in your pool. and you decided to connect to another wallet which is likely all that time working solo, excellent!
I leave my wallets at the old chain. You do as you know
The pools coind was having the DB exception constantly with over 10000+ delayed re-orgs. Appears a TX caused the max # of locks to be exhausted.Your pool started checking with block 14292** finished 135**** (-100 000) which was 28 July, all who mining on hobbypool last month lost their coins/
Rabbitcoin mining for the last month several people (acckkiller, miner, ariesteam and me) + someone else solo sometimes connected, and probably 90% of the blocks were in your pool. and you decided to connect to another wallet which is likely all that time working solo, excellent!
I leave my wallets at the old chain. You do as you know
I still have the other chain, I can put the node back on that chain but most of the network is on this other chain who is greater in height.
We'll need to come to some agreement on what is the official chain.
A new wallet with proper checkpoints will need to be built and released.
Jump to: