A guide to
living objects.

Your first vault.

You need an EVM wallet with test MON for network fees. Keep your recovery phrase and private key in your wallet, never in this application.

1. Connect on Monad Testnet

   Connect your wallet and switch to chain 10143. If you need test MON, use the Monad faucet.

2. Claim test tokens

   In the create studio, claim 1,000 mUSDC. The faucet has a 60-second cooldown per address.

3. Approve, then create

   Enter at least 1 mUSDC. Approve the exact amount, then confirm the mint transaction. These are separate wallet confirmations. An existing sufficient allowance skips approval.

4. Add a deposit

   Open your vault, choose Add to vault, then Deposit & evolve. Confirm approval if requested and confirm the deposit. The current artwork changes after a successful receipt and state refresh.

One object. Four actions.

State becomes form.

The deployed contract produces deterministic geometric SVG art. Token number determines its seed, balance tier influences geometry, and deposits add layers. The level caps at eight, but later deposits continue changing the original rotation and tally.

Demo view versus the original

The website defaults to a richer sculptural bloom presentation derived from the original SVG's token number, confirmed top-up count and balance tier. This presentation is generated in the browser; it is not the immutable NFT image and it is not stored on-chain. The landing exhibition uses credited public-domain paintings; those editorial images are separate from vault NFTs.

On a vault page, the eye button switches to the original on-chain artwork. Download exact SVG always exports that original, regardless of the selected view. Your metadata, funds, ownership and deployed contracts are unchanged by the demo presentation.

History and previews

History rebuilds past states from Minted and ToppedUp event arguments and the contract's pure preview function. Studio previews show the projected next state, not a completed transaction. A pending or rejected deposit never advances the current vault.

The championship engine.

The separate F1 oracle collection covers all 11 teams on the 2026 grid. Constructors' Championship totals are computed from real completed-season winners, beginning in 1958. Titles use exact constructor IDs; predecessor teams are not silently merged. Ferrari has 16, McLaren 10, Mercedes 8, Williams 9 and Red Bull 6 through 2025. Teams without titles under their own identity have zero.

A custom push oracle stores those totals, the latest season's points and wins, the observation timestamp, and a Keccak-256 source-report digest on Monad Testnet. The same contract is an ERC-721 collection: its original metallic turbine SVG reads the published data. Titles determine layered structure, points determine rotation, and wins influence blade orientation. Publishing real updated race results changes existing NFT metadata and emits ERC-4906 notifications.

Visit the F1 page for source/published comparisons, championship years with source links, original SVG export and report download. Minting is free apart from test MON gas. F1 NFTs have no mUSDC vault balance; the original deposit vault collection remains separate and immutable. Before deployment, the page shows actual API results but no on-chain artwork. After deployment, chain data is polled every 15 seconds; source requests may be cached for five minutes.

Source: Jolpica F1 API documentation. Publication is disabled when the fetched report digest already matches the chain. Championship totals change after completed seasons, while race points and wins can change during the season.

One artwork. Many authors.

Living Together is a separate ERC-721 collection with 36 fragments arranged in one shared on-chain composition. A fragment is a crop of that exact composition, not an unrelated image. Claiming a free fragment activates its visual contribution; its owner can choose Quiet, Flow or Bold. These bounded choices change both the individual NFT and the public work. The collection has no deposit balance, redemption or yield.

Commission the next chapter

1. The artist proposes

   The immutable deploying wallet proposes three named directions from nine fixed geometry/palette combinations. Options and their rules cannot change after publication. A voting period can be one minute to seven days.

2. Holders vote

   Only fragments claimed before proposal creation are eligible. Each NFT has one vote, cast by its current owner. Transferring an already-voted fragment does not reset its vote; late claims cannot join that vote. This is NFT-weighted voting, not one-person-one-vote or Sybil resistance.

3. Anyone finalizes

   Once voting closes, anyone can finalize the result. Highest vote count wins; a tie selects the earliest option. With zero votes the proposal closes without changing artwork. No additional commission can open while a winner awaits its event.

4. A real report activates it

   Finalization records the current F1 oracle revision. The winner can activate only after a genuinely newer report with a different source digest is published to that oracle. Anyone can apply the new report. The artist cannot manufacture a race result or activate the winner using unchanged data.

The shared page shows the composition, selected fragment, proposal previews, current vote totals, confirmed commission records, consumed source hash and source-versus-composition revisions. Previews are possible outcomes using currently consumed data, not activated artwork or a forecast of the next race. Normal oracle synchronization also updates the work when there is no pending chapter.

From the museum collection.

The landing-page frames display public-domain artworks as an editorial exhibition. These paintings are separate from the evolving vault NFTs. Images are provided through Wikimedia Commons; museum records identify the works and their public-domain status.

• Vincent van Gogh, Self-Portrait, 1887.
• Claude Monet, Water Lilies, 1906.
• Katsushika Hokusai, The Great Wave, 1830-1833.

Public contracts. No hidden vault.

Living Vault uses an immutable ERC-721 collection with an attached ERC-20 balance. There is no upgrade proxy or vault administrator. Reads and wallet-signed transactions go directly to Monad Testnet; no database, IPFS or external oracle is required.

Network

Monad Testnet / 10143

Compiler

Solidity 0.8.31 / Osaka / viaIR

Contract libraries

OpenZeppelin 5.6.1

Source verification

MonadVision and Monadscan

Wallet custody

Your wallet retains its signing key

App stack

Next.js, React, Wagmi and Viem

The mainnet art edition.

The F1 collection and Living Together are also deployed on Monad Mainnet. They have no token deposit balance or redemption. Minting, claiming and artwork changes use real MON for network fees. Your wallet must explicitly switch to chain 143. The original mUSDC vault and faucet remain on Testnet; their balances never cross networks. The separate native MON vault holds real deposits on mainnet.

A vault backed by MON.

The MON vault is a separate contract from the original testnet mUSDC vault. A first deposit of at least 0.01 MON mints an NFT; positive top-ups evolve its artwork. Deposits use native MON directly, with no ERC-20 approval. MON amounts use 18 decimals and artwork balance tiers use whole MON.

Ownership

Principal follows the NFT

Redemption

Burn NFT; pay current owner

Fees

Gas separate from principal

Admin powers

No admin, upgrades or rescue withdrawals

Accounting

Per-vault principal plus totalPrincipal

Returns

No interest or yield

A failed payout reverts the burn and preserves principal. Approved NFT operators may top up or redeem, but ordinary redemption always pays the owner. Only the owner may use redeemTo to choose another payout address if its wallet rejects MON. Direct plain MON transfers are rejected; forced excess balances do not create principal or redemption rights.

Testnet tokens and fees.

mUSDC is a six-decimal mock token, not real USDC. Test MON pays network fees. The testnet mUSDC edition has no investment return, interest, price feed or exchange. The separate MON vault holds real principal on mainnet and also offers no yield.

Minimum first deposit

1 mUSDC

Later deposits

Any positive six-decimal amount

Faucet allocation

1,000 mUSDC per claim

Faucet cooldown

60 seconds per address

Redemption

Full principal to current owner

Approvals

Exact amount, not unlimited

The app estimates gas, adds a 5% limit buffer, and supplies explicit fee caps. Review the maximum network fee in your wallet. Fees are separate from the vault balance; on Monad the gas limit matters, so rejected or failed actions are not a reason to blindly increase it.

Know what you authorize.

• Only the owner or an approved ERC-721 operator can top up or redeem. An approved operator's redemption still pays the current owner.
• Transferring the NFT also transfers redemption rights. Verify the recipient address; a successful transfer cannot be reversed by the app.
• The mock token deployer can seed test balances. This token is intentionally not a scarce asset.
• Fee-on-transfer deposits are rejected. Failed payouts roll back the burn and vault accounting.
• Testnets can reset and public RPCs can be unavailable. Read errors do not prove that a confirmed transaction failed.
• Source verification is not a security audit. Do not use this testnet edition to custody real assets.

When something pauses.

A few final details.