timmy

The protocol,
without the fog.

This describes architecture in the repository, not a live product. Addresses, token identities, metadata, and integrations remain deliberately unconfigured.

A backed Timmy you can return.

There are 10,000 Timmy NFTs. Each requires 100,000 units of the separately configured backing token—the one-billion-token supply divided evenly across the collection. Acquiring Timmy moves that backing into the exchange contract. Returning him burns the NFT and releases the same 100,000 backing tokens with a permanent 0% swap fee.

“Backed” describes contract mechanics. It does not guarantee market value, liquidity, issuer redemption, security, or profit.

Explain first. Sign second.

STEP 1Review verified assets
STEP 2Preview cost and Timmy IDs
STEP 3Approve and exchange

The rebuilt interface will never infer a production address. A wallet action should remain disabled unless the network, backing asset, reward asset, and all protocol contracts are explicitly configured and presented to the user.

Two contracts, separate responsibilities.

TimmyNFT

Holds backing, mints and redeems Timmy NFTs at a permanent 0% swap fee, assigns the lowest available IDs, and notifies the reward vault around ownership changes.

TimmyRewardVault

Accounts for a generic reward asset with a fixed split, matures new positions, tracks claimable balances using a cumulative index, and keeps reward failures separate from NFT backing.

There is no governance contract and no holder voting system.

The asset is a placeholder until verified.

The intended category involves tokenized NVIDIA-linked market exposure. The exact legal name, issuer, contract address, transfer restrictions, and jurisdictional availability are unknown. Code therefore uses rewardAsset, and the UI displays “Legal name pending verification.”

Timmy is independent and is not affiliated with, sponsored by, or endorsed by NVIDIA or any token issuer.

The preserved release curve allocates more of the holder reserve as more Timmys become eligible: released = holder input × sqrt(eligible Timmys / maximum supply).

10,000 Timmys are ready.

The complete numbered image set is stored separately from the application and served from api.timmy.exchange/images/. The collection browser loads 50 images per page without copying the full artwork set into this repository.

The matching metadata is pinned to IPFS and maps every token ID to the same-numbered image. The separate API metadata route remains disabled until we decide whether it should mirror the immutable IPFS records.

Safe because it is not live.

  • No deployment records or verified production inputs remain.
  • No contract address, social link, sale link, metadata CID, or production RPC endpoint is configured.
  • The staging console is disabled.
  • The local frontend makes no blockchain request.