◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈

[thelonecrouton]

Hooked up most of this except the redemption bit:



As you can see, bit of a bargain currently.

Clicking the bid addresses opens up your default browser and takes you to that address on blockr.io or dashpay.io, the 'Bid with' buttons will open up bitcredit-qt etc. on linux if the binaries are in your PATH, eg in /usr/bin - supposedly something similar should happen on Win but I can't test that. I've stuck with the official clients for now due to SPV privkey issues, but I can add an option in the conf to put the path to whatever btc/ltc/dash client you like and have it use that in the future. Bid calc works. Superblock countdown works.

@bitcreditscc - I'm assuming that the btcbids/ltcbids/dashbids.dat files get wiped (or should do?) after each superblock? Or should I just get the current superblock numbers from final.dat instead? Or somewhere else?

edit: I should get the current total asset backing and assured min value and stick it somewhere on there too, although maybe that could/should be added on the main page?

[bitcreditscc]

Hooked up most of this except the redemption bit:



Clicking the bid addresses opens up your default browser and takes you to that address on blockr.io or dashpay.io, the 'Bid with' buttons will open up bitcredit-qt etc. on linux if the binaries are in your PATH, eg in /usr/bin - supposedly something similar should happen on Win but I can't test that. I've stuck with the official clients for now due to SPV privkey issues, but I can add an option in the conf to put the path to whatever btc/ltc/dash client you like and have it use that in the future. Bid calc works. Superblock countdown works.

@bitcreditscc - I'm assuming that the btcbids/ltcbids/dashbids.dat files get wiped after each superblock? Or should I just get the numbers from final.dat instead?

GREAT!! yeah they do get wiped, but that can be changed if you need it. Can you re-base your work on the latest master, i have changed how the values of the bids are represented in the bid file to ensure accurate payouts. Instead of fractions of BTC they are now represented as satoshis.

btw, only one error is preventing me from completing a android-QT build, very frustrating.

edit;- actually, get it from final.dat, it's getting updated every 5 minutes now so it's pretty accurate.

[thelonecrouton]

.Can you re-base your work on the latest master, i have changed how the values of the bids are represented in the bid file to ensure accurate payouts. Instead of fractions of BTC they are now represented as satoshis.

...

edit;- actually, get it from final.dat, it's getting updated every 5 minutes now so it's pretty accurate.

Suits me, one file to parse beats three. Will have another bout tomorrow, need sleep.

BTW am I correct in thinking that if you bid from the same btc/ltc/dash address you should only need to do the importprivkey thing once?

[bitcreditscc]

.Can you re-base your work on the latest master, i have changed how the values of the bids are represented in the bid file to ensure accurate payouts. Instead of fractions of BTC they are now represented as satoshis.

...

edit;- actually, get it from final.dat, it's getting updated every 5 minutes now so it's pretty accurate.

Suits me, one file to parse beats three. Will have another bout tomorrow, need sleep.

BTW am I correct in thinking that if you bid from the same btc/ltc/dash address you should only need to do the importprivkey thing once?

Yes, that is correct. It seems only a few spv wallets use different key types. I'll be looking into that in depth this weekend. May also try to write rpc commands for more stuff that seems to be GUI only.

Depending on progress over the next two days, maybe sunday will see the first multi-bn code going up.

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.

[proletariat]

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.

[dragos_bdi]

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

[proletariat]

.............

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.

[alganonim]

.............

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.

[proletariat]

.............

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.

[bitcreditscc]

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.

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.

[bitcreditscc]

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.

[bitcreditscc]

.............

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.

[bitcreditscc]

.............

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.

[dragos_bdi]

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 

[bitcreditscc]

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 

[dragos_bdi]

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

[starblocks]

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

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

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

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