With -reindex everyrhing worked fine
fresh sync is hard work. Had to restart daemon various times to finish
All synced until block 210004
Will there be another update or can I update my other nodes as well?
lg t.
Forgot some infos
on fresh install / sync are the following files missing (Or are they not created anymore?)
balances.dat
ratings-folder
bnlist.dat (maybe for the lack of active BNs)
And
can´t start banknode for "out of sync" reason:
bitcredit-cli banknode start
sync in process. Must wait until client is synced to start.
fresh sync is hard work. Had to restart daemon various times to finish
All synced until block 210004
Will there be another update or can I update my other nodes as well?
lg t.
Forgot some infos
on fresh install / sync are the following files missing (Or are they not created anymore?)
balances.dat
ratings-folder
bnlist.dat (maybe for the lack of active BNs)
And
can´t start banknode for "out of sync" reason:
bitcredit-cli banknode start
sync in process. Must wait until client is synced to start.
Ok, when you are @ block 210004 there has not yet been a message requiring build of grantsDb, if you "setgenerate true" it will build the grantDb and try to mine block 210005. balances.dat should be created, are you sure you are on the last commit "try now" or after? Banknodes will start if you mine 210005 while connected to another synced peer.
I was able to mine the block. Daemon is Version from this afternoon.
No grantdb error or something else seen.
bitcreditd -version
Bitcredit Core Daemon version v0.30.17.3-892e7c0-dirty
Can you please verfy?
So 2 BNs are now on the chain.
bitcredit-cli banknode list
{
"188.193.114.167:9995" : "ENABLED",
"91.230.123.11:8877" : "ENABLED"
}
This ist the decoded transaction:
{
"txid" : "26df3b688b41d4488e98135f6f744927b1cab04f4008e7197842a62f98352251",
"version" : 1,
"locktime" : 0,
"vin" : [
{
"coinbase" : "035534030109062f503253482f",
"sequence" : 4294967295
}
],
"vout" : [
{
"value" : 12.15000000,
"n" : 0,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 23ea5bdfb62292a58784ffd57d4d45ed417415eb OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a91423ea5bdfb62292a58784ffd57d4d45ed417415eb88ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"5tL9DZMCBmhcFKf3tVUJa2f1mYjTujiu87"
]
}
},
{
"value" : 1.80000000,
"n" : 1,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 08226e8d382b07d2cfe02c678937c82275b960aa OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a91408226e8d382b07d2cfe02c678937c82275b960aa88ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"5qoFUCqPUE4pyjus6U6jD6ba4oHR6NZ7c7"
]
}
},
{
"value" : 1.80000000,
"n" : 2,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 6d7733df664a56f942602300facd7c4119d52bd9 OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a9146d7733df664a56f942602300facd7c4119d52bd988ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"6133GZGV2XRnS53DkLSWrK661TsQMqnewL"
]
}
},
{
"value" : 2.25000000,
"n" : 3,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 dcee7e519cc25c52f52439dc9012e3d884d5ef18 OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a914dcee7e519cc25c52f52439dc9012e3d884d5ef1888ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"6BCRBKZLmq2JwWLWDtJZL26ao4uHhqG6mH"
]
}
}
]
}
So next block must be mined by another banknode, according to the new rules?
lg t.
