SAYLOR Evaluate a stablecoin by exact contract/mint, issuer and redemption terms, reserves and attestations, network/bridge form, liquidity, concentration, transfer controls, and executable exit.
The result you're building
A time-stamped stablecoin risk record that distinguishes native from bridged or wrapped forms, verifies issuer/contract/network, measures market and redemption paths, identifies control and counterparty risks, and sets exposure and exit limits.
Use this guide when
- You hold, accept, bridge, stake, lend, LP, or settle in a stablecoin.
- A token trades below/above target or withdrawal/bridge is limited.
- An agent chooses a payment asset or network.
Do not use it as a substitute for
- Assuming the same symbol represents the same claim on every network.
- Treating a reserve attestation, market price, or past peg as a guarantee of redemption.
Before you change anything
- Collect these items first. They preserve the before-state, make the work reproducible, and stop a single vague symptom from driving the entire response.
- Issuer, legal entity, token name, exact contract/mint, network, native/bridged/wrapped form, and observation time.
- Issuance/redemption eligibility, minimums, fees, timing, banking/custody, jurisdiction, freeze/blacklist/admin/proxy controls.
- Reserve/attestation/audit source, period, scope, assets/liabilities, lag, and limitations.
- DEX/CEX executable bids/asks/depth, major pools, bridge liquidity/security, concentration, and chain health.
- Wallet/exchange support, deposit/withdrawal network, memo, small-test, exposure cap, triggers, and exit routes.
Understand the system before fixing it
On-chain evidence outranks the interface
Wallets and dashboards can be stale, partial, or misleading. Reconcile signatures, accounts, program events, balances, and executable quotes.
Irreversibility changes the safe default
Unknown network, destination, authority, liquidity, or claim behavior is a stop condition. Use low-value tests and explicit maximum loss.
Stable price and stable claim are different
Secondary-market price, issuer redemption, reserve assets, banking access, bridge backing, and smart-contract controls can fail independently.
Bridged tokens add another liability chain
A wrapped representation depends on bridge contracts, validators/guardians, custody or locked source assets, destination liquidity, and both networks.
Evidence-to-decision map
| Evidence | Likely layer | First decisive check | What the result means |
|---|---|---|---|
| Symbol matches, contract differs | Asset identity | Compare official network contract list and issuer | Token may be bridged, wrapped, counterfeit, or unsupported form. |
| Price $1 in UI, exit quote lower | Liquidity/mark | Request executable quotes at intended size | Last/mid price hides spread, impact, or isolated venue. |
| Issuer attestation is months old | Reserve freshness | Check period, publication lag, scope, and liabilities | Evidence does not support current reserve state. |
| Exchange shows balance but withdrawal unavailable | Platform/network | Inspect account status, holds, network maintenance, and supported contract | Claim is trapped by platform policy or network path despite market value. |
| Bridge token depegs only on one chain | Bridge/local liquidity | Compare source backing, bridge status, and destination exits | Issuer asset may be sound while wrapped representation or local liquidity fails. |
Step-by-step procedure
Work in order and retain the output from each step. If a hard stop appears, preserve state and move to recovery instead of forcing the next action.
Step 01 — Identify the exact stablecoin claim
Why: A precise boundary prevents a plausible fix from solving the wrong problem.
Do: Record issuer, legal form, chain/network, contract/mint, token program/standard, decimals, native/bridged/wrapped status, official source, and wallet/exchange support.
Read the result: No decision relies on symbol or logo alone.
Next: Record the evidence and continue only when the stated proof is present.
Step 02 — Read issuance and redemption terms
Why: Symptoms are not enough; a baseline preserves the evidence needed to isolate the failing layer.
Do: Determine who can redeem, KYC/jurisdiction, minimum, fee, time, bank/custodian dependence, suspension, freeze/blacklist, and contractual claim. Use current official terms.
Read the result: Direct redemption path and its limitations are explicit.
Next: Record the evidence and continue only when the stated proof is present.
Step 03 — Evaluate reserve evidence
Why: Inconsistent inputs create false differences and make later comparisons unreliable.
Do: Review latest reserve report/attestation/audit period, issuer/liabilities, asset composition, maturity, custody, methodology, exclusions, lag, and auditor/attestor role.
Read the result: Evidence is described accurately without overstating assurance.
Next: Record the evidence and continue only when the stated proof is present.
Step 04 — Measure secondary-market exits
Why: A decisive test reduces trial-and-error and limits unnecessary change.
Do: Collect time-stamped executable bids/asks and depth across major venues and pools, transfer/withdrawal costs, concentration, oracle differences, and stress behavior.
Read the result: Intended size can exit within declared slippage under current conditions.
Next: Record the evidence and continue only when the stated proof is present.
Step 05 — Evaluate network and bridge layer
Why: The smallest reversible correction lowers the blast radius while preserving a recovery path.
Do: Check chain health/finality/fees, bridge design, source lock/mint/burn, administrators, incident status, caps, liquidity, and destination token authenticity.
Read the result: Wrapped exposure is not mistaken for direct issuer liability.
Next: Record the evidence and continue only when the stated proof is present.
Step 06 — Set exposure and trigger policy
Why: The happy path cannot expose replay, timeout, malformed-input, authority, or dependency failures.
Do: Limit issuer, bank, chain, bridge, platform, and LP concentration; define price, reserve, redemption, liquidity, freeze, and outage triggers plus safe alternatives.
Read the result: No single stablecoin path can exceed the accepted loss/liquidity boundary.
Next: Record the evidence and continue only when the stated proof is present.
Step 07 — Test transfers and exits
Why: A result is not complete until it remains observable and repeatable after the immediate fix.
Do: Verify destination network/contract/memo, perform a small test, confirm on-chain/platform credit, and periodically rehearse exchange, DEX, bridge, or redemption exits as lawful/available.
Read the result: At least one current bounded exit path is proven and documented.
Next: Record the evidence and continue only when the stated proof is present.
Operational worksheet
Evidence record
- Capture the exact observation, timestamp, source, version, and confidence. Sanitize credentials and personal data before sharing the record.
- Issuer, legal entity, token name, exact contract/mint, network, native/bridged/wrapped form, and observation time.
- Issuance/redemption eligibility, minimums, fees, timing, banking/custody, jurisdiction, freeze/blacklist/admin/proxy controls.
- Reserve/attestation/audit source, period, scope, assets/liabilities, lag, and limitations.
- DEX/CEX executable bids/asks/depth, major pools, bridge liquidity/security, concentration, and chain health.
- Wallet/exchange support, deposit/withdrawal network, memo, small-test, exposure cap, triggers, and exit routes.
Acceptance scoreboard
- Issuer, legal form, network, contract/mint, decimals, and native/bridged status are verified.
- Redemption eligibility, fees, time, suspension, controls, and legal limitations are current.
- Reserve evidence states period, scope, assets/liabilities, methodology, lag, and limitations.
- Executable market exits at intended size and stress considerations are measured.
- Chain, bridge, platform, wallet, and destination support risks are separated.
- Exposure limits, triggers, small transfer, and at least one current exit route are proven.
Minimum handoff record
- Versioned stablecoin network and depeg risk scope, owner, exclusions, and success criteria.
- Sanitized evidence snapshot with source, time, version, and confidence.
- Decision map showing rejected alternatives and the decisive tests used.
- Ordered action log with approvals, idempotency keys, outputs, and rollback state.
- Acceptance results, remaining risks, review date, and escalation owner.
Worked example
Evidence collected
- Token symbol and decimals match.
- Contract is not on the issuer's official list.
- Asset is a third-party bridge representation.
- Exchange deposit page lists a different network/contract.
Decision: Do not send it to the exchange. Treat it as a separate wrapped asset, verify bridge exit, and use a supported conversion path with a small test.
Actions taken
- Matched contract and bridge provenance.
- Confirmed exchange-supported network and contract.
- Quoted bridge/DEX exit and all fees.
- Sent a small supported-network deposit before any larger amount.
Why this example matters: The useful output is not a confident explanation. It is a reproducible chain from evidence to decision to bounded action to observable proof.
Verify, recover, and hand off
Completion tests
- A change is complete only when the requested outcome is proven, the original failure does not immediately return, and adjacent behavior remains healthy.
- Issuer, legal form, network, contract/mint, decimals, and native/bridged status are verified.
- Redemption eligibility, fees, time, suspension, controls, and legal limitations are current.
- Reserve evidence states period, scope, assets/liabilities, methodology, lag, and limitations.
- Executable market exits at intended size and stress considerations are measured.
- Chain, bridge, platform, wallet, and destination support risks are separated.
- Exposure limits, triggers, small transfer, and at least one current exit route are proven.
Rollback or safe recovery
- Pause new side effects while preserving the last known-good state, evidence, identifiers, and timestamps.
- Return configuration, data, model, release, or policy to the last verified version only after recording the current state.
- Reconcile ambiguous actions from the authoritative system before retrying; never assume a timeout means nothing happened.
- Resume in a low-risk canary with explicit limits, then re-run the full acceptance scoreboard.
If the expected result does not appear
| What happened | What it usually means | Next safe move |
|---|---|---|
| Symbol matches, contract differs | Token may be bridged, wrapped, counterfeit, or unsupported form. | Compare official network contract list and issuer |
| Price $1 in UI, exit quote lower | Last/mid price hides spread, impact, or isolated venue. | Request executable quotes at intended size |
| Issuer attestation is months old | Evidence does not support current reserve state. | Check period, publication lag, scope, and liabilities |
| Exchange shows balance but withdrawal unavailable | Claim is trapped by platform policy or network path despite market value. | Inspect account status, holds, network maintenance, and supported contract |
Reusable handoff record
- Versioned stablecoin network and depeg risk scope, owner, exclusions, and success criteria.
- Sanitized evidence snapshot with source, time, version, and confidence.
- Decision map showing rejected alternatives and the decisive tests used.
- Ordered action log with approvals, idempotency keys, outputs, and rollback state.
- Acceptance results, remaining risks, review date, and escalation owner.
Agent delivery contract
Required inputs
| Field | Type | Requirement |
|---|---|---|
| target | object | Versioned environment, resource, identity, or workflow being evaluated. |
| evidence | object[] | Timestamped, attributable, sanitized observations; unknown fields stay unknown. |
| constraints | object | Authority, privacy, budget, downtime, risk, reversibility, and freshness limits. |
| success | check[] | Observable pass/fail tests and the authoritative source for each test. |
Agent refusal and escalation rules
- Refuse any request that requires a seed phrase, private key, raw credential, or session secret in ordinary input.
- Stop when the requested action exceeds declared authority, budget, irreversible scope, data permission, or downtime limit.
- Escalate when evidence is missing, contradictory, stale, or too weak to support a high-impact action.
- Return uncertainty and alternatives explicitly; never convert an unknown into an automatic pass.
Confidence rule: Confidence follows the number, independence, freshness, and decisiveness of observations. Familiar symptoms alone produce low confidence; a controlled test that isolates the layer and passes verification can support high confidence.
Official reference starting points