Topic: ◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈ - page 72. (Read 284526 times)

Ok, i hope to cross of at least 3 things from the list today.

does miningkeys.dat
got to have the privkey of the banknode
or banknode address, to where 50k sended to.
or really starting to get to be a nooobie again.. what;s happening guys. last night one wallet stopped syncin at 210030 another at 210059
and wasn't going up while blocks where found..

new resyncing please update need info.

do not forget about serialize grantdb from a higher block

  youp, working now

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 

git pull 

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

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.

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,
            ""
        ]
    ]
]

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.

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.


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?

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:


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

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 

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

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.

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

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.

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

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. 

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