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.
Topic: ◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈ - page 97. (Read 284526 times)
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.
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?
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.
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.
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.
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.
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.
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
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.
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.
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.
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 ...
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.
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.
on the advice of a fellow more wizened coder, i am studying OP_RETURN and trying to figure out how each BN can use it to
1) Register itself on the chain
2) Sign Blocks
This will take some time and some doing but seems far more cryptographically accurate that just a look up of previous blocks.
The final decision will be made based on
1) Complexity
2) Security
3) Computational cost
For now i'll tentatively say that we are likely to institute the changes in two weeks. For now there is an update incoming (next few hours ) that should finally settle bid payouts.
Because p2pool is not respecting payout blocks , i am working on a new rule that will ensure that they are respected by the network
Latest Win 64 build https://mega.nz/#!rp9DULoK!nBLgm1zNCdjaDhcAsJ-4bMfSDuy-keZMhQIAJ6BddKs
Bitcreditscc, please update OP
Thanks, but wish you had waited a bit, got some code i am pushing to master in the hour that finishes the move to version 0.30.17. I promised voting so now i am delivering 
I guess i'll have to do a write up of it as well.
Sorry, I will rebuild again after you finish
All good, we are done now , you can build.
Meanwhile i almost have an android -QT build, save for one error
0.30.17.1 Download Link: https://mega.nz/#!LxNWwR6B!W35jyDBy5QiV9B-iT5OL46NwYWmVASJC2tI8cNjgWik
Nice work!
Going to check it out now
on the advice of a fellow more wizened coder, i am studying OP_RETURN and trying to figure out how each BN can use it to
1) Register itself on the chain
2) Sign Blocks
This will take some time and some doing but seems far more cryptographically accurate that just a look up of previous blocks.
The final decision will be made based on
1) Complexity
2) Security
3) Computational cost
For now i'll tentatively say that we are likely to institute the changes in two weeks. For now there is an update incoming (next few hours ) that should finally settle bid payouts.
Because p2pool is not respecting payout blocks , i am working on a new rule that will ensure that they are respected by the network
Latest Win 64 build https://mega.nz/#!rp9DULoK!nBLgm1zNCdjaDhcAsJ-4bMfSDuy-keZMhQIAJ6BddKs
Bitcreditscc, please update OP
Thanks, but wish you had waited a bit, got some code i am pushing to master in the hour that finishes the move to version 0.30.17. I promised voting so now i am delivering I guess i'll have to do a write up of it as well.
Sorry, I will rebuild again after you finish
All good, we are done now , you can build.
Meanwhile i almost have an android -QT build, save for one error
0.30.17.1 Download Link: https://mega.nz/#!LxNWwR6B!W35jyDBy5QiV9B-iT5OL46NwYWmVASJC2tI8cNjgWik
on the advice of a fellow more wizened coder, i am studying OP_RETURN and trying to figure out how each BN can use it to
1) Register itself on the chain
2) Sign Blocks
This will take some time and some doing but seems far more cryptographically accurate that just a look up of previous blocks.
The final decision will be made based on
1) Complexity
2) Security
3) Computational cost
For now i'll tentatively say that we are likely to institute the changes in two weeks. For now there is an update incoming (next few hours ) that should finally settle bid payouts.
Because p2pool is not respecting payout blocks , i am working on a new rule that will ensure that they are respected by the network
Latest Win 64 build https://mega.nz/#!rp9DULoK!nBLgm1zNCdjaDhcAsJ-4bMfSDuy-keZMhQIAJ6BddKs
Bitcreditscc, please update OP
Thanks, but wish you had waited a bit, got some code i am pushing to master in the hour that finishes the move to version 0.30.17. I promised voting so now i am delivering I guess i'll have to do a write up of it as well.
Sorry, I will rebuild again after you finish
All good, we are done now , you can build.
Meanwhile i almost have an android -QT build, save for one error
on the advice of a fellow more wizened coder, i am studying OP_RETURN and trying to figure out how each BN can use it to
1) Register itself on the chain
2) Sign Blocks
This will take some time and some doing but seems far more cryptographically accurate that just a look up of previous blocks.
The final decision will be made based on
1) Complexity
2) Security
3) Computational cost
For now i'll tentatively say that we are likely to institute the changes in two weeks. For now there is an update incoming (next few hours ) that should finally settle bid payouts.
Because p2pool is not respecting payout blocks , i am working on a new rule that will ensure that they are respected by the network
Latest Win 64 build https://mega.nz/#!rp9DULoK!nBLgm1zNCdjaDhcAsJ-4bMfSDuy-keZMhQIAJ6BddKs
Bitcreditscc, please update OP
Thanks, but wish you had waited a bit, got some code i am pushing to master in the hour that finishes the move to version 0.30.17. I promised voting so now i am delivering I guess i'll have to do a write up of it as well.
Sorry, I will rebuild again after you finish
.............
The crashes in QT are as a result of some race condition, these aren't easy to identify , but i'll try. Wish i was better at multi-threading.
The crashes in QT are as a result of some race condition, these aren't easy to identify , but i'll try. Wish i was better at multi-threading.
I truly struggled to get my nodes running because my main wallet with all the nodes info would crash on "done loading" I tried deleting everything, then one thing at a time but I always kept my wallet.dat So then I tried it with a new wallet and it worked OK... got my wallet back in there and it worked fine until i restarted the qt one of those times with the stuck network and again it crashed, returned to an empty wallet.dat and let it sync the latest one or two blocks missing.... returned to my old wallet.dat and again it worked alright. I'm my zero technical knowledge, I'd say there's 1% chance of it something to do with the wallet.dat
What could be different with my wallet.dat? perhaps the multiple BN setup in one single wallet, other than that I wouldn't know.
Do you have your wallet and data in default catalog (...appdata/roaming/bitcredit) or in custom? My default one is crashing often after closing, but custom works without problems. So win 8.1 has problem with elevated rights in these exes. Of course compatibility mode set to win 7 and run as admin in both cases.
Maybe some stupid Antivirus like defender or avast is messing with it.
@dev
Is this update mandatory or optional (bid fix only), I'm out of home till tomorrow.
Yes this is a mandatory update with bidding fixes going into effect immediately,
0.30.17.1 features
-fixed bidding for solo mining
-InstantX activation @ block 210000
- Voting system @ 210000
- Basics for Internal User/BN rating system
- Clean ups in lots of areas (fixed some random segfaulting)
Final push should be ready after hack finishes reading through.
.............
The crashes in QT are as a result of some race condition, these aren't easy to identify , but i'll try. Wish i was better at multi-threading.
The crashes in QT are as a result of some race condition, these aren't easy to identify , but i'll try. Wish i was better at multi-threading.
I truly struggled to get my nodes running because my main wallet with all the nodes info would crash on "done loading" I tried deleting everything, then one thing at a time but I always kept my wallet.dat So then I tried it with a new wallet and it worked OK... got my wallet back in there and it worked fine until i restarted the qt one of those times with the stuck network and again it crashed, returned to an empty wallet.dat and let it sync the latest one or two blocks missing.... returned to my old wallet.dat and again it worked alright. I'm my zero technical knowledge, I'd say there's 1% chance of it something to do with the wallet.dat
What could be different with my wallet.dat? perhaps the multiple BN setup in one single wallet, other than that I wouldn't know.
It's not you, it's QT. somewhere in there are are threads that are running concurrently and every time A beats B to the finish it crashes. We'll find it, one way or the other and resolve.
on the advice of a fellow more wizened coder, i am studying OP_RETURN and trying to figure out how each BN can use it to
1) Register itself on the chain
2) Sign Blocks
This will take some time and some doing but seems far more cryptographically accurate that just a look up of previous blocks.
The final decision will be made based on
1) Complexity
2) Security
3) Computational cost
For now i'll tentatively say that we are likely to institute the changes in two weeks. For now there is an update incoming (next few hours ) that should finally settle bid payouts.
Because p2pool is not respecting payout blocks , i am working on a new rule that will ensure that they are respected by the network
Latest Win 64 build https://mega.nz/#!rp9DULoK!nBLgm1zNCdjaDhcAsJ-4bMfSDuy-keZMhQIAJ6BddKs
Bitcreditscc, please update OP
Thanks, but wish you had waited a bit, got some code i am pushing to master in the hour that finishes the move to version 0.30.17. I promised voting so now i am delivering I guess i'll have to do a write up of it as well.
Sent my bid 
@Bitcreditscc
Do you have the text from the ann images and logo in vector format? I'm in no way a pro but I'd like to fiddle around with the ann to see if I can make it more visually appealing.
@Bitcreditscc
Do you have the text from the ann images and logo in vector format? I'm in no way a pro but I'd like to fiddle around with the ann to see if I can make it more visually appealing.
I don't think so but i'll try find a way to get you access to the site where it is stored in its individual components.
.............
The crashes in QT are as a result of some race condition, these aren't easy to identify , but i'll try. Wish i was better at multi-threading.
The crashes in QT are as a result of some race condition, these aren't easy to identify , but i'll try. Wish i was better at multi-threading.
I truly struggled to get my nodes running because my main wallet with all the nodes info would crash on "done loading" I tried deleting everything, then one thing at a time but I always kept my wallet.dat So then I tried it with a new wallet and it worked OK... got my wallet back in there and it worked fine until i restarted the qt one of those times with the stuck network and again it crashed, returned to an empty wallet.dat and let it sync the latest one or two blocks missing.... returned to my old wallet.dat and again it worked alright. I'm my zero technical knowledge, I'd say there's 1% chance of it something to do with the wallet.dat
What could be different with my wallet.dat? perhaps the multiple BN setup in one single wallet, other than that I wouldn't know.
Do you have your wallet and data in default catalog (...appdata/roaming/bitcredit) or in custom? My default one is crashing often after closing, but custom works without problems. So win 8.1 has problem with elevated rights in these exes. Of course compatibility mode set to win 7 and run as admin in both cases.
Maybe some stupid Antivirus like defender or avast is messing with it.
@dev
Is this update mandatory or optional (bid fix only), I'm out of home till tomorrow.
I have it on a custom folder but I also tried it with the default on appdata and it would behave the same.
.............
The crashes in QT are as a result of some race condition, these aren't easy to identify , but i'll try. Wish i was better at multi-threading.
The crashes in QT are as a result of some race condition, these aren't easy to identify , but i'll try. Wish i was better at multi-threading.
I truly struggled to get my nodes running because my main wallet with all the nodes info would crash on "done loading" I tried deleting everything, then one thing at a time but I always kept my wallet.dat So then I tried it with a new wallet and it worked OK... got my wallet back in there and it worked fine until i restarted the qt one of those times with the stuck network and again it crashed, returned to an empty wallet.dat and let it sync the latest one or two blocks missing.... returned to my old wallet.dat and again it worked alright. I'm my zero technical knowledge, I'd say there's 1% chance of it something to do with the wallet.dat
What could be different with my wallet.dat? perhaps the multiple BN setup in one single wallet, other than that I wouldn't know.
Do you have your wallet and data in default catalog (...appdata/roaming/bitcredit) or in custom? My default one is crashing often after closing, but custom works without problems. So win 8.1 has problem with elevated rights in these exes. Of course compatibility mode set to win 7 and run as admin in both cases.
Maybe some stupid Antivirus like defender or avast is messing with it.
@dev
Is this update mandatory or optional (bid fix only), I'm out of home till tomorrow.
So 10.35 is now normal fee for BN and 4.05 for BN mining, the last one comes very rare if it has to be this way then BN mining is not much profitable.
.............
The crashes in QT are as a result of some race condition, these aren't easy to identify , but i'll try. Wish i was better at multi-threading.
The crashes in QT are as a result of some race condition, these aren't easy to identify , but i'll try. Wish i was better at multi-threading.
I truly struggled to get my nodes running because my main wallet with all the nodes info would crash on "done loading" I tried deleting everything, then one thing at a time but I always kept my wallet.dat So then I tried it with a new wallet and it worked OK... got my wallet back in there and it worked fine until i restarted the qt one of those times with the stuck network and again it crashed, returned to an empty wallet.dat and let it sync the latest one or two blocks missing.... returned to my old wallet.dat and again it worked alright. I'm my zero technical knowledge, I'd say there's 1% chance of it something to do with the wallet.dat
What could be different with my wallet.dat? perhaps the multiple BN setup in one single wallet, other than that I wouldn't know.
on the advice of a fellow more wizened coder, i am studying OP_RETURN and trying to figure out how each BN can use it to
1) Register itself on the chain
2) Sign Blocks
This will take some time and some doing but seems far more cryptographically accurate that just a look up of previous blocks.
The final decision will be made based on
1) Complexity
2) Security
3) Computational cost
For now i'll tentatively say that we are likely to institute the changes in two weeks. For now there is an update incoming (next few hours ) that should finally settle bid payouts.
Because p2pool is not respecting payout blocks , i am working on a new rule that will ensure that they are respected by the network
Latest Win 64 build https://mega.nz/#!rp9DULoK!nBLgm1zNCdjaDhcAsJ-4bMfSDuy-keZMhQIAJ6BddKs
Bitcreditscc, please update OP
Jump to: