Vertcoin - First Scrypt N | First Stealth Address - Privacy without mixer

[donschoe]

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

[1715159431]

1715159431

[1715159431]

1715159431

[1715159431]

1715159431

[blacklig]

I dont understand, why not to implement KGW JUST RIGHT NOW?

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

What is happening now is really dangerous for coin.. hashrate dropped to half and still dropping.. meaning this round it taking more and more time to finish and poor miners who are doing "hard work" to mine through lower diff wont be rewarded enough.


So I think this KGW must be implemented NOW, not in 6th feb or so.. no reason for that.
And please explain me, why to wait? I am noob in this, I just like VTC too much to let it die this way

[nonny12]

I dont understand, why not to implement KGW JUST RIGHT NOW?

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

What is happening now is really dangerous for coin.. hashrate dropped to half and still dropping.. meaning this round it taking more and more time to finish and poor miners who are doing "hard work" to mine through lower diff wont be rewarded enough.


So I think this KGW must be implemented NOW, not in 6th feb or so.. no reason for that.
And please explain me, why to wait? I am noob in this, I just like VTC too much to let it die this way

Coin forks need to happen after sufficient notice is given, or else the whole network can get messed up. After the fork is announced, every pool, solo miner and vertcoin holder will need to update their wallet.

If you implement a fork without prior notice, then every miner would essentially be mining on the old, incorrect blockchain. This would be bad for vertcoin.

[BorisTheSpider]

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.

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.

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.

[mmihai1978]

full suport for boris, existing coins must be preserved.

[BorisTheSpider]

full suport for boris, existing coins must be preserved.

Well, there is no risk to existing coins as such, but there is a risk of a fork to two blockchains growing at "significant" pace if people haven't updated in time. It would be very disorderly. We're pushing really hard to make sure things happen as fast as is safely possible - everyone in #vertcoin_dev has basically spent their entire weekend working on this. We're very very close to a release announcement now - just getting the new wallets uploaded.

[shirenlihei]

high difficulty already killed the half the hashrate.

Waiting for the promised kgw.

No, it's just variance. The hashrate shown in the client and on the pools is _calculated_, not measured. So if diff doubles (which it did) and blocktimes double as a result, the calculation will be off while things settle down.

It happened what I described..Nethashrate was above 400mh/s now is 250mh/s..net round is close to 4min so next retarget will be in~ 5 days or more, I guess more people will stop mining in next 12-24h cause now it's not profitable..umtil You fix difficulty I'm off to mine something else.

p.s. DOGE is also preparing against ASICs
http://imgur.com/a/q3g8T

Unbelievable, the first clone of Vertcoin is Dogecoin....

[landcrab]

If TIPS is good enough for cryptsy then VTC should definitely be on there.

[roy7]

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!

[blacklig]

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.

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.

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?

[donschoe]

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

[BorisTheSpider]

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

Cool.

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.

[blacklig]

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

Cool.

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?

[BorisTheSpider]

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.

[josh_kaprun]

Recent discoveries:

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

That is all.

[blacklig]

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]

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]

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.

downloaded !
now lets fork!

[roy7]

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.

[roy7]

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.