Integrating DeWeb with Massa: A New Era of Censorship-Resistant, Autonomous dApps

Proposals
1
  1. Abstract. This proposal suggests adopting DeWeb, a decentralized web hosting protocol developed by Massa Labs, to improve the availability, security, and resilience of Superfluid’s key public resources — including superfluid.org and the SIPS governance system. DeWeb offers fully decentralized, censorship-resistant, and immutable web infrastructure without relying on IPFS or centralized servers.
  2. Type. Non Constitutional
  3. Motivation. Superfluid’s governance and developer ecosystem depend on the accessibility of its documentation, dashboards, and proposal processes. In regions subject to internet censorship or infrastructure shutdowns, access to centralized websites (even on IPFS gateways) may be unreliable.

By leveraging DeWeb, Superfluid can:

  • Ensure global, permissionless access to governance and documentation.
  • Protect critical infrastructure from takedowns or DNS-level interference.
  • Make the frontend immutable and verifiable, reducing attack surfaces.
  • Improve availability beyond IPFS by replicating websites across >1,200 nodes worldwide.
  1. Rationale. Why DeWeb over traditional or semi-decentralized hosting (e.g., IPFS gateways)?
  • Feature Traditional Hosting IPFS DeWeb
  • Censorship-resistance :cross_mark: :warning: (via gateways) :white_check_mark: Fully decentralized
  • Immutability :cross_mark: :white_check_mark: :white_check_mark:
  • Global availability :warning: :warning: :white_check_mark: (native redundancy)
  • On-chain deployment :cross_mark: :warning: :white_check_mark:

Hosting fees Recurring Low None (after upload)

  1. Specifications and Steps to Implement

We propose the following steps:

  • Mirror the static content of superfluid.org on DeWeb.
  • Publish SIPS-related content (specs, discussion threads, history) to an immutable DeWeb site.
  • Offer DeWeb as a publishing option for contributors and ecosystem apps.
  • Evaluate a long-term roadmap for progressive decentralization of Superfluid’s web stack.

All publishing to DeWeb is fully compatible with existing frontend workflows and does not require user-side changes.

  1. Timeline
  • Phase 1 Snapshot + deploy of superfluid.org static site Week 1
  • Phase 2 Deploy SIPS archive with metadata + versioning Week 2
  • Phase 3 Optional: enable DAO tooling, dashboards, etc. Week 3+
  • Support from Massa Labs (or community contributors) is available to assist in deployment and onboarding.
  1. Overall Cost - The total cost to implement the SIP.

Overall costs depends on size of the website. We estimate the range betwenn 2000 - 4000 $MAS equals 44-88 USDT.

Copyright and license remain as defined in Superfluid documentation. No intellectual property transfer required.

1 Like