Network Protect in case of EMP

[Mr760]

Is there anything being done to protect the Ripple Network from a EMP like situation? There's no hard wallet I can put into my Faracage for a backup. So if I'm doing that what IS Ripple doing to secure the network? Also... Will we have a secure place finally Ripple will stake a claim or guarantee to?

[Morty]

I'm working on a clockwork ripple node.

[Professor Hantzen]

14 hours ago, Mr760 said:

Is there anything being done to protect the Ripple Network from a EMP like situation? There's no hard wallet I can put into my Faracage for a backup. So if I'm doing that what IS Ripple doing to secure the network? Also... Will we have a secure place finally Ripple will stake a claim or guarantee to?

You can write your ripple secrets down on paper.  Same for bitcoin private keys.  You don't need hard wallets and a faraday cage to take your funds completely "offline". Though, the type of EMP event you seem to be suggesting - that would presumably require such measures - might also render the value of cryptocurrencies somewhat worthless, at least for the duration of time you'd immediately be requiring funds.  I'd expect you'd be better off stocking up on paper money, as that's what I'd imagine everyone would immediately revert to.  

Crypto-currencies have little value without a working set of interconnected nodes to process payments & mine, etc, not to mention people with working computers and internet access to interact with them.

[Sukrim]

Global EMP is unlikely, Amazon going down globally is more likely (and would have a bad impact on big parts of the whole internet). At least my local node has full history and I'm still looking into ways to make full historic data more available to others.

Keys can and should be stored in paper form and they are your responsibility alone.

[T8493]

8 minutes ago, Sukrim said:

Global EMP is unlikely, Amazon going down globally is more likely (and would have a bad impact on big parts of the whole internet). At least my local node has full history and I'm still looking into ways to make full historic data more available to others.

 

How do you plan to do this?

I'm trying to populate my CouchDB cluster with old transactions (retrieved from rippled), but the whole process is extremely slow and error-prone.

 

 

[Professor Hantzen]

2 hours ago, Sukrim said:

At least my local node has full history and I'm still looking into ways to make full historic data more available to others.

How big is the full history?  And is that compressed?

[Sukrim]

3 hours ago, Professor Hantzen said:

How big is the full history?  And is that compressed?

I would calculate with about 5 TB in total if you plan to set up a server (currently > 3 TB nodes and about 1 TB sqlite databases, give or take). Make sure to keep an extension plan in mind. I don't think there's much compression going on beyond snappy compressing individual nodes.

Also make sure to have this on SSDs by the way.

6 hours ago, T8493 said:

How do you plan to do this?

I'm trying to populate my CouchDB cluster with old transactions (retrieved from rippled), but the whole process is extremely slow and error-prone.

I query full ledgers in "binary" format, re-build the SHAmaps (and verify that I have all nodes), sort all nodes within a certain ledger range (to make this deterministic and externally reproducible) and dump them in storage format to a simple JSON text file. I still need a way to efficiently do this and to import them into RocksDB or (ideally) NuDB. The deterministically generated dumps could be shared (e.g. via BitTorrent) and archived, since they cannot change any more and they are extremely close to what actually is written in the databases so they are easy to import. Having them in a relatively verbose expanded format (text based JSON) doesn't really hurt, since it is easy to compress that with any modern compression algorithm.

Currently if you sync full history from scratch, in the best case you'll take a few weeks or months, unless you already get a database from someone else you trust. This data would still need to be verified though, so having it available for import might be better.

A less data intensive strategy would be this one: https://forum.ripple.com/viewtopic.php?f=2&t=7994

[T8493]

12 hours ago, Sukrim said:

I query full ledgers in "binary" format, re-build the SHAmaps (and verify that I have all nodes), sort all nodes within a certain ledger range (to make this deterministic and externally reproducible) and dump them in storage format to a simple JSON text file.

 

Why don't you use rippled to directly dump ledgers in JSON?

 

[Mr760]

Thanks for the replies everyone, My thoughts on an emp or smart/small nuke explosion brought about my thoughts regarding radiowave damage. Now... I was reading a comment by Professor Hantzen and  stocking on paper money but I think I will stick to coins, the gold and silver kind and hope that XRP and this wonderful idea (Ripple Network) do well globally and stay online cos I feel that Swift have been made an offer they can't refuse for long. So gold and silver are my bets and XRP..... Does anyone know if Bitcoin will crash?....You know the saying what goes up must come down.

Again guys, thanks for the reply. 

[kanaas]

cos I feel that Swift have been made an offer they can't refuse for long.

Hm.... Why do you think that?



Verzonden vanaf mijn iPhone met Tapatalk

[Mr760]

In short, the SWIFT systems old, expensive and slow and they're likely, to get left behind should another CBPS make sense of the market. Should there be another reason?

[Sukrim]

On 24.12.2016 at 1:00 PM, T8493 said:

Why don't you use rippled to directly dump ledgers in JSON?

I do, but this is not the format that is in the database, also it will not include inner nodes and will still have to be deduplicated.