I don't think you'll be able to mine anything until you get your BN(s) set up on 17.3.

I know it's as frustrating as hell for a lot of you, all these updates, bugs and breakages, it's frustrating for me being unable to help out more - but try and remember the goal - having a viable, scalable banking platform with a base currency that's actually, really worth something...

We can all name dozens of coins that have promised the earth where development has mysteriously ground to a halt after the initial pump and dump. Look at the BCR repo - and remember that for each push to it, there's hours of iterative testing that you don't see. Mistakes happen, but progress is being made and I can't speak for anyone else but personally I wouldn't be banging my head against bloody C++ if I didn't think that BCR will be worth a hell of a lot more in the future than it is currently.  

edit: If your client is showing anything beyond block 210004 (just now) you're going to have to resync from block 210000 when you get 17.3.

You'll need 17.3 I think, hopefully the excellent dragos will compile a Win version soon.

Chain is moving again, diff back down...

BCR is currently moving to Banknode only mining, so first you'll need to set up a Banknode. After that, add a "bnminingkey=<your-BN-BCR-address>" to your bitcredit.conf file, then just type "setgenerate true 1" in the console.

(You might need to wait a while to set up a BN as it's likely to take some time for existing BNs to CPU mine block 210002, after that the chain should be moving along again, but using less than 1% of the previous total power consumption.)

bitcreditscc has acknowledged the issue many times. There is a lot to be done and it can't all be done at once - hopefully dragos will nail this one.

Yes, getting a lot of "peer=497 using obsolete version 70011; disconnecting" type messages, also notice that on the 210000-210001 transition my wallet went from ~100 connections to 45. Diff dropped from 280 to 78, don't know it that's a normal move.

Haven't seen any consecutive block warnings yet as we're still on block 210001 - which is a hopeful sign -  but there were plenty earlier today before enforcement kicked in.

Block 210001, new rules should be in force, can renegade keep cockblocking the bids process?  

Where the blockchain is stored shouldn't matter then, it should hopefully work in future versions as long as the executable is in C:\ProgramFiles now that I've told it to launch with an .exe extension if it's compiled for Win.

Failing that I could just hide the buttons for Win users (or get rid of them entirely?) and they can open up whatever client they like themselves.  

Don't know why the addresses aren't opening up your browser unless you don't have a default browser set, will investigate. All works perfectly on the linux boxes I've tried.  

The bid-with buttons work if you have bitcoin-qt/litecoin-qt/dash-qt in /usr/bin (or anywhere else specified in your PATH) on linux. According to the QT docs it should look in C:\ProgramFiles I think on Windows. Can't test it myself though, don't have a Windows box.

edit: have added some compiler switches to launch eg. bitcoin-qt.exe on Win, instead of bitcoin-qt - this might help...  

Does clicking the bidding addresses open up your browser at the right page(s)?

Put it in whatever your data directory is, ie. where your wallet.dat is. Just make a file called mybanknodes.txt and stick you BN addresses in it. You don't need to restart the wallet, it checks for the file every 10-20 secs.

It should work (works fine for me) if you have a mybanknodes.txt file with your BN addresses listed one per line in it. You have to wait a few secs for the next banknode list refresh though after you check the box.

Got a BN up and running this morning on 17.3, left it mining on 1 core, we'll see what happens  @ 210000. 

Long wait for 210001 probably... 

OK, can you  delete overviewpage.cpp/overviewpage.h and remove all overviewpage lines from src/Makefile.qt.include? I'm not a programmer either... 

overviewpage is not used any more, I just didn't feel confident enough at the time to remove it completely until the 'new overviewpage' - transactionview.cpp was shown to be working correctly.

bitcreditscc is right, IIRC I got rid of the Dasksend balances as DS isn't being used, and also some 'watch only' balances, as I had no idea what they were and they didn't seem to be needed.

I'll change it to "Next 30000 BCR Superblock in..." - not sure where I'd fit any graphs in though, and anyway we wouldn't want to discourage those who really want all the BCR in that superblock...  

Backups, stored somewhere else! And dumpprivkey for any address you've got a big amount stored in, has saved me grief several times! 

Your BCR is safe, it doesn't live in the wallet. And if you don't trust the wallet, you shouldn't be using it to send money anywhere...  

Anyway, I've removed the non-working Redeem button on the bids page for the time being as interacting programatically with the RPC code is a PITA. I can do it pretty simply via an external call to bitcredit-cli but I'm doubtful about passing privkeys out to a terminal. In the meantime, I've put some hopefully clear instructions there instead:

Great news! Will update when I get home and chuck some more BNs up tonight.

Freshly minted BCR is available to anyone to bid for. In time there will be fiat bidding too. Substitute whatever word for 'bid' you like. The proceeds of those sales will be moved out of the bidding addresses that appear in-wallet daily into secure multisig storage. There are 5 of us with keys, 3 are needed to access the funds. It is my hope that the BTC/LTC/DASH we generate from BCR sales will be converted into PMs and securely vaulted in multiple locations (with a formal security structure yet to be decided) since it makes no sense to 'back' BCR with 'assets' (BTC/LTC/DASH) that are themselves unbacked, although it might make sense to keep maybe 10% as crypotofiat. Again, details to be confirmed.

BCR thus acquires real and tangible backing, and an ever growing assured minimum value, a step back towards sound money - a concept abandoned by for example your dear and fluffy US back in 1913 with the creation of the Federal Reserve, final nail in the coffin in 1971 when Nixon dropped the gold standard completely, which has resulted in you needing $1000 today to buy what $40 would have bought you a hundred years ago.

Succinct enough?


There's a link to the wiki in-wallet, click the About Bitcredit icon along the bottom. Or go read any CRAVE or DASH guide.

We're not buying BCR with the other coins, see above.

bitcreditscc is in control of all this, with input welcomed from whoever wishes to provide any. 'Trustless' is easy to do when all you've got is a fistful of air. It's impossible when you're trying to establish meaningful real world systems.

@bitcreditscc

bidtracker.cpp is looking for the DASH unspents here:

http://api.blockstrap.com/v0/drk/address/unspents/Xypcx2iE8rCtC3tjw5M8sxpRzn4JuoSaBH - but their blockchain seems frozen at block 332319, which would explain why my later DASH bids are not showing.

Chainz will give you access to an unspent API call if you ask them (BCT user Fairglu seems like a good guy) for a free API key... just an option if blockstrap continues to be unreliable...

Blockchain.info seems accurate for BTC and LTC though.

The only one to create any demand? There's been plenty of demand from me and I've never heard of you until now. And have you seen the amount of work bitcreditscc has put in? That has no value I suppose, all the demand was created by you.  


Wish I'd heard of BCR earlier! Where have you been for the past 3 months when all this was being publicly discussed and implemented?


No idea what you're talking about here.

Panic much? If we have to change a few strings based on region, and incorporate in Angola, then so be it. If you have any legal expertise, feel free to share!

At the moment all we're doing is selling our own product and accepting 3 other currencies as payment. You could even call it barter. Where exactly is that illegal?