◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈

[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

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)

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.


 

[bitcreditscc]

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.

[proletariat]

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.

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......

[dragos_bdi]

miner now successfully waits after mining block.

wait, but not start ...
I still have to issue "setgenerate true" ...

[thelonecrouton]

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.

I used dragos's bootstrap. Deleted grantsdb and restarted, it popped back a block or two later.

I seem to have mined 210067 though, at least chainz agrees with me: https://chainz.cryptoid.info/bcr/block.dws?210067.htm

[thelonecrouton]

miner now successfully waits after mining block.

wait, but not start ...
I still have to issue "setgenerate true" ...

I'm hoping bitcreditscc will demonstrate how to programatically call setgenerate, so I can copy it for the importprivkey bit of the bids page. Damned if I could figure it out. 

[bitcreditscc]

miner now successfully waits after mining block.

wait, but not start ...
I still have to issue "setgenerate true" ...

i just noticed this too, my mind is getting a bit slow, tired. I'll run a few tests and figure out what going on

[bitcreditscc]

miner now successfully waits after mining block.

wait, but not start ...
I still have to issue "setgenerate true" ...

I'm hoping bitcreditscc will demonstrate how to programatically call setgenerate, so I can copy it for the importprivkey bit of the bids page. Damned if I could figure it out.  

huh? you want a way to make call like rpc from the gui? best look at rpc classes inside qt folder. also, i'm thinking of bringing the mining GUI back.

[thelonecrouton]

miner now successfully waits after mining block.

wait, but not start ...
I still have to issue "setgenerate true" ...

I'm hoping bitcreditscc will demonstrate how to programatically call setgenerate, so I can copy it for the importprivkey bit of the bids page. Damned if I could figure it out.  

huh? you want a way to make call like rpc from the gui? best look at rpc classes inside qt folder. also, i'm thinking of bringing the mining GUI back.

Yeah I wrangled with it for 2 days, IIRC the RPC console object is already instantiated (but not yet displayed and therefore not properly memory-allocated by QT) by bitcreditgui - I couldn't programatically pass anything to it (or create another one) without segfaulting. Trivial to pass it as an external call to bitcredit-cli though, maybe that's OK and that's one of the reasons bitcoin-cli was split out from bitcoind? Passing plaintext privkeys to terminal seemed like a security risk to me though.

I should probably stick to faffing with widget layouts... 

[bitcreditscc]

miner now successfully waits after mining block.

wait, but not start ...
I still have to issue "setgenerate true" ...

I'm hoping bitcreditscc will demonstrate how to programatically call setgenerate, so I can copy it for the importprivkey bit of the bids page. Damned if I could figure it out.  

huh? you want a way to make call like rpc from the gui? best look at rpc classes inside qt folder. also, i'm thinking of bringing the mining GUI back.

Yeah I wrangled with it for 2 days, IIRC the RPC console object is already instantiated (but not yet displayed and therefore not properly memory-allocated by QT) by bitcreditgui - I couldn't programatically pass anything to it (or create another one) without segfaulting. Trivial to pass it as an external call to bitcredit-cli though, maybe that's OK and that's one of the reasons bitcoin-cli was split out from bitcoind? Passing plaintext privkeys to terminal seemed like a security risk to me though.

I should probably stick to faffing with widget layouts... 

Ok i've added it to the todo list, i'll pick it up in the morning, already i'm almost done writing the line that allow easy mining from a single node using all viable keys.

[thelonecrouton]

Ok i've added it to the todo list, i'll pick it up in the morning, already i'm almost done writing the line that allow easy mining from a single node using all viable keys.

No worries, you've been busy with far more important stuff - don't mistake my blather for complaint of any kind.

Looking forward to deploying my auto-bid script, gotta offload the DASH my MNs are accumulating...

[thelonecrouton]

Liking this 2W mining... hope I'm still on the right chain because I'm nailing those blocks with my spare abacus.

Wonder what mining profitability sites will make of a $0.12/day blockchain 

[catotune]

Hello everyone - I downloaded and compiled the latest source from Github (using Linux), and I re-downloaded the blockchain.

However bitcreditd always crashes right after these lines in debug.log:

Code:

2015-10-03 03:35:30  === Grant Database Block Height 210055 ===
2015-10-03 03:35:30 Checking Grant Database is updated. ===
=== Required Height : 210060, requested from: 210065 ===
2015-10-03 03:35:30   Processing the Next Block into the Grant Database for Block: 210056

Do I need to configure anything differently for my banknode?

I basically have the same configuration as before the blockchain got stuck, but I'm reading a lot in this thread about "setgenerate true" and grantdb, so I just want to make sure nothing has fundamentally changed as far as configuring the client. Is the latest code in the master branch stable, or are other folks crashing too? Thanks!

EDIT: Never mind - I restarted bitcreditd with "-reindex" and that seemed to work. 

I am still not exactly clear on the new developements - it seems that mining can only be done from within the wallet now? Blocks have grants in them? But I'll try to read further and catch up

[bitcreditscc]

Ok i've added it to the todo list, i'll pick it up in the morning, already i'm almost done writing the line that allow easy mining from a single node using all viable keys.

No worries, you've been busy with far more important stuff - don't mistake my blather for complaint of any kind.

Looking forward to deploying my auto-bid script, gotta offload the DASH my MNs are accumulating...

now testing the code for multi-key option, next i want to re-write the bidding code using json. If i can get it right, i'll also write fall back data sources.

Liking this 2W mining... hope I'm still on the right chain because I'm nailing those blocks with my spare abacus.

Wonder what mining profitability sites will make of a $0.12/day blockchain 

A lot of these sites would need to modify their metrics to be more realistic. Like seriously, markets caps based on # units * current price, when there is only 0.1 BTC buy support?

[bitcreditscc]

Hello everyone - I downloaded and compiled the latest source from Github (using Linux), and I re-downloaded the blockchain.

However bitcreditd always crashes right after these lines in debug.log:

Code:

2015-10-03 03:35:30  === Grant Database Block Height 210055 ===
2015-10-03 03:35:30 Checking Grant Database is updated. ===
=== Required Height : 210060, requested from: 210065 ===
2015-10-03 03:35:30   Processing the Next Block into the Grant Database for Block: 210056

Do I need to configure anything differently for my banknode?

I basically have the same configuration as before the blockchain got stuck, but I'm reading a lot in this thread about "setgenerate true" and grantdb, so I just want to make sure nothing has fundamentally changed as far as configuring the client. Is the latest code in the master branch stable, or are other folks crashing too? Thanks!

EDIT: Never mind - I restarted bitcreditd with "-reindex" and that seemed to work. 

I am still not exactly clear on the new developements - it seems that mining can only be done from within the wallet now? Blocks have grants in them? But I'll try to read further and catch up

glad you got it working, an additional git pull will get you  running on the version similar to mine, with this you can just add all your mining keys to one file "miningkeys.dat", and it will mine using any viable key. this is especially cruial as we will soon move from just consecutive to 20 or 40 Block spacing.

For now we are working of a side branch as we'd like to fix everything before pushing to master, This means a bit of tinkering and a bit of hair pulling at the odd times, but it's relatively better now.

There is a huge list of things to be done, i posted some of the stuff above, but that's just barely scratching the surface.

[dragos_bdi]

Hello everyone - I downloaded and compiled the latest source from Github (using Linux), and I re-downloaded the blockchain.

However bitcreditd always crashes right after these lines in debug.log:

Code:

2015-10-03 03:35:30  === Grant Database Block Height 210055 ===
2015-10-03 03:35:30 Checking Grant Database is updated. ===
=== Required Height : 210060, requested from: 210065 ===
2015-10-03 03:35:30   Processing the Next Block into the Grant Database for Block: 210056

Do I need to configure anything differently for my banknode?

I basically have the same configuration as before the blockchain got stuck, but I'm reading a lot in this thread about "setgenerate true" and grantdb, so I just want to make sure nothing has fundamentally changed as far as configuring the client. Is the latest code in the master branch stable, or are other folks crashing too? Thanks!

EDIT: Never mind - I restarted bitcreditd with "-reindex" and that seemed to work.  

I am still not exactly clear on the new developements - it seems that mining can only be done from within the wallet now? Blocks have grants in them? But I'll try to read further and catch up

glad you got it working, an additional git pull will get you  running on the version similar to mine, with this you can just add all your mining keys to one file "miningkeys.dat", and it will mine using any viable key. this is especially cruial as we will soon move from just consecutive to 20 or 40 Block spacing.

For now we are working of a side branch as we'd like to fix everything before pushing to master, This means a bit of tinkering and a bit of hair pulling at the odd times, but it's relatively better now.

There is a huge list of things to be done, i posted some of the stuff above, but that's just barely scratching the surface.

with lattest git "brake" is in place ...

2015-10-03 07:19:16 testHash e56c11854c8e49126a867f6497bab8e759cfa3171009b8f0703201833a1bad2c
2015-10-03 07:19:16 Hash Target 00e2cc0000000000000000000000000000000000000000000000000000000000
2015-10-03 07:19:17 testHash e56c11854c8e49126a867f6497bab8e759cfa3171009b8f0703201833a1bad2c
2015-10-03 07:19:17 Hash Target 00e2cc0000000000000000000000000000000000000000000000000000000000
2015-10-03 07:19:17 testHash e56c11854c8e49126a867f6497bab8e759cfa3171009b8f0703201833a1bad2c
2015-10-03 07:19:17 Hash Target 00e2cc0000000000000000000000000000000000000000000000000000000000
2015-10-03 07:19:17 testHash e56c11854c8e49126a867f6497bab8e759cfa3171009b8f0703201833a1bad2c
2015-10-03 07:19:17 Hash Target 00e2cc0000000000000000000000000000000000000000000000000000000000
2015-10-03 07:19:17 key new  6C4maPsTQYkPjgkU2sw3pNCobo1Uw5uRZB , keyprev     5wXSRF1wszBwEQiVGKr63MXedqwPgVtf9m

Edit:
bitcredit-cli listaddressgroupings
[
    [
        [
            "68FZz6Rw5Xys5vzkns8m1NCyUjW6woWFoi",
            0.24807342,
            ""
        ],
        [
            "61tAnviYXGwEYNNNXxwtXFk8DWejC6nr69",
            0.00000000,
            ""
        ],
        [
            "6C4maPsTQYkPjgkU2sw3pNCobo1Uw5uRZB",
            50165.75000182,
            ""
        ]
    ]
]

[bitcreditscc]

with lattest git "brake" is in place ...

2015-10-03 07:19:16 testHash e56c11854c8e49126a867f6497bab8e759cfa3171009b8f0703201833a1bad2c
2015-10-03 07:19:16 Hash Target 00e2cc0000000000000000000000000000000000000000000000000000000000
2015-10-03 07:19:17 testHash e56c11854c8e49126a867f6497bab8e759cfa3171009b8f0703201833a1bad2c
2015-10-03 07:19:17 Hash Target 00e2cc0000000000000000000000000000000000000000000000000000000000
2015-10-03 07:19:17 testHash e56c11854c8e49126a867f6497bab8e759cfa3171009b8f0703201833a1bad2c
2015-10-03 07:19:17 Hash Target 00e2cc0000000000000000000000000000000000000000000000000000000000
2015-10-03 07:19:17 testHash e56c11854c8e49126a867f6497bab8e759cfa3171009b8f0703201833a1bad2c
2015-10-03 07:19:17 Hash Target 00e2cc0000000000000000000000000000000000000000000000000000000000
2015-10-03 07:19:17 key new  6C4maPsTQYkPjgkU2sw3pNCobo1Uw5uRZB , keyprev     5wXSRF1wszBwEQiVGKr63MXedqwPgVtf9m

Edit:
bitcredit-cli listaddressgroupings
[
    [
        [
            "68FZz6Rw5Xys5vzkns8m1NCyUjW6woWFoi",
            0.24807342,
            ""
        ],
        [
            "61tAnviYXGwEYNNNXxwtXFk8DWejC6nr69",
            0.00000000,
            ""
        ],
        [
            "6C4maPsTQYkPjgkU2sw3pNCobo1Uw5uRZB",
            50165.75000182,
            ""
        ]
    ]
]

I take it this means it works?

you can just create a file called miningkeys.dat, place your mining/Bn keys in there and it will mine with any viable one. for now we are still using consecutive block rules, hopefully by end of day we can start testing 20 or 40 block rule.

[dragos_bdi]

with lattest git "brake" is in place ...

2015-10-03 07:19:16 testHash e56c11854c8e49126a867f6497bab8e759cfa3171009b8f0703201833a1bad2c
2015-10-03 07:19:16 Hash Target 00e2cc0000000000000000000000000000000000000000000000000000000000
2015-10-03 07:19:17 testHash e56c11854c8e49126a867f6497bab8e759cfa3171009b8f0703201833a1bad2c
2015-10-03 07:19:17 Hash Target 00e2cc0000000000000000000000000000000000000000000000000000000000
2015-10-03 07:19:17 testHash e56c11854c8e49126a867f6497bab8e759cfa3171009b8f0703201833a1bad2c
2015-10-03 07:19:17 Hash Target 00e2cc0000000000000000000000000000000000000000000000000000000000
2015-10-03 07:19:17 testHash e56c11854c8e49126a867f6497bab8e759cfa3171009b8f0703201833a1bad2c
2015-10-03 07:19:17 Hash Target 00e2cc0000000000000000000000000000000000000000000000000000000000
2015-10-03 07:19:17 key new  6C4maPsTQYkPjgkU2sw3pNCobo1Uw5uRZB , keyprev     5wXSRF1wszBwEQiVGKr63MXedqwPgVtf9m

Edit:
bitcredit-cli listaddressgroupings
[
    [
        [
            "68FZz6Rw5Xys5vzkns8m1NCyUjW6woWFoi",
            0.24807342,
            ""
        ],
        [
            "61tAnviYXGwEYNNNXxwtXFk8DWejC6nr69",
            0.00000000,
            ""
        ],
        [
            "6C4maPsTQYkPjgkU2sw3pNCobo1Uw5uRZB",
            50165.75000182,
            ""
        ]
    ]
]

I take it this means it works?

you can just create a file called miningkeys.dat, place your mining/Bn keys in there and it will mine with any viable one. for now we are still using consecutive block rules, hopefully by end of day we can start testing 20 or 40 block rule.

nope, it does not work.
it does break https://github.com/bitcreditscc/bicreditsnew/commit/b957e465ab5044da4a8101d20c576ce8f685b402#diff-4a59b408ad3778278c3aeffa7da33c3cR651
because mining key are not equal ...

[bitcreditscc]

with lattest git "brake" is in place ...

2015-10-03 07:19:16 testHash e56c11854c8e49126a867f6497bab8e759cfa3171009b8f0703201833a1bad2c
2015-10-03 07:19:16 Hash Target 00e2cc0000000000000000000000000000000000000000000000000000000000
2015-10-03 07:19:17 testHash e56c11854c8e49126a867f6497bab8e759cfa3171009b8f0703201833a1bad2c
2015-10-03 07:19:17 Hash Target 00e2cc0000000000000000000000000000000000000000000000000000000000
2015-10-03 07:19:17 testHash e56c11854c8e49126a867f6497bab8e759cfa3171009b8f0703201833a1bad2c
2015-10-03 07:19:17 Hash Target 00e2cc0000000000000000000000000000000000000000000000000000000000
2015-10-03 07:19:17 testHash e56c11854c8e49126a867f6497bab8e759cfa3171009b8f0703201833a1bad2c
2015-10-03 07:19:17 Hash Target 00e2cc0000000000000000000000000000000000000000000000000000000000
2015-10-03 07:19:17 key new  6C4maPsTQYkPjgkU2sw3pNCobo1Uw5uRZB , keyprev     5wXSRF1wszBwEQiVGKr63MXedqwPgVtf9m

Edit:
bitcredit-cli listaddressgroupings
[
    [
        [
            "68FZz6Rw5Xys5vzkns8m1NCyUjW6woWFoi",
            0.24807342,
            ""
        ],
        [
            "61tAnviYXGwEYNNNXxwtXFk8DWejC6nr69",
            0.00000000,
            ""
        ],
        [
            "6C4maPsTQYkPjgkU2sw3pNCobo1Uw5uRZB",
            50165.75000182,
            ""
        ]
    ]
]

I take it this means it works?

you can just create a file called miningkeys.dat, place your mining/Bn keys in there and it will mine with any viable one. for now we are still using consecutive block rules, hopefully by end of day we can start testing 20 or 40 block rule.

nope, it does not work.
it does break https://github.com/bitcreditscc/bicreditsnew/commit/b957e465ab5044da4a8101d20c576ce8f685b402#diff-4a59b408ad3778278c3aeffa7da33c3cR651
because mining key are not equal ...

git pull 

[bitcreditscc]

Voting code works : - https://chainz.cryptoid.info/bcr/block.dws?210100.htm

seems i'll need to write a guide, lol, this means i need to hurry up and write the ratings code