ndm-inf / ndm

Run IndImmUI Locally

This project was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.2.

Clone this repo: https://github.com/ndm-inf/ndm.git

Install Angular CLI: npm install -g @angular/cli

Install Dependencies: npm install

Run Locally: ng serve

Navigate to `http://localhost:4200/`

How does IndImm work

Below is a quick summary on how IndImm works. More detailed high level and low/dev level documentation for the IndImmUI application and the IndImm Message Protocol (IMP) will be provided shortly. All sourcecode is available at https://github.com/ndm-inf/ndm where the master branch is what is currently deployed.

The highlight/10,000 ft view of how IndImm works is that the IndImm Client utilizes the IndImm defined IndImm Message Protocol (IMP) operating on the Ripple block chain and takes any file and loads it into local memory in your browser with the IndImm client and attaches the file as a Base64 string to a ripple payment. When the payment is sent, the file data is attached directly to the payment and once confirmed on the ripple ledger across all decentralized ripple validators, it remains permanent on the ripple ledger and cannot be removed and changed and is therefore Indestructible and Immutable.

However, most files one would want to potentially store with IndImm will be much larger than what can be stored with a single ripple transaction and thus, IndImm chunks the file into small portions that each will fit into a single transaction and stores the file across multiple transactions which are chained together sequentially with pointers to each child transaction. Lastly, a root transaction is sent to ripple containing a reference to the transaction chain. To pull a file from the ripple blockchain, the root transaction is referenced and associated chained transactions chunks are pulled and recombined back into a single file. In addition to the file chain reference in the root transaction, additional text can be included with the file and is stored in a separate child transaction chain referenced by the root object.

Donate

XRP:rw2htZCsyJk8yNRYDxjiv9QFiZ2yqCQCPJ

XMR:47Nye79bFFea5Crez8xS7zjjjwBTYbSBD9mxDLfBcNPSXejx8MXxRgy545GNVEGu2HbSTyfJhHfcod9VcXXiZcYw7x3x6se

BTC:bc1q9nfy6f6t5rmd0pz0k4ygrycq7g2h5k5gg3a58k

ETH:0x37aaA1069c8E26d81fE2Bf6BE958f43cB6b731Ca

LTC:LgiG6nz4Q7zuYdT6Z2KC6BWevRGMXqDbfP

ndm's Issues

Please consider this

Let's start with a big thanks & hats off to you, as we can't have enough development in this ecosystem. Great to see you jumped in 😎

On a different note: I'm worried. I operate a full history node on the XRP ledger. I am very very much afraid of what will happen when your service will get some actual use. It'll be a matter of time before illegal content will be uploaded. Especially with the hate against the XRP community from maxi's. When someone uploads pirated content, or worse: child abuse images, no one would be able to remove that from their full history servers.

That would mean it would become a legal nightmare to run full history nodes, not only for me, but for all XRPL enthusiasts and businesses.

I would kindly ask (beg) you to take down the project.

P.S. In the long term I would suggest an amendment for the XRPL to exponentially increase the minimum transaction fee when large memo's are being sent. That would render this 'use case' non viable. Again: I really appreciate your efforts to develop for the XRP ledger, and please keep on doing so! But if you want to store files, consider using tech. meant to store files.