◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈ - page 108.

alganonim

sr. member

Activity: 260

Merit: 250

Quote from: bitcreditscc on August 31, 2015, 05:00:23 AM

Quote from: sawa on August 30, 2015, 01:23:36 AM

I think that in this situation there are two options:
1. Make another fork. Then from 199999 block will turn on the new version of the protocol. And wallets of old and new versions will stop communicating.
2. Or cancel the upgrade and return to the older version of the core.

Hmmm, looking at things from my PoV, the pools are already upgraded according to hack_, the upgraded version works as expected..... i think we should force everyone to upgrade, as most of the stragglers are multiple BN owners who just do not want the hassle.

We had a similar situation where people tried to exploit the compatibility between upgrades , and i think we should forge ahead now like we did then.

I am going to release an minor update that cuts off old clients... If anyone disagrees, i'm open to discuss the issue for the next few hours, but after that we have to act decisively.

I'm glad that I didn't upgraded my BNs so far, because it would ended up with 2x work/time/stress/whatever ... but I'm going to do it now, but please define a time we have left to do it or a specific block ?

Got to plan this and manage somehow, will try to compile a files once again or if fail will look for help ... and I wish You a good health, take care

dragos_bdi

sr. member

Activity: 322

Merit: 250

Quote from: bitcreditscc on August 31, 2015, 05:37:04 AM

Quote from: thelonecrouton on August 31, 2015, 05:13:46 AM

Quote from: bitcreditscc on August 31, 2015, 05:00:23 AM

Quote from: sawa on August 30, 2015, 01:23:36 AM

I think that in this situation there are two options:
1. Make another fork. Then from 199999 block will turn on the new version of the protocol. And wallets of old and new versions will stop communicating.
2. Or cancel the upgrade and return to the older version of the core.

Hmmm, looking at things from my PoV, the pools are already upgraded according to hack_, the upgraded version works as expected..... i think we should force everyone to upgrade, as most of the stragglers are multiple BN owners who just do not want the hassle.

We had a similar situation where people tried to exploit the compatibility between upgrades , and i think we should forge ahead now like we did then.

I am going to release an minor update that cuts off old clients... If anyone disagrees, i'm open to discuss the issue for the next few hours, but after that we have to act decisively.

If you think everything will work, do it.

I am looking forward to placing my first BCR-backing bid.

Thanks for the support, my health is not yet back to 100% but i'll do what i can. It appears the exchange is stuck as well, we'll have to contact them.

Here's how we'll do it:-

The new version will be protocol 70009 on everything and will refuse to connect to older clients, meanwhile i will ask hack_ to upgrade again so that everyone can sync from the pools and avoid issues.

Last time when I checked, the p2pool was not working with the new wallet.

Please update de github and push the enforcing to, let's say 205000.

And we will see if the found it blocks are accepted by the new version.

sawa

legendary

Activity: 1308

Merit: 1011

Quote from: bitcreditscc on August 31, 2015, 05:00:23 AM

Quote from: sawa on August 30, 2015, 01:23:36 AM

I think that in this situation there are two options:
1. Make another fork. Then from 199999 block will turn on the new version of the protocol. And wallets of old and new versions will stop communicating.
2. Or cancel the upgrade and return to the older version of the core.

I am going to release an minor update that cuts off old clients... If anyone disagrees, i'm open to discuss the issue for the next few hours, but after that we have to act decisively.

All right. Absolutely the right choice.

bitcreditscc

hero member

Activity: 602

Merit: 501

Quote from: thelonecrouton on August 31, 2015, 05:13:46 AM

Quote from: bitcreditscc on August 31, 2015, 05:00:23 AM

Quote from: sawa on August 30, 2015, 01:23:36 AM

I think that in this situation there are two options:
1. Make another fork. Then from 199999 block will turn on the new version of the protocol. And wallets of old and new versions will stop communicating.
2. Or cancel the upgrade and return to the older version of the core.

Hmmm, looking at things from my PoV, the pools are already upgraded according to hack_, the upgraded version works as expected..... i think we should force everyone to upgrade, as most of the stragglers are multiple BN owners who just do not want the hassle.

We had a similar situation where people tried to exploit the compatibility between upgrades , and i think we should forge ahead now like we did then.

I am going to release an minor update that cuts off old clients... If anyone disagrees, i'm open to discuss the issue for the next few hours, but after that we have to act decisively.

If you think everything will work, do it.

I am looking forward to placing my first BCR-backing bid.

Thanks for the support, my health is not yet back to 100% but i'll do what i can. It appears the exchange is stuck as well, we'll have to contact them.

Here's how we'll do it:-

The new version will be protocol 70009 on everything and will refuse to connect to older clients, meanwhile i will ask hack_ to upgrade again so that everyone can sync from the pools and avoid issues.

thelonecrouton

legendary

Activity: 966

Merit: 1000

Quote from: bitcreditscc on August 31, 2015, 05:00:23 AM

Quote from: sawa on August 30, 2015, 01:23:36 AM

I think that in this situation there are two options:
1. Make another fork. Then from 199999 block will turn on the new version of the protocol. And wallets of old and new versions will stop communicating.
2. Or cancel the upgrade and return to the older version of the core.

Hmmm, looking at things from my PoV, the pools are already upgraded according to hack_, the upgraded version works as expected..... i think we should force everyone to upgrade, as most of the stragglers are multiple BN owners who just do not want the hassle.

We had a similar situation where people tried to exploit the compatibility between upgrades , and i think we should forge ahead now like we did then.

I am going to release an minor update that cuts off old clients... If anyone disagrees, i'm open to discuss the issue for the next few hours, but after that we have to act decisively.

If you think everything will work, do it.

I am looking forward to placing my first BCR-backing bid.

bitcreditscc

hero member

Activity: 602

Merit: 501

Quote from: sawa on August 30, 2015, 01:23:36 AM

I think that in this situation there are two options:
1. Make another fork. Then from 199999 block will turn on the new version of the protocol. And wallets of old and new versions will stop communicating.
2. Or cancel the upgrade and return to the older version of the core.

Hmmm, looking at things from my PoV, the pools are already upgraded according to hack_, the upgraded version works as expected..... i think we should force everyone to upgrade, as most of the stragglers are multiple BN owners who just do not want the hassle.

We had a similar situation where people tried to exploit the compatibility between upgrades , and i think we should forge ahead now like we did then.

I am going to release an minor update that cuts off old clients... If anyone disagrees, i'm open to discuss the issue for the next few hours, but after that we have to act decisively.

gaazje

sr. member

Activity: 452

Merit: 250

Quote from: sawa on August 30, 2015, 01:23:36 AM

I think that in this situation there are two options:
1. Make another fork. Then from 199999 block will turn on the new version of the protocol. And wallets of old and new versions will stop communicating.
2. Or cancel the upgrade and return to the older version of the core.

in that case I vote for opinion 2

sawa

legendary

Activity: 1308

Merit: 1011

I think that in this situation there are two options:
1. Make another fork. Then from 199999 block will turn on the new version of the protocol. And wallets of old and new versions will stop communicating.
2. Or cancel the upgrade and return to the older version of the core.

bitcreditscc

hero member

Activity: 602

Merit: 501

Hi

sorry, had some personal stuff to deal with. I'm going to take a look and figure out what's wrong. It may take a few hours.

thelonecrouton

legendary

Activity: 966

Merit: 1000

Quote from: sawa on August 28, 2015, 08:53:54 AM

Quote from: thelonecrouton on August 28, 2015, 08:43:55 AM

Quote from: sawa on August 28, 2015, 08:27:28 AM

The problem is that many have not updated the wallet to the new version.

http://crypto.office-on-the.net:8776/ - new version of the wallet. Node is stopped
http://p2pool.website:8776 - new version of the wallet. Node is stopped
http://bcrp2pool.website:8776 - old version, Keep mining blocks with 50BCR value out.
Bitcredit Blockchain Explorer https://chainz.cryptoid.info/bcr/ - old version, shows blocks with 50BCR value out.

Dev, what are we gonna do?

The old and current master branch builds work fine, it's the RC versions that have stopped syncing at block 199999, as the bidding system isn't finalised yet.

Block reward was never meant to change from 50 BCR AFAIK?

From https://github.com/bitcreditscc/bicreditsnew/blob/master/src/main.cpp#L1490

Code:

    if (nHeight> 199999){ 
		nSubsidy = 18* COIN;

Haha, I've been thinking in terms of total daily emission this morning, plotting long term backing values, I'd forgotten about the actual superblocks. Cheesy

Guess we'll await instructions from the boss.

sawa

legendary

Activity: 1308

Merit: 1011

Quote from: thelonecrouton on August 28, 2015, 08:43:55 AM

Quote from: sawa on August 28, 2015, 08:27:28 AM

The problem is that many have not updated the wallet to the new version.

http://crypto.office-on-the.net:8776/ - new version of the wallet. Node is stopped
http://p2pool.website:8776 - new version of the wallet. Node is stopped
http://bcrp2pool.website:8776 - old version, Keep mining blocks with 50BCR value out.
Bitcredit Blockchain Explorer https://chainz.cryptoid.info/bcr/ - old version, shows blocks with 50BCR value out.

Dev, what are we gonna do?

The old and current master branch builds work fine, it's the RC versions that have stopped syncing at block 199999, as the bidding system isn't finalised yet.

Block reward was never meant to change from 50 BCR AFAIK?

From https://github.com/bitcreditscc/bicreditsnew/blob/master/src/main.cpp#L1490

Code:

    if (nHeight> 199999){ 
		nSubsidy = 18* COIN;

thelonecrouton

legendary

Activity: 966

Merit: 1000

Quote from: sawa on August 28, 2015, 08:27:28 AM

The problem is that many have not updated the wallet to the new version.

http://crypto.office-on-the.net:8776/ - new version of the wallet. Node is stopped
http://p2pool.website:8776 - new version of the wallet. Node is stopped
http://bcrp2pool.website:8776 - old version, Keep mining blocks with 50BCR value out.
Bitcredit Blockchain Explorer https://chainz.cryptoid.info/bcr/ - old version, shows blocks with 50BCR value out.

Dev, what are we gonna do?

The old and current master branch builds work fine, it's the RC versions that have stopped syncing at block 199999, as the bidding system isn't finalised yet.

Block reward was never meant to change from 50 BCR AFAIK?

sawa

legendary

Activity: 1308

Merit: 1011

The problem is that many have not updated the wallet to the new version.

http://crypto.office-on-the.net:8776/ - new version of the wallet. Node is stopped
http://p2pool.website:8776 - new version of the wallet. Node is stopped
http://bcrp2pool.website:8776 - old version, Keep mining blocks with 50BCR value out.
Bitcredit Blockchain Explorer https://chainz.cryptoid.info/bcr/ - old version, shows blocks with 50BCR value out.

Dev, what are we gonna do?

gavrilo77

hero member

Activity: 819

Merit: 502

Quote from: LucD88 on August 28, 2015, 03:42:29 AM

The latest wallet gets stuck synchronizing at block 189981, even after starting the wallet with the -reindex parameter. Also when I try to close the wallet it gets stuck at the "Closing the Bitcredit Core wallet..." message, I have to kill the process.

Any clues?

EDIT:
I removed the files inside the data folder and started the wallet again. Whilst having just 1 connection to the network it took a while (~1 hour) but it synchronized a bit further this time. However, I'm stuck again:

{
"version" : 301609,
"protocolversion" : 70008,
"walletversion" : 60000,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 199999,
"timeoffset" : 0,
"moneysupply" : 19594284.99810301,
"connections" : 1,
"proxy" : "",
"difficulty" : 0.00001604,
"testnet" : false,
"keypoololdest" : 1440751523,
"keypoolsize" : 2,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}

Same here

LucD88

hero member

Activity: 525

Merit: 510

The latest wallet gets stuck synchronizing at block 189981, even after starting the wallet with the -reindex parameter. Also when I try to close the wallet it gets stuck at the "Closing the Bitcredit Core wallet..." message, I have to kill the process.

Any clues?

EDIT:
I removed the files inside the data folder and started the wallet again. Whilst having just 1 connection to the network it took a while (~1 hour) but it synchronized a bit further this time. However, I'm stuck again:

{
"version" : 301609,
"protocolversion" : 70008,
"walletversion" : 60000,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 199999,
"timeoffset" : 0,
"moneysupply" : 19594284.99810301,
"connections" : 1,
"proxy" : "",
"difficulty" : 0.00001604,
"testnet" : false,
"keypoololdest" : 1440751523,
"keypoolsize" : 2,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}

SockPuppetAccount

hero member

Activity: 882

Merit: 500

MiG Messenger - earn while chatting

Quote from: Bobekko on August 27, 2015, 07:44:52 PM

What's the skinny on this one? Seems cheap given all the work going on. Why so?

Posting in this thread for the first time in a long, long time. I noticed this coin early on in it's life, and was following all it's developments closely for a while. The reason I haven't been active in this thread is probably for the same reasons that this coin is so cheap and getting such little attention. There is SO much going on here, so much being done, so many updates, so much work and development that it can be hard to keep up with. This is by no means a bad thing. It is a direct effect of this coin having one of the most, if not THE most, dedicated developers in altcoins today. He is just consistently pushing out update after update, commit after commit, and doing it all without any funding or an ICO. Developers like this are practically extinct today.

So while I haven't posted here in a long time, I am still sitting on my stash of bitcredits and am glad to see the project evolving further. This is absolutely THE hidden gem right under everyone's noses.

thelonecrouton

legendary

Activity: 966

Merit: 1000

Quote from: proletariat on August 27, 2015, 08:10:39 PM

Quote from: Bobekko on August 27, 2015, 07:44:52 PM

What's the skinny on this one? Seems cheap given all the work going on. Why so?

I'm going through all of the devs posts from the beginning to figure out what's going on and how it has been managed, not done with it yet but I suggest you do the same and try to clear your doubts after. Currently I'm in a state of "what the fuck have I been doing in other coins" this thing is a hidden gem with absolutely no hype, the dev is so passionate about his project and his work ethic is something I have not seen around here and has managed to get very smart people contributing to the code and ideas. ANN needs a revamp with things that are being worked on but also the same fact keeps unwanted people away IMO.

I think the only people left on BCT are the scammers chasing an ever dwindling population of marks and the die-hard supporters of a (very) few other projects that actually have some real development going on.

Nobody in the real world was ever interested, or ever will be, in digital tokens with absurdly high 'manufacturing' costs. The ideologues will never suss that out either, they'll be arguing about bloody block sizes until they grow old and die and the rest Planet Earth still won't care about a Ponzi scheme that needs petawatts of electricity to process a pitifully small number of transactions per second.

Bitcredit is bringing digital fluidity and physical assets together in as practical and useful a way as possible. Best of both worlds. When the bidding system is up and running I really don't think it will be long before there's a whole lot more interest from the 99.99999% of the world that hear about competitive PoW, laugh and move on. Pissing away money to utility and hardware companies does not lend a currency value.

Bitcoin has a blockchain backed by hot air. Bitcredit will have an assetchain.

proletariat

legendary

Activity: 1246

Merit: 1005

Quote from: Bobekko on August 27, 2015, 07:44:52 PM

What's the skinny on this one? Seems cheap given all the work going on. Why so?

I'm going through all of the devs posts from the beginning to figure out what's going on and how it has been managed, not done with it yet but I suggest you do the same and try to clear your doubts after. Currently I'm in a state of "what the fuck have I been doing in other coins" this thing is a hidden gem with absolutely no hype, the dev is so passionate about his project and his work ethic is something I have not seen around here and has managed to get very smart people contributing to the code and ideas. ANN needs a revamp with things that are being worked on but also the same fact keeps unwanted people away IMO.

Bobekko

full member

Activity: 137

Merit: 100

What's the skinny on this one? Seems cheap given all the work going on. Why so?

thelonecrouton

legendary

Activity: 966

Merit: 1000

I've made a quick python script to semiautomagically take all the service reward inputs from my BNs and send them to a consolidation address, since the banknode conf. donation thing doesn't work. You give the script your bitcreditd path and whatever address you want the mining inputs sent to, unlock your wallet for 30 secs or whatever, then run the script and it sends 'em off 5 at a time, eg: https://chainz.cryptoid.info/bcr/block.dws?200210.htm

I might expand it to 10 at a time but putting the createrawtransaction string together to pass to the daemon is a tedious business.

Should work with anything Bitcoin-derived, just eg. swap out the bitcreditd path for dashd. I'll post it when I've tested it a bit more and we've had some clarification on the current situation with block 200000/RC/syncing.

The hope is that it might help multiple-BN owners hoover up their earnings more easily, to create new BNs with. At least that's my plan.

Topic: ◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈ - page 108. (Read 284545 times)