dApp via GitHub saved to Filecoin-Pin, approved by Safe, updated to ENS

[timfong888]

What We're Building

Automated dApp deployment system triggered by git commits. When developers push updates to the repository, GitHub Actions automatically uploads the new version to IPFS via Filecoin Pin, then creates a Safe multi-sig proposal to update the ENS contenthash.

Reference: https://github.com/FIL-Builders/filecoin-pin-ens-demo

Target: https://github.com/safe-global/safe-wallet-monorepo

Trigger

Event: Developer commits and pushes dApp updates to main branch

Action: GitHub Actions workflow automatically executes:

1. Build updated dApp
2. Upload to IPFS via Filecoin Pin
3. Verify gateway accessibility
4. Create Safe proposal with new CID

Result: Safe signers receive proposal to update ENS to new version

Current Demo (Single Wallet)

Developer pushes to main branch
  ↓
.github/workflows/build-site.yml (triggered on push)
  └─> Builds dApp → artifact: site-dist
       ↓
.github/workflows/upload-to-filecoin-and-update-ens.yml (workflow_run trigger)
  ├─> Download site-dist artifact
  ├─> filecoin-project/filecoin-pin/upload-action@v0.9.2 → CID
  └─> scripts/update-ens.mjs
       └─> wallet.sendTransaction(resolver.setContenthash())
            ↓
ENS contenthash updated immediately

New Flow (Safe Multi-Sig)

Developer pushes dApp updates to main branch
  ↓
.github/workflows/build-site.yml (triggered on push)
  └─> Builds dApp → artifact: site-dist
       ↓
.github/workflows/upload-to-filecoin-and-update-ens.yml (workflow_run trigger)
  ├─> Download site-dist artifact
  ├─> filecoin-pin action → CID (keep existing)
  ├─> scripts/verify-ipfs-gateway.mjs (NEW - verify accessibility)
  │    └─> Try ipfs.io, gateway.ipfs.io, dweb.link
  │    └─> Retry up to 10 times with 6s delays
  │    └─> Exit 1 if inaccessible → workflow fails
  └─> scripts/create-safe-proposal.mjs (NEW - replaces update-ens.mjs)
       └─> Safe API: propose resolver.setContenthash() transaction
            ↓
Safe signers review and approve in Safe UI
  └─> Signers can test CID at https://ipfs.io/ipfs/{CID}
       ↓
Safe executes transaction when threshold met
  └─> ENS contenthash updated

Key changes:

1. Add gateway verification before Safe proposal
2. Replace update-ens.mjs with create-safe-proposal.mjs
3. ENS update requires multi-sig approval instead of immediate update

[v1rtl]

Omnipin already has such flow in-built, no custom code needed. Battle tested with some projects, works like a charm.

The process goes as follows:

— Upload to N providers on IPFS
— Locally construct and sign a transaction by a proposer
— Send the transaction to the Safe API
— Open Safe app to approve it or reject it

Further info here:

— How the proposer flow works: https://omnipin.eth.sucks/docs/how-it-works.html#proposer

— Sample GitHub Actions workflow: https://omnipin.eth.sucks/docs/ci-cd.html#github-actions

— omnipin ens command docs: https://omnipin.eth.sucks/cli/ens.html

If interested, I can cook up a simple GHA that reuses the outputs from filecoin-pin, or submit a new one that does it in one go

[timfong888]

How does your support the safe confirmation flow @talentlessguy

[v1rtl]

How does your support the safe confirmation flow @talentlessguy

OMNIPIN_PK=0xProposerPrivateKeyHere omnipin <deploy|ens> --safe 0xSafeAddressHere

both omnipin deploy and omnipin ens support the Safe proposer flow (and another one that's soon to be announced)

[timfong888]

I see. Got it. So the GitHub Action would use Omni pin. It would pin to multiple providers, one of which is the one that runs on Filecoin.

[v1rtl]

That, or filecoin-pin + blumen ens ${{ outputs.cid }} --safe 0xsafeAddr, both work

[timfong888]

Could we use this to get clarity on:

1. If @talentlessguy is blocked or can enable a PR that Safe can review?
2. What steps are needed for Safe to review and approve by 11/10-ish so we can have some airtime when we do announcement at DevConnect.