miner now successfully waits after mining block.
wait, but not start ...
I still have to issue "setgenerate true" ...
Topic: ◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈ - page 73. (Read 284526 times)
wait, but not start ...
I still have to issue "setgenerate true" ...
1) optimize internal miner
2) optimize databases
3) create new database for bank math calculations
4) learn boost serialization
5) write ratings code
6) complete vanity port
7) multi-bn code
multi- mining key logic
9) json for bids
10) write code for fiat bidding
11) figure out misplaced transactions
12) expand trust engine for new data
13) write rpc functions for all new code
14) debug IBTP
15) debug Escrow
16) figure out micro-page hosting
17) figure out bankDB and connection to client
18) figure out dynamic loading/unloading of wallets (no need for restart)
19) colored coins
20) write banking specific support code
21) write insurance specific support code
22) create third type of address
23) root out DS code
24) improve raw data extraction
25) create better map management
26) Fix messaging GUI
27) speed up sync and make db build a separate module
off the top of my head this is just what need to be done over the next two months for the core wallet, this doesn't even begin to touch on :-
Android wallet, Bitcreditj , PyBitcredit , ngcccbase-bcr , or multi-bcr and electrum.
2) optimize databases
3) create new database for bank math calculations
4) learn boost serialization
5) write ratings code
6) complete vanity port
7) multi-bn code
multi- mining key logic 9) json for bids
10) write code for fiat bidding
11) figure out misplaced transactions
12) expand trust engine for new data
13) write rpc functions for all new code
14) debug IBTP
15) debug Escrow
16) figure out micro-page hosting
17) figure out bankDB and connection to client
18) figure out dynamic loading/unloading of wallets (no need for restart)
19) colored coins
20) write banking specific support code
21) write insurance specific support code
22) create third type of address
23) root out DS code
24) improve raw data extraction
25) create better map management
26) Fix messaging GUI
27) speed up sync and make db build a separate module
off the top of my head this is just what need to be done over the next two months for the core wallet, this doesn't even begin to touch on :-
Android wallet, Bitcreditj , PyBitcredit , ngcccbase-bcr , or multi-bcr and electrum.
I'd be happy to vote YES on releasing eventual funds from the bidding system to pay for a code monkey to help you out while you concentrate on the code you consider requires your undivided attention at any given time. props to you and the guys helping out. nice thing going here......
1) optimize internal miner
2) optimize databases
3) create new database for bank math calculations
4) learn boost serialization
5) write ratings code
6) complete vanity port
7) multi-bn code
multi- mining key logic
9) json for bids
10) write code for fiat bidding
11) figure out misplaced transactions
12) expand trust engine for new data
13) write rpc functions for all new code
14) debug IBTP
15) debug Escrow
16) figure out micro-page hosting
17) figure out bankDB and connection to client
18) figure out dynamic loading/unloading of wallets (no need for restart)
19) colored coins
20) write banking specific support code
21) write insurance specific support code
22) create third type of address
23) root out DS code
24) improve raw data extraction
25) create better map management
26) Fix messaging GUI
27) speed up sync and make db build a separate module
off the top of my head this is just what need to be done over the next two months for the core wallet, this doesn't even begin to touch on :-
Android wallet, Bitcreditj , PyBitcredit , ngcccbase-bcr , or multi-bcr and electrum.
2) optimize databases
3) create new database for bank math calculations
4) learn boost serialization
5) write ratings code
6) complete vanity port
7) multi-bn code
multi- mining key logic 9) json for bids
10) write code for fiat bidding
11) figure out misplaced transactions
12) expand trust engine for new data
13) write rpc functions for all new code
14) debug IBTP
15) debug Escrow
16) figure out micro-page hosting
17) figure out bankDB and connection to client
18) figure out dynamic loading/unloading of wallets (no need for restart)
19) colored coins
20) write banking specific support code
21) write insurance specific support code
22) create third type of address
23) root out DS code
24) improve raw data extraction
25) create better map management
26) Fix messaging GUI
27) speed up sync and make db build a separate module
off the top of my head this is just what need to be done over the next two months for the core wallet, this doesn't even begin to touch on :-
Android wallet, Bitcreditj , PyBitcredit , ngcccbase-bcr , or multi-bcr and electrum.
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.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
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. {
"blocks" : 210062,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00000003,
"errors" : "",
"genproclimit" : 1,
"networkhashps" : 1,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : true,
"hashespermin" : 5
}
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)
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)
ok , did you sync from start? i think we'll push a version bump to cut out the old nodes. Your system will reject blocks @ 210065. stop client, delete the grantsdb.dat and start client, it will rebuild when it either receives block 210065 or it tries to mine it.
the bidding code is still very primitive. i need time to learn json then we can clean that up.
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.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
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. {
"blocks" : 210062,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00000003,
"errors" : "",
"genproclimit" : 1,
"networkhashps" : 1,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : true,
"hashespermin" : 5
}
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)
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.
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?
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?
miner now successfully waits after mining block.
just pushed temporary miner logic, now you can just do "setgenerate true" and if you can mine, it will, else it will wait
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
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
Will try it when I get back, maybe answer is simpler, forgot that you can't probably start it from win wallet yet.
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
There is not any windows version that works at present time. Still work to do for mining part
Which version of the client is good? 0.30.17.3.164bit-8b76deb82f?
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
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"
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 ?
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"
Still I got 2 wallets sync at the same block but I get "sync in process. Must wait until client is synced to start"
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.**
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 ...
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...
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
blocks
chainstate
ratings
balances.dat
miners.dat
till block 210023
Download link: https://mega.nz/#!Lxsj3LRI!jwam12_Vbg4NS-alkZySe4JvhxUOwUM2q2nNgwRoHgw
Jump to: