insrt
  • πŸ₯³Welcome to Insrt
  • Key Sections
    • 🌐Overview
    • πŸ€”FAQ / ELI:5
    • πŸͺ™$MINT token
    • πŸ‘©β€πŸ”¬Minting Resolution (Technical)
    • πŸšΆβ€β™‚οΈMinter Reward Model (the Math)
    • πŸ”—Contracts Architecture
    • πŸ‘©β€πŸ’»Contracts
    • πŸ›£οΈProduct Roadmap
    • πŸͺ™Token Mechanics
  • Blast Rewards
    • πŸͺ™Blast Points
    • πŸ₯‡Blast Gold
    • πŸ†Blast Bounty
  • Help Guide
    • πŸ’¬How To Mint?
    • πŸ“©How To Claim $MINT?
    • Ⓜ️How To Use $MINT?
    • 🎁How To Claim A Reward?
  • SHARDVAULTS
    • 🌐Overview
    • πŸ”§Mechanics
    • πŸ”—Contracts Architecture
    • πŸ¦„Vendor Abstraction
    • βš–οΈRisk Management
  • MISC
    • πŸ–ΌοΈinsrt NFTs
  • Socials
    • πŸ“¨Telegram
    • 🐦Twitter
    • πŸ“£Discord
Powered by GitBook
On this page
  1. Key Sections

Contracts Architecture

A representation of our contracts architecture

PreviousMinter Reward Model (the Math)NextContracts

Last updated 1 year ago

The PerpetualMint contract suite relies on the contracts to generate provably-fair random numbers. The entirety of the PerpetualMint product is split into the contracts which handle (PerpetualMintDiamond), and the contracts which handle the token (TokenDiamond). They are both upgradeable contracts via (DiamondProxy).

πŸ”—
Chanlink VRF
minting
$MINT
EIP-2535
High-level overview of the PerpetualMint contract suite