bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 28쪽 중 4쪽
ely when it is created. During this time, anyone can finish the escrow, but only if they supply the correct fulfillment to the crypto-condition. If no one finishes the escrow before its expiration time (
CancelAfter
field), the escrow becomes
Expired
. (An escrow without a finish-after time
must
have an expiration time.) In the expired state, the escrow can no longer be finished, and anyone can cancel it.
Limitations
The costs can make it infeasible for small amounts.
Escrow requires two transactions: one to create the escrow, and one to finish or cancel it. Crypto-Conditions incur a higher
transaction cost
than usual.
While the escrow is incomplete, the sender is responsible for the
reserve requirement
of the
Escrow
object.
You can't create an escrow with past time values.
Timed releases and expirations resolve according to
ledger close times
. In practice, actual release and expiration times can vary by about five seconds as ledgers close.
The only supported crypto-condition type is PREIMAGE-SHA-256.
If a token holder is deep frozen (Trust Line Tokens) or locked (MPTs), they cannot finish an escrow to receive tokens, but they can still cancel an escrow to return tokens to the sender. Individual or global freezes for Trust Line Tokens don't prevent escrow completion.
For tokens requiring authorization, both sender and recipient must be pre-authorized by the issuer before creating or finishing the escrow, respectively. Authorization cannot be granted during the escrow completion process.
EscrowFinish Transaction Cost
When using crypto-conditions, the EscrowFinish transaction must pay a
higher transaction cost
because of the higher processing load involved in verifying the crypto-condition fulfillment.
The additional transaction cost required is proportional to the size of the fulfillment. If the transaction is
multi-signed
, the cost of multi-signing is added to the cost of the fulfillment.
Currently, an EscrowFinish with a fulfillment requires a minimum transaction cost of
330
drops of XRP
plus 10 drops per 16 bytes in the size of the fulfillment.
Note
The above formula is based on the assumption that the reference cost of a transaction is 10 drops of XRP.
If
Fee Voting
changes the
reference_fee
value, the formula scales based on the new reference cost. The generalized formula for an EscrowFinish transaction with a fulfillment is as follows:
reference_fee * (signer_count + 33 + (fulfillment_bytes / 16))
See Also
For more information about Escrow in the XRP Ledger, see the following:
Escrow Tutorials:
Send a Timed Escrow
Send a conditional Escrow
Look Up Escrows
Cancel an Expired Escrow
Transaction Reference
EscrowCreate transaction
EscrowFinish transaction
EscrowCancel transaction
Ledger Reference
Escrow entry
## /docs/concepts/payment-types/checks
Checks
Copy
The Checks feature enables users to create deferred payments similar to personal paper checks. Unlike an escrow or payment channel, funds aren't set aside when a check is created, so money only moves when the check is cashed. If the sender doesn't have the funds at the time a check is cashed, the transaction fails; recipients can retry failed transactions until the check expires.
XRP Ledger Checks can have expiration times after which they may no longer be cashed. If the recipient doesn't successfully cash the Check before it expires, the Check can no longer be cashed, but the object remains in the XRP Ledger until someone cancels it. Anyone may cancel the Check after it expires. Only the sender and recipient can cancel the Check before it expires. The Check object is removed from the Ledger when the sender successfully cashes the check or someone cancels it.
Use Cases
Checks allow people to exchange funds using a process that is familiar to and accepted by the banking industry.
If your intended recipient uses
Deposit Authorization
to block direct payments from strangers, a check is a good alternative.
Flexible check cashes. The recipient can redeem the Check for between a minimum and maximum amount.
Check Lifecycle
The sender sends a
CheckCreate transaction
, which defines:
The recipient.
An expiration date.
The maximum amount that can be debited from their account.
When the transaction is processed, the XRP Ledger creates a
Check
object. The check can be canceled by the sender or receiver with a
CheckCancel transaction
.
The recipient submits a
CheckCash transaction
that transfers the funds and destroys the
Check
object. Recipients have two options for cashing checks:
Exact Amount: They specify an exact amount to cash that doesn't exceed the check maximum.
Flexible Amount: They specify a minimum amount to cash and the XRP Ledger delivers as much as possible up to the check maximum. If the sender doesn't have the funds to at least meet the specified minimum, the transaction fails.
If the check expires before the receiver cashes the check, the
Check
object remains until anyone cancels it.
See Also
For more information about Checks in the XRP Ledger, see:
Transaction Reference
CheckCreate
CheckCash
CheckCancel
Checks Tutorials:
Send a Check
Look up Checks
Cash a Check for an exact amount
Cash a Check for a flexible amount
Cancel a Check
Checks amendment
For more information about related features, see:
Deposit Authorization
Escrow
Payment Channels Tutorial
## /docs/use-cases/tokenization
Skip to content
Develop
Developer's Home
Learn
Code Samples
Docs
API Reference
Tutorials
Concepts
Infrastructure
Client Libraries
JavaScript
Python
PHP
Go
Use Cases
Payments
Direct XRP Payments
Cross-currency Payments
Escrow
Checks
Tokenization
Stablecoin
NFT
Credit
Lending (Open for Voting)
Trading
DEX
Permissioned Trading
AMM
Community
Community
Events
Blog
Funding
Contribute
Bug Bounty
Research
Ecosystem Map
Network
Resources
About
Download XRPL Brand Kit
Insights
Explorers
Amendment Voting Status
En
Real-World Asset (RWA) Tokenization
Learn how to issue crypto tokens and build tokenization solutions with developer tools and APIs.
Get Started Now
Why Financial Developers Choose XRPL as an RWA Tokenization Platform
Fast Settlement and Low Fees
Settle transactions in 3-5 seconds for a fraction of a cent — ideal for large-scale, high-volume RWA tokenization.
Onchain Metadata
Easily store key asset information or link to off-chain data using simple APIs, giving token holders more transparency and functionality.
Native Compliance Capabilities
Automatically check investor credentials, control who can transfer assets, and keep a full record of every transaction, offering a secure framework for the expanding RWA crypto market.
Delegated Token Management
Use a robust permission system to let trusted third parties manage the token on your behalf.
Multi Purpose Tokens (MPTs)
Issue, manage, and trade real-world assets without needing to build smart contracts. XRP Ledger's built-in functionality and compliance-enabling features allow asset tokenization without additional layers of complexity.
Download Whitepaper
Trusted by Leaders in Real-World Asset Tokenization
Token Utility and Market Integration
Trading
Utilize XRP Ledger's native decentralized exchange (DEX) with integrated Automated Market Makers (AMM) and onchain 24/7 order books, providing a developer-friendly environment to create DeFi solutions for traditional finance applications.
Decentralized exchange (DEX)
Collateral Mobility
Issuers can enable escrow functionality to lock tokens and facilitate secure, conditional transfers of assets based on time-locks or other conditions to enable automated financial use cases onchain.
Escrow functionality
Delegated Distribution
Token issuers can delegate user onboarding and token movement to distribution specialists, enabling them to scale their distribution network easily with a single transaction, while avoiding complex off-chain development.
Permission Delegation
Cross-Chain Markets
Access cross-chain trading and lending markets to enhance token utility and liquidity across ecosystems, a critical component for sustaining long-term XRP ledger tokenization growth.
Cross-chain trading
Developer Tools & APIs
Streamline development and build powerful RWA tokenization solutions with XRP Ledger's comprehensive developer toolset:
Get Started with Javascript
Get Started with Python
DEX Integration
Cross-Chain Interoperability
Defining Features of XRPL
01
Proven Open-Source Technology
With over 3.3B transactions processed, XRP Ledger has been a trusted, battle-tested blockchain for over a decade, supported by a global developer community committed to financial innovation.
02
Purpose-Built for Finance
XRP Ledger provides out-of-the-box institutional-grade functionality, reducing development overhead and eliminating the need for smart contracts, which makes it ideal for the RWA crypto space.
03
Native Compliance & Security
Maintain control over tokenized assets and enforce compliance using native tools such as issuer-defined Authorization, onchain Freeze capabilities, detailed metadata for attestations, and multi-signature accounts.
04
Optimal Liquidity Pathways
Streamline cross-currency transactions and trading as XRP Ledger's embedded trading features automatically identify the most efficient routes to enhance liquidity issued tokens and XRP.
Explore Trading on the XRPL
Stay Connected
Stay ahead in the world of tokenization. Subscribe to receive the latest insights, trends, and updates on payment solutions — delivered directly to your inbox.
Sign Up
Ask AI
## /docs/use-cases/tokenization/stablecoin-issuer
Stablecoin Issuer
Copy
As a financial professional, I want to issue a stablecoin so that I can earn revenue by charging fees for withdrawals or transfers of the stablecoin.
Stablecoins are tokens that are backed by assets outside of the XRPL. Stablecoins allow users to transact in familiar currencies, and provide a convenient way to get funds into and out of the XRPL blockchain.
The mechanics of issuing a stablecoin are not complicated.
Decide on the name for your stablecoin (either following the 3-character ISO standard or using a 160-bit hex string. See
Currency Codes
).
Create a trust line between the issuing account and a consuming account establishing a maximum number of stablecoins to transfer.
Send a payment of stablecoins to the consumer up to the maximum amount in the trust line.
While anyone can issue a token with any currency code in the XRP Ledger, stablecoin value comes from the promise that it can be redeemed for a corresponding asset. Issuing a stablecoin might involve regulatory obligations, which vary by jurisdiction. For these reasons, an established, reputable business is most likely to succeed in issuing a stablecoin.
There are many decisions to make and artifacts to generate as you prepare to release a new stablecoin. You can use the XRPL Foundation's
Self-assessment Questionnaire
as a starting point to gather and produce the necessary information for a successful launch.
Choose the Type of Stablecoin
The first step is to decide the type of stablecoin you want to create. Your choice of stablecoin type might require additional steps, such as signing on financial or audit partners.
There are five common types of currency tokens you can create on the XRPL: fiat-backed, crypto-backed, commodity-backed, financial instrument-backed, and non-collateralized. See
Stablecoins
.
Set Up Your Node Services
For lighter use cases and individual servers, you can often rely on free public servers. However, the more serious your use of the XRP Ledger becomes, the more important it becomes to have your own infrastructure.
There are many reasons you might want to run your own servers, but most of them can be summarized as: you can trust your own server, you have control over its workload, and you're not at the mercy of others to decide when and how you can access it. See
Reasons to Run Your Own Server
.
Alternatively, you can use an external node service provider like OpenNode. See
OpenNode
.
Sandbox Access
For testing purposes, you can implement, deploy, and trade your stablecoin on the XRPL Testnet or Devnet servers. Visit the XRP Faucets page to generate your test network credentials. Use the listed server URIs on that page to connect to and interact with your chosen test network. See
XRP Faucets
.
Stablecoin Settings
Before you mint your new stablecoin, you need to configure settings, some of which are immutable once you issue the first coin.
See
Stablecoin Settings
.
For more detail on configuration capbilities, see
Stablecoin Issuer Configuration
.
Asset Information
Publish standard information about your stablecoin to enable potential traders to verify the coin's stability.
Asset Nomenclature
Choose a 3-character string for your currency code. Per ISO 4217, supranational currency codes begin with the letter
X
for a currency that is not associated with a country. See
ISO 4217
.
Currency codes do not have to be unique. For instance, if you're issuing a stablecoin backed by a national fiat currency, it's better to use the official code for that currency, such as
EUR
.
xrp-ledger.toml
You can publish information about what currencies you issue, and which XRP Ledger addresses you control, to protect against impostors or confusion, using an
xrp-ledger.toml
file on your website. This machine-readable format is convenient for client applications to process. If you run an XRP Ledger validator, you can also publish the key in the same file.
You can use the
Currencies
table to provide additional information about your stablecoin. This makes the information about your cryptocurrency accessible in an expected place and format, and enhances transparency. See
xrp-ledger.toml File
.
Account and Key Management
Multisignature Schemes
By using multiple keys and signing weights, issuers and asset holders can distribute trust and responsibility for approving transactions for an account between different users and systems. This gives you the flexibility to gate those signatures using internal processes and controls.
See
Multi-signing
.
Token Operations
Issue a Stablecoin
Actually issuing a new stablecoin is straightforward. In practice, there are many considerations when issuing a stablecoin that users will trade with confidence.
Before you issue your stablecoin, download and read the questions in the
Self-assessment Questionnaire
. When you are ready to distribute your stablecoin, complete the public
Token Issuer Self-Assessment Questionnaire
. This allows full transparency to the XRPL community about your new stablecoin.
For additional considerations, see:
Stablecoin Issuer - Precautions
Stablecoin Issuer - Compliance Guidelines
Issue a Fungible Token
Create a Trust Line
Trust lines are structures in the XRP Ledger for holding tokens. Trust lines enforce the XRP Ledger's rule that you cannot cause someone else to hold a token they don't want. This precaution is necessary to enable the XRP Ledger's use case for community credit, among other benefits.
Each "trust line" is a bidirectional relationship consisting of:
The identifiers for the two accounts that the trust line connects.
A single, shared balance, which is positive from the perspective of one account and negative from the other perspective.
Various settings and metadata. Each of the two accounts can control its own settings on the trust line. Each side sets a limit on the trust line.
Each trust line is specific to a given currency code. Two accounts can have any number of trust lines between them for different currency codes, but only one shared trust line for any particular currency code.
See
Trust Line Tokens
.
Authorized Trust Lines
The Authorized Trust Lines feature enables issuers to create tokens that can only be held by accounts that the issuer specifically authorizes. This feature only applies to tokens, not XRP.
To use the Authorized Trust Lines feature, enable the
Require Auth
flag on your issuing account. While the setting is enabled, other accounts can only hold tokens you issue if you have authorized those accounts' trust lines to your issuing account.
See
Authorized Trust Lines
.
Freeze a Trust Line
If you issue tokens in the XRP Ledger, you can enable the
No Freeze
setting to permanently limit your own ability to use the token freezing features of the XRP Ledger. (As a reminder, this only applies to issued tokens, not XRP.)
If you do not enable the
No Freeze
setting, when an account shows suspicious activity or violates your institution's terms of use, you have the option of freezing the trust line while you resolve the issue.
See
Freezing Tokens
.
Global Freeze
If you see signs of suspicious activity, you can enact a global freeze on your account to prevent users from sending your tokens to each other and trading your token in the decentralized exchange.
See
Enact Global Freeze
.
Clawback
Clawback is an optional setting that you can choose before you begin to distribute your stablecoin. For regulatory purposes, some issuers
must
have the ability to recover issued tokens after they are distributed to accounts. For example, if an issuer were to discover that tokens were sent to an account sanctioned for illegal activity, the issuer could recover, or
claw back
, the funds.
See
Clawback
.
Requires the
Clawback
amendment
.
Loading...
Partial Payments
Look out for partial payments. Payments with the partial payment flag enabled can be considered "successful" if any non-zero amount is delivered, even minuscule amounts.
Check the transaction for a
delivered_amount
field. If present, that field indicates how much money
actually
got delivered to the
Destination
address.
In xrpl.js, you can use the
xrpl.getBalanceChanges()
method
to see how much each address received. In some cases, this can be divided into multiple parts on different trust lines.
See
Partial Payments
.
Burn
One way to manage the value of a token is to destroy, or
burn
tokens, which reduces the number of tokens in circulation. On the XRP Ledger, fungible tokens are automatically "burned" when they are sent to the issuing address. However, the issuer can freely create more tokens.
To ensure a limited supply, you can blackhole the issuer after issuing tokens, by setting its regular key to an address like
rrrrrrrrrrrrrrrrrrrrrhoLvTp
for which no one knows the private key, and disabling the master key pair.
Warning
A blackhole account has no way to send transactions of any kind, so you cannot update any settings or do any maintenance on the account afterwards!
See
Blackholed Accounts
and
Disable Master Key Pair
.
Reliable Transaction Submission
The goal of reliably submitting transactions is to achieve the following two properties in a finite amount of time:
Idempotency - Transactions should be processed once and only once, or not at all.
Verifiability - Applications can determine the final result of a transaction.
To submit transactions reliably, follow these guidelines:
Persist details of the transaction before submitting it.
Use the
LastLedgerSequence
parameter. (Many
client libraries
do this by default.)
Resubmit a transaction if it has not appeared in a validated ledger whose
ledger index
is bigger than or equal to the transaction's
LastLedgerSequence
parameter.
For more information, see
Reliable Transaction Submission
.
List on the XRPL Native DEX
Decentralized exchanges (DEXes) are integral to the decentralized finance ecosystem. Listing your token on the XRP Ledger's built-in DEX enhances its visibility and accessibility, thereby attracting more liquidity. Begin by placing sell offers using a suitable interface, such as
Sologenic
. As a precaution, use a separate account, not your issuing address, to trade.
List on an AMM
Automated Market Makers (AMMs) are smart contracts that provide liquidity in the XRP Ledger's decentralized exchange. Each AMM holds a pool of two assets and enables users to swap between them at an exchange rate set by a formula.
For any given pair of프로젝트로 돌아가기