Search content
Sort by
Showing 20 of 49 results by tombcoin
Re: [ANN] [SFR] SaffronCoin | Latest Version - 1.4.2/2.6.2 | Mandatory Wallet Update
I think if someone can fork this coin and make a new wallet with new road map with some idea, then this coin will be live again and can get it back on exchanges.
Usually the only reason some one does this is to generate a whole new generation of bag holders. I've got a small bag. It's worth zero. Thats the risk of crypto. But if someone wants to revive the coin, someone can have my little bag dumped on them.
If someone has a big enough bag they might do it. But they are probably to busy created pre-mined ICO's for people to invest in.
Brought SAF-chain online/running again.
Made some instances and fired up the chain by solo-mining.
Now take it and make the best out of it.
lg t.
Set up a fresh installed headless Linux with latest git.
New version of BCR does only connect to: 176.56.238.121:8877
with the result:
connect() to 176.56.238.121:8877 failed after select(): Connection refused (111)
socket recv error Connection reset by peer (104)
I didn´t set anything additional in bitcredit.conf.
Only rpcuser and rpcpassword which is needed for daemon to run.
Is this a wanted config?
lg t.
New version of BCR does only connect to: 176.56.238.121:8877
with the result:
connect() to 176.56.238.121:8877 failed after select(): Connection refused (111)
socket recv error Connection reset by peer (104)
I didn´t set anything additional in bitcredit.conf.
Only rpcuser and rpcpassword which is needed for daemon to run.
Is this a wanted config?
lg t.
I got the same problems with my BNs:
2015-12-14 11:25:38 UpdateTip: new best=000eec7c4c1fd2c1d488dc74d7ac80fa8829a41d3c02c01dae8ac2c87e11970a height=266996 log2_work=35.947744 tx=276481 date=2015-12-13 20:31:37 progress=0.991034 cache=2583
2015-12-14 11:25:38 ERROR: ConnectBlock(): coinbase key detected in last 40 blocks
2015-12-14 11:25:38 Misbehaving: 91.230.123.86:8877 (0 -> 100) BAN THRESHOLD EXCEEDED
2015-12-14 11:25:38 InvalidChainFound: invalid block=000944bcc77a8e9a81a4b3fc673dda17627830dd1a03bae35c974e580831cc9c height=266997 log2_work=35.947744
lg t.
2015-12-14 11:25:38 UpdateTip: new best=000eec7c4c1fd2c1d488dc74d7ac80fa8829a41d3c02c01dae8ac2c87e11970a height=266996 log2_work=35.947744 tx=276481 date=2015-12-13 20:31:37 progress=0.991034 cache=2583
2015-12-14 11:25:38 ERROR: ConnectBlock(): coinbase key detected in last 40 blocks
2015-12-14 11:25:38 Misbehaving: 91.230.123.86:8877 (0 -> 100) BAN THRESHOLD EXCEEDED
2015-12-14 11:25:38 InvalidChainFound: invalid block=000944bcc77a8e9a81a4b3fc673dda17627830dd1a03bae35c974e580831cc9c height=266997 log2_work=35.947744
lg t.
Re: BITCREDIT | UPDATE 08/10/15 | BID ON THE CHAIN | VOTE | ESCROW | WORK FOR COINS
Didn´t get an error like this on my ubuntu.
Only thing that changed is sqlite:
sudo apt-get install sqlite3 libsqlite3-dev
Then it should work.
Try to delete the local git-rep and clone new from github.
Then try again to compile.
lg t.
Only thing that changed is sqlite:
sudo apt-get install sqlite3 libsqlite3-dev
Then it should work.
Try to delete the local git-rep and clone new from github.
Then try again to compile.
lg t.
Re: BITCREDIT | UPDATE 08/10/15 | BID ON THE CHAIN | VOTE | ESCROW | WORK FOR COINS
Still no luck with the new wallet.
I tried headless daemon and qt-wallet each on a fresh built linux.
On each connect there is always this error:
'socket recv error Connection reset by peer (104)'
And remote peer disconnects.
Any suggestions?
lg t.
Forgot version:
v0.30.19.0-f8911fe
I tried headless daemon and qt-wallet each on a fresh built linux.
On each connect there is always this error:
'socket recv error Connection reset by peer (104)'
And remote peer disconnects.
Any suggestions?
lg t.
Forgot version:
v0.30.19.0-f8911fe
Re: BITCREDIT | UPDATE 08/10/15 | BID ON THE CHAIN | VOTE | ESCROW | WORK FOR COINS
Hi, thanks for the bootstrap.
But... is there a new client?
balances.dat now placed in folder 'ratings'
miners.dat is missing.
New: rawdata.db
What is the matter with this?
I think that old clients can´t do anything with it.
lg t.
But... is there a new client?
balances.dat now placed in folder 'ratings'
miners.dat is missing.
New: rawdata.db
What is the matter with this?
I think that old clients can´t do anything with it.
lg t.
Re: BITCREDIT | UPDATE 08/10/15 | BID ON THE CHAIN | VOTE | ESCROW | WORK FOR COINS
try adding this node :-91.230.123.101
Thanks, but it is not the missing node. I got enough other nodes connected.It is the error that blocks the sync.
lg t.
Re: BITCREDIT | UPDATE 08/10/15 | BID ON THE CHAIN | VOTE | ESCROW | WORK FOR COINS
Hi together,
I tried to sync a new client, but get stuck at this point:
I tried with both last versions: 30.17.6-64bit and 30.17.8-rc2 and each with a new wallet.
Same result with both versions.
Any suggestions to resolve this?
lg t.
I tried to sync a new client, but get stuck at this point:
Code:
2015-11-05 10:38:10 UpdateTip: new best=0002746187aeb4aa7e229ebe27f500843f8858658b40436106fd34878abae642 height=236432 log2_work=35.943277 tx=24523
0 date=2015-11-04 16:06:23 progress=0.991353 cache=50606
2015-11-05 10:38:11 UpdateTip: new best=0000ede34e6921527e79b462ba2df67b6087f8f39bb9ee21cbe1cd8ad8eecb5d height=236433 log2_work=35.943277 tx=24523
1 date=2015-11-04 16:06:35 progress=0.991354 cache=50607
2015-11-05 10:38:11 ERROR: ConnectBlock(): banknode miningkey invalid
2015-11-05 10:38:11 Misbehaving: 91.230.123.11:8877 (0 -> 100) BAN THRESHOLD EXCEEDED
2015-11-05 10:38:11 InvalidChainFound: invalid block=0002093181003c6baccefa037daff9471eaffb1757a745ed7933e762a30730c3 height=236434 log2_work=35.943
277 date=2015-11-04 16:10:09
2015-11-05 10:38:11 InvalidChainFound: current best=0000ede34e6921527e79b462ba2df67b6087f8f39bb9ee21cbe1cd8ad8eecb5d height=236433 log2_work=35.943
277 date=2015-11-04 16:06:35
2015-11-05 10:38:11 ERROR: ConnectTip(): ConnectBlock 0002093181003c6baccefa037daff9471eaffb1757a745ed7933e762a30730c3 failed
2015-11-05 10:38:11 InvalidChainFound: invalid block=0002093181003c6baccefa037daff9471eaffb1757a745ed7933e762a30730c3 height=236434 log2_work=35.943
277 date=2015-11-04 16:10:09
2015-11-05 10:38:11 InvalidChainFound: current best=0000ede34e6921527e79b462ba2df67b6087f8f39bb9ee21cbe1cd8ad8eecb5d height=236433 log2_work=35.943
277 date=2015-11-04 16:06:35
0 date=2015-11-04 16:06:23 progress=0.991353 cache=50606
2015-11-05 10:38:11 UpdateTip: new best=0000ede34e6921527e79b462ba2df67b6087f8f39bb9ee21cbe1cd8ad8eecb5d height=236433 log2_work=35.943277 tx=24523
1 date=2015-11-04 16:06:35 progress=0.991354 cache=50607
2015-11-05 10:38:11 ERROR: ConnectBlock(): banknode miningkey invalid
2015-11-05 10:38:11 Misbehaving: 91.230.123.11:8877 (0 -> 100) BAN THRESHOLD EXCEEDED
2015-11-05 10:38:11 InvalidChainFound: invalid block=0002093181003c6baccefa037daff9471eaffb1757a745ed7933e762a30730c3 height=236434 log2_work=35.943
277 date=2015-11-04 16:10:09
2015-11-05 10:38:11 InvalidChainFound: current best=0000ede34e6921527e79b462ba2df67b6087f8f39bb9ee21cbe1cd8ad8eecb5d height=236433 log2_work=35.943
277 date=2015-11-04 16:06:35
2015-11-05 10:38:11 ERROR: ConnectTip(): ConnectBlock 0002093181003c6baccefa037daff9471eaffb1757a745ed7933e762a30730c3 failed
2015-11-05 10:38:11 InvalidChainFound: invalid block=0002093181003c6baccefa037daff9471eaffb1757a745ed7933e762a30730c3 height=236434 log2_work=35.943
277 date=2015-11-04 16:10:09
2015-11-05 10:38:11 InvalidChainFound: current best=0000ede34e6921527e79b462ba2df67b6087f8f39bb9ee21cbe1cd8ad8eecb5d height=236433 log2_work=35.943
277 date=2015-11-04 16:06:35
I tried with both last versions: 30.17.6-64bit and 30.17.8-rc2 and each with a new wallet.
Same result with both versions.
Any suggestions to resolve this?
lg t.
Re: BITCREDIT | UPDATE 08/10/15 | BID ON THE CHAIN | VOTE | ESCROW | WORK FOR COINS
And again...
9c9df79842231f216466a6cd0b666c71df169426adf775e3205eb87372decfc7
30,000.0 BCR
Generation + Fees
5tpz37vJdQaXppzVy66JffgLA7q43daTB7
23,991.75 BCR
5qoFUCqPUE4pyjus6U6jD6ba4oHR6NZ7c7
3,000.0 BCR
6133GZGV2XRnS53DkLSWrK661TsQMqnewL
3,000.0 BCR
5xS7zFmHV72SvKdotNQ4tq6b2bM4Q5Speo
6.0 BCR
6BCRBKZLmq2JwWLWDtJZL26ao4uHhqG6mH
0.9 BCR
6BCRdofKg8ThBV8hbK5tik425gMuy8wreJ
0.45 BCR
6BCRmofCHJyan1JJvz31171QWJumQUuKWz
0.45 BCR
6BCRtofNDwhUxroaVVi1hN7wfX1w1A7K6z
0.45 BCR
Solomining wins
This address isn´t a banknode (it seems it has been a banknode earlier), so the block is found by a wallet solomining
lg t.
9c9df79842231f216466a6cd0b666c71df169426adf775e3205eb87372decfc7
30,000.0 BCR
Generation + Fees
5tpz37vJdQaXppzVy66JffgLA7q43daTB7
23,991.75 BCR
5qoFUCqPUE4pyjus6U6jD6ba4oHR6NZ7c7
3,000.0 BCR
6133GZGV2XRnS53DkLSWrK661TsQMqnewL
3,000.0 BCR
5xS7zFmHV72SvKdotNQ4tq6b2bM4Q5Speo
6.0 BCR
6BCRBKZLmq2JwWLWDtJZL26ao4uHhqG6mH
0.9 BCR
6BCRdofKg8ThBV8hbK5tik425gMuy8wreJ
0.45 BCR
6BCRmofCHJyan1JJvz31171QWJumQUuKWz
0.45 BCR
6BCRtofNDwhUxroaVVi1hN7wfX1w1A7K6z
0.45 BCR
Solomining wins
This address isn´t a banknode (it seems it has been a banknode earlier), so the block is found by a wallet solomining
lg t.
Not miners' fault, mine.
Never mind. Mistakes happen.
Re: BITCREDIT | UPDATE 08/10/15 | BID ON THE CHAIN | VOTE | ESCROW | WORK FOR COINS
And again...
9c9df79842231f216466a6cd0b666c71df169426adf775e3205eb87372decfc7
30,000.0 BCR
Generation + Fees
5tpz37vJdQaXppzVy66JffgLA7q43daTB7
23,991.75 BCR
5qoFUCqPUE4pyjus6U6jD6ba4oHR6NZ7c7
3,000.0 BCR
6133GZGV2XRnS53DkLSWrK661TsQMqnewL
3,000.0 BCR
5xS7zFmHV72SvKdotNQ4tq6b2bM4Q5Speo
6.0 BCR
6BCRBKZLmq2JwWLWDtJZL26ao4uHhqG6mH
0.9 BCR
6BCRdofKg8ThBV8hbK5tik425gMuy8wreJ
0.45 BCR
6BCRmofCHJyan1JJvz31171QWJumQUuKWz
0.45 BCR
6BCRtofNDwhUxroaVVi1hN7wfX1w1A7K6z
0.45 BCR
Solomining wins
This address isn´t a banknode (it seems it has been a banknode earlier), so the block is found by a wallet solomining
lg t.
9c9df79842231f216466a6cd0b666c71df169426adf775e3205eb87372decfc7
30,000.0 BCR
Generation + Fees
5tpz37vJdQaXppzVy66JffgLA7q43daTB7
23,991.75 BCR
5qoFUCqPUE4pyjus6U6jD6ba4oHR6NZ7c7
3,000.0 BCR
6133GZGV2XRnS53DkLSWrK661TsQMqnewL
3,000.0 BCR
5xS7zFmHV72SvKdotNQ4tq6b2bM4Q5Speo
6.0 BCR
6BCRBKZLmq2JwWLWDtJZL26ao4uHhqG6mH
0.9 BCR
6BCRdofKg8ThBV8hbK5tik425gMuy8wreJ
0.45 BCR
6BCRmofCHJyan1JJvz31171QWJumQUuKWz
0.45 BCR
6BCRtofNDwhUxroaVVi1hN7wfX1w1A7K6z
0.45 BCR
Solomining wins
This address isn´t a banknode (it seems it has been a banknode earlier), so the block is found by a wallet solomining
lg t.
Re: BITCREDIT | UPDATE 25/09/15 | BID ON THE CHAIN | VOTE | ESCROW | WORK FOR COINS
@bitcreditscc
I think you overwrite the "miner wait" push ...
https://github.com/bitcreditscc/bicreditsnew/commit/6bc38a93d5b50536195f60a3d2f8b6002642762f
There is not anymore in master ...
I think you overwrite the "miner wait" push ...
https://github.com/bitcreditscc/bicreditsnew/commit/6bc38a93d5b50536195f60a3d2f8b6002642762f
There is not anymore in master ...
I changed that logic users now use the miningkeys.dat file with the required keys for mining.
Can confirm that it works. But it seems that it does not take the keys one by one.
It think is just hopping between the first keys.
Since chainz is behind, I just decoded some blocks by hand.
Also put no comments behind the keys nor between the lines in the miningkey.dat.
Throws out an error: wrong key
lg t.
Re: BITCREDIT | UPDATE 25/09/15 | BID ON THE CHAIN | VOTE | ESCROW | WORK FOR COINS
Got it 
Now diff is acceptable again.
{
"version" : 301705,
"protocolversion" : 70012,
"walletversion" : 60000,
"balance" :
"darksend_balance" : 0.00000000,
"blocks" : 210288,
"timeoffset" : 0,
"connections" : 2,
"proxy" : "",
"difficulty" : 0.00000143,
"testnet" : false,
"keypoololdest" : 1442913009,
"keypoolsize" : 2,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}
Now diff is acceptable again.
{
"version" : 301705,
"protocolversion" : 70012,
"walletversion" : 60000,
"balance" :
"darksend_balance" : 0.00000000,
"blocks" : 210288,
"timeoffset" : 0,
"connections" : 2,
"proxy" : "",
"difficulty" : 0.00000143,
"testnet" : false,
"keypoololdest" : 1442913009,
"keypoolsize" : 2,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}
Re: BITCREDIT | UPDATE 25/09/15 | BID ON THE CHAIN | VOTE | ESCROW | WORK FOR COINS
I deleted the post linking to that trash article. We are not ready for media attention.
Well done
Syncing will kill me soon, nervwrecking and stupid.
Seeing lines scrolling and scrolling. Tons of lines.
Can´t even remember which nodes I have updated and which not.
Hope there will be a normal way of life soon.
lg t.