Subverse

Subverse is a decentralized infrastructure protocol designed to power the next generation of Web3 subscriptions. It solves key problems in traditional subscription models — such as lack of transparency, non-transferability, and platform lock-in — by leveraging smart contracts, on-chain identity, and NFT-based access control.

With Subverse, users truly own their subscriptions, can transfer or resell access, and projects can build interoperable, censorship-resistant subscription experiences. Whether it's for tools, communities, creators, or DAOs, Subverse is building the foundation for a more open, secure, and composable subscription economy — right at the edge of the $1.5 trillion market boom.

Through integration with Model Context Protocol (MCP), Subverse enables seamless cross-platform subscription management, including NFT-based subscription transfers, delegation, and contextual actions — all executed with a single, standardized command interface. This empowers both users and developers to create flexible, interoperable experiences across the Web3 ecosystem.

Subverse was built as a modular Web3 subscription infrastructure using modern frontend and blockchain tooling. The core architecture includes a React-based frontend powered by Vite, integrated with "Wagmi v1" and "Viem" for seamless smart contract interactions across chains.

We use "NFTs as access tokens" for subscriptions, which enables secure, verifiable, and transferable ownership. These NFTs are minted and managed via custom smart contracts written in Solidity and deployed to EVM-compatible testnets.

To enhance interoperability and command-based interactions, we integrated "Model Context Protocol (MCP)". MCP enables users to perform contextual actions—such as transferring an active subscription NFT—through a standardized prompt interface. This provides a CLI-like experience on the frontend and supports easy integration with third-party wallets or assistants.

🔧 Technologies Used:

• Frontend: React + Vite + CSS
• Wallet & Contracts: Wagmi v2, Viem, Ethers, MetaMask, WalletConnect
• Smart Contracts: Solidity (ERC-721 + custom access logic), deployed via Foundry
• MCP Integration: Text-command interface + NFT transfer triggers
• Deployment: GitHub Pages (frontend), testnet (contracts)

🧪 Notable Hacky Bits:

• We implemented a manual MCP-compatible command parser to extract and execute subscription transfers from plain text input (e.g. transfer Netflix to 0xABC...), bypassing traditional UI flows.
• To simulate transferable subscriptions, we encoded metadata inside NFTs (e.g., service name, expiry) and enforced logic through view functions rather than backend logic.
• Since subscriptions are usually non-transferable off-chain, we had to emulate a "transfer flow" using re-minting logic + metadata continuity checks.