◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈

[bitcreditscc]

I think a simpler method could be possibly a time-based wait period, that sort of follows the coding style already present in the mining code The logic is already there.

@dragos_bdi
Thoughts?

Still exists the possibility that the same wallet find 2 blocks in row.

Could you write a function that if the miner address that found the last block equal with the -bnminingkey, the miner threads sleep for 1 sec or so ?

Yeah, that's the plan, i want it to check if it mined the last block, but instead of waiting for a new block signal, it just uses time delay.

[dragos_bdi]

I think a simpler method could be possibly a time-based wait period, that sort of follows the coding style already present in the mining code The logic is already there.

@dragos_bdi
Thoughts?

Still exists the possibility that the same wallet find 2 blocks in row.

Could you write a function that if the miner address that found the last block equal with the -bnminingkey, the miner threads sleep for 1 sec or so ?

Yeah, that's the plan, i want it to check if it mined the last block, but instead of waiting for a new block signal, it just uses time delay.

Perfect !

[bitcreditscc]

I deleted the post linking to that trash article. We are not ready for media attention.

[tombcoin]

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.

[dragos_bdi]

for those who not wish to wait for -reindex the blockchain, or download it again everything, I bootstrapped the correct blockchain with everything that it's needed:

blocks
chainstate
ratings
balances.dat
miners.dat

till block 210023

Download link: https://mega.nz/#!Lxsj3LRI!jwam12_Vbg4NS-alkZySe4JvhxUOwUM2q2nNgwRoHgw

[doesntmatter]

you should make it time based, if chain not moving then should be ok to mine consecutive blocks... if 1 every half hour? needs to be less than an hour so wallets can still sync no new restart...

[dragos_bdi]

you should make it time based, if chain not moving then should be ok to mine consecutive blocks... if 1 every half hour? needs to be less than an hour so wallets can still sync no new restart...

I was thinking about it, but it's possible to create forks.

For chain to moving, it's mandatory to be at least 2 wallet that mine ...

[bitcreditscc]

you should make it time based, if chain not moving then should be ok to mine consecutive blocks... if 1 every half hour? needs to be less than an hour so wallets can still sync no new restart...

I was thinking about it, but it's possible to create forks.

For chain to moving, it's mandatory to be at least 2 wallet that mine ...

In a nutshell , you guys are right, there has to be a failsafe mechanism that keeps the chain moving.

option 1) basic code (temporary) to keep the chain moving

2) wait a little and see what user response is , if there are 2 unique mining keys in use, the chain will move

I prefer option 2 because it allows us time to observe and decide, the eventual aim is to have a low power, efficient system.  at hashrates of < 0 h/s for the network, people can host a BN on a r-pi 2 and mine as well if they want.

Also we can use this time to do local debugging and ironing out the remaining issues.

**All those having problems, i strongly urge you to open issues on github, everyone who participates in BCR development is immediately alerted.**

[alganonim]

Great work guys, what's the next step to start a BNs ?

Still I got 2 wallets sync at the same block but I get "sync in process. Must wait until client is synced to start"

[bitcreditscc]

Great work guys, what's the next step to start a BNs ?

Still I got 2 wallets sync at the same block but I get "sync in process. Must wait until client is synced to start"

1) make sure system time is correct

2) whats your block height ?

[alganonim]

Both wallets in sync since 2 hours, from debug.log both have now 15:20 but my local time is 2 hours ahead, both now at block 210054

[gavrilo77]

Which version of the client is good? 0.30.17.3.164bit-8b76deb82f?

[dragos_bdi]

There is not any windows version that works at present time. Still work to do for mining part

[bitcreditscc]

Both wallets in sync since 2 hours, from debug.log both have now 15:20 but my local time is 2 hours ahead, both now at block 210054

I suspect a corrupted database, you can verify in debug.log. download a copy of dragos files and bootstrap , it's faster. make sure you delete everything except wallet and conf

210055 is a grant block, so it's likely saying there is something wonky with your grantdb

[alganonim]

Will try it when I get back, maybe answer is simpler, forgot that you can't probably start it from win wallet yet.

[dextronomous]

at synced from dragos files,

now 2100056 inside wallet cannot start getblocktemplate

18:37:41

CreateNewBlock() : TestBlockValidity failed (code -1)

does start banknode does start setgenerate,

how to make the mining work and should i have all my coins inside one wallet to be fine. or finer>.?


GUI: void QWindowsClipboard::propagateClipboardMessage(UINT, WPARAM, LPARAM) const: Cowardly refusing to send clipboard message to hung application...
CreateNewBlock(): total size 1000

and this last line is because of another mined block direct after the previous.?

ERROR: ConnectBlock(): consecutive coinbase key detected
CreateNewBlock(): total size 1000
CheckBlock() : Using non-specific banknode payments 210058
CheckBlock() : Using non-specific banknode payments 210058
ERROR: ConnectBlock(): consecutive coinbase key detected

[bitcreditscc]

just pushed temporary miner logic, now you can just do "setgenerate true" and if you can mine, it will, else it will wait

[bitcreditscc]

miner now successfully waits after mining block.

[dextronomous]

i understand it waits with the necessary cpu cycles thrown at, wich miner?

 and if waiting are these threads still active when waiting to be next miner in line?

or because of previous mined block, waiting with full cycles and all threads at sleep,

then gets a punch on the block of someone else and then starts mining again?

[thelonecrouton]

Both wallets in sync since 2 hours, from debug.log both have now 15:20 but my local time is 2 hours ahead, both now at block 210054

I suspect a corrupted database, you can verify in debug.log. download a copy of dragos files and bootstrap , it's faster. make sure you delete everything except wallet and conf

210055 is a grant block, so it's likely saying there is something wonky with your grantdb

Can't start a BN either, same sync issue. My grantdb.dat @ 210062:

Code:

210055
13
5qoFUCqPUE4pyjus6U6jD6ba4oHR6NZ7c7
37809900000000
5rNk8orWGkJbhmA7Vgb9312FSYtiNffUmS
176400000000000
5riCm1shhPavn5rbBdB4xfeUyFLkSbU3dW
12000000000
5tL9DZMCBmhcFKf3tVUJa2f1mYjTujiu87
10200000000
5tpz37vJdQaXppzVy66JffgLA7q43daTB7
12600000000
5wvszqSmRxDW9NHSYJqDWBH1EQqEMEKvDo
4200000000
5z5ECKDqbZqAUuhFeRTVGqLstq1RgxoWv8
20000000000
5zoh1bN2XTbFrbM5yPiBEK1R2nomhPa9dY
19800000000
6133GZGV2XRnS53DkLSWrK661TsQMqnewL
37809900000000
61ewtAVfqugxhfWN91Vs7UzmJ3BvjM87FE
6000000000
66znmMzEZmJsZ5dAt5ZB4jChzqSkENZ5PL
4200000000
6C4maPsTQYkPjgkU2sw3pNCobo1Uw5uRZB
10200000000
6E9FhwnJ5QjYgqCrok6hxizFpamnEZxQi2
126000000000000
0
0
0
0
0

Can't see any grantdb related errors in debug.log, system and wallet times are matched.

I appear to be able to mine though, at least top shows the client using a full core all the time after 'setgenerate true 1' - plus:

Code:

getmininginfo
{
"blocks" : 210062,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00000003,
"errors" : "",
"genproclimit" : 1,
"networkhashps" : 1,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : true,
"hashespermin" : 5
}

100W blockchain back in action.


Also at some point in last hour or so my BN list emptied, chainz also currently shows zero BNs...?

edit: had this happen a few times

Code:

************************
EXCEPTION: St12out_of_range       
basic_string::substr: __pos (which is 18446744073709551615) > this->size() (which is 0)       
bitcredit in updatebids       

terminate called after throwing an instance of 'std::out_of_range'
  what():  basic_string::substr: __pos (which is 18446744073709551615) > this->size() (which is 0)
Aborted (core dumped)

Issues raised on github.