◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈

[alganonim]

I got again "Exception caught basic_string::substr: __pos (which is 18446744073709551615) > this->size() (which is 74)" on one of my virtual ubuntu wallet, found this out but it didn't helped me much http://stackoverflow.com/questions/2258900/unexplained-out-of-range-in-stringsubstr

1. Vanity options are inactive yet ? Patterns field can't be filled with anything.
2. Arleady reported but "start mining" everytime results with wallet crashing.

Tried it with empty wallet, the same results, I know thats WIP, but so far the latest version is unstable for me even stuck sometimes after starting wallet.
Sometimes when wallet crashes and you try to kill it with terminal - grantdb is still building which can be checked in debug.txt, waiting for it to fininsh results in crash anyway.

After few weeks of testing, bootstrap swaping and comparing, it's obvious that linux wallet is more stable than windows version, but it didn't saved me from one bn wallet corruption.
Everything goes well until I try to send some coins, crash after passphrase and so on ... after clean start with bootstrap the same on both win and linux, no fear cause I got backup and it worked.

Are you building from master branch ? have you pulled the commits fro the last two days, in case you are working of dev branch? 

I have not seen "rc 2" before, so I was using "working rc"  https://github.com/bitcreditscc/bicreditsnew/commit/138cbedad47edae0d37bd955e50ed32e48a0dca6 till now, will try rc2 but only on virtual test machine.

This was also reported previously but last working windows wallets are stopping at some blocks and stops bn-mining, strange but they look to be in-sync till you check actual last block and restart them, then you got to bootstrap again or download all blockchain. These are empty wallets destined to bn-mining only, all settings done: bnmininkey in conf, miningkeys.dat set and in place.

[bitcreditscc]

I got again "Exception caught basic_string::substr: __pos (which is 18446744073709551615) > this->size() (which is 74)" on one of my virtual ubuntu wallet, found this out but it didn't helped me much http://stackoverflow.com/questions/2258900/unexplained-out-of-range-in-stringsubstr

1. Vanity options are inactive yet ? Patterns field can't be filled with anything.
2. Arleady reported but "start mining" everytime results with wallet crashing.

Tried it with empty wallet, the same results, I know thats WIP, but so far the latest version is unstable for me even stuck sometimes after starting wallet.
Sometimes when wallet crashes and you try to kill it with terminal - grantdb is still building which can be checked in debug.txt, waiting for it to fininsh results in crash anyway.

After few weeks of testing, bootstrap swaping and comparing, it's obvious that linux wallet is more stable than windows version, but it didn't saved me from one bn wallet corruption.
Everything goes well until I try to send some coins, crash after passphrase and so on ... after clean start with bootstrap the same on both win and linux, no fear cause I got backup and it worked.

Are you building from master branch ? have you pulled the commits fro the last two days, in case you are working of dev branch? 

I have not seen "rc 2" before, so I was using "working rc"  https://github.com/bitcreditscc/bicreditsnew/commit/138cbedad47edae0d37bd955e50ed32e48a0dca6 till now, will try rc2 but only on virtual test machine.

This was also reported previously but last working windows wallets are stopping at some blocks and stops bn-mining, strange but they look to be in-sync till you check actual last block and restart them, then you got to bootstrap again or download all blockchain. These are empty wallets destined to bn-mining only, all settings done: bnmininkey in conf, miningkeys.dat set and in place.

Ok, the bnminingkey has been removed, only "miningkeys" is necessary. I'm not sure why it would stop, but i'll look into it. I havent used a windows wallet since i started working on the UI again, so i'll let you know when i have tested.

[alganonim]

So bnminingkey is removed since RC2 version or earlier, got to know this because don't know if it is needed in Windows version, latest 0.30.17.6-9cb23de-dirty (64-bit),  linux ver. is at 0.30.17.8-rc2 now.

EDIT:

Thanx I get it, straight answers will be enough for me , so it's since RC2.

[bitcreditscc]

So bnminingkey is removed since RC2 version or earlier, got to know this because don't know if it is needed in Windows version, latest 0.30.17.6-9cb23de-dirty (64-bit),  linux ver. is at 0.30.17.8-rc2 now.

linux is always a step ahead because that is developers' enviroment. we are going to dedicate an update to GUI issues, then another one to just help/support

[tommyj1]

wallet get stuck after a few hours, have to force close it and resync. what to do?

Code:

EXCEPTION: St13runtime_error       
CDB : Error -30974, can't open database        
C:\Users\Desktop\bcr wallet\0.30.17.6-64bit\bitcredit-qt.exe in ProcessMessages()       

2015-10-15 09:08:22 Successfully synced, asking for Banknode list and payment list
2015-10-15 09:08:22 ProcessMessage(block, 289 bytes) FAILED peer=4
2015-10-15 09:08:22 Successfully synced, asking for Banknode list and payment list
2015-10-15 09:08:22 Successfully synced, asking for Banknode list and payment list
2015-10-15 09:08:22 Successfully synced, asking for Banknode list and payment list
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-10-15 12:50:51 GUI: "registerShutdownBlockReason: Successfully registered: Bitcredit Core didn't yet exit safely..."

[dragos_bdi]

FOR TESTING ONLY !!!

Blockchain Bootstrap @217702
Download Link: https://mega.nz/#!C9d1wBiL!eHzZM5SwVzKw5XQLkxek4WvgjS1GfETrB-lhIK2DmY0

Windows 64bit Wallet - 0.30.17.8-rc2
Downlaod Link: https://mega.nz/#!TwtCzTSY!32mON-XoNgcFKcofReeV0Kj1_d7SXrYwQeopx3RtPRo

[jasemoney]

FOR TESTING ONLY !!!

Blockchain Bootstrap @217702
Download Link: https://mega.nz/#!C9d1wBiL!eHzZM5SwVzKw5XQLkxek4WvgjS1GfETrB-lhIK2DmY0

Windows 64bit Wallet - 0.30.17.8-rc2
Downlaod Link: https://mega.nz/#!TwtCzTSY!32mON-XoNgcFKcofReeV0Kj1_d7SXrYwQeopx3RtPRo

your links are missing the ":" colon in http:// when firefox is pointed to them (donno it was weird)

[alganonim]

FOR TESTING ONLY !!!

Blockchain Bootstrap @217702


Windows 64bit Wallet - 0.30.17.8-rc2

Thanx

I guess that splashing version info at start of the wallet is not changed, so it still shows 0.30.17.6-337389b-dirty or I messed something ?

[dragos_bdi]

FOR TESTING ONLY !!!

Blockchain Bootstrap @217702


Windows 64bit Wallet - 0.30.17.8-rc2

Thanx

I guess that splashing version info at start of the wallet is not changed, so it still shows 0.30.17.6-337389b-dirty or I messed something ?

Still ...

[bitcreditscc]

version number will be bumped after a few more tweaks

[alganonim]

I give up for now with bn-mining, it's a waste of my time. 4 Windows and 1 VM Ubuntu machine constantly spilling with "EXCEPTION:12bignum_error
CBigNum:operator/ : BN_div failed" or  St12 , St13 Exceptions, sometimes they work for some time with blockchain in sync but stop mining, it's easy to check, when processes are using less than 20 % of CPU and less than 800MB of ram.

[Nik4691]

FOR TESTING ONLY !!!

Blockchain Bootstrap @217702
Download Link: https://mega.nz/#!C9d1wBiL!eHzZM5SwVzKw5XQLkxek4WvgjS1GfETrB-lhIK2DmY0

Windows 64bit Wallet - 0.30.17.8-rc2
Downlaod Link: https://mega.nz/#!TwtCzTSY!32mON-XoNgcFKcofReeV0Kj1_d7SXrYwQeopx3RtPRo

Thanks dragos_bdi.
That strange feeling again... The wallet didn't crash.
It opens every time, as it should.
I open it frequently just for fun 

[hack_]

I give up for now with bn-mining, it's a waste of my time. 4 Windows and 1 VM Ubuntu machine constantly spilling with "EXCEPTION:12bignum_error
CBigNum:operator/ : BN_div failed" or  St12 , St13 Exceptions, sometimes they work for some time with blockchain in sync but stop mining, it's easy to check, when processes are using less than 20 % of CPU and less than 800MB of ram.

Ignore the exception, it only means the bidtracker was unable to retrieve all data. The falling out of sync issue is likely connection related, make sure you aren't just connected to one peer or multiple peers on outgoing connections only.

[hack_]

Things are quiet in this thread, dev do something ! 

[alganonim]

I give up for now with bn-mining, it's a waste of my time. 4 Windows and 1 VM Ubuntu machine constantly spilling with "EXCEPTION:12bignum_error
CBigNum:operator/ : BN_div failed" or  St12 , St13 Exceptions, sometimes they work for some time with blockchain in sync but stop mining, it's easy to check, when processes are using less than 20 % of CPU and less than 800MB of ram.

Ignore the exception, it only means the bidtracker was unable to retrieve all data. The falling out of sync issue is likely connection related, make sure you aren't just connected to one peer or multiple peers on outgoing connections only.

I can't ignore this exceptions because it ends with bn-mining stoping or wallet crashing even on ubuntu. This is only about individual pcs but on rather good connection, yeah firewalls, routers, etc. could be connected with this problems, but I cannot avoid that.

Remote BNs on VPS are stable as never (I don't bn-mine on it), but only on latest master branch wallet, previous test versions gave me a headache, so I will not try latest test version on it.

So to sum it up, now I am testing latest version (master or rc) on individual pcs, when it's stable enough then it goes to BNs on VPS, if not then I will stay with previous version.

[dextronomous]

what with that vanity thingy, what to do with that.
This market is in danger of de-listing due to low trade volume and lack of user interest. It may be removed on October 23rd unless the average daily trade volume for the last 7 days exceeds 0.2 BTC.
someone anyone still buying that shit out of 0.2btc. my .5 already ready to buy in jiffy,


edit nice to see trading started again at trex..

[cisahasa]

static const unsigned int DEFAULT_MAX_ORPHAN_TRANSACTIONS = 100;

this makes my old lap top cpu usage to 100%+++

 

I have and 8350 + 8GB ram running 40 instances of the wallet, no problems.

so could i do at same setup.. no problems
512mb ram slow celeron, 100 orpahans and client is stuck.
if there is a problems debug will name multiple orphans as 101, different hash. <--loop is ready.

we had same issue with hexx, had to fix it because of some service running on low end servers.
not sure about your coin but check this, blackcoin had this problem already.
i did not believe it until i tried it my self.

[LucD88]

FOR TESTING ONLY !!!

Blockchain Bootstrap @217702
Download Link: https://mega.nz/#!C9d1wBiL!eHzZM5SwVzKw5XQLkxek4WvgjS1GfETrB-lhIK2DmY0

Windows 64bit Wallet - 0.30.17.8-rc2
Download Link: https://mega.nz/#!TwtCzTSY!32mON-XoNgcFKcofReeV0Kj1_d7SXrYwQeopx3RtPRo

There was a double http:// in the links, fixed them in the quote above.

Testing as we speak!

[LucD88]

FOR TESTING ONLY !!!

Blockchain Bootstrap @217702
Download Link: https://mega.nz/#!C9d1wBiL!eHzZM5SwVzKw5XQLkxek4WvgjS1GfETrB-lhIK2DmY0

Windows 64bit Wallet - 0.30.17.8-rc2
Download Link: https://mega.nz/#!TwtCzTSY!32mON-XoNgcFKcofReeV0Kj1_d7SXrYwQeopx3RtPRo

There was a double http:// in the links, fixed them in the quote above.

Testing as we speak!

My quick test results on Windows 8.1 Pro x64 & Windows 10 Pro x64:

Wallet version: v0.30.17.8-rc2

[V] Open/close wallet 20 times, crashes: 0!
[V] With Bootstrap: Succesfully synced 100% (same block height [220402] as the Block Explorer)
[V] Without Bootstrap: Succesfully synced 100% (same block height [220402] as the Block Explorer)

Getinfo:

Code:

"version" : 301706,
"protocolversion" : 70013,
"walletversion" : 60000,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 220402,
"timeoffset" : 0,
"connections" : 1,
"proxy" : "",
"difficulty" : 0.00000051,
"testnet" : false,
"keypoololdest" : 1445084806,
"keypoolsize" : 2,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""

Does the wallet have hardcoded nodes? Because I never added any nodes in the config file, yet it synced succesfully.

[dragos_bdi]

Does the wallet have hardcoded nodes? Because I never added any nodes in the config file, yet it synced succesfully.

Yes.