• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
Bastard GAN Punks V2 (DAO)Bastard GAN Punks V2 (DAO)by0xD3ff454f44Fd17224902BbA8BdBf410Dd29178d7segwitnitwit

BGAN V2 Metadata Migration Proposal (IPFS)

3 days left to voteActive vote

TL;DR:

  • Move BGAN V2 metadata from Berk's private server to IPFS (decentralized storage)

  • Eliminate single point of failure and improve long-term reliability

  • I will handle migration + ongoing maintenance

  • Cost: 1 ETH upfront + 0.05 ETH/month


Problem:

  • Currently, BGAN V2 metadata is hosted on a private server managed by Berk

  • Example:
    https://api.bastardganpunks.club/1234

  • This introduces a single point of failure:

    • If the server goes down, metadata becomes inaccessible

    • If maintenance stops, the collection’s integrity is at risk


Proposed Solution:

  • Migrate all metadata and assets to IPFS

  • Use redundant pinning:

    • Pinata (paid)

    • My IPFS node

  • Benefits:

    • Redundancy (no single failure point)

    • Decentralization (no reliance on one server)

    • Persistence (data remains accessible as long as pinned)

    • Flexibility (metadata still updatable via baseURI)

  • Trust minimization:

    • Data is publicly accessible and independently pinnable

    • System can be taken over by any contributor if needed


Implementation Plan:

  • Download + verify all metadata and assets

  • Pin all data on Pinata + my IPFS node

  • Update contract baseURI:
    https://snapshot.4everland.link/ipfs//

  • TokenURI format:
    https://snapshot.4everland.link/ipfs//

  • Refresh metadata on OpenSea (Blur auto-updates)

  • Validate full collection

  • Publish GitHub documentation


Ongoing Responsibilities:

  • Manage metadata updates:

    • Update files → re-pin → new CID → update baseURI → refresh marketplaces
  • Maintain infrastructure:

    • Keep IPFS node online and serving data

    • Maintain Pinata redundancy

  • Ensure reliability:

    • Validate metadata integrity

    • Fix issues across IPFS / OpenSea / Blur

  • Maintain documentation + handoff readiness


Cost:

  • Initial migration, infrastructure setup, and verification: 1 ETH

  • Ongoing maintenance and support: 0.05 ETH / month


Payment Structure:

  • 50% upfront, 50% upon completion

  • Completion defined as:

    • Metadata migrated to IPFS

    • baseURI updated

    • All tokens verified

    • Marketplaces refreshed

  • Monthly maintenance begins after completion


Summary:

  • Removes centralized dependency

  • Improves resilience and longevity of the collection

  • Establishes a maintainable, DAO-controlled metadata system


Off-Chain Vote

For
47 100%
Against
0 0%
Download mobile app to vote

Timeline

Mar 18, 2026Proposal created
Mar 18, 2026Proposal vote started
Mar 22, 2026Proposal updated