Futardio Launch IP Details - 2026-05-28

This packet is the public IP/control summary for the PrivateDAO Futardio and MetaDAO launch workflow. It is written for reviewers, token participants, and the future DAO Cayman SPC entity. It does not publish private keys, seed phrases, API secrets, local wallet paths, or personal operator documents.

Launch Fields

• Token name: PrivateDAO
• Ticker: PDAO
• Raise goal: 50,000 USDC
• Monthly spending limit: 6,500 USDC
• Duration: 3d
• Team token allocation: 2,580,000
• Unlock period: 18 months
• Legal terms URL: https://privatedao.org/legal/
• Token image: https://privatedao.org/assets/launch/privatedao-futardio-token-image-400.png
• Banner image: https://privatedao.org/assets/launch/privatedao-futardio-banner-16x9.png

The raise goal is a fixed target. If the platform mechanics require the target to be reached before funding is released, partial completion should be treated as market feedback rather than withdrawable treasury funding.

GitHub Repositories And Organizations

Current project code is maintained under:

• GitHub organization/account: X-PACT
• Main repository: https://github.com/X-PACT/PrivateDAO

The repository contains the Solana programs, web application, scripts, documentation, proof packets, reviewer materials, launch pages, and public assets. The DAO Cayman SPC entity should receive ownership or admin-level access over the repository and any future GitHub organization used for official PrivateDAO development. If direct ownership transfer is not immediately available, the entity should receive admin access, branch protection control, release control, and the right to appoint maintainers.

Domain Names

Primary public domain:

• privatedao.org

Current public surfaces:

• https://privatedao.org/
• https://www.privatedao.org/
• https://api.privatedao.org/

The DAO entity should own or control the registrar account, DNS records, SSL configuration, deployment settings, and all subdomains used for the public product, API, proof pages, launch pages, docs, and future application surfaces.

Brand Assets

The DAO entity should own or control:

• PrivateDAO name.
• PDAO ticker and project naming.
• Logos, SVG marks, token image, launch banner, cover images, profile images, and future brand guidelines.
• Website visual identity, route inventory, product copy, launch materials, demo assets, and proof documents.
• Social and community accounts created for PrivateDAO.
• Unregistered trademarks and brand goodwill associated with PrivateDAO and PDAO.

Current public launch assets are available under:

• https://privatedao.org/assets/launch/privatedao-futardio-token-image-400.png
• https://privatedao.org/assets/launch/privatedao-futardio-banner-16x9.png
• https://privatedao.org/assets/launch/privatedao-social-cover.png

Deployed Contracts And Programs

Current Solana Testnet program and proof surfaces:

• PrivateDAO Anchor program ID: EP9xE8MJZ6FfyEwLqns6HDdUZBknEa7WGYs1Jzsecuva
• Current PDAO Token-2022 governance mint evidence: documented in the public PDAO token surface and reviewer packets.
• Squads/multisig and timelock evidence: documented in the public proof and reviewer documents.
• ZK/Groth16 verifier, encrypted execution, private payment, payroll, and proof routes: documented as Testnet and mainnet-readiness surfaces.

The DAO entity should ultimately control or have enforceable governance rights over:

• Program upgrade authority.
• Treasury authority.
• Admin authority.
• Multisig or vault authority.
• Future mainnet program deployments.
• Token metadata/update authority for official PDAO launch assets where applicable.
• Future production contracts, programs, deployment authorities, and operational controls.

Mainnet control remains gated on external review, custody controls, monitoring, production release checks, and recorded governance decisions.

Cloud Infrastructure And API Keys

The DAO entity should own or control the administrative accounts required to operate PrivateDAO:

• Website deployment and GitHub Pages configuration.
• API/read-node infrastructure behind api.privatedao.org.
• DNS and SSL configuration.
• Database and receipt storage services.
• RPC/provider accounts.
• Monitoring, analytics, and operational dashboards.
• Storage for proof documents, launch media, reviewer packets, and public assets.
• Third-party service accounts used for runtime health, proof automation, wallet intelligence, encrypted execution, or community operations.

Private keys, seed phrases, API secrets, and local wallet material must never be placed in public repositories, launch forms, token metadata, or public documents. Any previously exposed wallet material must be treated as unsafe for treasury or authority use.

Patents And Licenses

No filed patents are claimed in this launch packet.

The codebase should remain governed by the open-source license currently present in the repository unless the DAO later approves a license change through a formal governance process. Even when code is open source, the DAO entity should control repository settings, branch protection, release tags, package publishing permissions, deployment credentials, official brand assets, and official distributions.

Entity And Launch Boundary

The MetaLeX/Cayman entity workflow is being used for the Futardio launch path. The public site should reference the legal terms URL and this IP packet, not private operator links, local PDFs, private emails, or personal wallet material.

The purpose of this packet is to make PDAO ownership meaningful: the future DAO entity should hold or control the project package it is funding, including source code, domains, brand, launch assets, deployed program authorities, cloud infrastructure, proof materials, and future production deployment rights.