> For the complete documentation index, see [llms.txt](https://synthesys-2.gitbook.io/synthesys-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://synthesys-2.gitbook.io/synthesys-docs/mint-overview.md). # Mint Overview Synthesys Mint is an institutional-grade tokenization platform that enables fund managers and transfer agents to issue, manage, and distribute natively on-chain fund tokens. Built in partnership with Chainlink, the industry's leading oracle and smart contract infrastructure provider, Mint bridges traditional fund operations with blockchain-native distribution without requiring participants to possess deep technical knowledge of blockchain systems. *** ### Platform Architecture Mint is built on a two-layer architecture: an application layer developed and maintained by Synthesys, and a core smart contract infrastructure layer provided by Chainlink. | Layer | Synthesys (Application) | Chainlink (Infrastructure) | | -------------- | ------------------------------------------------------- | ------------------------------------------------------ | | Primary Role | API, UI, and integration layer | Smart contracts and oracle services | | Key Components | Mint UI, Mint API, Network distribution | DTA smart contracts, Smart NAV Oracle, CCIP | | Responsibility | Fund setup, investor onboarding, workflow orchestration | On-chain logic, minting/burning, cross-chain transfers | | Audit Standard | Application-level logging and reconciliation | Audited smart contracts, immutable blockchain records | | Token Contract | Deployed by Synthesys per fund | Governed by Chainlink DTA logic | #### On-Chain Components Three smart contract components underpin every tokenized fund on the Mint platform: * **Fund Token Contract:** A unique ERC-compliant token contract deployed by Synthesys for each fund. This contract governs token issuance, transfers, and maintains the investor whitelist. Only wallets on the whitelist can hold or receive tokens. * **Chainlink DTA Smart Contract:** The Digital Transfer Agency (DTA) contract handles all transfer agency logic on-chain. It receives instructions from the Mint API to mint or burn tokens, and uses the Smart NAV Oracle to calculate correct token quantities. * **Chainlink Smart NAV Oracle:** A secure, tamper-proof oracle that delivers the fund's daily Net Asset Value (NAV) on-chain, enabling precise and automated token quantity calculations for subscriptions and redemptions. *** ### Subscription Flow All subscriptions on Mint follow a Maker/Checker approval model, with every on-chain action executed through a Safe Multisig wallet. No single operator can unilaterally mint tokens — every critical step requires independent review and multi-party sign-off before execution.

1. **Maker Creates Subscription Draft** — The Maker (Transfer Agent operations user) logs into the Mint UI and creates a subscription request, entering the fund details, subscription amount, distributor wallet address, and target chain. 2. **Checker Submits Subscription Request On-Chain via Safe** — The Checker reviews the subscription request, verifies it is valid, and approves — creating the first on-chain transaction. 3. **Maker Enters Fiat Payment Details** — Once the on-chain subscription request is confirmed, the Maker records the off-chain fiat payment information in the Mint UI — including bank reference, sender details, amount received, and receipt date. 4. **Checker Validates Payment and Submits Processing Request via Safe** — The Checker independently reviews the payment details entered by the Maker, verifies they are correct, and approves. 5. **Checker Completes Settlement and Tokens are Minted via Safe** — The Checker initiates the token minting process and the tokens are minted in the issuer wallet. 6. **Checker Transfers Minted Tokens to Distributor** — Once the tokens are minted, the Checker transfers the tokens to the distributor wallet, completing the subscription flow. *** ### Redemption Flow

The redemption flow operates under the same Maker/Checker approval model as subscriptions. Token burns only occur after on-chain transfer is verified, and fiat payment is confirmed before the redemption is marked complete. 1. **Investor Submits Redemption Request** — The investor submits a redemption request to the fund admin, specifying the number of shares and the fund. The Maker creates the order with a status of Pending Approval. 2. **Checker Reviews and Approves the Order** — The Checker reviews the redemption order in the Mint UI and approves it. The platform registers the redemption request on-chain. The investor is notified to proceed with transferring their tokens. 3. **Investor Transfers Tokens to the Fund Wallet** — The investor receives a link via email to transfer their fund tokens to the designated fund wallet on-chain. The investor submits the transfer hash to the platform, which verifies the on-chain transfer. 4. **Checker Burns the Tokens On-Chain** — The Checker initiates the token burn via the Mint UI. The Chainlink DTA burns the redeemed tokens on-chain. 5. **Fiat Settlement — Checker Sends Payment to Investor** — The fund admin initiates a bank transfer of the redemption proceeds to the investor. The Maker submits the payment details to the platform. 6. **Payment Verification and Redemption Completion** — The Checker independently verifies the payment details and confirms. The platform marks the redemption as complete on-chain, and the investor receives a final Redemption Completed notification. *** ### NAV & Pricing Token pricing is derived exclusively from the fund's official NAV, published daily by the Fund Administrator to the Chainlink Smart NAV Oracle. This ensures: * Token quantities are calculated using the same NAV as the fund's traditional unit-based subscriptions. * NAV data is secured by Chainlink's decentralised oracle network, preventing manipulation. * All pricing calculations are performed on-chain and are fully auditable. *** ### Fees The Mint platform does not charge investors or distributors any platform-level transaction or subscription fees. The only fees applicable to tokenised funds on Mint are **management fees**, which are set entirely at the discretion of the individual fund manager. Management fee rates, calculation methodology, and payment terms are disclosed in each fund's offering documents. *** ### Chain Accessibility & Cross-Chain Capability Mint is designed to be chain-agnostic at the infrastructure level. Fund tokens are deployed on a primary blockchain selected during fund setup, with optional cross-chain mobility enabled through Chainlink's Cross-Chain Interoperability Protocol (CCIP). Mint will launch on **Ethereum Mainnet** — the most widely adopted and institutionally recognised public blockchain, and the primary network supported by Chainlink's DTA infrastructure. | CCIP Feature | Description | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------ | | Secure Messaging | Cross-chain instructions are verified by Chainlink's decentralised oracle network, not a centralised bridge. | | Compliance Preservation | KYC/whitelist status checks are enforced on the destination chain — non-compliant wallets cannot receive tokens across chains. | | Token Standards | Supports lock-and-mint and burn-and-mint cross-chain transfer models. | | Audit Trail | All cross-chain transfers are traceable with on-chain transaction hashes on both source and destination chains. | *** ### DeFi Distribution via Zodiac For fund managers seeking broader DeFi distribution, Synthesys offers the Zodiac wrapper — an optional layer that enables permissioned fund tokens to be wrapped into DeFi-compatible tokens. See the Zodiac documentation for details. *** ### Security & Infrastructure #### Smart Contract Security * Chainlink DTA smart contracts are fully audited by leading blockchain security firms. * Role-based access control: the minter/burner roles on the Fund Token Contract are granted exclusively to the Chainlink DTA — no other party can mint or burn tokens. * All contract addresses, roles, and configurations are set at fund initialisation and are immutably recorded on-chain. #### Oracle Security (Smart NAV) * NAV data is delivered via Chainlink's decentralised oracle network — multiple independent nodes must agree before data is recorded on-chain, preventing single points of failure or manipulation. * Oracle addresses are configured per fund during initialisation and cannot be changed without an authorised transaction. #### Application Security * Mint API and UI are hosted on enterprise-grade, security-hardened infrastructure. * Role-based user access controls govern which fund administrators and TAs can perform which actions. * All API calls to smart contracts are logged with full audit trail. #### Key Management * Private keys for fund contract administration are managed using institutional-grade key management practices. * Multi-signature requirements are configurable for high-value operations such as contract upgrades or role changes. *** ### Audit Trail & Reconciliation Every action performed within the Mint platform is logged with: * User identity (the TA or fund administrator who performed the action) * Action type and timestamp * On-chain transaction hash, directly linking the off-chain record to the immutable blockchain entry This creates a complete, tamper-proof chain of evidence from order intake through to final on-chain settlement. Mint's API can provide structured transaction data exports to facilitate automated reconciliation within existing fund administrator systems. *** ### Contact For fund onboarding, integration scoping, or general questions about Mint, contact: * **Developer support:** * **General inquiries:** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://synthesys-2.gitbook.io/synthesys-docs/mint-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.