Vertcoin - First Scrypt N | First Stealth Address - Privacy without mixer - page 608.

CSM00

member

Activity: 98

Merit: 10

Quote from: BorisTheSpider on January 26, 2014, 10:18:49 PM

Quote from: jballs on January 26, 2014, 10:12:43 PM

Yes this will be a noob question but in the interest of learning... since all the wallets have to sync to the network pretty much whenever they are open, why is it not possible to just push an upgrade notification/requirement whenever a wallet syncs to the network?

jballs that's a good suggestion. I haven't seen anyone implement that in a wallet before, but it would be very useful to have a notification popup telling you if you need to update the wallet. Maybe we'll look into that soon.

If I remembering correctly, it can be done with the alert key or an extension to the QT client. I seem to remember updating my Litecoin wallet a few weeks ago from a notification within the QT client.

It'd probably have to be built into a release to be prepared for future upgrades, so wouldnt work for this one.

BorisTheSpider

full member

Activity: 210

Merit: 100

Quote from: jballs on January 26, 2014, 10:12:43 PM

Yes this will be a noob question but in the interest of learning... since all the wallets have to sync to the network pretty much whenever they are open, why is it not possible to just push an upgrade notification/requirement whenever a wallet syncs to the network?

jballs that's a good suggestion. I haven't seen anyone implement that in a wallet before, but it would be very useful to have a notification popup telling you if you need to update the wallet. Maybe we'll look into that soon.

jballs

member

Activity: 182

Merit: 10

Yes this will be a noob question but in the interest of learning... since all the wallets have to sync to the network pretty much whenever they are open, why is it not possible to just push an upgrade notification/requirement whenever a wallet syncs to the network?

BorisTheSpider

full member

Activity: 210

Merit: 100

Keep asking at https://coinex.zendesk.com/hc/en-us/requests/new and at https://bitcointalksearch.org/topic/poll-next-cryptocurrency-candidates-for-coinex-291647 if you want to trade VTC at Coinex.pw

BorisTheSpider

full member

Activity: 210

Merit: 100

The new wallet with Kimotos Gravity Well and updated N-factor scheduling is now available.

THIS IS A MANDATORY UPDATE - PLEASE UPDATE YOUR WALLET NOW

We have chosen a fork height of block 26754 which should occur on or around Saturday 1st February 2014 (5 days from wallet release). Difficulty will retarget every block after this block height.

We have also backported all the fixes from Litecoin 0.8.6.2, so this release is Vertcoin 0.8.6.2

Please use the following links rather than using vertcoin.org to download the new wallet, the links on vertcoin.org
are to the new updated wallet, but it would be appreciated if you would please use the links below instead to spread
the server load.

0.8.6.2 changes

Fork to Kimoto Gravity Well difficulty adjustment at block 26754 (Around midday UTC on 1st February 2014)
Implement new N-factor schedule
Update to boost 1.55 to fix Windows connectivity issue
Fix custom build on MacOS X 10.9
Fix QT5 custom build
Update Debian build instructions
Update homebrew build
DNS seeds updated to include vtc.kilovolt.co.uk and vtcpool.co.uk
Checkpoint at block 24200

Windows installer: https://www.amazon.co.uk/clouddrive/share?s=uLJdNjcnQN4n9VbuUuZbVk

Windows QT (non installer): https://www.amazon.co.uk/clouddrive/share?s=EICOyiLjSWks3W-ZJBDaBw

Source: https://github.com/vertcoin/vertcoin

Pool operators, please note that to make MPOS display the correct interval between difficulty adjustments, you will want to update /var/www/MPOS/public/include/config/global.inc.php to set
$config['coindiffchangetarget'] = 1; - please do this on fork day, at or as near to block 26754 as you can.

roy7

sr. member

Activity: 434

Merit: 250

josh, yes, because people on the old wallet would be using one difficulty, and people on the new wallet would be using the new difficulty.

BorisTheSpider

full member

Activity: 210

Merit: 100

Quote from: roy7 on January 26, 2014, 08:37:28 PM

Edit: I apparently updated my git clone wrong since I see changes in the git web site that aren't in my code. Yet 'git fetch' tells me I'm up to date. Hmm.

Roy I think it's because it's tagged as a new release - you're probably just pulling changes to the old one. I bet if you "git describe" it says 0.8.6.1 rather than 0.8.6.2

I'd just delete the whole folder and git clone afresh (because I suck at git), someone else will probably be able to tell you the proper way to do it.

josh_kaprun

newbie

Activity: 29

Merit: 0

Quote from: roy7 on January 26, 2014, 08:39:41 PM

Quote from: josh_kaprun on January 26, 2014, 08:32:31 PM

Quote from: blacklig on January 26, 2014, 08:31:58 PM

And also price is recovering

Also true.

Additional idea, why not just change the difficulty retarget time until the KGW is put in place? Isn't that something that could be implemented today? That way, we don't have to suffer though such an unnecessarily high difficulty while waiting on the KGW switch.

Anyone miners or pools using the old wallet would end up forked on an separate chain and wasting their time/losing coins. People have to be given a reasonable amount of time to upgrade.

So, would just changing the difficulty retarget time to something like 3 hours require a different wallet? I'm not talking about making the KGW switch sooner as that obviously needs a new wallet to work.

Full disclosure: I have never developed a coin, so I don't know all of the specifics of what goes into programming one. So, I apologize if my suggestion is simply not possible.

Quote from: BorisTheSpider on January 26, 2014, 08:43:51 PM

I don't know where everyone is getting this idea that we're at high difficulty compared to hashrate! I think probably, a miscalculation or gremlin somewhere in the reported nethash is at fault, and rumours spread from there!

Here's the actual data:

Last 500 blocks in 24 hours: http://explorer.vertcoin.org/chain/Vertcoin?count=500&hi=24681

Which is an average of 2.88 minutes vs. a target of 2.5 minutes, so only about 15% off.

Last 100 blocks in 4 hours: http://explorer.vertcoin.org/chain/Vertcoin?count=100&hi=24681

Which is an average of 2.4 minutes, so _faster_ than target blocktime, albeit only slightly.

I was not aware of that. In that case, my idea not being possible wouldn't be nearly as bad.

BorisTheSpider

full member

Activity: 210

Merit: 100

Quote from: josh_kaprun on January 26, 2014, 08:32:31 PM

That way, we don't have to suffer though such an unnecessarily high difficulty while waiting on the KGW switch.

I don't know where everyone is getting this idea that we're at high difficulty compared to hashrate! I think probably, a miscalculation or gremlin somewhere in the reported nethash is at fault, and rumours spread from there!

Here's the actual data:

Last 500 blocks in 24 hours: http://explorer.vertcoin.org/chain/Vertcoin?count=500&hi=24681

Which is an average of 2.88 minutes vs. a target of 2.5 minutes, so only about 15% off.

Last 100 blocks in 4 hours: http://explorer.vertcoin.org/chain/Vertcoin?count=100&hi=24681

Which is an average of 2.4 minutes, so _faster_ than target blocktime, albeit only slightly.

Quote

Additional idea, why not just change the difficulty retarget time until the KGW is put in place?

That would also require a hardfork. It would require exactly the same mandatory update of the wallet, and a period of time to allow people to do that, as we are doing now for KGW.

The takeaway message really though is - actually look at the blocktimes! We are mining at an entirely appropriate difficulty, and blocks are coming very close to the target rate. KGW will be great, and will be in effect very soon, but there is no problem right now!

roy7

sr. member

Activity: 434

Merit: 250

Quote from: josh_kaprun on January 26, 2014, 08:32:31 PM

Quote from: blacklig on January 26, 2014, 08:31:58 PM

And also price is recovering

Also true.

Additional idea, why not just change the difficulty retarget time until the KGW is put in place? Isn't that something that could be implemented today? That way, we don't have to suffer though such an unnecessarily high difficulty while waiting on the KGW switch.

Anyone miners or pools using the old wallet would end up forked on an separate chain and wasting their time/losing coins. People have to be given a reasonable amount of time to upgrade.

roy7

sr. member

Activity: 434

Merit: 250

My two p2pool nodes are running new wallet. However I did a git fetch and a make, but the only file it recompiled was version.cpp. Shouldn't other files have been updated/recompiled for the KGW?

Code:

:~/vertcoin/src$ make -f makefile.unix
/bin/sh ../share/genbuild.sh obj/build.h
g++ -c -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -D_FILE_OFFSET_BITS=64 -I/home/ubuntu/vertcoin/src -I/home/ubuntu/vertcoin/src/obj -DUSE_IPV6=1 -I/home/ubuntu/vertcoin/src/leveldb/include -I/home/ubuntu/vertcoin/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/version.d -o obj/version.o version.cpp
g++ -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -D_FILE_OFFSET_BITS=64 -I/home/ubuntu/vertcoin/src -I/home/ubuntu/vertcoin/src/obj -DUSE_IPV6=1 -I/home/ubuntu/vertcoin/src/leveldb/include -I/home/ubuntu/vertcoin/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -o vertcoind leveldb/libleveldb.a obj/alert.o obj/version.o obj/checkpoints.o obj/netbase.o obj/addrman.o obj/crypter.o obj/key.o obj/db.o obj/init.o obj/keystore.o obj/main.o obj/net.o obj/protocol.o obj/bitcoinrpc.o obj/rpcdump.o obj/rpcnet.o obj/rpcmining.o obj/rpcwallet.o obj/rpcblockchain.o obj/rpcrawtransaction.o obj/script.o obj/scrypt.o obj/sync.o obj/util.o obj/wallet.o obj/walletdb.o obj/hash.o obj/bloom.o obj/noui.o obj/leveldb.o obj/txdb.o -Wl,-z,relro -Wl,-z,now   -Wl,-Bdynamic -l boost_system -l boost_filesystem -l boost_program_options -l boost_thread -l db_cxx -l ssl -l crypto -Wl,-Bdynamic -l z -l dl -l pthread /home/ubuntu/vertcoin/src/leveldb/libleveldb.a /home/ubuntu/vertcoin/src/leveldb/libmemenv.a

Edit: I apparently updated my git clone wrong since I see changes in the git web site that aren't in my code. Yet 'git fetch' tells me I'm up to date. Hmm.

blacklig

sr. member

Activity: 504

Merit: 251

josh_kaprun

newbie

Activity: 29

Merit: 0

Quote from: blacklig on January 26, 2014, 08:31:58 PM

And also price is recovering

Also true.

Additional idea, why not just change the difficulty retarget time until the KGW is put in place? Isn't that something that could be implemented today? That way, we don't have to suffer though such an unnecessarily high difficulty while waiting on the KGW switch.

blacklig

sr. member

Activity: 504

Merit: 251

Quote from: josh_kaprun on January 26, 2014, 08:10:16 PM

Recent discoveries:

1 - the new wallet works
2 - CoinedUp works slightly better in Internet Explorer

That is all.

And also price is recovering

josh_kaprun

newbie

Activity: 29

Merit: 0

Recent discoveries:

1 - the new wallet works
2 - CoinedUp works slightly better in Internet Explorer

That is all.

BorisTheSpider

full member

Activity: 210

Merit: 100

The new wallet with Kimotos Gravity Well and updated N-factor scheduling is now available.

THIS IS A MANDATORY UPDATE - PLEASE UPDATE YOUR WALLET NOW

We have chosen a fork height of block 26754 which should occur on or around Saturday 1st February 2014 (5 days from wallet release). Difficulty will retarget every block after this block height.

We have also backported all the fixes from Litecoin 0.8.6.2, so this release is Vertcoin 0.8.6.2

Please use the following links rather than using vertcoin.org to download the new wallet, the links on vertcoin.org
are to the new updated wallet, but it would be appreciated if you would please use the links below instead to spread
the server load.

0.8.6.2 changes

Fork to Kimoto Gravity Well difficulty adjustment at block 26754 (Around midday UTC on 1st February 2014)
Implement new N-factor schedule
Update to boost 1.55 to fix Windows connectivity issue
Fix custom build on MacOS X 10.9
Fix QT5 custom build
Update Debian build instructions
Update homebrew build
DNS seeds updated to include vtc.kilovolt.co.uk and vtcpool.co.uk
Checkpoint at block 24200

Windows installer: https://www.amazon.co.uk/clouddrive/share?s=uLJdNjcnQN4n9VbuUuZbVk

Windows QT (non installer): https://www.amazon.co.uk/clouddrive/share?s=EICOyiLjSWks3W-ZJBDaBw

Source: https://github.com/vertcoin/vertcoin

Pool operators, please note that to make MPOS display the correct interval between difficulty adjustments, you will want to update /var/www/MPOS/public/include/config/global.inc.php to set
$config['coindiffchangetarget'] = 1; - please do this on fork day, at or as near to block 26754 as you can.

blacklig

sr. member

Activity: 504

Merit: 251

Quote from: BorisTheSpider on January 26, 2014, 07:44:54 PM

Quote from: blacklig on January 26, 2014, 07:39:27 PM

ok, good post

Now I am happy to know that and good to hear forking is going to be earlier

Cool.

Quote

Anyway, I think no one is solomining atm so it is sufficient just to update pools, reset wallet addresses and that is it.. , no?

There's no need to reset wallet addresses or do anything. Just install the new wallet over the top of the old one. Nothing else needs changing.

Ok, good..
so where is the hot info with details? Cheesy

BorisTheSpider

full member

Activity: 210

Merit: 100

Quote from: blacklig on January 26, 2014, 07:39:27 PM

ok, good post

Now I am happy to know that and good to hear forking is going to be earlier

Cool.

Quote

Anyway, I think no one is solomining atm so it is sufficient just to update pools, reset wallet addresses and that is it.. , no?

There's no need to reset wallet addresses or do anything. Just install the new wallet over the top of the old one. Nothing else needs changing.

donschoe

full member

Activity: 157

Merit: 100

Hello Coins

Quote from: roy7 on January 26, 2014, 07:32:39 PM

Quote from: donschoe on January 26, 2014, 06:26:13 PM

Hi community.

I've added a p2pool node with a great worker tracker, check it out: http://q30.qhor.net:9171/
I also adapted p2pool-scanner for VTC, check out public nodes: http://q30.qhor.net:9172/

Please add me to the pools list.

Cheers
donSchoe

Welcome aboard! I like those stats!

Thanks!

Code is now on github, support decentralization, run your own nodes: https://github.com/donSchoe/p2pool-vtc

blacklig

sr. member

Activity: 504

Merit: 251

Quote from: BorisTheSpider on January 26, 2014, 06:54:36 PM

Quote

Devs, show me one person that doesnt want to implement NOW

You, if you have any VTC or are mining it! For the reasons explained below.

Quote

So I think this KGW must be implemented NOW, not in 6th feb or so.. no reason for that.

Implementation will happen much sooner than that. I will post in the next few minutes with the full details.

Quote

And please explain me, why to wait?

It's necessary that users, _especially_ pool operators, update their wallet BEFORE the fork actually happens. If they didn't, the network would mine on the old legacy difficulty algorithm fork, and peoples coins mined on that fork would become invalid when they finally updated their wallets.

It is absolutely essential that time is allowed for an orderly transition. We have cut the time down to the minimum necessary to ensure that happens. As I said above, full details coming in a few minutes.

ok, good post

Now I am happy to know that and good to hear forking is going to be earlier

Anyway, I think no one is solomining atm so it is sufficient just to update pools, reset wallet addresses and that is it.. , no?

Topic: Vertcoin - First Scrypt N | First Stealth Address - Privacy without mixer - page 608. (Read 1232701 times)