Welcome to USD1readiness.com

USD1readiness.com is an educational site about USD1 stablecoins used in a purely descriptive way: any digital token designed to be stably redeemable 1:1 for U.S. dollars. This page focuses on the practical meaning of readiness: the set of decisions, controls, and habits that let you use USD1 stablecoins safely and predictably in day-to-day life.

Readiness is a broad topic because USD1 stablecoins sit at the intersection of payments, software, and financial risk. A transfer can be fast, but you still have to manage custody (who controls the keys), compliance (rules and policies that apply), and operations (repeatable processes that do not rely on heroics).

This guide is educational and is not legal, tax, or investment advice. It aims to help you understand what questions to ask and what tradeoffs to notice.

What readiness means for USD1 stablecoins

In everyday language, readiness means you can do a thing reliably when it matters, not only when everything goes smoothly. Readiness for USD1 stablecoins means you can:

obtain USD1 stablecoins using a method you understand,
store USD1 stablecoins with controls that match the value at risk,
send and receive USD1 stablecoins with predictable timing and costs,
keep records you can explain later (to yourself, to counterparties, and in many cases to auditors or regulators), and
convert USD1 stablecoins back to U.S. dollars when you need to.

In practice, readiness is about aligning the technology with your obligations. If you are a business, your obligations include customer expectations, supplier terms, payroll timing, accounting rules, and risk limits. If you are an individual, your obligations include not losing access, not overpaying fees, and not getting tricked by scams.

Many global policy reports treat stablecoins as arrangements (a set of contracts, entities, technology, and governance) rather than a simple product. That framing matters for readiness because it pushes you to look beyond the token itself and focus on the full system you depend on.^[1]^[4]

Why readiness matters, even when the price is meant to be stable

A stablecoin (a digital token designed to keep a steady price, often by referencing a national currency) can be useful because it aims to combine internet-speed transfers with a familiar unit of account (a way to measure value, like dollars). But "stable" is an objective, not a guarantee. Readiness matters because several things can go wrong that have nothing to do with your intentions.

Depegging and confidence shocks

A depeg (when a token’s market price moves away from its target value) can happen for many reasons: fear about reserves, operational outages, legal actions, or market stress. Even if redemption is ultimately available, the experience of volatility can matter for anyone who needs immediate liquidity (the ability to turn an asset into spendable money quickly).

Policy bodies focus on confidence because payments depend on trust. If users lose confidence in redemption, a stablecoin can face rapid outflows and liquidity pressure.^[1]^[2]

Payment speed is not the same as business certainty

A blockchain (a shared ledger run by many computers that records transactions) can move value quickly, but your business may still need certainty about:

when a transfer is considered final (settlement finality, meaning it is extremely unlikely to be reversed),
whether transaction fees (network fees paid to process transfers) may spike during congestion, and
whether a platform or service you rely on can pause, restrict, or delay activity.

Readiness is about knowing where certainty comes from in your flow: the chain, the service provider, your own processes, or some combination.

Rules and expectations evolve

Stablecoin activity often touches regulated services: custody, money transmission, payments, and exchange activity. Even if you personally are not regulated, your bank, payment processor, exchange, or counterparties may have policies that affect you. Standards from bodies like the Financial Action Task Force (FATF, an intergovernmental organization that sets anti-money-laundering standards) shape how many service providers operate across borders.^[3]

Operational mistakes are common and often irreversible

In many stablecoin systems, a completed on-chain transfer (a transfer recorded on a blockchain) is hard or impossible to reverse. That makes operational quality a safety feature. Readiness is not only about preventing hacks; it is about preventing avoidable errors.

Readiness is a spectrum, not a switch

People often ask, "Are we ready?" The more useful question is, "Ready for what, at what scale, with what consequences if we are wrong?"

Readiness has levels:

Personal readiness: you can hold and move modest value safely and recover access if a device is lost.
Small business readiness: you can accept payments, handle refunds, keep basic records, and convert to bank money when needed.
Enterprise readiness: you have governance, segregation of duties (separating responsibilities so one person cannot move funds alone), audit trails (records that show who did what and when), vendor management (how you evaluate and monitor providers), and resilience planning (how you keep operating under stress).
Platform readiness: you build products that handle many users and need monitoring, incident response, and strong user safety.

A useful concept here is risk appetite (how much risk you are willing to accept to achieve a goal). If your risk appetite is low, you will prioritize strong custody controls, conservative exposure (the amount of value you can lose if things go wrong), and dependable conversion back to bank money. If your risk appetite is higher, you may tolerate more technology risk in exchange for speed or new capabilities.

Common use cases and what readiness looks like in each

Readiness becomes clearer when tied to a real use case. Here are a few common scenarios and the readiness questions they raise.

Use case 1: Sending value across borders

If you send USD1 stablecoins across borders, you are often trying to reduce time and friction. Readiness considerations include:

on-ramp and off-ramp access (on-ramp means converting bank money into tokens, off-ramp means converting tokens back into bank money),
fees across the full route (bank fees plus network fees plus service fees),
timing variability (bank cutoffs, weekends, holidays, and compliance reviews),
local restrictions or provider policies that can block conversion, and
the recipient’s ability to store funds safely.

Cross-border readiness is less about a single transaction and more about making sure the last mile, conversion into usable money, actually works.

Use case 2: Merchant acceptance for goods and services

If you accept USD1 stablecoins for sales, readiness depends on how you price, settle, and support customers.

Key readiness points include:

confirmation policy (how many confirmations you wait before delivering goods),
refund policy (how you process returns when transfers are not reversible),
customer support scripts (clear explanations for fees and timing),
accounting mapping (how each receipt is classified in your books), and
fraud controls (how you handle suspicious activity).

Even for a small merchant, readiness improves when these policies are written down.

Use case 3: Business-to-business settlement and treasury

If you use USD1 stablecoins for settlement between businesses, the main gains may be faster settlement and easier automation, but the readiness needs are higher.

Common readiness needs include:

clear contract terms for payment and acceptance,
approval workflows (who can initiate and who can approve),
whitelisting (allowing transfers only to approved addresses),
reconciliation processes that match invoices to transfers,
audit readiness for external reviews, and
contingency plans for provider issues or chain congestion.

Policy bodies often emphasize governance and risk management for stablecoin arrangements at scale because operational weaknesses can create broader spillovers.^[1]^[4]

Readiness pillars for USD1 stablecoins

A practical way to structure readiness is to break it into pillars. Each pillar answers a question, and gaps in any pillar can undermine the rest.

Pillar 1: Purpose and scope

What is the purpose of using USD1 stablecoins, and what is within scope?

A pilot that handles small amounts for internal testing can tolerate more friction and manual steps. A production payment system cannot. Readiness improves when scope is explicit: which customers, which regions, which transaction sizes, and which timelines.

Pillar 2: Understanding redemption and backing

Redemption (exchanging a token for the referenced asset) is the core promise behind many fiat-backed stablecoins (tokens referenced to government-issued money). Readiness includes understanding who offers redemption, how it works, and what limits exist.

Reserve assets (the pool of assets held to support redemptions) influence confidence, especially during stress. Transparency about reserves and governance is a recurring theme in policy work because it affects market discipline and consumer expectations.^[1]^[4]

Pillar 3: Custody and access control

Custody (who controls the keys that move funds) drives the practical security model. A private key (a secret value that proves control over a wallet) authorizes transfers on most blockchains. If someone else gets your private key, they can move USD1 stablecoins.

Readiness includes choosing a custody model that matches your scale and then implementing access control (rules that decide who can do what). A common principle is least privilege (giving each person only the access they need to do their job).

Pillar 4: Operational process and documentation

Operations include approvals, recordkeeping, reconciliation, and customer support. Operational documentation (written procedures that others can follow) reduces key-person risk (risk created when a single individual holds critical knowledge).

Pillar 5: Compliance and partner expectations

Compliance includes anti-money-laundering controls, sanctions screening, recordkeeping, and provider policies. FATF guidance is widely referenced because it describes a risk-based approach (controls that scale with risk) for virtual asset activity and service providers.^[3]

Pillar 6: Monitoring and resilience

Monitoring (watching systems and activity for problems) and resilience planning (preparing for stress scenarios) turn readiness into a maintained condition rather than a one-time setup. Security frameworks such as the NIST Cybersecurity Framework provide structured ideas for identifying, protecting, detecting, responding, and recovering.^[5]

Redemption and backing: the core promise behind stable value

If you rely on USD1 stablecoins as "digital dollars," the most critical question is how the token relates to actual U.S. dollars.

What redemption really means

Redemption is the process by which a holder exchanges USD1 stablecoins for U.S. dollars. Readiness means you know:

who is eligible to redeem (some systems restrict direct redemption to certain customers),
what verification steps apply (including identity checks),
what time frames and cutoffs apply,
what fees apply, and
what circumstances can delay redemption.

A common readiness gap is assuming redemption is always instant and always available. In practice, redemption is an operational service, and it can be affected by banking hours, compliance reviews, and capacity.

Reserve assets, liquidity, and stress

Reserve assets back the promise of redemption. Some reserves are highly liquid (easy to sell for cash quickly), while others may take time to liquidate without loss. The composition of reserves and the legal structure of claims are central topics in stablecoin policy discussions because they influence how stable a stablecoin remains under stress.

Proof of reserves and attestations

Proof of reserves (methods used to show that assets exist to support redemptions) can range from periodic statements to more technical approaches. An attestation (a report where an independent professional provides assurance on certain information) can improve transparency, but it is not the same as a full audit (a deeper review of financial statements and controls).

Readiness includes understanding what type of assurance you are relying on and how often it is produced.

Governance and legal clarity

Governance (how decisions are made and documented) affects readiness because it determines how changes happen: fee updates, redemption policy changes, chain support changes, or emergency actions. If you cannot get clear answers about governance, you should treat that as a readiness risk.

Market and liquidity readiness: stable value is not the whole story

Even if USD1 stablecoins aim to stay near one dollar, market mechanics still matter.

Liquidity and market depth

Liquidity (how easily an asset can be exchanged without causing large price moves) depends on market depth (how much buying and selling interest exists at nearby prices). When liquidity is thin, a large sale can cause slippage (the difference between the expected price and the price you actually get).

Readiness includes knowing where you will obtain and dispose of USD1 stablecoins at your expected size and how pricing behaves during stress.

Conversion risk and timing risk

Many users care less about trading and more about conversion: moving between USD1 stablecoins and bank money. Conversion can be affected by:

banking cutoffs and settlement times,
provider limits or holds,
compliance reviews,
chain congestion and fee spikes.

The result is timing risk (the risk that you cannot convert or transfer at the time you need).

Concentration risk in liquidity routes

If you have only one place you can convert, you have concentration risk (risk from reliance on a single point). Readiness improves when you understand alternative routes and maintain relationships early rather than trying to establish them during a crisis.

Custody and wallets: being ready to protect access

A wallet (software or hardware that stores keys and helps you send and receive tokens) is the most visible part of stablecoin use. Yet readiness is less about the app and more about the control model behind it.

Custodial wallets: convenience with tradeoffs

In a custodial wallet, you typically sign in with an email and password, and the provider handles key storage. The benefits are convenience, password recovery, and sometimes integrated conversion between bank money and tokens.

The tradeoffs are:

you rely on the provider’s security and solvency (ability to meet obligations),
the provider can restrict activity based on policy or legal duties, and
your access is mediated by an account relationship.

If you use custodial storage, readiness includes understanding the provider’s terms, knowing what triggers holds, and planning for what you will do if the provider has an outage.

Noncustodial wallets: control with responsibility

In a noncustodial wallet, you control the private keys, often backed by a seed phrase (a set of words that can recreate the wallet). This model reduces dependence on a single provider, but it creates a new responsibility: protecting the seed phrase.

Common readiness practices include:

storing the seed phrase offline (not in cloud notes or email),
protecting devices from malware (malicious software),
using a hardware wallet (a physical device designed to store keys securely) for higher amounts, and
using multisignature (requiring more than one key to approve a transfer) for organizational funds.

Multisignature can prevent a single mistake or compromise from becoming a total loss, but it adds operational complexity. You need to plan who holds keys, what happens when someone is unavailable, and how to recover if a key is lost.

Role-based access for teams

For organizations, role-based access control (permissions based on job role) helps keep custody manageable. You can separate viewing rights (who can see balances) from transfer rights (who can move funds), and you can set a rule for additional approvals for larger transfers.

Even if you use a custodial provider, you still need to configure internal access correctly.

Address hygiene and human error

Blockchain addresses are long strings of characters. Copying an address wrong can send USD1 stablecoins to the wrong place, and many transfers cannot be reversed. Readiness includes basic address hygiene (safe handling practices), such as:

verifying the first and last characters of an address,
using address books carefully (stored recipient lists),
confirming network selection (the specific blockchain network used), and
testing with a small transfer when operationally sensible.

These steps are not glamorous, but they prevent a large share of real-world losses.

Transaction workflows: from intent to usable funds

A transaction workflow is the full path from "I want to send" to "the other side has funds they can use." Readiness means understanding each stage and where uncertainty can enter.

Broadcast, confirmation, and finality

When you broadcast a transaction (send it to the network), it is not instantly final. It is included in a block (a batch of transactions) and then builds confirmations (additional blocks after it). Many businesses choose a confirmation policy to balance speed and safety.

Finality (the point where reversal becomes extremely unlikely) depends on the chain’s design. Readiness includes knowing the confirmation policy you rely on and communicating it clearly to customers and partners.

Fees, congestion, and user experience

Transaction fees (network fees) can rise when a chain is congested (busy). If your service needs predictable costs, readiness may include fee policies and user experience design (how it feels to use a product) that warns about high fees and delays.

Third-party holds and operational buffers

Many service providers run checks on transfers, especially when tokens move between accounts they control. You may see pauses for review, extra verification, or rejection. This is common where anti-money-laundering controls and sanctions restrictions apply.^[3]

Readiness means you plan operational buffers (time you build into schedules) so a compliance review does not break a critical payment.

Refunds are new transfers, not reversals

In many stablecoin systems, refunds are not automatic reversals. A refund is usually a new transfer initiated by the merchant. That changes your customer support model.

If you accept USD1 stablecoins, readiness includes a refund policy that addresses:

how you verify the original payment,
how you confirm the refund address, and
how you handle timing and pricing changes between purchase and refund.

Compliance and policy readiness: staying usable with banks and partners

Compliance is not only about avoiding enforcement. It is also about staying bankable and partnerable (able to keep relationships with banks and counterparties). Many organizations discover late that their stablecoin activity triggers internal policies at their bank or payment processor.

Know your customer and anti-money-laundering basics

Know your customer checks (identity verification steps used by financial services) and anti-money-laundering controls (processes to deter and detect illicit financial activity) are common in services that convert between bank money and tokens.

FATF guidance is widely referenced because it describes how many jurisdictions apply a risk-based approach to virtual assets and service providers. Readiness means you know which of your providers ask for what information and you collect it early enough that it does not block time-sensitive operations.

Sanctions screening and restricted activity

Sanctions (legal restrictions on dealing with certain people, entities, or regions) can apply to stablecoin transfers depending on the parties involved. Many providers screen transactions and addresses. If you operate internationally, readiness includes recognizing that a transfer can be restricted even if the sender and receiver have no malicious intent.

Travel rule considerations

The travel rule (rules to transmit certain sender and recipient information for some transfers) influences how regulated providers design transfer flows and what information they collect. Implementation details vary by jurisdiction, but readiness improves when you assume requests for information can be part of normal operations.

Policy alignment and governance expectations

Organizations like IOSCO and the Financial Stability Board have published recommendations and reports on stablecoin arrangements, focusing on governance, risk management, and transparency.^[1]^[4] Even if you are not a regulated entity, these documents influence market expectations and can become reference points in audits and vendor reviews.

Business operations: making USD1 stablecoins controllable

Businesses often underestimate the operational side of stablecoin use. The technology can be simple, but the process must fit accounting, procurement, and audit expectations.

Governance and approvals

Governance (how decisions are made and documented) is crucial when value can move quickly. A common control goal is to prevent any single person from having unilateral power over large transfers.

Readiness practices often include:

approval thresholds (limits above which extra approvals are needed),
separate roles for initiating and approving transfers,
documented signers (who is authorized), and
escalation paths (who decides when something goes wrong).

Vendor management and service commitments

If you rely on custodians, exchanges, payment processors, or blockchain infrastructure providers, vendor management matters. One helpful concept is a service-level agreement (a documented commitment about service availability and response time). Even when you do not have a formal agreement, you can still document what you expect and what you observed.

Vendor readiness questions commonly focus on:

security controls and incident history,
financial strength and operational capacity,
compliance program maturity,
transparency and reporting, and
outage and recovery procedures.

Recordkeeping and reconciliation

On-chain activity provides a transaction history, but finance teams still need records that match invoices, counterparties, and internal categories.

Reconciliation (matching records between systems) becomes easier when you:

standardize internal notes for transfer purpose,
maintain a clean mapping of addresses to counterparties, and
capture the business purpose of transfers at the time they happen.

If you wait until month-end, details are forgotten and errors compound.

Liquidity planning and payment timing

Liquidity planning is not only about price. It is also about operational access. If payroll is due on Friday, but a conversion route has a multi-day hold, you have operational liquidity risk.

Readiness includes planning buffers, diversifying conversion routes, and understanding the cutoffs that affect your flow.

Incident response and business continuity

Incident response (a plan for detecting, managing, and recovering from incidents) is part of mature readiness. Business continuity (planning to keep critical operations running during disruption) matters when payments are core to your business.

Security frameworks such as NIST provide a structured vocabulary for these ideas, even if you implement them in a lightweight way.^[5]

Accounting and audit readiness: being able to explain what happened

Accounting and audit readiness is often where stablecoin projects slow down, especially in regulated industries or public companies. You do not need to be an accountant to understand the core readiness goal: you must be able to explain, with evidence, what happened and why.

Classification and valuation questions

Accounting treatment depends on facts and local standards, and organizations should consult qualified professionals. Conceptually, readiness includes deciding how you will treat holdings and flows: what category they fit, how you measure value, and what events trigger gains or losses.

Even when USD1 stablecoins aim for stable value, accounting still cares about:

timing (when you recognize receipt or payment),
control (who had authority over the asset),
evidence (what documents support the transaction), and
disclosure (what stakeholders need to know).

Audit trail quality

An audit trail (records that show who did what and when) is stronger when you can tie together:

internal approvals,
on-chain transaction records,
invoices and contracts,
provider statements, and
bank statements for conversions.

The goal is not paperwork for its own sake. The goal is to reduce disputes and make reviews faster.

Data retention and privacy boundaries

Organizations should keep the records they need, but also respect privacy and data protection obligations. Readiness improves when you decide early what personal information (details that can identify a person) you will collect, why you need it, and how you will protect it.

Developer readiness: integrating USD1 stablecoins without surprising users

If you build products that involve USD1 stablecoins, readiness includes user safety, technical correctness, and operational maturity.

Smart contracts and security reviews

A smart contract (code deployed on a blockchain that can hold and move assets according to rules) can introduce both power and risk. Bugs can be permanent and exploitable.

Readiness practices often include:

limiting contract complexity,
security reviews (structured review of code and logic),
staged rollouts (gradual release to reduce blast radius), and
clear emergency procedures for pauses or upgrades.

Integration boundaries and APIs

An API (a way for software systems to talk to each other) often sits between your app and wallets, chains, analytics, and compliance tooling. Readiness includes clarity on which system is the source of truth for each fact: balances, transaction status, user identity, and risk decisions.

Edge cases and user messaging

Even "standard" token behavior can have edge cases: rounding, decimal precision, and unexpected reverts (transaction failures). Readiness means testing on the networks you support and building clear messages that help users recover without panic.

Bridges and cross-chain risk

A bridge (a system that moves assets between different blockchains) can be a major risk point. If you rely on cross-chain movement for USD1 stablecoins, readiness includes minimizing bridge use, communicating delays and risks, and having a plan if a bridge is paused.

Privacy and scams: readiness for the human layer

Many readiness failures are social, not technical. Even strong cryptography (math-based security) cannot protect a user who is tricked into giving away keys.

Public ledgers and unintended disclosure

Many blockchains operate as a public ledger (a record that anyone can view). That can create privacy issues. If you reuse addresses or share address information publicly, others may be able to see transaction history.

A block explorer (a website that lets you view blockchain transactions and addresses) makes this visibility easy. Readiness includes being intentional about what you share and using operational practices that reduce unnecessary exposure.

Phishing, impersonation, and support scams

Phishing is common in the digital asset world. Attackers often impersonate support agents, send fake links, or create lookalike websites. Readiness includes knowing that legitimate providers will not ask for your seed phrase and that urgent pressure is a common scam tactic.

Social engineering and internal controls

Social engineering (manipulating people into unsafe actions) affects businesses too. A convincing email can trigger an unauthorized payment if approvals are weak. Readiness includes layered controls: approvals, address whitelists, and verification steps outside email.

Monitoring and resilience: maintaining readiness over time

Readiness is not something you complete once. It is a condition you maintain.

Monitoring what matters

Monitoring might include:

address monitoring (alerts when funds move),
provider status monitoring (alerts when a custodian or exchange has issues),
fee monitoring (alerts for unusually high network fees), and
compliance monitoring (alerts for abnormal patterns).

Monitoring is only useful when it is tied to response: who receives alerts, what they do, and how quickly.

Scenario planning and stress testing

Scenario planning (thinking through plausible bad situations) helps teams avoid panic. Useful scenarios include:

fee spikes that make small transfers impractical,
congestion that delays settlement for hours,
bank delays that slow conversion back to U.S. dollars,
loss of access to a key holder, and
policy changes at a critical provider.

Global policy work often emphasizes that stablecoin arrangements can become systemically significant (meaning they can matter for the broader financial system) under scale, which is why resilience planning matters for larger users.^[1]^[2]

Controls that scale with value

A common readiness mistake is using the same controls for all amounts. Controls should scale with exposure. What is acceptable for a small pilot may be unacceptable for treasury-scale balances.

Banking supervisors have discussed differentiated treatment of cryptoasset exposures, including stablecoins, reflecting that not all digital assets present the same risk profile.^[6]

Common readiness mistakes and how to avoid them conceptually

The goal here is not a rigid checklist, but patterns that repeatedly cause pain.

Mistake 1: Treating USD1 stablecoins like bank money

USD1 stablecoins can behave like a fast settlement instrument, but they do not necessarily carry the same protections as bank accounts. Readiness means you understand what protections exist, who provides them, and under what conditions.

Central bank discussions of digital money often stress that different forms of money have different legal and risk characteristics.^[7]

Mistake 2: Over-relying on one provider or one chain

If your entire flow depends on one exchange, one custodian, or one chain, you have concentration risk. Readiness includes alternatives and contingency plans.

Mistake 3: Ignoring operational documentation

If only one person understands how funds move, you have key-person risk. Readiness includes documentation that others can follow, along with periodic reviews so documents stay accurate.

Mistake 4: Underestimating reporting obligations

Tax rules and reporting obligations vary widely, and digital asset activity can create complex reporting needs. International bodies like the OECD have published frameworks focused on tax transparency for crypto-asset activity, showing that reporting expectations are evolving.^[8]

Readiness means you keep accurate records from the start rather than trying to reconstruct them later.

Mistake 5: Not planning for security incidents

Security incidents are not only hacks. They include lost devices, compromised emails, and insider mistakes. A security readiness mindset, such as the one promoted by NIST, helps teams prioritize basic protections and recovery planning.

Bringing it together: what "ready" really means

Readiness for USD1 stablecoins is the overlap of five things:

Purpose: you know why you are using USD1 stablecoins and what success looks like.
Controls: you have custody, approvals, and monitoring matched to the value at risk.
Operations: you can run the process repeatedly without heroics.
Compliance: your activity remains usable with banks, providers, and partners.
Resilience: you can adapt when systems are stressed.

The stablecoin ecosystem sits at the intersection of payments, markets, and public policy. Reports from standard setters highlight both potential benefits and meaningful risks, which is why readiness should be treated as an operational discipline, not a setup chore.

FAQ: quick answers about readiness for USD1 stablecoins

Is readiness only for large institutions?

No. The scale changes the controls, but the concept applies to everyone. An individual may focus on seed phrase safety and scam avoidance. A business may focus on governance, approvals, and conversion routes.

Do USD1 stablecoins remove all payment risk?

No. USD1 stablecoins can reduce some forms of settlement friction, but they introduce other risks: custody risk, provider risk, chain congestion, policy restrictions, and operational mistakes.

What is the single most central readiness decision?

For many users, it is custody. Deciding who controls keys and how approvals work has outsized impact on safety.

Do I need to understand every technical detail of a blockchain?

No. You do need to understand the few details that affect your obligations: confirmation timing, fee variability, reversibility, and provider controls.

Why do policy documents matter if I just want to use a token?

Because policy guidance shapes how banks and service providers behave. Even if you are not regulated, your access can be affected by policies informed by these standards.^[1]^[3]^[4]