At a 150 percent ratio, minting to a total supply of 1,000 units requires a valid claim for at least 1,500 units.
An issuer declares a stablecoin's reference currency and price as claims on the token's own identity, and the platform shows the peg next to every mint, transfer, and freeze the token logs. The classification itself does not guarantee redemption or independently verified reserves.
When collateral enforcement is enabled, every mint is checked against a valid, unexpired claim that covers the post-mint supply at the configured ratio, so a mint the attested collateral cannot cover fails before it completes. The ratio defaults to 100 percent, and a ratio of zero disables this check.
Reserve reports and attestations attach to the same asset record for independent review. Uploading them does not verify a reserve balance on chain.
Why a peg belongs on the token's own record
A stablecoin is an instrument of the cash asset class. An issuer selects that class at design time, and the platform deploys it through the same factory, identity contract, roles and rules as a bond or an equity share.
Off-platform, a stablecoin's peg and its reserve backing are usually published as separate documents the issuer controls. A whitepaper states the peg, and a periodic attestation states the reserve, with no structural link between what circulates on chain and what either document covers. On this platform, the declared reference currency and price are claims, signed attestations that an issuer adds to the token's identity contract, which the token names on chain. The token contract itself logs every transfer and freeze, and the platform shows both on one asset record. When collateral enforcement is turned on, the mint check reads a claim from that same identity, so a reviewer who already checked the peg claim finds the collateral claim beside it.
Running issuance, disclosure and enforcement in separate systems creates handoffs where a ledger state and an attested record can drift apart, as Asset Lifecycle describes. The platform shows a stablecoin's peg claim, its collateral check and its uploaded reserve documents beside its transfer and freeze history on one asset record. The claims and the history are on chain, and the platform stores the documents. An integrator or an auditor reads one asset view for what the token claims and what has happened to it, instead of reconciling a chain state against a separately maintained attestation file. The token's governance role can add and remove the token's claims.
That record answers what the contract enforces. It does not answer whether the reserve behind the peg exists at the stated size. That question is verified through the issuer's own operating process and the documents reviewed under Review reserve evidence separately.
Configure the token and its disclosures
An issuer creates a stablecoin in the cash asset class, either directly through the creation API or through an Instrument Template, the reusable issuance blueprint that pre-fills required fields and disclosures. Both paths accept the same declared reference currency and declared price, and a collateral ratio that defaults to 10,000 basis points, which is 100 percent, when the request leaves it out. Send 0 to issue without the collateral check. A request can also carry a peg mechanism, one of fiat-backed, crypto-backed, algorithmic, or commodity-backed, and a free-text reserve description. Either one attaches as a claim on the token's own identity the moment it is supplied, and leaving both out attaches nothing. The template also configures a Composable Token, the token assembled from configurable permissions and controls, and can require further features and metadata.
The seeded Fiat-Backed Stablecoin template collects issuer and reserve-attestation metadata alongside the declared peg. Inspect the selected template's own fields before issuance: the platform validates what is submitted, and validation is not evidence that the disclosed reserves exist or hold the stated value.
The Console displays the peg currency when price-currency data is available. It displays the peg mechanism and reserve description when the token's identity claim supplies them. Missing details stay absent. They are not evidence that a reserve is empty or verified.
Start with issuing an asset to select a template and inspect its required fields. Use the API reference for the creation contract.
Collateral enforcement checks the attested amount
Collateral enforcement is a compliance rule on the token. It checks claims on the token's own On-Chain Identity, the registry of attestations attached to that token, and accepts a valid, unexpired claim from an issuer that the trusted issuers registry trusts for the collateral topic, or from an issuer that the rule's own configuration names. Governance sets that configuration, so check that the attesting issuer is independent of the token's issuer. The claim's amount must cover the supply after the proposed mint at the configured ratio.
The required amount is the post-mint supply multiplied by the ratio, rounded up to a whole base unit. For example, 1,000 base units at 150 percent require a claim for at least 1,500 base units. Keep supply and claim amounts in the same units. The check does not convert a reserve's market value into token units.
A signed claim can be valid while its underlying reserve report is wrong. The check inspects the attestation and the amount it states. Independent reserve verification is the issuer's responsibility and happens outside the check.
The collateral check runs at mint. It does not recheck collateral on transfer or burn, and a later claim expiry does not remove existing supply. Other token controls can still restrict those operations.
When collateral enforcement is absent or the ratio is zero, this check does not limit minting. A token's other configured permissions and compliance rules continue to apply. The token's governance role can turn off, remove or reconfigure the collateral rule, ratio included, so review who holds that role and the token's compliance history as well as the current ratio.
Price freshness follows the feed configuration
Every token's price feed has its own staleness window: the maximum age a price observation may reach before a mint or another price-dependent check treats it as unusable. The platform can express a price feed window that never expires, alongside an ordinary maximum-age window measured in seconds. A declared peg price suits the non-expiring kind, since a fixed peg does not go stale the way a moving market feed does.
The feed system supports a non-expiring window, and the business class does not set one, so check the asset's own feed configuration. A non-expiring window treats the declared peg price as fixed. It does not show that a market price still matches it. Market Data explains feed observations and their validation.
Review reserve evidence separately
The platform provides document categories for reserve audits, attestation reports, and reserve composition. It also supports legal opinions and regulatory filings. The category list describes the documents an issuer can attach. It is not a requirement that every stablecoin has supplied them.
Verify the reserve account, valuation method, report date, and redemption terms through the issuer's operating process. A document upload, declared peg, or successful mint does not establish that holders can redeem at the stated price.
Frequently asked questions
Why does a mint fail after a collateral claim expires?
With a nonzero collateral ratio, the mint check requires a valid claim that covers the resulting supply. Renew the attestation through a trusted issuer and confirm its amount before retrying. A larger mint can also fail when the claim remains valid but no longer covers the required amount.
Does a collateral ratio of 150 percent establish 150 percent reserve backing?
It requires an attested amount of at least 150 percent of post-mint supply. Establishing the underlying reserve balance requires separate evidence.
Does a stablecoin classification enable collateral checks?
Yes, by default. A stablecoin created without a ratio gets the 100 percent default, so its mints are checked. Send a ratio of 0 to turn the check off. Inspect the asset's compliance rules for the collateral rule and its ratio, because governance can change them after issuance.