Rasco let's go, let us dream. (And die of envy.)

 

What we are talking about is a share of more than 51% of the network weight,
a parameter that is constantly changing and represents the value of the sum of the individual stake multiplied by the degree of their "age",
present in all wallet that are currently open.

So it is not 51% of the static sum of all the coins generated so far (56M) , but the 51% of all mature
coins in wallet that are currently open.

This number is obviously much smaller than the first because at every moment in the world there are
some users who are off line, or they keep their wallets closed, or have a significant proportion of
coins at the exchage.

And this weakness of the network, in the presence of a single user relatively strong,
in certain conditions should already be sufficient to generate a burst of consecutive
blocks necessary to perform a double spend attack or other damage.
How the other hand, the screenshot shown by Rasco appears to confirm.

Explanation botched enough but hopefully understandable.

This is the result of pure calculation.
In practice, though, as it produces?

WoW!! Your weight is th 55%  of the entire network. Amazing!

Seem really its the first time I meet a whale. ^__^

Please Rasco, don't buy anymore.

It's the same for me too. I get some rare "GnA" with many type of coin, in POS or in POW solo.

Imho, are the others blocks of Rasco which seem a little strange, too much fast and consecutive,
I'm worried he is staking in little fork, but maybe I'm wrong, this is why I asked him to check.

What surprise me is not the generated but not accepted block, but the large number of block generated, one after another,  practically consecutive.

This is not what was to be avoided to resist to a 51% attack ?

Rasco2010 can you check with the block explorer if you are presently in sync ?


The "generated but not accepted" block, usually will be generated again some time later, so you don't lose anything.


PS:
Welcome back SoopY

First reply:
Exactly, the checkpoint now can't ensure the continue sync with mintpal, so if the goal is maintain the sync with them in the next days, then maybe  it behooves us to use them as the first reference node.

This solution does not really like not even to me, but IMHO it would be an immediate solution, available to everyone.
Anyway, in two weeks this solution will no longer work when mintpal will shutdown his wallet.

My preferred solution is a autocheckpoint like the that in Philosopherstone with a checkpoint every five block, but i don't think we have the time to import this solution now, but it can be one of the solution to consider for the next future.


Second reply:
I know, to implement the reading of checkpoint from external file we must anyway patch the source, but this will be one time for good.
When any new fork will rise, we will need only to update the external simple text, and re-download the blockchain, not patch again the source code, recompile and create the bin file for windows \ mac \ etc. for all different system and user.

We can't make a update with checkpoint to select a fork which work for some system and not for other, it will be useless if not even negative for the entire community and the blockchain.

Again this is not the my best solution, but a temporary, simple, quick & dirty practical way.

Glad to read you again.

To avoid further problems, until the next news will come out, hold everything, but the breath.

This problem is already noted from many persons, identified and described nine day ago in the forum,
and a PM was sent to the Dev with more description and thing to do to solve.
(No reply so far)

Seen you are in the role of give announcements and communications, would be so kindle to give us
all the data regarding the two double spend attack ?

We have some data for the attack at Bittrex which is leaked in some message, but nothing regarding those at BTER.

Last question,  who is responsible for updating the website and Open Page?

Did you fear some desease ? 


Regarding this, recently  I' haven't read any message from Cienki7 by many day.

Usually he was very active.... I'm a little worried for him.

First question,  to maintain in sync the wallet blockchain with MintPal, would not be more simple ask directly to MintPal
their node ip and put this as first addnode in the .conf file ?

Second question, regarding the modify at the wallet source, don't will be more practical do a patch to force the wallet
to read the additional checkpoint at start, from a external text or json file ?

In this mode we don't need to recompile\download the entire wallet at any fork or checkpoint update, and the patch
should be relatively simple to do.

Nothing... the void.

I hope this can help.


_Preliminary data subject to revision_

SPECIFICATION:
 
               General:
                                   Symbol: NAV
                                   Algorithm: X13 POW/POS (POW Ended, now pure POS)
                                   Block Time: 30 seconds
                                   Swapped Coins: 25,232,976 -- amount of coins on the SummerCoinV1 Chain (swapped at 1:1 ratio)
                                   Un-swapped Coins: 260,586.00121295   (Donated to the Foundation)

                                   RPC Port: 44444
                                   P2P Port: 44440


               POW (Phase 1 Ended):

                                   Total Coins (by POW): 50,000,000  54260826.00  (see below)
                                   Difficulty Retarget: From block 0 to 250: each 25 blocks, From block 251 on, adjust each block
                                   POW Max Block Height: 14000  (7 days POW only before POS starts along)
                                   Block Reward: 1500                          
                                   Block Halving: 14,000 Blocks (Reward: 150 Coins) , Block 50,000 (Reward 15 Coins)  , Block 100,000 (End of POW)

              Totals at End of POW Phase 1 (block 100000), are been generated :
                                   POW Block : 69518
                                   POS Block  : 30482
                                   POW Coin  : 54260826.00
                                   POS Coin   : 28374.67420825
                        Total Coin Generated  : 54289200.67420825

 

               POS (Phase 1 Ended) :
                                   Min age: 4 days
                                   Max age: unlimited
                                   Minted Blocks Maturity: 60
                                   POW Max Block Height: 14000
                                   Stake Interest: First Year: 20%
                                                   Second Year: 10%
                                                   Third Year + nYears: 5%


              POW (Phase 2 Ended):
                                   Extra Coin for Repay Exchanges : 2.6 million
                                                     (Generated on BLK 141351)
                                   POW Start Date:  July 16, 2014
                                   POW End Date:    July 20, 2014                  
                                   POW Min-Max Block Height:  141296-160000
                                   Block Reward: 1.5 Navajo Coin                          
                                   POW Effective Block:     9584
                                   Total Coins (by POW):  14374.5



              POS (Phase 2 Started) :
                                   Min age: 2 Hours
                                   Max age: 1 Day
                                   Minted Blocks Maturity: 60
                                   POS phase 2 Start after Block Height: 141350               // FIXME
                                   Stake Interest: Rest of first Year: 20%
                                                   Second Year: 10%
                                                   Third Year + nYears: 5%

                          
 
_End Preliminary data subject to revision_


EDIT:   Totals Recalculated

Thanks for info.

A great idea.... Big rollback of the Bit-coin and every coin, and all other exchanges too.    O:-)
(I foresee a generalized riot)

AFAIK there is not a rollback, the blockchain is going forward.

Personally, I would like to know why for other coin all exchanges accepted to do a rollback, and this is not happen for NavajoCoin.


Replying to another message:

The beta test i think is never started, it's just shifted to later time not yet announced, but surely less of 3 week.

If you would search,  you can find more detail in one of the previous message of SoopY.

Someone else replied at a similar request in the past, He wrote:

"You can try repairing your wallet with the command "repairwallet", open console and type this.  "

I hope this method will work good for you also.

AFAIK, if a sum of coin is already in staking, you can't stop in the middle of process,
the sum must mature 60 blocks before they can be spent.
Of course not all your coin will go in staking at same time.

One other point to think is how much time the exchanges take before to accept and complete a deposit.

Few day ago I made a series of a test, depositing few NAV to the exchanges.
Poloniex had requested 15 confirm to complete the deposit, BittTrex 30,
Bter 30 confirm to show a sign plus another 30 to process.

If you consider each confirm should be roughly long 30 second (but with POS it
may be irregular, even much longer), we get a long time to complete a single transaction
to the exchanges, and the market quotations in meantime can be radically changed.

I appreciate your effort, but subsequent data of the coin are obsolete, they have been changed in the latest update of SoopY.

The pow phase seem it's gone, again. Now only POS.

Keep the wallet opened.

Sorry GreedyJohn, for stolen your style. 

In part, I agree with you.

Honestly though, we must recognize that there are many members of the foundation who are active,
sometimes even too much    , but they can not always be present H24 / 7.

And even they sometimes have no information, like us.

I appeal to boys of foundation:
from what I read above, it seems to me that Soopy expects from you  do all the necessary updates to the OP.

And there are a lot of updates to do, practically almost all the technical specifications of coin have changed.
Nowhere in the OP has been written that the wallet must be kept open, in order to regularize the block chain.

Now I do not know who within the Foundation has the mandate to physically update the OP, but at least I would
kindly ask that someone of you will begin the work, preparing a draft ready to update the OP as soon as possible.
(Yesterday possibly. )

IMHO,  If we want Soopy can go on in its work in the better way, the boys of the foundation should help in the easier tasks.