◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈

[dragos_bdi]

Trying 0.30.17.1 and I know I sound like a broken record.

Deleted everything in appdata but wallet.dat, config and back up.

Started wallet at least 30 times and it just force closes without running.

Going back to 0.30.17 and hope it works.

At me works ...

I am on Windows 7 64 bit.

What OS are you running?

Edit: I seen it is Windows 64 build.

Edit 2: Maybe I have bad nodes. Is there a current list of working nodes.  I have a ton in my config file.

Window 10 64 bit
Windows 2012 Server 64 bit

82.211.1.181:8877
91.230.123.101:8877
41.191.238.189

[antonio8]

Trying 0.30.17.1 and I know I sound like a broken record.

Deleted everything in appdata but wallet.dat, config and back up.

Started wallet at least 30 times and it just force closes without running.

Going back to 0.30.17 and hope it works.

At me works ...

I am on Windows 7 64 bit.

What OS are you running?

Edit: I seen it is Windows 64 build.

Edit 2: Maybe I have bad nodes. Is there a current list of working nodes.  I have a ton in my config file.

Window 10 64 bit
Windows 2012 Server 64 bit

82.211.1.181:8877
91.230.123.101:8877
41.191.238.189

Thanks,

Got 1 connection so far but it is downloading the blockchain again.

[dextronomous]

Guys.,

wallets don't work any new ones.. keep quitting. dbg log 9 AppInit2 : parameter interaction: -connect set -> setting -dnsseed=0
2015-09-18 18:38:09 AppInit2 : parameter interaction: -externalip set -> setting -discover=0

Opened LevelDB successfully
2015-09-18 18:38:09 LoadBlockIndexDB: last block file = 0
2015-09-18 18:38:09 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01)
2015-09-18 18:38:09 Checking all blk files are present...
2015-09-18 18:38:09 LoadBlockIndexDB(): transaction index disabled
2015-09-18 18:38:09 LoadBlockIndexDB(): address index disabled
2015-09-18 18:38:09 Initializing databases...
2015-09-18 18:38:09 Pre-allocating up to position 0x1000000 in blk00000.dat

so did everything else before told.. clean simple new wallet. nogo, old files nogo, where mi coins.. is there a new version out.

when we get the compiled version's download link. have been trying to start the wallet all evening,,
no luck so far. dunno why.

hellup needed.

[bitcreditscc]

Guys.,

wallets don't work any new ones.. keep quitting. dbg log 9 AppInit2 : parameter interaction: -connect set -> setting -dnsseed=0
2015-09-18 18:38:09 AppInit2 : parameter interaction: -externalip set -> setting -discover=0

Opened LevelDB successfully
2015-09-18 18:38:09 LoadBlockIndexDB: last block file = 0
2015-09-18 18:38:09 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01)
2015-09-18 18:38:09 Checking all blk files are present...
2015-09-18 18:38:09 LoadBlockIndexDB(): transaction index disabled
2015-09-18 18:38:09 LoadBlockIndexDB(): address index disabled
2015-09-18 18:38:09 Initializing databases...
2015-09-18 18:38:09 Pre-allocating up to position 0x1000000 in blk00000.dat

so did everything else before told.. clean simple new wallet. nogo, old files nogo, where mi coins.. is there a new version out.

when we get the compiled version's download link. have been trying to start the wallet all evening,,
no luck so far. dunno why.

hellup needed.

Are you on linux or windows?

[dextronomous]

hi,

this is a windows 64 bit os. all wallets worked until so far.. after not having got the 17.0 version but went to 17.1 directly no blocks pasted copied. no work. crash boom..

maybe i've should have done the 17.0 version first..

OK..
got 2 03017.0 downloading blocks..

then again. the newer one is scheduled to be installed next. wish this easy, and don't know why 030171 didn't work..
how will we be mining in all of this.. how many blocks can one mine is it all about cpu or gpu power. or the amount of BCR coins inside the wallet.

thanks for your help.

[bitcreditscc]

I'll investigate this, but this update did not involve any changes to db related areas.

[thelonecrouton]

17.1 (built on xubuntu 14.10) synced fine from scratch after I specified port=8878 in bitcredit.conf. (I had it set on another port previously.)

Sadly still can't redeem:
"Invalid private key encoding (code -5)"

edit: just closed he client and got this on stdout:
"before X....blah.....blah.......r after M......blah..... blah..........7" - where the before was the dash privkey.

Alas, trying to import the 'after' privkey also gave:
"Invalid private key encoding (code -5)" - BCR privkeys should begin with a 'K' ?

edit2:  banknode up and mining on 1 core.

[bitcreditscc]

17.1 (built on xubuntu 14.10) synced fine from scratch after I specified port=8877 in bitcredit.conf. (I had it set on another port previously.)

Sadly still can't redeem:
"Invalid private key encoding (code -5)"

edit: just closed he client and got this on stdout:
"before X....blah.....blah.......r after M......blah..... blah..........7" - where the before was the dash privkey.

Alas, trying to import the 'after' privkey also gave:
"Invalid private key encoding (code -5)" - BCR privkeys should begin with a 'K' ?

Yeah that's debug, still looking into why some keys are working and others arent, should have an answer by morning

[proletariat]

core limitation is enforced in this update?

[thelonecrouton]

core limitation is enforced in this update?

I'm not sure if we're BN-only mining yet but I've hit 4 blocks out of the last 23 with a quarter of my old laptop's i5.

getmininginfo:
{
"blocks" : 204388,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00000002,
"errors" : "",
"genproclimit" : 1,
"networkhashps" : 19,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : true,
"hashespermin" : 4
}
.. which puts me at a mighty 0.35% of the total hash if that's valid data.

So, I have no idea.

[bitcreditscc]

core limitation is enforced in this update?

I'm not sure if we're BN-only mining yet but I've hit 4 blocks out of the last 23 with a quarter of my old laptop's i5.

getmininginfo:
{
"blocks" : 204388,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00000002,
"errors" : "",
"genproclimit" : 1,
"networkhashps" : 19,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : true,
"hashespermin" : 4
}
.. which puts me at a mighty 0.35% of the total hash if that's valid data.

So, I have no idea.

Do a git pull, i just fixed the standard key import.

Tested with hundreds of keys from all 3 prefixes.

[bitcreditscc]

Quick word


Please everyone, build and run with wallet support. Many things in trhe client now depend on the wallet. I actually intend to reove the option of using without a wallet. Also use bdb 4.8 , some of the newer versions are completely incompatible.

[thelonecrouton]

Do a git pull, i just fixed the standard key import.

Tested with hundreds of keys from all 3 prefixes.

It seems to work, I get a 'Rescanning' popup with progressbar, but no new BCR address or BCR.  

Some old bids still in final.dat, maybe they haven't been 'processed?'

[bitcreditscc]

Do a git pull, i just fixed the standard key import.

Tested with hundreds of keys from all 3 prefixes.

It seems to work, I get a 'Rescanning' popup with progressbar, but no new BCR address or BCR.  

Some old bids still in final.dat, maybe they haven't been 'processed?'

Likely


The reason i changed the format of payouts was to sort out the zero payments issue , lets wait and see the next payout block.

[thelonecrouton]

I've been telling people for 18 months that a single crappy old celeron could handle the entire Bitcoin blockchain with ease, and probably that of every other active altcoin simultaneously. They look at me (or type at me anyway) like I'm crazy for thinking that anything under a petawatt's worth of compute power could possibly cope.

Anyway, BCR's blockchain is currently humming along on a bit more than one crappy celeron, but not much - ("networkhashps" : 1,) - and I just squeezed over 300 txes into block 205593 and ... no issues, surprise. I shall be consolidating the rest of my BN payments shortly.  

Competitive PoW is utterly fucking daft.  


Also, it occurs to me that another aspect of BCR being, among other things, a (worlds first?) p2p hedge fund is that assuming the bid price follows to some extent the market price, any pumping will result in permanently locked in value.

BCR is one of a very few (Xaurum, backed by gold?) cryptocurrencies that can't be dumped to zero, assuming any of the underlying assets still have market value.

[thelonecrouton]

Anyone know how to launch eg. bitcoin-qt with a URI? I know it's possible because you can click on a bitcoin URI in a browser and it works, but I can't find how the browser passes the URI to the client... 

I'm looking for something like,  'bitcoin-qt --URI=<blah>' ...?

[proletariat]

I've been telling people for 18 months that a single crappy old celeron could handle the entire Bitcoin blockchain with ease, and probably that of every other active altcoin simultaneously. They look at me (or type at me anyway) like I'm crazy for thinking that anything under a petawatt's worth of compute power could possibly cope.

Anyway, BCR's blockchain is currently humming along on a bit more than one crappy celeron, but not much - ("networkhashps" : 1,) - and I just squeezed over 300 txes into block 205593 and ... no issues, surprise. I shall be consolidating the rest of my BN payments shortly.  

Competitive PoW is utterly fucking daft.  


Also, it occurs to me that another aspect of BCR being, among other things, a (worlds first?) p2p hedge fund is that assuming the bid price follows to some extent the market price, any pumping will result in permanently locked in value.

BCR is one of a very few (Xaurum, backed by gold?) cryptocurrencies that can't be dumped to zero, assuming any of the underlying assets still have market value.

I'm confused. When I have a BN running do I setgenerate true or how is it "BN only mining"? also, are all your nodes running from the same machine? because i gave up yesterday trying to run more than 2 on my vps.

[bitcreditscc]

I've been telling people for 18 months that a single crappy old celeron could handle the entire Bitcoin blockchain with ease, and probably that of every other active altcoin simultaneously. They look at me (or type at me anyway) like I'm crazy for thinking that anything under a petawatt's worth of compute power could possibly cope.

Anyway, BCR's blockchain is currently humming along on a bit more than one crappy celeron, but not much - ("networkhashps" : 1,) - and I just squeezed over 300 txes into block 205593 and ... no issues, surprise. I shall be consolidating the rest of my BN payments shortly.  

Competitive PoW is utterly fucking daft.  


Also, it occurs to me that another aspect of BCR being, among other things, a (worlds first?) p2p hedge fund is that assuming the bid price follows to some extent the market price, any pumping will result in permanently locked in value.

BCR is one of a very few (Xaurum, backed by gold?) cryptocurrencies that can't be dumped to zero, assuming any of the underlying assets still have market value.

I'm confused. When I have a BN running do I setgenerate true or how is it "BN only mining"? also, are all your nodes running from the same machine? because i gave up yesterday trying to run more than 2 on my vps.

Slowly, people will start to get it.

@ pro, you know that the eventual system design will encourage every BN to participate in mining right? I tried running 8 off my 8 core box, no such luck. The computing requirements are getting higher, as such for a single core VPS i encourage running only one BN.

Full BN only mining will come in a few weeks, for now my focus has been debugging the existing material , fork resolution and fine tuning the bidding code. Over the next few days , the git will light up once again with more code and fixes as i start work towards 0.30.18

[dextronomous]

015-09-19 16:14:01 Locking Banknodes:
2015-09-19 16:14:01 fEnableDarksend 0
2015-09-19 16:14:01 fLiteMode 0
2015-09-19 16:14:01 nInstantXDepth 5
2015-09-19 16:14:01 Darksend rounds 2
2015-09-19 16:14:01 Anonymize Bitcredit Amount 2000
2015-09-19 16:14:01 Secure messaging starting.
2015-09-19 16:14:01 Error opening file: No such file or directory (877)
2015-09-19 16:14:01 Failed to read smsg.ini
2015-09-19 16:14:01 No address keys loaded.
2015-09-19 16:14:01 Processed 0 files, loaded 0 buckets containing 0 messages.
2015-09-19 16:14:01 Secure messaging enabled.
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
2015-09-19 16:14:03 GUI: "registerShutdownBlockReason: Successfully registered: Bitcredit Core didn't yet exit safely..."
2015-09-19 16:14:03

one of my wanting to try second wallets, that won't start has got this inside the debug.log.

how to get rid off this smsg.ini or not important

[proletariat]

I've been telling people for 18 months that a single crappy old celeron could handle the entire Bitcoin blockchain with ease, and probably that of every other active altcoin simultaneously. They look at me (or type at me anyway) like I'm crazy for thinking that anything under a petawatt's worth of compute power could possibly cope.

Anyway, BCR's blockchain is currently humming along on a bit more than one crappy celeron, but not much - ("networkhashps" : 1,) - and I just squeezed over 300 txes into block 205593 and ... no issues, surprise. I shall be consolidating the rest of my BN payments shortly.  

Competitive PoW is utterly fucking daft.  


Also, it occurs to me that another aspect of BCR being, among other things, a (worlds first?) p2p hedge fund is that assuming the bid price follows to some extent the market price, any pumping will result in permanently locked in value.

BCR is one of a very few (Xaurum, backed by gold?) cryptocurrencies that can't be dumped to zero, assuming any of the underlying assets still have market value.

I'm confused. When I have a BN running do I setgenerate true or how is it "BN only mining"? also, are all your nodes running from the same machine? because i gave up yesterday trying to run more than 2 on my vps.

Slowly, people will start to get it.

@ pro, you know that the eventual system design will encourage every BN to participate in mining right? I tried running 8 off my 8 core box, no such luck. The computing requirements are getting higher, as such for a single core VPS i encourage running only one BN.

Full BN only mining will come in a few weeks, for now my focus has been debugging the existing material , fork resolution and fine tuning the bidding code. Over the next few days , the git will light up once again with more code and fixes as i start work towards 0.30.18

I see.
Yes I knew BN mining would eventually be encouraged I just didn't know if there was an actual command to make the BN mine or just by simply running the QT. Also will a cold node setup work aswell? or does the BN need to be running with the wallet.dat holding the funds in order to mine?