hi, blockexplorer, I think requires a fix, because it doesn't show correctly the data from my wallet and data from blockexplorer in my purse a large amount than shows the total amount in blockexplorer
The RichList for the old BlockChain, is for the moment still reachable to its old url: http://www.navcoin.org/rich-listand as far as I can see it is updated and correct. Regarding the new blockchain, the new richlist is much more complete, but at least in this case a little slow in the updates, but substantially correct. In the new blockchain explorer, there is also a list of the Largest Wallets, it is similar to the rich list, but they are two different things, do not be confused. In case you have an urgent need to control, I have included the usual unofficial richlist, but as usual there may be some inaccuracies. Deep Watch Report block 1 to 156372 at 2016-07-07 15:42:08 UTC
Hash 1634dfa569eed897bb7bdac813e5c64bf7339e57a1ae42eceb795ed8721c8dcb
DWR Rank Address total share Last (UTC) 1st (UTC) POS POW C-Pile
DWR 1 Na9PwB...6UCtS 10000000.000000 16.68 2016-06-06 02:33:04 2016-06-01 0 0 2
DWR 2 NaoDjc...yQSAc 4949999.900000 8.26 2016-06-06 02:33:04 2016-06-06 0 0 1
DWR 3 NLGTav...9AjAX 4949999.900000 8.26 2016-06-06 02:33:04 2016-06-06 0 0 1
DWR 4 NgiAp2...NYLxG 4942974.964792 8.24 2016-07-07 15:42:08 2016-06-03 39543 0 29332
DWR 5 NWgu38...Rz3J7 4899999.800000 8.17 2016-06-06 02:33:04 2016-06-06 0 0 1
DWR 6 NWSEfX...rqssB 4619744.878472 7.70 2016-06-20 02:38:40 2016-06-20 0 0 4
DWR 7 Ndb76o...hN71N 2355585.630122 3.93 2016-06-22 07:29:36 2016-06-13 0 0 1
DWR 8 NSjqWe...84Qfk 2288185.759900 3.82 2016-06-22 07:29:36 2016-06-13 0 0 1
DWR 9 NSeqnr...WjwDa 1803841.677524 3.01 2016-07-07 02:52:16 2016-06-04 6350 0 5004
DWR 10 NbJYKx...9u7Mi 1701758.903461 2.84 2016-06-22 07:29:36 2016-06-13 0 0 1
DWR 11 NZdHXd...G5s8B 1652168.899400 2.76 2016-06-22 07:29:36 2016-06-12 0 0 2
DWR 12 NXB5rR...VJtiQ 1214426.968584 2.03 2016-07-07 15:41:52 2016-06-03 10664 0 6282
DWR 13 Nekc2U...a9ErC 1199900.000000 2.00 2016-07-07 14:43:12 2016-07-06 0 0 2
DWR 14 NiYv2p...8p1JJ 1106074.391930 1.84 2016-06-26 02:33:04 2016-06-26 0 0 1
DWR 15 NVDtgD...Fr4dL 1078211.246478 1.80 2016-06-22 07:29:36 2016-06-10 0 0 1
DWR 16 NicQT5...fe5RV 1076481.875503 1.80 2016-07-06 15:04:00 2016-06-20 432 0 441
DWR 17 NiQzyh...T9uSy 1035476.704888 1.73 2016-06-19 12:53:36 2016-06-03 4082 0 4012
DWR 18 NbzMQu...WQibd 558139.424463 0.93 2016-07-07 11:00:48 2016-06-03 744 0 750
DWR 19 NhfDxW...v6gWF 499596.194511 0.83 2016-06-14 04:57:52 2016-06-13 1 0 1
DWR 20 NWCXzC...1SQss 480653.009581 0.80 2016-07-07 15:41:52 2016-06-03 4199 0 509
DWR 21 NgXr3W...vyAfF 477684.390839 0.80 2016-07-05 20:22:56 2016-07-04 0 0 5
DWR 22 NN2jTv...r9orR 469336.987966 0.78 2016-07-06 07:35:12 2016-06-03 928 0 932
DWR 23 NiZwVH...R8Vxd 434722.361201 0.72 2016-07-07 15:34:24 2016-06-03 5612 0 2164
DWR 24 NWQyCL...ik1PL 409000.000000 0.68 2016-07-02 02:14:40 2016-06-13 0 0 1
DWR 25 Nf3BJB...G2sEU 390044.188837 0.65 2016-07-07 15:26:08 2016-06-03 3850 0 1984
DWR 26 Nb5Q5x...qzGJe 348824.053585 0.58 2016-07-06 14:27:28 2016-06-03 86 0 88
DWR 27 NMsVo3...7r4cs 334904.667751 0.56 2016-06-06 05:15:44 2016-06-03 46 0 52
DWR 28 NfHBNj...WobmN 313909.294127 0.52 2016-07-07 15:39:12 2016-06-14 2194 0 1389
DWR 29 NTDDhw...DLBhe 300821.345989 0.50 2016-07-03 08:29:04 2016-06-04 239 0 240
DWR 30 NRxCcT...dGTbk 293730.518384 0.49 2016-06-27 23:00:00 2016-06-14 0 0 1
DWR 31 NTRzvV...tFAqA 216215.247766 0.36 2016-07-06 00:05:04 2016-07-02 1 0 1
DWR 32 NaqyfU...MV2K9 215146.668668 0.36 2016-07-07 15:06:08 2016-06-03 161 0 163
DWR 33 NYJSZa...Yv3ZL 211722.907495 0.35 2016-07-07 15:39:44 2016-06-03 1971 0 1543
DWR 34 NTUCeR...7EAj8 207489.901340 0.35 2016-07-06 00:05:04 2016-07-06 0 0 1
DWR 35 NQzRPy...uymRT 194645.273520 0.32 2016-07-07 15:00:16 2016-06-27 454 0 456
DWR 36 NYiwzX...tYhGk 158947.577914 0.27 2016-06-13 08:09:36 2016-06-01 1345 0 865
DWR 37 NdNekw...TdVAZ 154000.934702 0.26 2016-07-06 01:15:12 2016-06-04 1180 0 864
DWR 38 NVgmJU...Pb1b7 150073.837972 0.25 2016-07-07 15:37:04 2016-06-03 2731 0 866
DWR 39 NaU5qx...46BN9 147000.000000 0.25 2016-07-06 01:25:36 2016-06-03 0 0 2
DWR 40 NfQJDy...3TMiG 143153.926986 0.24 2016-07-07 11:10:56 2016-06-27 9 0 13
DWR 41 NWKF67...51ecs 134448.465157 0.22 2016-07-07 09:30:24 2016-07-04 7 0 9
DWR 42 NdSaNQ...e7UDf 116519.964246 0.19 2016-07-07 15:35:12 2016-06-12 520 0 514
DWR 43 NMTjWT...AD4V8 113775.523742 0.19 2016-06-04 01:43:44 2016-06-04 0 0 1
DWR 44 NdwYDT...64s7s 110693.692096 0.18 2016-07-07 15:05:04 2016-06-04 889 0 500
DWR 45 NXryKP...ebABU 103231.673531 0.17 2016-07-07 15:15:44 2016-06-03 979 0 473
DWR 46 NiJyHq...F13LE 103188.484119 0.17 2016-07-07 15:32:16 2016-06-03 1014 0 777
DWR 47 Nc3Xur...TNsdy 100369.844617 0.17 2016-07-07 15:20:00 2016-06-08 894 0 397
DWR 48 NUftRd...1rGHs 100136.750575 0.17 2016-07-06 21:01:36 2016-06-03 162 0 168
DWR 49 NS9MCQ...PyS1m 83542.293147 0.14 2016-06-13 08:09:36 2016-06-01 740 0 399
DWR 50 NMqF9t...sxXrT 80513.428627 0.13 2016-06-13 08:09:36 2016-06-01 722 0 420
DWR 51 NdjxXB...QXnFB 77754.318653 0.13 2016-06-13 08:09:36 2016-06-01 725 0 356
DWR 52 NerBSP...J48SM 67973.547506 0.11 2016-07-07 12:53:04 2016-06-03 39 0 40
DWR 53 Ng3Hnv...avozu 61010.429044 0.10 2016-06-20 05:53:36 2016-05-12 14125 0 365
DWR 54 NgucLL...4ZRYh 60155.519177 0.10 2016-07-07 14:40:16 2016-06-03 40 0 41
DWR 55 NgpyGU...x2Y5L 60139.398766 0.10 2016-07-07 13:37:04 2016-06-03 48 0 49
DWR 56 NizS5V...3kwAX 60128.704657 0.10 2016-07-07 15:37:52 2016-06-03 32 0 34
DWR 57 NUDke4...i7ugk 53657.377283 0.09 2016-07-07 15:40:48 2016-05-12 13024 0 243
DWR 58 NPRfHV...HUifT 50225.108097 0.08 2016-07-07 14:15:12 2016-06-11 282 0 196
DWR 59 NTDNVR...5vDd8 49131.426225 0.08 2016-07-07 12:46:56 2016-06-11 310 0 230
DWR 60 NVtky7...hTKSL 40127.603249 0.07 2016-07-07 00:41:52 2016-06-05 212 0 199
DWR 61 NVBhMo...GvC9G 30899.406190 0.05 2016-07-07 01:26:24 2016-07-07 0 0 1
DWR 62 NZqoLb...Be9KV 26181.054974 0.04 2016-07-06 00:02:24 2016-06-14 141 0 104
DWR 63 NLkEcT...EYcot 25513.384863 0.04 2016-07-07 14:00:00 2016-06-05 87 0 84
DWR 64 NaX7KL...WTuoA 25294.124647 0.04 2016-07-06 22:49:36 2016-06-04 44 0 18
DWR 65 NhaeTt...NaPoC 23677.695305 0.04 2016-07-04 05:02:56 2016-06-03 85 0 53
DWR 66 NizhaA...7h12p 22789.597181 0.04 2016-07-03 21:28:00 2016-07-03 0 0 1
DWR 67 NgKQrR...dw2kF 20238.011017 0.03 2016-06-15 16:42:24 2016-06-04 59 0 57
DWR 68 Nh7dv9...pfwjf 20159.916543 0.03 2016-07-06 23:20:32 2016-07-06 0 0 1
DWR 69 NLuDD9...M32NN 19753.883735 0.03 2016-07-06 13:12:16 2016-07-06 0 0 1
DWR 70 NYuKYF...ej2UQ 19111.347571 0.03 2016-07-07 11:12:00 2016-06-20 68 0 69
DWR 71 NPdVzK...EoyMd 16849.987705 0.03 2016-07-06 16:30:24 2016-07-05 3 0 7
DWR 72 NgotyM...phzhQ 14117.965392 0.02 2016-07-06 18:46:24 2016-06-01 206 0 77
DWR 73 NRsZoV...XeCGH 10002.833561 0.02 2016-07-07 08:09:04 2016-07-04 11 0 12
DWR 74 NYznZD...SJhmU 9607.032307 0.02 2016-07-07 14:43:12 2016-06-03 5 0 16
DWR 75 Nd8u8H...fd3x3 9028.785753 0.02 2016-07-06 18:33:52 2016-06-04 48 0 39
DWR 76 NPP6Vx...8A4CU 7996.877133 0.01 2016-07-07 15:31:28 2016-07-05 2 0 4
DWR 77 NLEx6R...K669E 7017.170821 0.01 2016-07-05 15:46:08 2016-06-04 50 0 46
DWR 78 NhfUtg...4vvGQ 5517.228136 0.01 2016-07-06 13:24:32 2016-06-04 20 0 1
DWR 79 Nfh8ha...Dc1FA 3932.427523 0.01 2016-07-06 02:56:16 2016-07-06 0 0 1
DWR 80 NZjh6G...wtBZw 3534.756057 0.01 2016-07-06 16:30:24 2016-07-06 0 0 1
DWR 81 NP21hv...nvSju 3149.655541 0.01 2016-07-07 01:10:56 2016-07-07 0 0 1
DWR 82 NaS1Eb...8UA5d 3120.096163 0.01 2016-06-10 14:15:44 2016-06-10 0 0 1
DWR 83 NNjz1x...AbTpE 2784.410560 0.00 2016-06-27 22:41:52 2016-06-13 0 0 1
DWR 84 NXUKxN...zXG9f 2000.000000 0.00 2016-07-05 02:25:52 2016-07-05 0 0 1
DWR 85 NbV6iZ...zwWir 1881.912154 0.00 2016-06-30 12:58:56 2016-05-13 512 0 16
DWR 86 NbDYv6...de8b9 1800.000000 0.00 2016-07-06 01:55:12 2016-07-06 0 0 1
DWR 87 NdeXFg...7PeeQ 1724.909403 0.00 2016-07-07 02:04:16 2016-05-13 538 0 12
DWR 88 NUPUqf...Nnx1f 1652.808496 0.00 2016-07-05 09:38:56 2016-05-13 446 0 10
DWR 89 NZMCRi...wNDVi 1584.800000 0.00 2016-06-21 19:19:44 2016-06-21 0 0 1
DWR 90 NTpr56...d9MyN 1316.161369 0.00 2016-07-04 06:17:36 2016-05-13 432 0 7
DWR 91 NQrtJD...o2dxB 1000.000000 0.00 2016-06-03 21:17:20 2016-06-03 0 0 1
DWR 92 NZpTYy...KbVkg 902.818704 0.00 2016-07-06 05:04:16 2016-06-04 5 0 6
DWR 93 NQx7Tc...epof5 899.799900 0.00 2016-06-04 14:21:04 2016-06-04 0 0 1
DWR 94 NTJAiR...Sbzcu 799.999800 0.00 2016-05-14 08:30:56 2016-05-14 0 0 1
DWR 95 NVtqsT...HfeFh 778.536612 0.00 2016-07-05 21:56:32 2016-06-04 11 0 2
DWR 96 NaRZDk...woXkq 702.803520 0.00 2016-07-06 22:55:44 2016-06-08 10 0 1
DWR 97 Ne3bSS...1aYbk 671.677259 0.00 2016-07-01 01:16:48 2016-05-13 406 0 5
DWR 98 NUyWv7...VpuUZ 498.899900 0.00 2016-07-07 13:40:16 2016-06-03 0 0 1
DWR 99 Nj4hig...jyXZ6 466.679080 0.00 2016-07-04 01:37:52 2016-06-11 3 0 4
DWR 100 NTmVEB...XYq8N 272.174306 0.00 2016-06-22 09:31:28 2016-06-13 0 0 1
|
|
|
|
In some extreme case can help, but in normal condition this is not the best possible solution.
completely agree Remy. however this seems to be needed as I only know of two definitive nodes on the old blockchain. Without adding the max connections of 2, the wallet could get confused by connecting with nodes on the new and old chain. I should have added a disclaimer that is only done in certain situations and should be removed immediately after. Perfect.  In theory, the seed node should only propagate the correct nodes, but in this transitional situation, where there are new and old wallet, all waiting on the same port, there may be incomplete attempts. PS: In addition, if the wallet has been stopped for a _long_ time, it might be useful to delete the old peers.dat file. |
|
|
|
for anyone having syncing issues on the old chain, please try putting the following into your navcoin.conf file:
maxconnections=2
connect=95.183.50.58
connect=5.230.142.254
And REMOVE any other addnode lines from your config file.
What this does is only allows your wallet to have a maximum of 2 connections and the 'connect' variables will force the wallet to ONLY connect to the nodes listed above.
Without this, your wallet will try to connect to as many nodes as possible, whether on the new or old network and cause delays on syncing to the old chain.
once your wallet is open, you can verify if it has worked by typing, 'getpeerinfo'. If you only have the nodes with IP's above, it worked.
I haven't test this on NAV since I had my coins on Bittrex for the swap, but the above method has saved numerous headaches for me on other coins.
Please let us know if this fixes the issue.
Remove the old obsolete addnde is correct, but so drastically restrict the number of connections, IMHO not seem at all the best solution possible, and it does not help other peers in the same condition. Especially I would like to avoid that this idea was perceived as overall definitive solution, valid in all cases, even in the future, because in the long run would be deleterious. The proper functioning of a crypto currency is based on the creation of distributed network of peers, sharing and exchange among themselves the blocks with the transaction between all nodes. Limit the nodes that way, it ends up transforming the structure of the peer's network of cryptocoin in a centralized manner, making it very slow, and at the same time this overloaded its supernodes, making them into weak points in a centralized structure. In some extreme case can help, but in normal condition this is not the best possible solution. |
|
|
|
I'm proud of poloniex. I hate these manual coin swaps. What was the reason why my addresses and balances couldn't be included in the genesis block of V2. I have my coins stored away for 5 years in a paper wallets. It's extremely annoying that I can get my coins stolen right out of my paper wallet. NAUT did this to me. My 200 NAUT paper wallet is now worthless! grrr
I understand your deep and sincere disappointment. It must not have been easy to print five years ago a paperwallet for NavajoCoin, expecially considering the fact that this coin was founded only two years ago. I have to admit it, I'm really amazed by the ability to foresight of the future which you showed us. Or instead more banally, do You have used a DeLorean? |
|
|
|
I see some "new" names in here blaming devs for this , My advice if u don't know what your talking about maybe u STFU ?
 I think this represents very well the moment. |
|
|
|
I think it's fair to honor the swap requests with no time limit, because besides
Cryptsy there are also others address who are not active for some time, but
that may eventually return.
Also in my opinion, it could demonstrate a commitment and sense of seriousness
in the Foundation, and show a continuity of NAV, which is itself a value.
No time limit makes no sense you cant expect the devs to keep the old chain around indefinatly that doesn't make sense. The fact that the swap has no time limit, does not mean that the blockchain should be kept alive at all costs. Probably we can imagine different scenarios, and I have no idea what will be done really, then the rest is just my hypothesis. IMHO, the most important thing in making a swap and that the applicant must prove, without a shadow of a doubt that: A) an address is his property. B) the extent to which it possessed in it. C) the amount can not be swapped again, transferred to others or sold elsewhere. With the current automatic procedure implemented by the DevTeam, virtually all the work is done by the wallet on the basis of the blockchain rules in operation, as a normal transaction. But now as hypothesis, we imagine that the blockchain is totally blocked and frozen, forever. With regard to point B, the amount of what is held can still be checked on the data of blockchain last available block, or on the basis of a specific block took as a reference, and this is a sure fact and is verifiable. With regard to demonstrate possession of an address, this can be achieved by signing a message with that address. Every old wallet or other tools, are in grade to verify if the signature is genuine and it has been made with the key to that address. Obviously, the same amount can not be transferred, or sold, as it is impossible, there are no blocks that can distribute the new transaction. With regard to manually swap twice the same address, Well... this is at the attention DevTeam avoid it.  Surely it is a long manual process, awkward and complicated, that would be worth to do only as a last resort, if and when the blockchain is no longer able to function. I do not remember the details, but it seems to me that in the past swap from SummerCoin to NavajoCoin some addresses have been carried out in a similar way, manually. Excuse the length of reply, but it is an imaginary hypothesis, so it must be described in general at least one bit. |
|
|
|
|
Now a pretty technical question for Pakage about the code of Nav 2 wallet:
For a common user, how much is necessary for the proper functioning of the its wallet
the function FindTransactionsByDestination?
I ask this because I think, that the continuous updating of the data used by this
function (which happen mainly in ConnectBlock()) is one of the the main cause of
the great grow of the size of txleveldb directory, and this causes a progressive
significant slowdown during loading/acceptance of the blocks.
If not strictly necessary for common user, I think this updating of should be made optional,
and normally disabled.
|
|
|
|
If by some miracle Cryptsy is brought back online with all its NAV wallets intact, then we would also gladly swap those coins too, even if it meant the Foundation had to buy back coins it had used for projects.
As far as I can see, the group of addresses which are probably the old "hot" wallets of Cryptsy (approx 963K Nav) are always there, still frozen at 2015-12-06. I think it's fair to honor the swap requests with no time limit, because besides Cryptsy there are also others address who are not active for some time, but that may eventually return. Also in my opinion, it could demonstrate a commitment and sense of seriousness in the Foundation, and show a continuity of NAV, which is itself a value. Personally I still think that the not swapped funds, should not be sold, but the Foundation should only use the proceeds from the staking, but this is just my humble opinion and then honestly it does not count. The members of the Foundation over time may change, and the new members (or those current still remained there) could found themselves having to comply with a relevant undertaking given previously, (re-buy at unknown market price the Nav 2 sold now) without being totally aware of it. Apart from that, during the sync of the old wallet, I noticed that one of the peers still was using the wallet 2.05. I was wondering, the DevTeam, could send via blockchain an "alert" to all the old version, warning that their wallet is obsolete and must make the swap? It may have side effects? I thank you Pakage, for having reported us the concerns of Tristan to make him an automatic swap, but there are reactions from Polo about the other two options, I refer to the enlinst Nav 2 in parallel as a new currency, and / or the simple de-list of Nav 1? |
|
|
|
ok, Everyone pull your coins from poloniex and swap them!
Yes please. We would have a much easier time getting them to upgrade to the new chain if there was no nav on their system. Part of their complaint is that they have no permission to swap people's coins without agreement from each individual. This complaint would disappear if there was no nav in their system. Understandable their ethical scruples, and also very appreciated by a certain point of view. However, it is unfortunate that with the continuation of time this behavior could lead to a certain loss for their clients. I'd like to know, what kind of scruples prevents them, to put on-line as of now the wallet NAV 2.0, and open it to trading? Perhaps, customers might notice the newness of doubles NAV, and at least begin to make to himself a few questions. In this regard, what kind of scruples prevents them to put a banner on the "NAV 1.0" trading / wallet page, which informs that the blockchain has a hardfork and it is advisable to perform the swap ASAP? The same things could be said also for a message in their other social media. With regard to obtain the consent of each client, they know the identity of each client, for AML/KYC, so should not be a problem at least inform them. For last, I do not think that the lack of a formal agreement with each clients had stopped them in the past, when they made the de-listing of entire markets. That said, there are other parts in their complaint? I'm not against Polo, of course the same things will apply also to cryptopia and yobit. |
|
|
|
It seems like the last few believers are in this thread but there are not that many more. although most of the NAV got swapped for 2.0 I only see a few people posting there.
For all the new stuff NAV has recently added and the mobile wallets coming up I expected a lot more attention.
Perhaps it could be for the reason that if the demands remain unheeded, anyone can lose the will to write again. If even the most simple requests remain unanswered, what sense would it make other more detailed questions? |
|
|
|
|
Hi guys!
Shahim or Pakage,
before the start of the traffic for manual swap, I would like to ask you for a
confirmation, what is currently the size of blk0001.dat, and of the txleveldb folder?
Out of curiosity, I can not actually do that, but you've got to measure how
much is the traffic in I/O to the mass storage device, when a new block is accepted?
TIA
|
|
|
|
So swap Nav its free donating because who dont tracking coins lost them ? If 10 % coins not be swapped its 6 000 000 Nav coins to dev team. I am sure that abandon or forgotten coins will be 10%+ (with cryptsy ofc).
Pakage show his wallet adress long time ago and I thing his bought his nice amoun Navs but I am not happy if dev team take all not swapped coins in ratio 1:1 for free because was swap ....
If I something dont understund tell me when I wrong.
This is one of those days when I am very happy to not be part of the DevTeam or foundation.  In fact the question has pretty delicate ethical implications, and it is easy to have doubts, bad moods or misunderstanding. I hope that the automatic translator not make errors and respects the right terms, which in this case are important. If I understand correctly from the official announcement, what the team will have to do, it is not to take the "ownership" of unswapped, dormant or abandoned sums, but rather intends to take the "custody", a subtle but important difference. If you allow me the parallel, the DevTeam will be like a shepherd with the job to care a flock of sheep for grazing, he will have control over them and the responsibilities that them are not lost or get sick, but in the end, the shepherd must return all the sheep to the rightful owner when he requests it. However, as the sheep can produce milk without being consumed, the orphan sums if enabled at staking potentially can produce a small annual gain, and without touching the initial total. I guess this is the gain, which in future will be entrusted to the foundation in a separate fund, and that the foundation from time to time, will authorize the use of this fund to pay for server expenses, and keeping alive and healthy the blockchain, which mean in this parallel, for the good and live of the entire population of sheep. Of course, considering the sensitivity of the matter it could be placed a number of restrictions and rules of conduct, both ethical and technical, but this is a subject very wide. Obviously this is only my point of view. |
|
|
|
We strongly recommend that everyone use Bittrex as the swap mechanism. Manual swaps after the end of the Bittrex coin swap are possible but it does take us a reasonable amount of effort per swap and I'm sure you would rather we are busy working on new Nav features like the mobile wallet rather than being flooded with coin swaps to perform.
Already in contact with other exchange? They accepted? I fear some might consider the Nav2.0 not as an evolution, but as a new currency and put forward new requests. In reference to the operations for manual swap, I was thinking, do you could readjust partly your system for anonymous transaction and use it to perform the manual swap, in "automatic"? If you see it in a very abstract way, after all, these are two very similar tasks. [1] The current system anonymously sends back the transaction in input, and the output on the same blockchain. In that hypothetical ad hoc system for "manual swap", it would accept the input transaction from Nav 1.0, and here it will be burned, sending it to a (malformed) burn-address. At the same time on blockchain NAV 2.0 would start an equivalent transaction from your fund for the conversion, sending it to the new true final destination. All without any real manual intervention by your part. In this regard, I would like your own opinion. Could You ask to Bittrex, if they before closing their old wallet, they can put as last command the order to burn all the old NAV, sending everything to a burn address? IMHO this could facilitate the accounting operations, on what has been converted, and what was left of "live" in the old blockchain. Or may be just a useless complication. Now Package would make a recommendation to you, while you're in the phase of creating the new wallet, I would urge you to bring in even somethings that have been found useful in the old wallet, the system synchronization of time based on NTP, and if possible to improve it by making more stringent the control over the time, and mandatory for all. (There are still a couple of wallet around which do not use it) Most of all, Craig, I strongly urge you to check that the new wallet, do not inherit the old nonlinearities that plague the old wallet. Well, I can only wish you good job. [1] And if in the future, using the same auto-manual-swap system you wanted to create a system for automatic conversion, like shapeshift well... you'd be already in the middle of work done. PS: Sorry for long posts |
|
|
|
I read the announce, the reactions, and I was surprised... well... I expected a lot more insults. Ok, jokes aside, I am pleased that there were no bad moods, I think that the road taken by the DevTeam, is one that allows to get the best results quickly. After the announce, there were some intelligent questions on the technical side, and I think they deserve a little more depth reasonings and answers. For example, the demand on the type of hashing and if there will be a POW phase. If I have understand correctly, the Nav 2.0 is a predominantly POS type coin, then there is not necessity of a strong POW algorithm to enforce a high difficulty or Asic resistance. So I wonder, is it really necessary for calculating the blocks hash, to use all the 13 algorithms of the X13 ? Whereas this is a choice that will take you from here on out, it would not be better to resort immediately to a calculation of the hash more simpler and lighter for the CPU? Regarding the POW stage, I think that a small initial phase is necessary, at least from a technical point of view. In case of pure POS coin, in the initial stage of life of the new blockchain, there is a risk that it might get stuck because there are no mature coins ready for the POS, and without a stream of blocks the Exchanges would not be able to distribute the coins to the holders of the new wallet. If the concern is not to increase the total NAV, the Dev might perform the POW with a reward fixed at 0, it possibly should be enabled\permitted automatically just when there were no blocks at least for a certain number of seconds. The DevTeam would be so kind to give us some more detail on this? Another intelligent question, it is about the interval time of the blocks and the waste of space in bytes which results in inflating of blockchain. In order to reduce the daily blocks (and MByte), it has been suggested to double the block time to 60 sec / 6 minutes for the minimum confirm. But this request as been denied, and the time will still remain to 30 sec / 3 Min, just like as it is now. Personally, I like a quick time for blockchain, IMHO, it favors the ease of use of the coins in real life, and it is more easier for everyone to produce POS block. At same time, I understand very well the concern about waste of bytes \ resource (and at long cpu time) that all this can leads, we have all a proof of what this mean. If we see at the NAV 1.0 blockchain, it is just a raw estimate, but I think over 95% of the blocks that have been generated so far are useless, because they do not have recorded new real transactions, but only the TX needed for the POS itself. IMHO, This it one thing that few can know, but that should not be ignored. Of course part of reasons of this, is due ehm... the lack of real use of coin, and I hope for all of you this belong to the past, but in any type activity there are moment of high load and other with zero work. The new bigger size for block of NAV 2.0 can do its best in the moment of hight load, but IMHO can do nothing for blocks with zero payload. I would ask: would not be useful if DevTeam study also a system with a variable interval time between the blocks? Try to imagine a system which provides minimum interval time for blockchain, to be used just when there are new transactions or they need to be confirmed, and another more relaxed interval time, (ie a minute or more) to be used when there are no real transactions in progress. This system can potentially maintain a low transaction time, but at same time avoid useless waste of byte for long series of empty block. Or maybe they can explore other solution, with new more complex^2 routines, able to recycle or "forget" the previous empty blocks, but at the same time safeguarding the revenues of the POS of their respective owners. What do you think? |
|
|
|
For those that need to move a large amount of coins
Should they move them in 1 transaction. Or send a quarter at a time.
Example. If I had 5million NAV
. Should I send 250,000 at a time instead of the 5 million in 1 shot to Bittrex
I remember Remy5 had some suggestions on Transaction amounts and network strength
You rang?  At the moment I do not remember the precise case. However in general the splitting of payments is more important when you transfer from Exchange to your wallet, so you have more number of stacks of coins that may in the future create new blocks. But sometimes, this can be paid too much for it, because of the fixed fee for each withdrawal applied by the exchange. However, as a general safety rule, when you make a big transfer to and from an exchange (especially one of those small\new exchange) it is better to make a little initial transfer for test, to check if your wallet and that of exchange are both operational and synchronized on the same fork. It costs nothing, aside a little of time, but this can avoid "unpleasant" effects in case of mishaps. This reminds me that there are some things I want to ask .... but first I have other duties. |
|
|
|
Before you start to quarrel, , here is a unofficial rich list just generated today. There was movement at the top. Deep Watch Report block 1 to 2620883 at 2016-02-05 09:57:31 UTC
Hash ea5169d115eb96d88906dfbde697b1a16f8d85a61e69e2b61da241ecd6b84ad3
DWR Rank Address total share Last (UTC) 1st (UTC) POS POW C-Pile
DWR 1 sYYdeJ...J94iE 5886745.776178 9.87 2016-02-02 20:51:03 2016-02-02 0 0 11
DWR 2 sKwYCF...213W3 4457584.523681 7.48 2016-02-05 09:57:31 2015-09-27 223897 0 4223
DWR 3 sJVkG6...zaRCQ 3000000.000000 5.03 2015-02-13 02:02:39 2014-08-14 0 0 1
DWR 4 sfHdGy...Ehvw8 2502000.000000 4.20 2016-02-02 17:46:33 2014-06-12 0 0 4
DWR 5 sa17i3...HZC1u 2311736.041184 3.88 2016-02-01 00:59:20 2014-07-19 10466 0 2539
DWR 6 sX1u5F...LSXkn 2179995.982540 3.66 2016-01-06 16:03:52 2015-12-08 16 0 10
DWR 7 sNoAao...EEVt8 1700000.000000 2.85 2015-07-18 02:25:24 2014-07-10 0 0 3
DWR 8 sU9R59...ci29b 1511192.605901 2.53 2016-02-05 09:54:58 2015-09-30 13174 0 1371
DWR 9 sWqp2p...K6grR 1500000.000000 2.52 2015-12-17 20:17:50 2015-02-13 0 0 3
DWR 10 sh4ztZ...sg6xt 1199999.999900 2.01 2016-01-25 08:43:45 2014-08-24 0 0 3
DWR 11 sTRoU3...ZwzB4 1173548.773112 1.97 2016-01-11 14:00:47 2014-06-05 44045 0 1036
DWR 12 seQ4HR...kRw2b 1071271.421639 1.80 2015-03-14 10:43:47 2015-01-22 117 0 46
DWR 13 sdVwLj...dnmkd 1070046.433783 1.79 2016-01-28 22:27:37 2014-07-31 7263 0 447
DWR 14 seoJDq...sA9C7 1027917.351353 1.72 2016-02-05 09:57:24 2015-12-17 9981 0 894
DWR 15 sVRy5x...K6bF1 993965.000000 1.67 2015-07-10 04:40:10 2015-03-24 0 0 2
DWR 16 sQ3Mbu...9Kg5J 881298.000000 1.48 2015-11-19 22:08:20 2014-07-24 0 0 2
DWR 17 sKWtWm...Syjvq 814700.000000 1.37 2015-11-11 10:51:08 2015-02-17 0 0 2
DWR 18 sMx3hv...p9yR3 732570.304609 1.23 2016-01-09 00:33:51 2014-10-02 0 0 1
DWR 19 sYoVSp...5KBcM 644776.720445 1.08 2015-11-07 04:58:16 2014-06-09 29653 16 640
DWR 20 sb2UWN...3tjyj 644182.778398 1.08 2016-02-05 09:55:47 2015-10-20 13293 0 591
DWR 21 sabh4N...gLMXu 620462.162600 1.04 2016-02-05 09:55:30 2014-06-06 28483 0 563
DWR 22 sKtTgv...zZxpG 597898.519408 1.00 2016-02-05 09:31:41 2014-06-20 5953 0 304
DWR 23 sgNMkC...u9Tws 597409.000000 1.00 2016-02-03 22:19:30 2014-06-17 0 0 1
DWR 24 sYda5n...ji5CF 581625.362596 0.98 2016-02-05 09:52:04 2014-07-17 89359 0 559
DWR 25 sbZuh8...JRrRi 580125.104264 0.97 2016-02-05 09:24:01 2015-05-05 46979 0 619
DWR 26 sX8wkq...V6EKH 577266.807313 0.97 2015-10-01 05:27:31 2015-09-28 81 0 82
DWR 27 sLAucj...7ZSm2 568883.647688 0.95 2016-02-05 09:18:06 2014-08-03 9605 0 520
DWR 28 sQmrFt...JoXD1 515718.201000 0.87 2015-06-30 11:38:02 2015-01-17 0 0 1
DWR 29 sPH7SH...XWyFd 500000.000000 0.84 2016-02-04 16:20:19 2014-07-18 0 0 5
DWR 30 sVXQUU...qcq7f 491280.911205 0.82 2016-02-05 09:48:41 2015-04-18 40488 0 448
DWR 31 sRsizG...FMBgU 486541.000000 0.82 2015-09-24 08:45:20 2014-06-24 0 0 1
DWR 32 sb5oyr...G1eeA 466060.768776 0.78 2016-02-05 09:25:46 2014-08-11 12938 0 389
DWR 33 sVUJMv...4aZwb 429777.963570 0.72 2016-02-05 09:44:18 2015-11-03 12104 0 420
DWR 34 sJUNsL...AanGG 414995.802154 0.70 2016-02-05 09:54:36 2015-03-17 30769 0 375
DWR 35 sSHFR5...HYmG2 405407.340554 0.68 2015-04-17 02:14:18 2015-04-17 0 0 1
DWR 36 sJNqJd...svXMe 400000.000000 0.67 2015-05-01 09:31:52 2014-07-14 0 0 1
DWR 37 sTrVPn...x2jTF 399999.800000 0.67 2014-09-28 15:47:57 2014-09-28 0 0 1
DWR 38 sbyhP1...Cy5Ld 395994.795880 0.66 2016-02-05 01:04:49 2015-01-22 15859 0 343
DWR 39 sQyBKd...gACMS 325000.000000 0.55 2015-08-12 05:42:56 2014-06-09 0 0 1
DWR 40 sUS3fx...pWXJs 321869.018385 0.54 2016-02-04 18:34:44 2015-02-09 3562 0 325
DWR 41 sVzRju...Y3Q4s 321511.233871 0.54 2016-02-05 08:40:57 2014-08-03 9358 0 287
DWR 42 sL2cHa...rCQbt 319111.390921 0.54 2016-02-05 09:21:45 2014-07-17 43294 0 292
DWR 43 sghSvJ...i3ois 301402.300759 0.51 2015-12-17 00:33:11 2015-04-26 3170 0 229
DWR 44 sdR5v6...FjuWJ 300000.000000 0.50 2015-03-27 19:26:29 2014-06-17 0 0 1
DWR 45 sVvNHc...wJEdB 293998.655126 0.49 2016-02-05 09:57:01 2015-04-02 27095 0 300
DWR 46 sboGA4...DMtBK 291536.291497 0.49 2016-02-05 09:45:09 2015-02-26 31826 0 284
DWR 47 sX1TKv...6pZ1V 275884.715282 0.46 2016-02-05 09:29:12 2015-03-21 24511 0 267
DWR 48 sK2Ktg...GdzXW 273698.616272 0.46 2016-02-05 08:49:57 2015-06-01 7893 0 233
DWR 49 sU5VKf...aaHuR 263722.025130 0.44 2016-01-21 04:10:08 2014-11-01 3791 0 167
DWR 50 sdeEZZ...WhSrS 261119.539151 0.44 2016-02-05 08:49:13 2015-03-21 23383 0 237
DWR 51 sSLRfD...Dc5Kz 259410.568394 0.44 2015-12-07 09:32:13 2015-07-17 9782 0 252
DWR 52 sLT24z...x6pL1 254606.088413 0.43 2016-01-11 09:21:45 2015-06-10 18234 0 247
DWR 53 se7WiX...yDhMm 229707.257810 0.39 2016-02-05 09:16:11 2015-06-23 14325 0 221
DWR 54 seQ5NU...2gZgj 228951.790000 0.38 2016-02-04 06:11:16 2015-06-26 0 0 1
DWR 55 sPkA1Q...SF7FM 228614.609436 0.38 2016-02-05 09:02:37 2014-08-03 6666 0 195
DWR 56 sMUihp...kAeeo 220569.850470 0.37 2016-01-24 00:57:51 2014-11-09 2300 0 160
DWR 57 sQp9HC...1Y7hg 217917.966411 0.37 2016-02-05 09:22:05 2014-08-03 6399 0 195
DWR 58 sT1pma...rwThv 215797.853110 0.36 2016-02-05 08:03:01 2015-03-27 6478 0 181
DWR 59 sUBhKt...tyjKV 207364.527389 0.35 2015-12-06 02:04:01 2014-12-29 44292 0 207
DWR 60 sXzjTC...2tEHr 205414.579509 0.34 2016-02-01 15:47:53 2015-03-18 300 0 23
DWR 61 sfBhjn...45pf8 201645.003225 0.34 2014-08-09 11:38:13 2014-06-11 3 0 1
DWR 62 sRARBC...ZMNx7 200000.000000 0.34 2015-04-18 18:11:57 2015-04-16 0 0 1
DWR 63 sRvDoh...E1qRv 187625.492038 0.31 2016-02-04 08:52:56 2015-03-06 15028 0 184
DWR 64 sW6RQJ...Dk2XR 184613.805840 0.31 2016-01-23 20:29:33 2015-05-30 3019 0 155
DWR 65 sXTF4X...XJXdw 179568.615097 0.30 2015-12-25 07:52:21 2014-08-27 881 0 83
DWR 66 scr7hU...snsH9 173615.343137 0.29 2016-02-05 09:39:18 2014-06-28 29509 0 172
DWR 67 sNdVzF...mboYE 159921.605445 0.27 2015-01-17 14:04:22 2014-07-03 1982 0 152
DWR 68 sRrcRd...bN7zX 159515.000000 0.27 2016-02-05 08:03:01 2014-11-23 0 0 1
DWR 69 sQn22B...B2ZUQ 158786.652703 0.27 2016-02-05 09:03:22 2015-02-03 9338 0 129
DWR 70 sKbets...pCKQP 152537.481769 0.26 2015-12-29 10:37:20 2014-08-27 0 0 3
DWR 71 sZ7NLF...AQvWu 151773.072517 0.25 2016-02-04 16:55:50 2015-04-24 1693 0 144
DWR 72 sbP3nh...FxaSL 151391.714459 0.25 2014-07-16 18:13:30 2014-06-03 3953 0 1999
DWR 73 safd7Z...P2gQG 150300.013200 0.25 2014-07-12 07:11:08 2014-06-03 0 20487 993
DWR 74 sceBnh...T3qUa 149999.800000 0.25 2015-02-02 19:35:48 2015-02-02 0 0 1
DWR 75 sKqMpP...4J2Ye 143222.858228 0.24 2015-03-01 09:22:38 2014-06-03 7687 0 135
DWR 76 sKHSvY...Q87Xo 134013.415106 0.22 2015-11-12 00:53:21 2014-06-04 3440 0 132
DWR 77 sSR9o3...uNr9g 129709.883610 0.22 2016-02-05 09:39:18 2014-06-27 20209 0 121
DWR 78 sRiAYM...sqzEZ 122755.709889 0.21 2015-05-13 08:14:32 2015-01-15 412 0 63
DWR 79 sRTSzg...p2YUM 122491.311914 0.21 2016-02-05 09:15:21 2015-03-21 10923 0 109
DWR 80 seB9ju...c66pT 120365.552825 0.20 2016-02-05 08:13:58 2015-01-24 13252 0 111
DWR 81 sUZtrs...58RFa 112737.496383 0.19 2016-02-05 09:48:56 2014-07-31 2242 0 100
DWR 82 sJZL5Q...HXPLV 112569.660787 0.19 2016-01-27 17:35:16 2014-08-03 2153 0 96
DWR 83 seJwpj...vZAyM 108078.885975 0.18 2015-06-26 17:37:55 2014-07-23 6419 0 101
DWR 84 saNZFD...JNCoy 106343.742762 0.18 2016-02-05 09:33:24 2015-03-03 10942 0 55
DWR 85 sJkVxT...BNco2 105607.318952 0.18 2016-01-27 18:30:49 2014-08-03 4547 0 106
DWR 86 sXQban...yWCZL 102548.018668 0.17 2014-09-20 06:40:48 2014-06-04 353 0 101
DWR 87 sP2yNX...T5Haf 100242.176621 0.17 2016-02-05 09:16:11 2015-03-28 453 0 65
DWR 88 sPBC2t...C9wnj 100021.956792 0.17 2015-09-24 09:24:58 2014-06-29 2524 0 84
DWR 89 sWhia2...zWrQm 100000.596148 0.17 2015-12-24 04:23:11 2015-12-23 1 0 2
DWR 90 sPaJXe...L9ogi 99215.732911 0.17 2015-11-23 00:48:45 2014-06-05 1107 0 75
DWR 91 sTGR9c...m3VJy 93954.270789 0.16 2015-05-19 15:39:43 2014-06-09 4134 0 83
DWR 92 sdUAeD...w5fzg 92661.632420 0.16 2015-12-06 01:49:52 2014-09-23 23722 0 99
DWR 93 sfFDdd...aAS6D 91956.673060 0.15 2015-08-30 17:50:16 2014-10-10 329 0 43
DWR 94 sTofnn...5h6YD 87630.912774 0.15 2014-06-23 18:39:58 2014-06-13 701 580 834
DWR 95 sXfRzJ...X9SzK 84239.578717 0.14 2015-03-31 19:23:48 2015-03-31 0 0 2
DWR 96 sQJE41...jPu8Q 83944.623239 0.14 2015-11-10 11:51:30 2015-04-19 3029 0 168
DWR 97 sSj43k...HHRxJ 83750.011165 0.14 2015-07-05 07:23:55 2014-07-18 1062 0 65
DWR 98 sJVrei...TKSjc 83429.112967 0.14 2016-01-26 19:20:53 2016-01-26 0 0 1
DWR 99 sVrFsL...tJiUZ 79999.560100 0.13 2015-11-10 13:21:03 2014-06-11 7594 0 111
DWR 100 sgsER9...62ug2 79895.715010 0.13 2015-03-24 10:47:32 2015-03-24 0 0 1
Regarding the value of the "bounty" address, the Nav Currency part, my wallet sees this: Deep Watch Report block 1 to 2620900 at 2016-02-05 10:06:36 UTC
Hash 8daef0c51d7a31d32710c142c6ecda03482512a98e99529303f0d77a8d8f549f
DWR Rank Address total share Last (UTC) 1st (UTC) POS POW C-Pile
DWR 1 sVKbj8DddwjQ3aSVUSd4ywdeaBdvfWVVen 25000.020117 0.04 2016-02-01 00:36:31 2014-10-28 0 0 3
Below is the list of differences in a month. Deep Watch Report block 2599703 to 2620994 at 2016-02-05 10:50:59 UTC
Hash 3935491ba21550c30ebb5e70acc7ea2000cac31ea37f91a5c3d5125cf56e34fd
DWR Rank Address total Last (UTC) 1st (UTC) POS POW C-Pile
DWR 1 sYYdeJ...J94iE 5886745.776178 2016-02-02 20:51:03 2016-02-02 0 0 11
DWR 2 sRrcRd...bN7zX 159515.000000 2016-02-05 08:03:01 2016-02-04 0 0 1
DWR 3 sbZuh8...JRrRi 34320.120172 2016-02-05 10:39:59 2016-01-29 837 0 -19
DWR 4 seajdZ...grybb 29006.000000 2016-02-05 08:03:01 2016-02-04 0 0 2
DWR 5 sbVt6h...Y3Mxf 20272.829581 2016-02-05 05:31:17 2016-01-31 16 0 11
DWR 6 sLsrJk...EwT63 19999.800000 2016-02-02 20:16:48 2016-02-02 0 0 1
DWR 7 scX4Ro...Aqz9G 18444.590135 2016-02-03 22:19:30 2016-02-03 0 0 1
DWR 8 shRbhx...c4MyN 11556.789999 2016-02-05 03:48:48 2016-02-03 2 0 3
DWR 9 sT1pma...rwThv 7723.423079 2016-02-05 10:23:47 2016-01-30 266 0 -5
DWR 10 sKwYCF...213W3 3973.873038 2016-02-05 10:50:39 2016-01-29 8244 0 -60
DWR 11 sQjzvX...8QrKw 2949.133899 2016-02-02 17:58:54 2016-02-02 0 0 1
DWR 12 sWiBDU...hYfeG 2843.383703 2016-02-04 17:46:59 2016-02-04 0 0 1
DWR 13 sSR4r9...62HEX 1869.360069 2016-02-02 09:05:27 2016-02-02 0 0 1
DWR 14 seoJDq...sA9C7 1462.080107 2016-02-05 10:36:24 2016-01-29 1809 0 31
DWR 15 sRv14o...kVAE7 1360.028765 2016-02-02 14:57:25 2016-02-02 0 0 1
DWR 16 sU9R59...ci29b 1292.606709 2016-02-05 10:41:00 2016-01-30 1184 0 -60
DWR 17 sTW25B...mVBGm 1204.833884 2016-02-02 09:27:52 2016-02-02 0 0 1
DWR 18 sRWvAC...MAmx8 1056.264321 2016-02-02 18:02:16 2016-02-02 0 0 1
DWR 19 sXhutL...RFtj9 988.018882 2016-02-02 18:02:16 2016-02-02 0 0 1
DWR 20 sP4o9x...uqSEJ 901.195223 2016-02-02 18:02:16 2016-02-02 0 0 1
DWR 244 sMLCvQ...7HaYm -996.200941 2016-02-02 18:02:16 2016-02-02 0 0 -1
DWR 245 sPH7SH...XWyFd -1010.000000 2016-02-04 16:20:19 2016-01-29 0 0 -2
DWR 246 sgCmyH...Jeq7u -1070.324395 2016-02-02 18:02:16 2016-02-02 0 0 -1
DWR 247 sK3wsK...v4k9r -1137.191016 2016-01-29 13:59:42 2016-01-29 0 0 -1
DWR 248 sVqjGx...d6pDi -1360.028865 2016-02-02 14:57:25 2016-02-02 0 0 -1
DWR 249 sdjvce...dseqe -1667.952725 2016-02-01 09:50:42 2016-02-01 0 0 -1
DWR 250 shAWqL...YJVrx -1999.900000 2016-02-04 17:46:59 2016-02-04 0 0 -1
DWR 251 scZ7dt...fXd8J -2406.538769 2016-02-01 19:37:03 2016-02-01 0 0 -1
DWR 252 sebTJ5...Y8mc9 -2525.900639 2016-01-31 05:06:15 2016-01-31 0 0 -6
DWR 253 sSM6ma...fRSR1 -3049.133999 2016-02-02 17:58:54 2016-02-02 0 0 -1
DWR 254 seywxL...k76SJ -5000.000000 2016-02-02 20:16:48 2016-02-02 0 0 -1
DWR 255 sJQWDU...Q2Czd -6442.626833 2016-02-02 01:04:02 2016-02-02 0 0 -1
DWR 256 sT3ChZ...KimwA -16235.194117 2016-02-02 17:46:33 2016-02-02 0 0 -1
DWR 257 sb2UWN...3tjyj -29409.927982 2016-02-05 10:35:57 2016-01-29 1140 0 -55
DWR 258 sWkqF8...uuXX4 -30054.411535 2016-01-31 05:06:15 2016-01-29 8 0 -28
DWR 259 sVXQUU...qcq7f -30407.784250 2016-02-05 10:50:17 2016-02-04 64 0 -37
DWR 260 sbqbZf...KbLHk -33333.000000 2016-02-01 00:55:20 2016-02-01 0 0 -1
DWR 261 sUuajz...1n6FD -123330.000000 2016-02-02 17:46:33 2016-02-02 0 0 -1
DWR 262 sPEbnD...cjqPR -159495.625473 2016-02-04 23:48:50 2016-02-04 0 0 -8
DWR 263 sfHdGy...Ehvw8 -503842.000000 2016-02-02 17:46:33 2016-02-02 0 0 -1
DWR 264 sRXgDD...YmUAu -5243095.842849 2016-02-02 20:51:03 2016-02-02 15 0 -2574
Bye |
|
|
|
* Name & Logo changed to prevent any future issues and now we are free and safe from any issues in anyway.
Regarding the name change, what do you mean with "now we are free" ? |
|
|
|
The admin your referring to telling people to upgrade to Tier 2 was Horus if I'm not mistaken I saw him do that in the Chat box.
He was on Dark something radio and he just straight up lied about it and said that wasn't him doing that.
I was warning people in the chat box Not to send such documents to an exchange that was at least in trouble and at worst dying.
I also found it very strange why they would ask for those documents since people that had tier 2 already where not able to withdraw either Scary stuff I'm glad they don't have my documents there god knows what people that dishonest would do with those.
Yes, I remember that some users have reported this point, and in some cases were not treated well. The admin that I had seen do this advert was JShock perhaps, but I think that many have to repeat it, a kind of periodic announcement, and some of them were only moderators. It would be interesting to know who gave them the order to say this, they were probably in good faith. Or perhaps the admission of the old BTC theft, an unfortunate event happened to many exchanges in the past, is not used at this time to divert attention from other more direct event. |
|
|
|
DROp DEAD
Yes... we are losing it. I'm try to staking, but I have just 1 nodes: "addr" : "108.49.48.139:13876". Someone would want to say a few words? |
|
|
|
Currently ALL Cryptocurrencies need to go via a BTC transaction before you can even buy or sell a single Navajocoin. Navajocoin could do extremely well BUT if BTC which is in the technological past has a stumble the entire chain of crypto Currencies pay the price. This is not a Decentralized system. It's not the way for innovation and evolution of this new Monetary system.
If we had a hypothetical vote. Which currency is better Bitcoin or Navajocoin. Navajocoin would win on every comparison .
ROTFL Hashforce is totally gone. It reminds me of a joke of an ant trying to strangle an elephant. However, many believe that all the various AltCoin are nothing but a system to support the existence of bitcoin, and the whole industry which moves around. |
|
|
|
|
Show Posts
