DAO owned and managed website

Panther Ecosystem
1

Hello Panther Community! Below is a draft and call for feedback / discussion regarding a much needed dedicated website for the Panther Protocol project and ecosystem.

Proposal Overview

This proposal seeks approval for the Panther DAO to create and set up a dedicated website for Panther Protocol, and to use it as the main gateway to the Panther dApp.The DAO would have full ownership, control, and ongoing management of this domain.

Currently, PantherProtocol.io is not owned or managed by the Foundation or the DAO, which:

  • Limits the project’s ability to keep content accurate and up to date (the PantherProtocol.io website has not been updated in over 2 years)

  • Creates brand, security, and continuity risks

  • Undermines our ability to communicate effectively with users, partners, and regulators

  • The dApp front-end is only accessible via IPFS, through direct links rather than a DAO-controlled domain.

If passed, this proposal will:

  1. Register a new domain name, or transfer an existing domain name, along with the web hosting, under DAO-controlled infrastructure.

  2. Establish a DAO-governed Website Working Group responsible for content, design, and maintenance.

  3. Deliver a modernized website aligned with Panther’s current product offering, branding, and privacy-tech positioning.

  4. Provide a smooth, low-friction access point to the dApp via a DAO-operated website

Motivation

Current Situation

  • The main Panther website, PantherProtocol.io is not controlled by the DAO or Foundation, which means:

    • No formal governance over messaging or updates.
    • Limited ability to align the website with current product and governance realities.
    • No updates to the website in over 2 years, missing the opportunity to leverage the website to build and expand the Panther ecosystem.

  • The dApp front-end is currently only accessible via IPFS, typically:

    • Through direct IPFS links shared in docs, Discord, or social posts.
    • Without a simple, memorable, DAO-owned URL (e.g. app.<official-domain>.xyz as an example pattern).
    • New users must rely on IPFS links or third-party references to find the dApp.
    • Non-technical users may not understand IPFS URLs, gateways, or trust which links are legitimate.
    • This fragmentation increases phishing risk (fake domains appearing more “official” than the real IPFS link), and weakens user trust in finding and using the real Panther dApp.

Proposed Changes

1. Website Domain DAO Ownership

Negotiate to purchase a new domain name (or transfer an existing domain) to host and serve as a primary gateway for the Panther Protocol project and ecosystem, under a DAO-controlled structure:

  • Multisig-managed registrar account, or
  • The Panther Foundation registers and purchases the domain name on behalf of the DAO, or
  • Legal wrapper representing the DAO

2. dApp Hosting via DAO-Operated Website

  • Currently, the dApp is only reachable via IPFS URLs shared manually, resulting in poor user experience, and leaves the project vulnerable to fragmentation and security risks.
  • After proposal: dApp becomes accessible via a clean, DAO-managed URL, such as app.<official-domain>.xyz

Benefits:

  • Minimal friction: users don’t have to understand or handle IPFS directly.
  • Stronger guarantees: the community knows that dApp access via the DAO-owned domain is the canonical, legitimate entry point.
  • Flexibility: the DAO can update IPFS deployments, gateways, or routing while keeping a stable public URL.

3. Website Working Group

Form a Panther Website Working Group under the DAO with responsibilities to:

  • Own and maintain:
    • Website content, information architecture, and UX.
    • dApp access routes (links, subdomains, navigation).
  • Coordinate with:
    • Core developers for technical accuracy.
    • Governance contributors for proposal, voting, and DAO information.
    • Marketing/BD contributors for announcements and partner materials.

Mandate & Reporting:

  • Publish an initial Website & dApp Access Plan (scope, milestones, and design direction).
  • Provide periodic updates to the DAO (e.g. once per month or per milestone).
  • Return with a renewal / follow-up funding proposal for ongoing work after the initial term.
2 Likes
2

Hello Chris! Great proposal…Like you mentioned it’s really important for the DAO zone to have a good website and entry point (link) to the main Dapp via said website. The Dapp can be managed by the foundation…but the DAO zone definitely needs a site for the retail…I’m in full support of this proposal and request the Foundation to grant the funds for the purchase and maintenance of this website for the DAO Zone!

3 Likes
3

I like Chris Proposal I hope the DAO will be able to vote for this soon.

2 Likes
4

Hi Chris i think your point is a very good fit for the project, go on to an official Pip.

1 Like
5

Thank you for meeting with us - it was a pleasure discussing your designs.

Regarding your proposal:

  • Points 1 and 2 have been resolved and don’t require further action.
  • For Point 3, we’ll consult with the foundation on how best to bring your design to life. The goal is to establish a working group including your team, the council, and the foundation to coordinate branding and messaging efforts.

All of this will proceed without the need for a proposal to be voted on.

1 Like
8

It was a pleasure meeting and discussing these initiatives @Praetorian! I am excited to implement the ideas we discussed. I created a working Telegram group to coordinate our efforts further. Looking forward to working with you all to bring an updated web presence for ZKP!

2 Likes