Skip to content

Instantly share code, notes, and snippets.

@ajcwebdev

ajcwebdev/index.md

Last active May 1, 2024 18:09
Show Gist options
  • Save ajcwebdev/8feab31c915a4b2eb8160a5bf9d7c541 to your computer and use it in GitHub Desktop.
Save ajcwebdev/8feab31c915a4b2eb8160a5bf9d7c541 to your computer and use it in GitHub Desktop.
Download ZIP
IPFS and Dash
Raw
index.md

walker — 04/01/2024

Using Dash platform as a CID repository is one use case, but much different from hosting your whole front-end over IPFS.

  • The latter situation assumes you have an application in the first place.
  • It is a second-phase type of a problem, and likely premature optimization, unless the trust-less-ness is truly a requirement (or at minimum a significant selling point) for the app to exist at all.

Demo idea

create the minimal html+javascript (aka "the wrapper)

  1. import helia
  2. present the user with a form field to input a CID
  3. user inputs the CID of a dapp
  4. dapp gets loaded via helia using the trustless http protocol
  5. dapp is rendered within a child element
  6. message is give to user confirming that the dapp CID and the fetched content all verify together

The wrapper is hosted using normal web2, from a host that the user trusts.

  • It basically acts like a storefront.
  • Any application CID input into the wrapper gets validated and presented to the user.

Maybe

  • Maybe it does a lookup on Dash platform to verify the CID has been registered in a Dash platform registry contract and fetches the Dash identity associated with that, then presents that info to the user.
  • Maybe also shows the database query proof as well. That is starting to sound a bit more interesting now.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment