and host in on three P2P protocols (DAT, IPFS and Swarm).
Let's Try It!
Ingress' offers a quick way to get your ÐApp file hosted and served from P2P storage, even if you don't have P2P storage clients installed.
If you have built a ÐApp that talks to a blockchain on the back-end, your back-end is as secure as the blockchain and your Smart Contract code. But serving your ÐApp's front-end from a centralized server using DNS can create painful security risks for your users.
You can also have Ingress "cross-pollinate" your ÐApp file already living on one P2P protocol and replicate it on to two others. Ingress currently supports DAT, IPFS, and Swarm as P2P file storage protocols that can be automatically cross-pollinated to.
Your ÐApp now has your <ingress> tag injected into it. Download your tagged version using the button above. You can now add your ÐApp to Peer-to-Peer file systems by using the form below.
Register your ÐApp and its checksum to Ingress' smart contract Registrar (requires ETH for gas). Ingress will consult your registration and checksum on each ÐApp load for your users.
View your registered manifest by clicking the button above.
This feature is a simple checksum utility which allows you to checksum a ÐApp file quickly without adding it to Peer-to-Peer filesystems. It does not inject an Ingress tag, but will allow you create a checksum that Ingress can validate if you add your own tag.
For end-users using ÐApps that have been registered to Ingress, you can use this tool to check it's checksum if you got it from somewhere other than Ingress or if you do not want to load it directly though Ingress.
to automate validation of your ÐApp's front-end for your users.
Take me to it!
Help bring some of the security of your ÐApp's blockchain back-end to its front-end by registering its front-end code to a blockchain too. This feature allows you to register your ÐApp's metadata and its checksum to an Ethereum Smart Contract registrar on the Ethereum Foundation public blockchain (note: this feature requires a web3 compatible wallet or browser and a small amount of Ethereum for gas).
By registering your ÐApp's front-end to a public blockchain registrar you can prove your authorship if needed, but more importantly, you can build security features into your ÐApp experience that utilize an immutable and decentralized version of an application certificate registry.
Once your ÐApp is registered, you can use Ingress' client-side validation features to build tools that perform a "decentralized version" of a sub-resource integrity check by consulting the registrar to check for modifications if served over different environments.
Load a ÐApp
securely from P2P protocols.
Let's Try It!
For many ÐApp users, it can be kind of scary to use a ÐApp. A lot of us remember the Mt. Gox hack that sent Bitcoin prices tumbling. You also might remember the more recent hacks on EtherDelta and MyEtherWallet.
There's a lot of talk about how well-witnessed blockchain networks are secure, immutable, and borderline "un-hackable," and yet cyber-theft of cryptocurrency still happens. But the majority of those incidents are not an issue with the blockchains. The common issue in the hacks mentioned were vulnerabilities in the older, "centralized" infrastructure of the internet used to interact with them.
This feature allows you to load a ÐApp stored on newer and decentralized internet architecture, P2P file storage protocols, without having to install the P2P client software yourself. When you load a ÐApp from a P2P protocol over Ingress, Ingress tacks on some additional security precautions for you to create a safer ÐApp experience that bridges the security of blockchains with the convenience of surfing the web and the redundancy of P2P file storage.
if code has changed or new versions are available.
Load a random ÐApp
When you load a ÐApp over Ingress that has been checksummed and registered to Ingress' Registrar, Ingress will consult the registrar and determine if the ÐApp file loaded is the same as the one registered. In cases where the file has been tampered with since the original developer registered the ÐApp, Ingress will throw warnings signaling that the checksums do not match.
Additionally, if you have a favorite ÐApp that the developer has registered to Ingress, Ingress will monitor the Registrar for newer versions from the same developer for the same ÐApp and let you know that a newer version has been released.
Support & Secure ÐApps
by pinning them to your own nodes and keeping them available.
Ingress.one is a free service running an instance of Ingress, the application. It helps ÐApp developers store and serve their ÐApps over Peer-to-Peer filesystems and it helps users have more confidence in the ÐApp files they are accessing. You can help the ÐApp community keep ÐApps alive by running an Ingress node of your own -- and it will talk to and sync with this one.
Ingress.one is using HyperDB to store data. HyperDB is a "distributed data store" which acts like a database that is stored on a decentralized file system just like the ÐApp files Ingress serves. When you run an Ingress node, you can connect your node to Ingress' HyperDB, which will allow your node to sync with the ÐApps Ingress.one and all other Ingress nodes are hosting and know about.
Ingress nodes come equipped with IPFS and DAT as two distributed file systems out of the box, and Swarm as an additional file system that it supports after Swarm is installed externally. By running a node, you can help "pin" ÐApp files, check the Ingress Registrar for users connecting to your node, and help keep the ÐApp community safe.