Relic Forge uses an immediate-ownership Forge Reveal architecture. The collector receives the NFT in the mint transaction, verified randomness is requested automatically, and the callback budget scales with the size of each reveal group. Ethereum Mainnet is available for production launches, while Sepolia remains available for rehearsals and development.
Connect the EVM wallet that owns the creator controls. Cloud project saves are wallet-scoped. Downloaded project backups remain a separate recovery path.
Upload an organized folder, create empty layers, add traits later, upload several traits to an existing layer, or create a category from loose files. Categories remain editable before final compile.
Use percentages, exact quantities, manual token curation, or a collection manifest. Auto Fill preserves entered values and distributes only the remainder. Optional full 1/1 artwork occupies its own recipe slot and supports token-specific metadata.
Hide selected None traits, hide a rendered category from metadata, or hide individual traits only on tokens that use them. These settings affect token attributes, not the visual render.
Resolve rule, exact-count, and rarity-distribution conflicts. Preview the collection and compile the exact recipe set. Relic Forge validates recipes before ProjectData can be sealed.
Confirm name, symbol, description, maximum supply, payout receiver, royalty receiver, and royalty percentage. Creator proceeds stay separate from reveal funding.
Deferred Reveal = 0. NFTs mint immediately with the pre-reveal artwork. The creator later completes a two-transaction reveal: Step 1 freezes the minted set and prepares its randomness budget; Step 2 requests verified randomness. The callback finishes the reveal automatically—there is no third creator reveal transaction.
Forge Reveal = 1. NFTs mint directly to the collector. The same mint transaction automatically requests randomness for groups of at most 20. After verified randomness arrives, the recipes are assigned and the NFTs reveal automatically.
The Forge batch window is 30 seconds and the maximum randomness cost per request/group is 0.005 ETH. Both are platform-managed. Studio shows them in the Technical breakdown instead of exposing creator-editable fields.
Creator Covers Platform Fee prepays the quoted platform fee at launch and initializes reveal funding. Collector Covers Platform Fee adds the active fee during mints when the ETH/USD quote is healthy. Reveal funding uses the collection hopper first and the shared Reserve only for an allowed bounded shortfall.
MintPhases stores public and Approved Wallet stages, including price, schedules, stage supply, wallet caps, proofs, priority, enabled state, and the master Minting switch.
The Relic Forge Factory creates the collection and its linked data and mint-stage contracts, then Studio writes artwork and recipe data, validates recipes, seals content, creates stages, and verifies the final bindings.
Confirm the deployment system, payout and royalty receivers, fee model, reveal mode, mint-stage schedule, immediate ownership, and automatic reveal behavior. A complete Sepolia rehearsal is strongly recommended before a production launch.
Relic Forge sizes the consumer callback gas to the reveal group rather than paying for a single fixed callback envelope. Groups larger than 20 split automatically.
| Stage | What happens |
|---|---|
| Collector signs mint | The Collection validates MintPhases, price, limits, and remaining supply. |
| Immediate ownership | The NFT Transfer events are emitted in the mint transaction. The collector owns the NFTs before the randomness request is created. |
| Automatic request | The Collection groups the newly minted NFTs into reveal groups of at most 20, selects the adaptive callback-gas tier, checks the platform 0.005 ETH ceiling, and requests randomness automatically. |
| Verified word | The Chainlink adapter records the exact verified random word first and attempts delivery to the Collection. The word is retained even if downstream delivery needs a retry. |
| Automatic reveal | Successful delivery assigns unique recipes to the group and completes reveal. The collector does not sign a second transaction. |
| Exceptional replay | If automatic downstream delivery fails, the stored exact word can be replayed permissionlessly with replayFulfillment(localRequestId). Replay uses the same word—no reroll or replacement randomness. |
Deferred mints create owned ERC-721s immediately with the placeholder. When the creator is ready, prepareDelayedReveal() is Step 1: it freezes the minted supply and prepares the request budget. requestDelayedReveal() is Step 2: it requests verified randomness using the prepared budget. Delivery reveals the frozen set automatically.
If Deferred Reveal happens before sellout, future unsold supply switches to Forge Reveal. Recipes consumed by the delayed permutation cannot be reused by later Forge mints.
Creator Mint uses the same immediate-ownership semantics. In Collector Covers Platform Fee mode, MintPhases exposes creatorTeamFeeQuote(quantity); Studio quotes and attaches the required value automatically.
Creator sale proceeds accrue separately from reveal funding and can be withdrawn to payoutReceiver. The reveal hopper funds requests first. If necessary, the shared Reserve may fund an allowed exact shortfall. The Reserve's 0.20 ETH retention threshold is a withdrawal/revenue-safety rule, not a collection activation gate.
sealContent().