◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈

[jasemoney]

someone on the 210001-210003 chain could dump the block hash(s) and we could checkpoint the fork block maybe? also we could put up a bootstrap blocks chainstate folder for windows users when the 17.3 win wallets ready so they can sync easy. consider making this a harder fork by making a larger diff retarget down per block to get us on track quicker? heck if bittrex was working i could set up another 2 banknodes to mine against

[dextronomous]

so who's got a working 30173 version or 30172 version that accepts blocks from 30173?

 cause no one has got the 030.17.3 version besides a few, blocks out of that one aren't showing inside 030172 and or other way around !

211008 this should be the longest chain not on version 3 but on 2? i guess.

chainz is at 210004 still for several hours. any compiled version on that last one>
guess the test version is not the one with version .3 but still v0.30.17.2-alpha

thanks will go to sleep after a nice answer

[jasemoney]

if theres no win based 30.17.3 in the next few hours ill try and dig up a virtual machine and import my banknode to a linux build to try and move this forward. fingers crossed for a win build.

[alganonim]

Tried to sync newest wallet in ubuntu, even clean from the start , still sync to 210000 then stops.
Which addnodes to use, this from chainz :

addnode=146.90.136.80
addnode=188.193.114.167

or previous, old once ? Used the first and nothing.

[bitcreditscc]

someone on the 210001-210003 chain could dump the block hash(s) and we could checkpoint the fork block maybe? also we could put up a bootstrap blocks chainstate folder for windows users when the 17.3 win wallets ready so they can sync easy. consider making this a harder fork by making a larger diff retarget down per block to get us on track quicker? heck if bittrex was working i could set up another 2 banknodes to mine against

It's quite alright. mining is not an issue right now, there was a problem with a premature pointer that has been resolved, so sync from the start is not an issue anymore, also since we had already slowed down i'm taking the time to try and find the causes of the many issues raised. IN a few hours the net will be moving smoothly again as diff has already adjusted down.

[jasemoney]

someone on the 210001-210003 chain could dump the block hash(s) and we could checkpoint the fork block maybe? also we could put up a bootstrap blocks chainstate folder for windows users when the 17.3 win wallets ready so they can sync easy. consider making this a harder fork by making a larger diff retarget down per block to get us on track quicker? heck if bittrex was working i could set up another 2 banknodes to mine against

It's quite alright. mining is not an issue right now, there was a problem with a premature pointer that has been resolved, so sync from the start is not an issue anymore, also since we had already slowed down i'm taking the time to try and find the causes of the many issues raised. IN a few hours the net will be moving smoothly again as diff has already adjusted down.

ok ill just wait for the formal release (win binaries) to get running again.

[alganonim]

There's no need to donwload the whole blockchain, I had used some chain before 210000 block.

In debug.log found out that some nodes even if are in official chainz Node List for /Section32:0.30.17.3/ are misbehaving , so I deleted them :


188.193.114.167
91.230.123.101:8877 (nodes on a a previous version and on wrong block)
91.230.123.11:8877

only left:
41.191..238.238.189 (looks like 2 first nodes are inactive)
82.211.1.181.:8877
146.90.136.80 (this is good)

This looks like state for now and can change in second, but I finally am in sync at block 210004  

[thelonecrouton]

146.90.136.80 (this is good)

This looks like state for now and can change in second, but I finally am in sync at block 210004  

Thanks.

Weirdly, after crashing my laptop earlier playing with Blender, I'm only able to sync back up to 210001...

[bitcreditscc]

146.90.136.80 (this is good)

This looks like state for now and can change in second, but I finally am in sync at block 210004  

Thanks.

Weirdly, after crashing my laptop earlier playing with Blender, I'm only able to sync back up to 210001...

One of the issues that held me up all this time. I'm fairly confident we are fine now, though users who deviate from instructions will suffer forks.

Strange....i had two catastrophic crashes this weekend  HHDs screwed, lost 100K  BCR in the mining wallets.

To avoid being slowed down by my old hdds i'm gonna open up my private nodes top the public again.

After this we have a big issue to discuss.

[antonio8]

Silly question as I am behind and just catching up.

Which is the current version of working wallet we should be using? Wallet Links  -- Current Version 0.30.17.2 from the OP or 0.30.17.2.-fixssl from the last version in the thread?

[bitcreditscc]

Silly question as I am behind and just catching up.

Which is the current version of working wallet we should be using? Wallet Links  -- Current Version 0.30.17.2 from the OP or 0.30.17.2.-fixssl from the last version in the thread?

just give me a moment to give the all clear, im currently looking over the voting code again, i want to avoid further minor patches

[dragos_bdi]

0.30.17.3
Windows 64bit - update commit 8b76deb82f

0.30.17.3.164bit-8b76deb82f.7z
https://mega.nz/#!bs0kDZKA!fMol_D_qPJJglLhVMwMZG7hSejBa6yqEgcCz_E0hskY

[doesntmatter]

without block movement no more network or transfers... lol
i can't make the transfer required to setup a node... !!!
new wallet can't sync, even though it is... 210004!!! 27 hours behind
this is so much better than me getting blocks! LOL

doesntmatter

[jasemoney]

0.30.17.3
Windows 64bit - update commit 8b76deb82f

0.30.17.3.164bit-8b76deb82f.7z
https://mega.nz/#!bs0kDZKA!fMol_D_qPJJglLhVMwMZG7hSejBa6yqEgcCz_E0hskY

runs and starts fine, used an olde blockchain copy from before 210000 it synced to 210000 real quick but hasnt gotten past it, ive tried the 18.3 nodes listed on chainz. no love

*edit i got it synced on 210004 had to remove then replace my wallet file and synce from before 210000 again.


PROBLEM===

the build linked above crashes any time i do setgenerate true 1
also in case it needs to be a banknode.. since the chain is so far behind, it wont let me start my banknode as its still "syncing"
so i guess hopefully someone solves a block :/

[proletariat]

0.30.17.3
Windows 64bit - update commit 8b76deb82f

0.30.17.3.164bit-8b76deb82f.7z
https://mega.nz/#!bs0kDZKA!fMol_D_qPJJglLhVMwMZG7hSejBa6yqEgcCz_E0hskY

Your last 'test' build didn't crash a single time. This one does, not with a new fresh wallet.dat though.

[bitcreditscc]

0.30.17.3
Windows 64bit - update commit 8b76deb82f

0.30.17.3.164bit-8b76deb82f.7z
https://mega.nz/#!bs0kDZKA!fMol_D_qPJJglLhVMwMZG7hSejBa6yqEgcCz_E0hskY

Your last 'test' build didn't crash a single time. This one does, not with a new fresh wallet.dat though.

can confirm this, tried to setup a node. no dice. If the transaction view is causing this maybe we should separate it from the main view..or disable it until a user requests to see the list?

[thelonecrouton]

0.30.17.3
Windows 64bit - update commit 8b76deb82f

0.30.17.3.164bit-8b76deb82f.7z
https://mega.nz/#!bs0kDZKA!fMol_D_qPJJglLhVMwMZG7hSejBa6yqEgcCz_E0hskY

Your last 'test' build didn't crash a single time. This one does, not with a new fresh wallet.dat though.

can confirm this, tried to setup a node. no dice. If the transaction view is causing this maybe we should separate it from the main view..or disable it until a user requests to see the list?

Transaction view isn't causing any probs on linux (never has) compiled from the latest master, but can't restart BN despite being synced up to 210004, "banknode start" and "banknode debug" give me:

"sync in process. Must wait until client is synced to start."

[dextronomous]

  still working better than the test version that one was syncin with the highest blockchain.

this one isn;t direct hit from only good peers. one error with startup, but i didn;t check admin rights just started it, win7 compatibility mode neither,,
still second try started like a charm, or did also use my own wallet.dat file that is 40mb sized, with my own conf.file and mybanknodes.txt, and in total 20 files in my bitcredit folder.

think is syncin really fast as well. bid, back shows everything i guess, amount of blocks, not the bids,
if wan't to debug just /add /debug in your shortcut,. creates might create very big debug.log file inside your folder.

what is in options? advertised balance, what should i type there, just 1million?
how does it work?

thanks in advance guys

[bitcreditscc]

I'm almost done, all that remains is resolving 2 conflicts that are happening during initial sync.

The BN requirement is preventing nodes from fully syncing @ start. I can';t just overlook with a switch because that opens up potential avenue for exploits. Neither can we just bootstrap, it has to sync fro start for it to be a viable solution.

[doesntmatter]

so this will happen anytime there is an update?  it doesn't update the node list cause it won't sync...

is there a way you can tell it to relax some of the rules if the blocktime is to far out?  or are we going to have to hardfork?