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

For those missed the above update.

Update your wallets to v2.1.0.0 & sync from scratch everyone!

Party starts tomorrow!

Hello s3v3nh4cks,

Great news!

Synced and waiting. Right now my wallet shows that it's late a few days. Will it resolve itself after 9PM EST? I hope it will not bring conflicts.

As as side note, the link in the OP for the linux wallet is broken. Btw would you mind releasing a 32bit compiled version please?


muchoman, please look at the bolded part in the statement of s3v3nh4cks  

Let's POS.


I hope so... should be once the exchanges have updated their wallets and resend txs. Please keep us posted.


wise words. I agree.

Backup did the trick, wallet does not crash anymore, thanks.
Still getting masternode error.

masternode start
Not capable masternode: Could not find suitable coins!


masternode status
{
    "vin" : "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
    "service" : "127.0.0.1:51472",
    "status" : "Not capable masternode: Could not find suitable coins!"
}

you need to try with a backup of your wallet file
i had the same issue and it was the wallet.dat file that was corupt


thanks
Paul

Thanks for your hard work, looks promising! Do we have test cases for the new functions already?

You will have to ask one of the windows guys, but I'm gonna guess maybe you didn't delete all your files except the wallet.dat, and the (2) .conf files and resync from scratch?? maybe not though?? just guessing...

edit: I just realized I said only delete your peers.dat file, but essentially when you do a sync from scratch, you should always delete everything except the wallet.dat, and the (2) .conf files

Latest windows wallet still crashing

Windows wallet crash debug.

*** System error while flushing: CDB : Error -30974, can't open database
2016-08-15 16:25:29 CDBEnv::EnvShutdown : Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery

https://s3.postimg.org/wyexvbqib/darknet.jpg

Not to celebrate prematurely but great job!

I love the fairness of the solution.

Yep, nice work guys. This has been the kind of crypto experience we should have had from the start. Now I hope my entire stash shows up when we get going lol

I am so happy the DNET community was patient enough to let us put together one of the most up to date PoS wallets on the market. This is a cool community, lots of people willing to help out when it was needed. Thanks guys!

Thanks s3v3nh4cks! Upgrading my wallets & MNs to v2.1.0.0 now.

Ok Everyone, We are pretty confident this is the one..

Fair Release for Staking tomorrow at 9PM EST

Instructions,

-Remove addnodes from conf file

-Delete all your files except the wallet.dat, and the (2) .conf files

-Sync from Scratch, Wallet will stop at 259200 until 9PM EST

Then everyone can start to stake..

Thank You for your Patience..

Wallets are uploaded and ready, Links in the OP are updated as well.

always stuck under 2.0.5 ..

i launch sync to 500 blocs then stuck ..
i relaunch sync to 1000 blocs and stuck ..
i relaunch sync to 1500 blocs and stuck ..
etc ..

Now running version v2.0.5.0-3bddcd3. Wallet only.

Any way that block reorganization requests can be used to exploit the network by a malicious staker or masternode? For example to fork the chain?

$ darknet-cli getblockhash 263033
6cc1893f9f06f29157f23595f3f2d812a47fbf263ee23af7457d1c5d5d05e012
$ TZ=UTC date
Mon Aug 15 22:53:21 UTC 2016

I just uploaded some new wallets with adjusted reorg code. Seems to be working much better so far.

https://github.com/Darknet-Crypto/Darknet/releases

I did the same as you did mikegi, and this is what I got:

[
    {
        "height" : 262900,
        "hash" : "7985769b9ffb902c14cb50baa2be99a755c87c1469eeef819ff4fe9a41a9d6cc",
        "branchlen" : 0,
        "status" : "active"
    },
    {
        "height" : 262677,
        "hash" : "33f4ac34855efd8ffcc376999723a5e65c30e615e232be18c96925ec5001c763",
        "branchlen" : 3,
        "status" : "valid-fork"
    },
    {
        "height" : 262675,
        "hash" : "75ca5173f84da3021c36b51b11388eed59b34e900c3c4e801e000e47b5755a3e",
        "branchlen" : 1,
        "status" : "headers-only"
    },
    {
        "height" : 262643,
        "hash" : "e49574080e0244eb01734c20d3580234c5b22acc27215322510ea27127bb190a",
        "branchlen" : 1,
        "status" : "invalid"
    },
    {
        "height" : 262643,
        "hash" : "7b72f6ed5a739a56b9fdb6473be586ff3d002d15f1b1bbfe284bf715a58dc088",
        "branchlen" : 1,
        "status" : "headers-only"
    },
    {
        "height" : 262635,
        "hash" : "86e97163796515daae3ab7d27ec4d29bf7a4f251d651ff89838369f032999ed4",
        "branchlen" : 1,
        "status" : "headers-only"
    },
    {
        "height" : 262632,
        "hash" : "39e47cabf83edeecd1b917349acb7f9f34b2481dd5ec4fb22ec2b956c0220150",
        "branchlen" : 1,
        "status" : "headers-only"
    },
    {
        "height" : 262626,
        "hash" : "19aa520834ea1519f1cb6b6b339cbdb47ed2f6a0cb94eec8141afea663ef65c2",
        "branchlen" : 1,
        "status" : "headers-only"
    },
    {
        "height" : 262608,
        "hash" : "bce3b95c160b40c39ebe3c510c20db9e475d91e2eb7b4c705d5043fdce0bb6a5",
        "branchlen" : 1,
        "status" : "headers-only"
    },
    {
        "height" : 262597,
        "hash" : "1badce15278ca8c788c37ee865b105ae07639a8d8da71894673d7ad9f3adc223",
        "branchlen" : 1,
        "status" : "headers-only"
    },
    {
        "height" : 262597,
        "hash" : "9066b3bc1ab4ffb622a1e1b51683c60771a7770fe37f8ea53b6b48191acfb259",
        "branchlen" : 1,
        "status" : "headers-only"
    },
    {
        "height" : 262597,
        "hash" : "2d8767763d82afc4501d7532288561c37c1380cd532c3337efee0f69a71632a6",
        "branchlen" : 1,
        "status" : "invalid"
    },
    {
        "height" : 262595,
        "hash" : "c6527686b6179a5bbd32450d362b6f9b88929f937805afcbdbfdb819a012c7ad",
        "branchlen" : 1,
        "status" : "headers-only"
    },
    {
        "height" : 262549,
        "hash" : "63a27b14237ae10a24d19ac886ed4c218161a5dff20b2280f2b23ff83c62ef02",
        "branchlen" : 2,
        "status" : "headers-only"
    },
    {
        "height" : 262549,
        "hash" : "195faf8b1018593344180f3a0a34e6cbeead9c2a1a7dcaeab521ec0ef3870ed8",
        "branchlen" : 2,
        "status" : "valid-fork"
    },
    {
        "height" : 262548,
        "hash" : "3c236ec5116c17b1ea7955b7166a9234ca3671e3ce0dad79c08afa6d316ae2e3",
        "branchlen" : 1,
        "status" : "headers-only"
    },
    {
        "height" : 262545,
        "hash" : "6d71b2506a01586477013125de1a97ab480c243b563894202ac845966bfec03b",
        "branchlen" : 8,
        "status" : "valid-headers"
    },
    {
        "height" : 262539,
        "hash" : "0e4c8c0038b65dfaf7a7b156881f902b376dbe936090bd4091eb8e871cc42224",
        "branchlen" : 1,
        "status" : "headers-only"
    },
    {
        "height" : 262533,
        "hash" : "7448cfe5de30a82c9b20623a1901ed93dc3d2c940e5eecc4f40d0d30adf7263e",
        "branchlen" : 6,
        "status" : "valid-headers"
    },
    {
        "height" : 262502,
        "hash" : "429f9ae8eb17e8ef7dd70b8d8af61488182fe2fe5bfb2372982cbc377c0ae1ec",
        "branchlen" : 1,
        "status" : "headers-only"
    },
    {
        "height" : 262496,
        "hash" : "1d24a317d4eba89ed358b122b3f39c47fead6422af7753244e03514f0c3ee85b",
        "branchlen" : 1,
        "status" : "valid-fork"
    },
    {
        "height" : 262470,
        "hash" : "ff91d53d533c0824afbda47ac788377e7966bcad9a0a1e5ebf4bab40ededdd44",
        "branchlen" : 25,
        "status" : "valid-headers"
    },
    {
        "height" : 262166,
        "hash" : "2feface4e615def83c4351709a56919271e7e512cd9d76436dec7b5ce87d46cc",
        "branchlen" : 97,
        "status" : "valid-headers"
    }
]

So if I understand well the "active" is the chain. the valid-fork and valid-headers are a little bit unclear... fork I guess and valid headers is that the block didn't sync just the headers?

I hope it helps.

$ darknet-cli getblockhash 262860
b5e4fdf0bf92076f1749179f0e5d11fdbb79a2777adc53a5f6b7e62278d89fbb

darknet-cli getchaintips
[
    {
        "height" : 262868,
        "hash" : "d7d87bbbaaf7d32df05b21595ec080de7e13e402bb84a686913a13d0b02682f6",
        "branchlen" : 0,
        "status" : "active"
    },
    {
        "height" : 262677,
        "hash" : "33f4ac34855efd8ffcc376999723a5e65c30e615e232be18c96925ec5001c763",
        "branchlen" : 3,
        "status" : "valid-headers"
    },
    {
        "height" : 262545,
        "hash" : "403ea002e727e8050b191b0a64c0ceded6e61c10e225cbee5893dad3b1d6c026",
        "branchlen" : 18,
        "status" : "valid-fork"
    },
    {
        "height" : 262496,
        "hash" : "1d24a317d4eba89ed358b122b3f39c47fead6422af7753244e03514f0c3ee85b",
        "branchlen" : 1,
        "status" : "valid-fork"
    },
    {
        "height" : 262445,
        "hash" : "e9cf640b337db2572406860cecb1fce771f8030cd85d7ac848acccb3a5079e06",
        "branchlen" : 3,
        "status" : "valid-fork"

$  TZ=UTC date
Mon Aug 15 20:21:46 UTC 2016

a little check to see if everyone is on the same chain... I got stuck at 262851. relaunched the wallet and it synced again and move perfectly to the next blocks...

getblockhash 262860

b5e4fdf0bf92076f1749179f0e5d11fdbb79a2777adc53a5f6b7e62278d89fbb

Can someone hook me up with a Darknet slack Invite?

Automagicaly back on same (with block explorer too) chain at all nodes.