◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈

[jasemoney]

Small like 32kb it was a clean install fresh wallet no tx's

left it open, looks like it cleared the issue after some time, the log had a lot of update chain tips. Either way it went back in time from 4 weeks to 9 weeks. seeing if it will start syncing again.
And looks like it ended up with error connect block invalid block at height 210005.
will restart a few times.

edit to add, looks like ill just try from scratch again overnight.

Bitcreditscc, can you look at the seed nodes you put up? I dont know where to look in the code but have they been hardcoded?
I see 6 out of the 8 nodes i connect to are stuck at 258882 and have been since the recent bootstrap was released.

And something harder to look at would be for the wallet to reject the error for connect invalid block. due to mining key issue. Seems like multiple people have had the issue where if they happen to restart their wallet it sticks at whatever block they were last synced to and wont move forward.

[bitcreditscc]

Small like 32kb it was a clean install fresh wallet no tx's

left it open, looks like it cleared the issue after some time, the log had a lot of update chain tips. Either way it went back in time from 4 weeks to 9 weeks. seeing if it will start syncing again.
And looks like it ended up with error connect block invalid block at height 210005.
will restart a few times.

edit to add, looks like ill just try from scratch again overnight.

Bitcreditscc, can you look at the seed nodes you put up? I dont know where to look in the code but have they been hardcoded?
I see 6 out of the 8 nodes i connect to are stuck at 258882 and have been since the recent bootstrap was released.

And something harder to look at would be for the wallet to reject the error for connect invalid block. due to mining key issue. Seems like multiple people have had the issue where if they happen to restart their wallet it sticks at whatever block they were last synced to and wont move forward.

The restart issue is already resolved , i have been testing the windows build in a vm for almost 12 hours now. Yeah, i am going to remove the stuck seeds i the final rc.

[jasemoney]

Small like 32kb it was a clean install fresh wallet no tx's

left it open, looks like it cleared the issue after some time, the log had a lot of update chain tips. Either way it went back in time from 4 weeks to 9 weeks. seeing if it will start syncing again.
And looks like it ended up with error connect block invalid block at height 210005.
will restart a few times.

edit to add, looks like ill just try from scratch again overnight.

Bitcreditscc, can you look at the seed nodes you put up? I dont know where to look in the code but have they been hardcoded?
I see 6 out of the 8 nodes i connect to are stuck at 258882 and have been since the recent bootstrap was released.

And something harder to look at would be for the wallet to reject the error for connect invalid block. due to mining key issue. Seems like multiple people have had the issue where if they happen to restart their wallet it sticks at whatever block they were last synced to and wont move forward.

The restart issue is already resolved , i have been testing the windows build in a vm for almost 12 hours now. Yeah, i am going to remove the stuck seeds i the final rc.

ok goodluck with testing. will wait for the RC with database beta to attempt fresh sync again.

[bitcreditscc]

Is anyone still having sync issues? make sure you are on the latest version

[alganonim]

Is anyone still having sync issues? make sure you are on the latest version

Maybe not sync but latest demo version still got problem to start and hangs on my win 7 x64 with "loadind wallet" info , from debug.txt

2015-12-09 15:14:22 nFileVersion = 301900
2015-12-09 15:14:22 Keys: 0 plaintext, 0 encrypted, 0 w/ metadata, 0 total
2015-12-09 15:14:23 Performing wallet upgrade to 60000

I had deleted even wallet.dat file before, so it's converting what ? 

[jasemoney]

Is anyone still having sync issues? make sure you are on the latest version

Maybe not sync but latest demo version still got problem to start and hangs on my win 7 x64 with "loadind wallet" info , from debug.txt

2015-12-09 15:14:22 nFileVersion = 301900
2015-12-09 15:14:22 Keys: 0 plaintext, 0 encrypted, 0 w/ metadata, 0 total
2015-12-09 15:14:23 Performing wallet upgrade to 60000

I had deleted even wallet.dat file before, so it's converting what ? 

I let it sit for 10-15 minutes and it finally cleared.

[hack_]

  the diff on the next block

[hack_]

Does anyone support a change to sha256D? momentum is memory heavy , sha256D hashes can be produced easily by smaller power efficient machines such as rasberry pi

[alganonim]

Does anyone support a change to sha256D? momentum is memory heavy , sha256D hashes can be produced easily by smaller power efficient machines such as rasberry pi

Definietly, can't imagine mining on all BNs, it was good theory only on paper or if there was a limit to have only few BNs (yeah I know we are early adopters    )

But still I think that even more important should be resolving the need for multiple cores for mining, I get that I don't have to mine on every BN and I'm thankful for that, consecutive block mining should be stopped also but please correct my logic.

If I use BN mining, find a block then process stops, can't mine for another block, got to execute setgenerate command after some time again (about hour), earlier it wont even start, no one will manage it, then try to do it for multiple BNs.

[dragos_bdi]

Does anyone support a change to sha256D? momentum is memory heavy , sha256D hashes can be produced easily by smaller power efficient machines such as rasberry pi

Definitely no.

This will kill mining. Gpu's, fpga, asics ....

[dragos_bdi]

the diff on the next block

I was afraid of this ... there is not at least 40 50k miners that can found a block ...

[bitcreditscc]

the diff on the next block

I was afraid of this ... there is not at least 40 50k miners that can found a block ...

No that's not it, i have an address with 50K that i set try try mine this block, but the diff is pretty high, may need to use a gpu on this.

[hack_]

Does anyone support a change to sha256D? momentum is memory heavy , sha256D hashes can be produced easily by smaller power efficient machines such as rasberry pi

Definitely no.

This will kill mining. Gpu's, fpga, asics ....

The balance and 40 block limit take care of that

[jasemoney]

looks like you guys got past the hard block.
yes the 40 requirement and collateral make asics fgpas whatever not work for this. but your going to be inviting in people who hate to read and end up pissed they bought hash or tried solo mining when their setup wont allow them to submit a valid block.
not everyone but most people run a vps which can handle 1 thread of momentum. by making keeping it hard to mine your leveling the playing field allowing many people to participate and be rewarded.

anyways so I dont mind momentum, I do mind having to enter setgenerate true after i solve a block. even with multiple keys in miningkeys.dat if i solve a block it cuts off the in wallet miner. if i type setgenerate true again to soon it crashes.  We could really use some internal logic so that the miner restarts after an appropriate ammt of time(blocks past), and also so the in wallet miner recognizes the extra keys, as it doesnt seem to in all cases. some of this might be accoutned for already but in practice it doesnt seem smooth in my experience.

Is anyone using an external cpu only miner solo?

Im guessing all GPU mining is out because there has never been a proper solo mining momentum gpu miner, they all worked on pools.

[hack_]

Oh, yeah, i am using an external miner, just plugged in my gpu ,  no need to worry about "setgenerate true"

Anyone else have ideas about the algorithm? I think that the benefits are pretty obvious, even the dev has been pushing for android versions, sha256 would make mining possible off your old android hardware. We once had a situation where we proved the network could run off a single cpu , why not take that further and make it such that the network can run off any number of low powered devices but still be secure?

[bitcreditscc]

Oh, yeah, i am using an external miner, just plugged in my gpu ,  no need to worry about "setgenerate true"

Anyone else have ideas about the algorithm? I think that the benefits are pretty obvious, even the dev has been pushing for android versions, sha256 would make mining possible off your old android hardware. We once had a situation where we proved the network could run off a single cpu , why not take that further and make it such that the network can run off any number of low powered devices but still be secure?

If it's all the same with you, i'd rather focus on some other issues for now.

[jasemoney]

what miner to solomine or solo gpu mine @ hack_

also whats stopping someone if this was sha from running/renting a Ghash or tons more of sha on BTC for 30 min and BCR for 1 min on a round robin pool setup. no one will be able to compete with that as a solo miner or a phone user. I say phone users only need an app that can do the basic features. if you want phone mining use mangocoins or a pos coin that stakes on your phone. if someone wants to contribute with their phone they can be a banknode if the droid version is like craves phone app was.

anyways theres a lot more to deal with than picking a new algo. the one we have works well enough. sha isnt appropriate for a phone app and neither will momentum be.

[bitcreditscc]

URGENT UPDATE  i discovered a small error , fixed. Also added changes to bidtracker to prevent chain stall when explorers give null values. And lastly the slow sync is now only an issue if you have the -banknode flag on. Otherwise we should return to speedy sync times now.

While i further investigate i encourage everyone to update to 0.30.19.1 and use this bootstrap :- https://codeload.github.com/bitcreditscc/blocks/zip/master

This will become the permanent location of bootstraps, don't clone as it will grow pretty fast, rather download as a zip. You'll also need 7zip as i had to make it multi-volume to comply with github rules.

A windows version is building right now and will be available in a short while both in the OP and in the link i post.

[antonio8]

Does anyone support a change to sha256D? momentum is memory heavy , sha256D hashes can be produced easily by smaller power efficient machines such as rasberry pi

I also disagree.

The raspbery pi will mine for like a day or so before other rigs jump on it.

I can personally raise the difficulty so a raspberry will be useless.

[bitcreditscc]

Does anyone support a change to sha256D? momentum is memory heavy , sha256D hashes can be produced easily by smaller power efficient machines such as rasberry pi

I also disagree.

The raspbery pi will mine for like a day or so before other rigs jump on it.

I can personally raise the difficulty so a raspberry will be useless.

You have 2 M +  BCR