I  was amazed at how you are able to integrate well and quickly an image taken for
a joke and have given him a sense. My compliments.

I just ruined your image a bit, and I would have to alternate better levels of snowflakes
and coins, to give more depth to the image.

The character in the photo intrigued me, and I found out who it is: "Ragnar" the official
mascot of the Minnesota Vikings, it looks like a singular type.
His site:
http://www.ragnartheviking.com/

Who would like to see him in "action", while parodies of cheerleaders, here's a video:
https://www.youtube.com/watch?v=Xh4HJilqEyQ

It is my duty to advise against the vision from people faint of heart and pregnant women.


Another clumsy attempt to imagine Ragnar \ Hashforce in his role in the defense:


Bye Bye

Something starting from this image?



 

Roughly speaking, in order to compare, how many watts it consumes?
And there would be enough resources for wallet of other currencies?

Bye Bye

Basically you place an elephant on a matchbox.
Do any of you know if there is an organization that fights the badness against microprocessors?

 

I never thought that Win 7 could also run on Raspberry.

The remote procedure call (RPC), give a interface to external program (or remote
computer) to interact with the your wallet, to give at it commands and get
from it some responses.

Normally the user of the GUI Wallet, don't need to use it explicitly, can more
simply use the debug\console windows without the need of other permanent
settings.

But in a more complex scenario, like nogui Linux wallet demon, or solo mining,
or other integrated service (IE payment platform, block explorer etc) , then
 in this case you must use the RPC, and You must give to the wallet a set of
secret setting like RPC User\Password\Port\AllowIp for autorize the incoming
connection only to you, and your programs.

Otherwise, if you don't have previously locked the wallet,  an external user could
give at your wallet some nasty command, like transfer away all your funds.

So if you don't use RPC, don't worry, but if you must use it, then use long
user\passoword and keep it secret.

Regarding the power waste, I think the Raspberry Pi (a lilliputian micro sistem)
plus a external usb memory card \ hd, can be a valid solution, but i don't have
any direct experience.

Here someone else can give more information than me.

Bye Bye

 

Few hours? On my experience, You are a very lucky man. )


Yes, you are right, the database can only grow, IMHO this is a common
problem with all the cryptocoins in general.

Recently I not followed the new coins, so I don't know there is any
new way or idea to shrink the blockchain database, but I think
it would require a complete redesign of the structure of the cryptocoin
itself.

In some operating systems, you can automatically compress a directory or just some files,
it might seem a simple solution, but in this case IMHO I do not think it's a good idea
because the database files have continuous access, and this continuous de \ compress
the data files may slow down the system too.

To reduce sync time, Shahim proposed an idea of storing on the site a set of
small blockchain datafile, to be loaded by the wallet in case of necessity.

This idea can help, but it don't change the ever growing way of work of wallet.


Ehmmm... no. It is used by internal database, but it is not the database.
Its contents change at every installation, and don't grow much.
No need to share.


Used in some way for the transanction's database and index,
grow with use.


This is THE blockchain database, it grow with every block, with time it grow, grow a lot.


It avoid multiple istances of wallet, and db.log store the log in case of internal
database problem, usually they don't grow.


Keep a trace of many wallet's internal activity, and grow a lot, especially in case
of error. If you dig enough is the only way to hypothesize the reason of errors.
If it become too big, usually, it is auto-cutted during the wallet restart.


Dynamic-Link Library, some set of common or standard routine and API for\from GCC, C++,
and Thread used by the PC Win program, in this case the wallet.


This file store a sort of ip:port phonebook, with the list of other wallets (peer),
those peers form the coin network.
This file is regenerated and continuously updated by wallet, and the element
in list are tested and exchanged between peers, to keep the network working and alive. 


Good question.  The wallet can work even without a conf file, using hard coded value.
In it you can also set some start commandline parameters.
NOTE: The rpcuser and rpcpassword must never be show to other or shared.

I'm sorry to have given some answers in a hasty or superficial manner, it's late night.

Bye Bye

No for Your tentative of immediately fix the site, there will be not forgiveness, and no appeal.
This will be His condemnation: stay on their knees, on the dried chickpeas, for all the
time needed to recharge the block chain, reciting in rhyme, the hash of each block loaded.

 


Joking aside, it seems clear from the reactions that the pages of the faucet and richlist,
enjoy of a constant audience.

Considering this fact and leaving unbridled the imagination, in the future it would not be
the case to consider the idea to put some form of banners for a fee?
In this way, with the proceeds, you might find a stable form of self-financing for the
faucet mainly and in part for the Foundation.

Of course I realize that it would not be nice to see on the official site, the presence
of banners that advertise for example some emerging competitor, but maybe you could
find a compromise solution, which protects both the aesthetics and the authority of the site,
and the opportunities for self-financing.

After all, the servers that are used by the sites, they do not pay for themselves magically.

Bye Bye

Typically it should be updated every hour, unfortunately is missing (yet) an indication
of the time of last update.

Indeed some voice in the list, right now seem a bit outdated.

Only as a hypothesis, perhaps when there was a change of server,
the update of the counts was slowed.

Surely Pakage or Shahim, will control the site as they come back again on-line.

Meanwhile, try to verify your addresses in the block explorer, which AFAIK is correct.

Bye Bye

"And in the naked light I saw
Ten thousand people maybe more
People talking without speaking
People hearing without listening
People writing songs that voices never shared
No one dared
Disturb the sound of silence"

http://www.youtube.com/watch?v=L-JQ1q-13Ek


Ok, maybe not the right place, but it is always a pleasure for me to remember its melody.

Bye Bye

A brave move, my best wish.

This recall me a message of some time ago, in that message was announced the near launch of a new coin,
created by an artist to be used for advertise and sell its album, based on the anonymity model of NavajoCoin.

Now I don't want to revamp the old polemics, I would just know if the coin has been succesful launched,
and possibly its name.  Just curious.

Maybe I did not understand your statement.

From what it seems from block 663 086 (2014-11-22 07:16:31 UTC), up to now Blk 667992,
only four addresses have really produced some blocks.

They are :
sQUPW9 ... Fk6XG
sXKG7M ... tzXin
sZSXPj ... oUjKo
sYpxBb ... nQWLG

If one of your addresses is among those written above, please double check your system clock.
It is wrong, and is disturbing the blockchain.

Bye Bye

+1  

Personally I think to leave the wallet open, at least I can follow the events.

And then we can always hope for a small blackout very localized.


Bye Bye

There is a command of the wallet, who writes in debug.log a representation of the entire tree of blockindex,
with all blocks which have been registered in the database of the wallet, including orphans blocks and incomplete chains.

After a long wait, the result is a huge mass of shapeless text, in this case about 100MB, difficult to manage.

Now to answer your question, with all the necessary precautions, as far as I can understand, from the block  662 984
which is prior to the current problem, until the block 665 908, they form a single chain.

At least we have one good news.

Bye Bye

I am always too cryptic, sorry.

I was referring to hashforce101 only for its constant commitment to NavajoCoin propaganda,
and in the way he still find the bright side of everything.

Do not really want to offend anyone, I want to be clear on this.

Regarding the technical side, there are always many ways of doing things, each with its
pros and cons, and often even the best ideas can hide potential pitfalls.

So IMHO, any intervention requires a acute analysis of the DevTeam, to properly evaluate the effects
possible in every scenario.

Personally I would not want it to be made a modification too botched, forced by the urgency,
which can create more damage than it solves, as sometimes I've seen in other currencies,
but this is just my opinion.

For the rest, I basically agree with you.

It seems to me that from the block 663085 there are only four addresses, it is probably a single (heavy) user.

Bye Bye

Another way of looking at the situation is that we can now say with absolute certainty
and without fear of contradiction, that the Navajo Coin is so directed toward the stars
and projected for the future, that at this very moment is already gone in the tomorrow.

I will not take off work to hashforce101, it's just a (sad but true) joke. 

Who knows, maybe repeat the warning to check the system clock in other languages
harder to comprise, for example, Mandarin Chinese, could help.

You're both right, and it's already happened in fact, I think they were called TimeBomb.

I do not remember the details, so sorry for the great inaccuracy, but something related to the negative
time of the block, and the mechanism of Difficulty, it's already happened in the past to philosopherstone long
ago and Tek few weeks ago.

In those cases a malicious block originated in the "past", had set up the Pos-Diff to the stars and it was almost
impossible to generate a new block POS.
Those coins were still usable because they were hybrid POW / POS, and the POW has not been
affected and has kept alive the coin until their Dev applied a patch to PosDif.

It seems to me, that a different fate befallen to another currency (BC or WC can not remember),
that even before the previous cases (or perhaps the first ever to suffer from this problem) had been
attacked in the same manner, and being only POS had been badly damaged remains completely paralyzed,
and has required a lot of time and work to be started again.

From this kind of problem more serious, NavajoCoin is already vaccinated, the source code limits the problem
of the times negative, the most harmful.

So the maximum we can suffer is the inverse, it is an excess of blocks, just as we have just experienced,
followed by a scarcity of blocks due to the fact that in the meantime, many users have produced stakes,
and then have groups of coins immature.
But thanks to the minimum time of stakes of 2 hours, the stream of blocks stabilizes a bit at a time in a short time.

(I can guess for a while there will be a bit of "elastics effect" until the Diff and CoinAge will settle again.)

As you can see there is a evolution, and recent wallet learn from the problems of the oldest.

Thanks, just try to help.

Over time, sometimes the old block explorer was not available, or it was too awkward to use,
so to get the aggregate data, I was forced to reinvent the wheel, and do some personal routine
(constantly changing) that could extract some data from the wallet.

A few times I have called them "independent research".

Most often this data is just a blob of boring data, where it's easy to lose your bearings, or routines
that freeze the PC and the wallet for 20 minutes, then impractical or even counter productive,
but sometimes they can be useful.

I guess the real developers have their own tools to analyze the block chain.

Bye Bye

Take him to the stake ... I mean the burning pyre.
    

However don't worry, you are not the first, had already happened on a smaller scale to
another heavyweight few days ago, and luckily he has correct his watch.

Bye Bye