Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 361. (Read 782375 times)

It was exciting for that first 15 blocks at least. We'll think of it as a teaser.

More time for me to get my wallets ready.

Correct. They are active now, they should be fine once the chain starts moving again tomorrow.

lol nvm then spose it gives everyone time to update and get masternode started. bed it is then.

We shouldn't have to reactivate masternodes once there done now? It will auto go on to next one tomorrow?

No. Just figured out the issue. I screwed up. Last night when I entered the time parameter I added a day to the converter without looking at the date. I inadvertently made the start time tomorrow at 9PM EST by doing that. It is too late to change that now and still have a fair launch. Totally my fault, I am so sorry. It is what it is now.

For anyone wondering, the reason for the blocks that did go through is that I had to make a custom wallet to get the chain moving again. Otherwise everyone would be sitting there waiting for the sync to finish before they could stake, and with no one staking the newest block would have continue to be 2 days old, and no one would start staking, and so on and so on.

So, with that said, tomorrow, same bat time, same bat channel.

It did serve as a good quick test. Thanks for forgiving my screw up.

staking is not active as well on my wallet. restarted it and it is unnlocked.

259215 been on that block for 10 minutes...? has it got stuck again?

80 masternodes up a few minutes ago, now 143, now 163, now 188... now 220 ... 17 nodes on tor.

Past bedtime... Thanks! Good night.

And we're off!!!

"Not capable masternode: Hot node, waiting for remote activation"

... here goes...

nope, you are good, we release the primer block a bit ago, if you are not showing it, add connect=coin-server.com and restart your wallet..

or wait until the chain starts to move..

Nope, that is the 201 block I checkpointed in to be sure we are all starting on the same chain.

$ darknet-cli getblockhash 259200
0000000000b469fb33c2e0911409d6c06183c13e6dd88ac5d827d39ecf3e1b4a
$ darknet-cli getblockhash 259201
fc21adc0a966464eecee91fb0eb785623b041befd67a2b5f433f1d8f750e2a6c

.... is this early?

        "id" : 2,
        "addr" : "72.49.184.206:51472",
        "addrlocal" : "197.231.221.211:21027", (TOR)
        "services" : "0000000000000001",
        "lastsend" : 1471394897,
        "lastrecv" : 1471394898,
        "bytessent" : 1959,
        "bytesrecv" : 10789,
        "conntime" : 1471393576,
        "pingtime" : 0.89766800,
        "version" : 70650,
        "subver" : "/DarkNet Core:2.1.0/",
        "inbound" : false,
        "startingheight" : 259201,
        "banscore" : 0,
        "synced_headers" : -1,
        "synced_blocks" : -1,
        "inflight" : [
        ],
        "whitelisted" : false


        "id" : 16,
        "addr" : "173.245.158.8:51472",
        "addrlocal" : "197.231.221.211:2565", (TOR)
        "services" : "0000000000000001",
        "lastsend" : 1471394896,
        "lastrecv" : 1471394896,
        "bytessent" : 626,
        "bytesrecv" : 9809,
        "conntime" : 1471394175,
        "pingtime" : 0.24584900,
        "version" : 70650,
        "subver" : "/DarkNet Core:2.1.0/",
        "inbound" : false,
        "startingheight" : 259201,
        "banscore" : 0,
        "synced_headers" : -1,
        "synced_blocks" : -1,
        "inflight" : [
        ],
        "whitelisted" : false


        "id" : 29,
        "addr" : "173.245.158.8:51472",
        "addrlocal" : "176.126.252.12:61328", (TOR)
        "services" : "0000000000000001",
        "lastsend" : 1471394808,
        "lastrecv" : 1471394809,
        "bytessent" : 690,
        "bytesrecv" : 9928,
        "conntime" : 1471393967,
        "pingtime" : 0.94120200,
        "version" : 70650,
        "subver" : "/DarkNet Core:2.1.0/",
        "inbound" : false,
        "startingheight" : 259201,
        "banscore" : 0,
        "synced_headers" : -1,
        "synced_blocks" : -1,
        "inflight" : [
        ],
        "whitelisted" : false

Bittrex is on board as well, Yobit.. well, their new policy for coin updates is they have 8-12 days to make the update, so who knows where they are with everything.

EDIT: I just sent Yobit another reminder, haven't heard from them yet on the original submission yet either.

Congrats! I lost the "Jr. Member" status recently.

just an hour left. hope it all goes smoothly.

oooo hero member now lol

PM your email address to s3v3n and he will send you an invite.

Can someone please invite me to the Slack channel???

Nice work. Fresh chain downloaded and synced to 259200. Will Bittrex and YoBit be up to speed so that we can make withdrawals?

ok party on, i'm ready

most excellent, all nodes (total of 46) and an UI wallet have been successfully upgraded and running (no coins were lost during last week perturbations ,combination of backup/rescan and salvagewallet did help great deal,some scare because even @ this amount of coins that was like close to two grand or somethin... )

"version" : 2010000,
"protocolversion" : 70650,
"walletversion" : 61000,

thanks much fella's ,anonymous transactions interest is coming back BIG time, lookin good! see ya tomorrow morning!