de-landing

The system is designed to create land based projects under a ENS name.. with a defined number of slots. The slots limit the number of people involved in the project and map to subdomains of the project domain.. A slot is a stewardship position and can be transferred to another member.. basic data is recorded, optionally the steward might include their personal ENS name. each new member goes through a registration and attestation process (attestation will be proof of human based v2). The progenitor of the project defaults as admin on user attestations. once slots are full the entire details are encrypted and stored on walrus (sui)

Stack: Next.js 16 (App Router, Turbopack), React 19, TypeScript, Tailwind v4, viem for all chain interaction, Privy for wallets, ENS on Sepolia, and Walrus on Sui testnet for published evidence bundles.

Privy handles the wallet without a browser extension — but the app prefers an injected wallet when one is connected, because if the signer already owns the project name no approval step is needed at all. Both the wallet client and the public client are built over the same EIP-1193 provider, so there's no NEXT_PUBLIC RPC anywhere and no signing key in the repo.

Walrus stores registry snapshots as content-addressed blobs, uploaded server-side to dodge CORS. Each bundle embeds its own provenance block declaring which parts are live and which are simulated, so the artifact states its own limits instead of relying on a README.

The hacky part — we shipped onto ENSv2 with sparse / missing docs