Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Here we explain what UTXOs are and how to manage it. What are UTXOs
A UTXO is the amount of digital currency remaining after a blockchain transaction is executed.
Transaction Creation: When a transaction is made, it consumes one or more UTXOs as inputs and creates new UTXO**s as outputs
When you send Bitcoin, several steps programmatically take place. One of the earliest steps in the transaction process is for your cryptocurrency wallet to scan the blockchain for the amount of funds you have. These funds are known as unspent transaction outputs (UTXOs).
The funds are considered “unspent” because they are freely available for you to send to someone or move to another wallet.
They are called “transaction outputs” because they were created from previous transactions.
UTXOs are processed continuously and are responsible for beginning and ending each transaction.
When a transaction is completed, any unspent outputs are deposited back into a database as inputs, which can be used at a later date for a new transaction.
Example:
You can think of UTXOs as loose change leftover from previous Bitcoin transactions.
If you spend $12 on lunch using a $20 bill, you’d have $8 leftover. In this example, the leftover $8 would be an unspent transaction output. It would be generated as an entirely new “$8 bill” UTXO and go back to your wallet, ready to be used to buy something else.
Just as you can’t physically give a shopkeeper a $5 bill and then give the same $5 bill to someone else, a Bitcoin user cannot successfully use the same unspent transaction output in two separate blockchain transactions.
In this way Bitcoin solves the double-spending problem. The other widely used concept of wallet balance tracking is called Account/Balance model. It’s being used by EVM chains like Ethereum, EOS, Tezos etc.
Managing UTXOs For some transactions, such as bulk minting Runes or sending multiple transaction in one block, you would need to have your BTC divided in lesser or bigger UTXO pieces. To adjust them to the size needed, you would either have to split or consolidate your UTXOs.
Split:
To split UTXOs you would need to use third-party services. As for now, the best options are:
How many sats per UTXO are optimal for bulk Runes mints? Here you will need to estimate how much a mint will cost. At times of low mempool occupancy, the gas fee rate ranges at about 25-35 sats/vB. Therefore, for optimal speed and in order to not get front ran, you’d like to set the gas fee slightly (~5 sats) above the current average rate. An absolute minimum per UTXO would be 50,000 sats = 0.0005 BTC ($35 if BTC=$70k). This would be enough to cover up to 10 mints per UTXO in separate blocks (at low fee rates). In the best scenario, you’d have a mint strategy that involves different sized UTXOs. If your BTC is split in larger UTXOs, you’ll be able to mint during the high network fees.
BTC=$70k
1,000,000 sats = 0.01 BTC ($700)
500,000 sats = 0.005 BTC ($350)
400,000 sats = 0.004 BTC ($280)
300,000 sats = 0.003 BTC ($210)
200,000 sats = 0.002 BTC ($140)
100,000 sats = 0.001 BTC ($70)
50,000 sats = 0.0005 BTC ($35)
Consolidation:
You can consolidate UTXOs by sending them to the wallet, where you'd like to get 1 consolidated UTXO. You can as well consolidate within the wallet. To do so, just enter the address you're sending from as a receiver address.
Unlike traditional exchanges that rely on order books to match buyers and sellers, RunesDeX facilitates trades directly against the liquidity pool, providing a decentralized and permissionless trading experience.
Welcome to Runes Dex docs! This book is intended for any audience looking to our main product:
Runes Dex - implements the functionality of an automated market maker (AMM).
The Runes Dex Exchange have a several features for decentralized Runes trading:
Following this, we would suggest utilising the quick guide on Runes Dex.
Runes Dex is an Automated Market Maker (AMM), and the exchange is the central component of Runes Dex.
The protocol is operational on Bitcoin Runes, providing safe and decentralised trading opportunities on the Bitcoin mainnet.
Runes Dex enables users to trade directly from their own wallets, circumventing the necessity for a CEX. This ensures the retention of complete control over one's assets, obviating the need to entrust them to a third party.
Token exchanges on Runes Dex are only possible when there is sufficient liquidity for those tokens. Without adequate liquidity, trading can be difficult, expensive or impossible.
The Auto Market Maker (AMM) is the core of pool models and liquidity pools, instead of using the Oracle price, AMMs determine the prices by the algorithm.
Users can provide liquidity to RunesDeX by depositing an equivalent value of BTC and Runes tokens into a pool.
The addLiquidity function
allows users to add liquidity to a RunesDeX pool, contributing both BTC and Runes tokens.
As a user, you deposit an equivalent value of BTC and Runes tokens into the liquidity pool. This helps maintain the balance in the pool, ensuring that trades can occur smoothly.
When you add liquidity, you will receive pool tokens representing your position. These tokens automatically earn fees proportional to your share of the pool, and can be redeemed at any time. By adding liquidity you'll earn 0.25% of all trades on this pair proportional to your share of the pool. Fees are added to the pool, accrue in real time and can be claimed by withdrawing your liquidity.
The removeLiquidity function
allows users to withdraw their liquidity from the pool by redeeming their LP tokens for the underlying BTC and Runes tokens.
Calculate Withdrawal Amounts:
The amount of BTC and Runes tokens you receive is based on your share of the pool. The pool calculates your proportionate share and returns the corresponding amounts of BTC and Runes tokens to you.
Receive BTC and Runes Tokens:
The calculated amounts of BTC and Runes tokens are transferred from the pool back to your wallet, completing the withdrawal process.
Removing pool tokens converts your position back into underlying tokens at the current rate, proportional to your share of the pool. Accrued fees are included in the amounts you receive.
Liquidity providers earn a 0.25% fee on each trade proportional to their share in the pool.
A portion of the transaction fee is transferred to the liquidity pool. This fee, which is not less than the dust BTC amount, compensates the liquidity providers for their participation and risk in the pool. This fee helps maintain the pool's operation and incentivizes liquidity provision.
Runes DeX earns 0.25% fee on each transaction to the treasury.
Another portion of the transaction fee is directed to the RunesDeX treasury. This fee, also not less than the dust BTC amount, supports the maintenance and development of the RunesDeX platform, ensuring its sustainability and growth.
The total swap fees for Runes Dex are 0.5%.
Users can swap between BTC and Runes tokens available in the RunesDeX liquidity pools. The swap price is determined by the ratio of the tokens in the pool, adjusted according to the constant product formula.
1. User's Runes with Dust BTC or BTC Transfer to Swap
The user initiates the SWAP by transferring their Runes tokens along with a small amount of BTC (dust BTC) or BTC directly to the swap contract. This step includes the user's intention to exchange Runes tokens for BTC or vice versa.
2. Fee Transfer to the Pool (Not Less Than Dust BTC)
A portion of the transaction fee is transferred to the liquidity pool. This fee, which is not less than the dust BTC amount, compensates the liquidity providers for their participation and risk in the pool. This fee helps maintain the pool's operation and incentivizes liquidity provision.
3. Fee Transfer to the Treasury (Not Less Than Dust BTC)
Another portion of the transaction fee is directed to the RunesDeX treasury. This fee, also not less than the dust BTC amount, supports the maintenance and development of the RunesDeX platform, ensuring its sustainability and growth.
4. Pool's Runes with Dust BTC or BTC Transfer to Swap
The liquidity pool responds by transferring the corresponding amount of Runes tokens with dust BTC or BTC to the user’s wallet. This step completes the exchange process, ensuring the user receives the desired tokens as per the swap rate.
5. Transfer Back the User's Unused BTC from Input UTXOs
If the user initially transfers more BTC than is required for the swap, the unused BTC is returned to the user's wallet. This step ensures that only the necessary amount of BTC is used for the transaction, and any excess BTC is safely returned.
6. Transfer Back the Pool's or User's (Based on Sender) Unused Runes
Similarly, if the liquidity pool or user transferred more Runes tokens than required for the swap, the unused Runes tokens are returned to the respective sender. This step ensures efficient use of the tokens and avoids any excess transfer.
AMMs use liquidity pools, where users can deposit cryptocurrencies to provide liquidity. These pools then use algorithms to set token prices based on the ratio of assets in the pool. When a user wants to trade, they swap one token for another directly through the AMM, with prices determined by the pool's algorithm.
RunesDeX utilizes a simple mathematical formula:
Where x represents the quantity of BTC, and y represents the quantity of Runes tokens in a liquidity pool, with k
being a constant. This formula ensures that the product of the token quantities remains constant during trades.
Unlike traditional exchanges that rely on order books to match buyers and sellers, RunesDeX facilitates trades directly against the liquidity pool, providing a decentralized and permissionless trading experience.
Slippage occurs when the actual price you get for a trade is different from the expected or quoted price. It often happens in situations of high market volatility or low liquidity. If you want to buy or sell an asset at a specific price, but the market conditions change before your trade is executed, you might end up with a slightly different price than you anticipated. Slippage can result in a higher or lower cost for your trade than you initially planned.
Impermanent loss is a term used in liquidity provision. When you provide liquidity to a pool by depositing two different assets, the value of your assets can change over time due to price fluctuations. Impermanent loss occurs when the value of your assets in the pool is less than if you had simply held those assets without providing liquidity. It's "impermanent" because the loss can decrease or disappear as the prices of the assets change.
Detailed about impermanent loss
Liquidity providers face the risk of impermanent loss, which occurs when the price of the deposited tokens changes compared to the price at the time of deposit, potentially leading to less favorable returns compared to simply holding the tokens.
Price impact refers to the effect a large trade has on the price of an asset in a market. When someone buys or sells a significant amount of an asset, it can cause the price to move in the direction of the trade due to the imbalance in supply and demand. The larger the trade relative to the overall liquidity in the market, the greater the price impact. Price impact can lead to higher or lower prices depending on whether it's a buy or sell order.
A Bitcoin Taproot address is a relatively new kind of Bitcoin address. Also known as Pay-to-Taproot (P2TR) addresses, it leverages the Taproot protocol to provide a more efficient mechanism for transacting with Bitcoin.
Taproot is the latest Bitcoin address format designed to enhance privacy, scalability, and scripting capabilities. Addresses in this format start with "bc1p."
Taproot allows the aggregation of multiple signatures, making complex transactions more efficient and cost-effective.
Taproot has enabled new smart contract functionalities on Bitcoin, paving the way for the emergence of Ordinals and Bitcoin-native tokens like BRC-20 and Runes.
Example Taproot Address: bc1pavlmkapyn630588yvykxuhhwgzke7d7h0lcgca8a9uczcrct8elq7aqmt8
Runes Dex Have a user friendly interface so swaps can be easy compared for any users.
Before started you should install wallet compatible with BTC and Runes protocols. You can learn how to get it .
Let's start trading:
Go to the Runes Dex .
Connect your wallet.
Choose the token you want to trade from the dropdown menu in the upper section. Whichever token you choose, you will need to make sure you have a sufficient amount of them in your wallet to trade with.
Next, either type an amount in the upper section to input the number of tokens you want to swap (spending amount). Or, type an amount in the lower section to input the number of tokens you want to swap to (receiving amount).
Check all the details, and click the Confirm button.
Then Confirm transaction in your wallet.
Done! You can check your transaction on .
Coming soon....
Runes: Runes is the new protocol on top of Bitcoin, which enables the users to inscribe certain values to the fractions of Bitcoin (sats), and in this way, create the ERC-20-like experience for creating, trading and managing Bitcoin native assets. In simple words, Runes are “kind of” the fungible tokens on the Bitcoin Blockchain. BRC-20 tokens: An older token experimental standard, demonstrating that you can create off-chain balance states with inscriptions on Bitcoin. Likely to be replaced by Runes. What is RUNES DEX?
RUNES DEX has been building the first decentralized AMM on the Bitcoin Blockchain for Runes, Ordinals & BRC-20.
Can I add my own tokens to Runes Dex exchange?
Everyone can create liquidity pools by depositing liquidity on Runes Dex.
Figma
Explore detailed Runes on our Runes Dex Explorer.
TICKER - RUNES•NETWORK.
RUNES-NETWORK total supply - 690,690,690.
Explorer - https://ordiscan.com/rune/RUNESNETWORK
Get started interacting and building on top of the RunesDeX Platform with our REST API. For access please reach out to partners@runesdex.com.
Base URL: https://app.runesdex.com/v1
The RunesDEX API uses API keys to authenticate requests. The API key you’ve been provided must be included in the x-api-key
HTTP header in all authenticated requests. To request an API key, please reach out to the RunesDEX team.
200 OK: The swap was successful. The response will include details of the transaction.
400 Bad Request: The request was invalid (e.g., missing parameters, invalid values).
500 Internal Server Error: An error occurred on the server while processing the request.
Bitcoin Runes - Bitcoin Runes is kind of a new token standard in the Bitcoin ecosystem. In simple terms, Bitcoin Runes are a new token standard for creating fungible tokens on Bitcoin.
The protocol was introduced last September by Bitcoin developer Casey Rodarmor, the creator of the Bitcoin Ordinals. Runes improves fungible tokens on Bitcoin. One of their benefits is that they increase Bitcoin’s appeal and could onboard millions to the network. Runes make it easier to create memecoins and other community-based projects on Bitcoin. There are already lots of memecoin projects on the Runes train.
In addition, the Bitcoin Rune inherits some of the native features of the Bitcoin chain, including its security. However, it is important to proceed with caution as Runes are still in their early stages.
Runes is different from other Bitcoin tokens standarts because it doesn't use a native token or off-chain data. It's a UTXO-based model that uses unspent transaction outputs (UTXOs) to track the Runes balance. Each transfer transaction is split into different UTXOs, each holding a different amount of Runes.
The Runes protocol’s launch on the Bitcoin mainnet on April 20, 2024.
Runes come into existence by being etched. Etching creates a rune and sets its properties. Once set, these properties are immutable, even to its etcher.
Rune protocol messages, called runestones, are stored in Bitcoin transaction outputs.
A runestone output's script pubkey begins with an OP_RETURN
, followed by OP_13
, followed by zero or more data pushes. These data pushes are concatenated and decoded into a sequence of 128-bit integers, and finally parsed into a runestone.
A transaction may have at most one runestone.
A runestone may etch a new rune, mint an existing rune, and transfer runes from a transaction's inputs to its outputs.
A transaction output may hold balances of any number of runes.
Runes are identified by IDs, which consist of the block in which a rune was etched and the index of the etching transaction within that block, represented in text as BLOCK:TX
. For example, the ID of the rune etched in the 20th transaction of the 500th block is 500:20
.
Request parameters | Type | Description |
---|---|---|
A valid response body is structured as follows:
For more information regarding the fields returned in the response body, reference the table below. In cases where a non 2xx
HTTP status code is returned, reference the Error Response
tab of this section to identify root causes.
Field Name | Type | Description |
---|---|---|
Information about all runes like that:
Token name
ID / Rune Ordinal Number
Minted / By now
Divisibility
Deployment Timestamp
For search, click the magnifier in the upper right corner of the list
In this video you’ll learn how to set up an , the leading Bitcoin wallet for Ordinals, BRC20 and Runes.
Segwit Address (3): Store your Bitcoin (also used for purchasing Ordinals, Runes, etc)
Taproot Address (bc1p): Store ordinal inscriptions, BRC-20 tokens, and Runes.
For other wallets we recommend to use only Taproot address ( bc1p )
Taproot Wallets Top Picks:
Most major exchanges provide a wide range of payment options, enabling users to purchase BTC using debit or credit card, Apple Pay, Google Pay, Samsung Pay, or wire transfer.
That's it! You're now ready to take on Bitcoin web3. Remember, use a non-custodial wallet, meaning you have 100% control of your funds at all times. It's essential to stay vigilant and backup your secret recovery phrase.
Our API is defined using the OpenAPI 3.0 specification. You can easily explore and test the endpoints using tools like Swagger UI, or Postman. For convenience, you can interact with our API on our hosted SwaggerUI page:
You can also quickly send sample API requests using the below. If you'd prefer to use a tool like Postman, download our OpenAPI spec available at:
HTTP Status Code | Error Message | Description |
---|---|---|
have different types of addresses to manage various assets securely. Here’s a quick overview:
In , both addresses support Runes, but it would be preferable to use Taptroot Adresses.
At this point, RunesDEX has integrated , , wallets and will be adding further options in the nearest future.
bid_asset
String
The asset being offered in the swap.
bid_amount
Number
The amount of the bid asset being offered.
bid_address
String
The address from which the bid asset is being sent.
bid_address_pubkey
String (optional)
The public key associated with the bid address, if available.
ask_address
String
The address to which the ask asset is being sent.
ask_amount
Number
The amount of the ask asset being requested.
fee_address
String
The address to which any fees are being sent.
fee_address_pubkey
String (optional)
The public key associated with the fee address, if available.
rate
Number
The exchange rate for the swap.
slippage
Number
The allowed slippage percentage for the swap.
slippage_tolerance
Boolean
Indicates whether slippage tolerance is enabled.
request_id
String
A unique identifier for the liquidity change request.
pair_id
Number
The identifier of the trading pair involved in the liquidity change.
pair
String
The name of the trading pair, typically in the format "base/quote".
base_address
String
The address associated with the base asset in the liquidity change.
quote_address
String
The address associated with the quote asset in the liquidity change.
base_amount
Number
The amount of the base asset involved in the liquidity change.
quote_amount
Number
The amount of the quote asset involved in the liquidity change.
btc_tx_fee
Number
The transaction fee in satoshis for the Bitcoin transaction.
psbt
String
The Partially Signed Bitcoin Transaction (PSBT) in base64 format.
raw_tx
String
The raw Bitcoin transaction in hexadecimal format.
base_inputs
List[Number]
A list of input indices for the base asset in the transaction.
quote_inputs
List[Number]
A list of input indices for the quote asset in the transaction.
400 Bad Request
"pool_address in invalid"
Returned when the pool address is invalid.
400 Bad Request
"tx params are invalid"
Returned when transaction parameters are invalid.
400 Bad Request
"can't verify rate"
Returned when the swap rate cannot be verified.
400 Bad Request
"don't have balance for operation"
Returned when the user does not have sufficient balance for the operation.
401 Unauthorized
Returned when the partner API key does not exist.
500 Internal Server Error
"can't create signer"
Returned when there is an error creating a signer.
500 Internal Server Error
"failed to sign swap tx"
Returned when there is an error signing the swap transaction.
500 Internal Server Error
"can't save request"
Returned when there is an error saving the liquidity change request.
500 Internal Server Error
"can't fetch btc price"
Returned when there is an error fetching the BTC price.
500 Internal Server Error
"can't fetch pool fees"
Returned when there is an error fetching the pool fees.
This endpoint is used to check if the service is up and running.\
Ok Status
This endpoint is used to get the version of the service.\
App Info
"runes_dex"
"main"
"03798661f49a25592975d96bf9a80b9b0555ae5a"
"0.4.5"
Returns the last indexed block to assert the status of the service.\
Sync status is returned
Height of the last indexed block
10
"runes_index"
This endpoint is used to get a BTC balance by address.\
"tb1ps07g3t8hctex0ula3jaxxa85dqw28ewl0krmnt8mlpxukmzp9zeqmzjfdw"
Success
"tb1ps07g3t8hctex0ula3jaxxa85dqw28ewl0krmnt8mlpxukmzp9zeqmzjfdw"
This endpoint is used to add a new user to the database.\
"bc1p0x6psjqeawtw8zvekup2gcg8uuwejhgjfad3sp9xklmpeaq80m4qd0ly9f"
Success
This endpoint allows to submit a transaction to the Bitcoin network.\
Success
"af7ef135a4469ec63af59e7244693418fdb96e852baf84c0adb70b28d9ec99e1"
"pending"
This endpoint is used to get a user from the database.\
"tb1ps07g3t8hctex0ula3jaxxa85dqw28ewl0krmnt8mlpxukmzp9zeqmzjfdw"
List of addresses
"bc1p0x6psjqeawtw8zvekup2gcg8uuwejhgjfad3sp9xklmpeaq80m4qd0ly9f"
This endpoint is used to list balances of Runes by address.\
Success
0
50
0
123
"BTC"
"Bitcoin"
"B"
8
"21000000000"
"21000000000"
"bc1p0x6psjqeawtw8zvekup2gcg8uuwejhgjfad3sp9xklmpeaq80m4qd0ly9f"
"1000000000"
This endpoint is used to get a Rune balance by address.\
BTC or rune name
Success
"BTC"
"Bitcoin"
"B"
8
"21000000000"
"21000000000"
"bc1p0x6psjqeawtw8zvekup2gcg8uuwejhgjfad3sp9xklmpeaq80m4qd0ly9f"
"1000000000"
This endpoint is used to get a user's liquidity positions.\
"tb1ps07g3t8hctex0ula3jaxxa85dqw28ewl0krmnt8mlpxukmzp9zeqmzjfdw"
Success
2
"BTC"
"Bitcoin"
"B"
8
"21000000000"
"21000000000"
"0.153"
"1223123.23"
"333.33"
"1223123.23"
"1223123.23"
This endpoint is used to get the position of an address in a trading pair.\
"BTC"
"MYLOVELYRUNE"
"tb1ps07g3t8hctex0ula3jaxxa85dqw28ewl0krmnt8mlpxukmzp9zeqmzjfdw"
Success
2
"BTC"
"Bitcoin"
"B"
8
"21000000000"
"21000000000"
"0.153"
"1223123.23"
"333.33"
"1223123.23"
"1223123.23"
This endpoint is used to create a new trading pair.
Idempotent. If pair exists, returns existing pool address.
"BTC"
"MYLOVELYRUNE"
"BTC"
"MYLOVELYRUNE"
Success
2
"tb1pptp2yfl3xjvltfxwwvqnsspe60uyc0a24d90ymas4qxl8xs8rxss94quj9"
This endpoint is used to get the price history of a trading pair.\
"BTC"
"MYLOVELYRUNE"
Gapfilled candlestick data
Serialized as an array of fields (9 elements).
Fields: [start_time, trading_pair_id, open, close, high, low, base_volume, quote_volume, count]
All points are gapfilled - meaning that even if database contains 0 trades in range [start_time
...end_time
], but there were trades before start_time, then returned array will contain (end_time
- start_time
) points (with interval
between them).
This endpoint is used to calculate the base and quote amounts.\
"BTC"
"MYLOVELYRUNE"
"BTC"
"MYLOVELYRUNE"
Success
"1000"
"10000"
This endpoint is used to list UTXOs by asset and address.\
Number of runes to return.
Filter by rune name as %NAME%. "SUPER" will match "MYSUPERRUNE", for example.
"SUPER"
Order of the results.
"ASC"
Page number for pagination.
Success
0
50
0
123
123
3009048
1
"af7ef135a4469ec63af59e7244693418fdb96e852baf84c0adb70b28d9ec99e1"
0
"MAXDECIMALSRUNESOBIG"
"bc1p0x6psjqeawtw8zvekup2gcg8uuwejhgjfad3sp9xklmpeaq80m4qd0ly9f"
"76a914c0e3d9d0c2f0a5e2a0d6a9e1f3c5f6e8c8d7d88ac"
"1000000000"
600
false
This endpoint is used to get a Rune by name.\
Success
block number : transaction number in that block
"3009048:5"
"MAXDECIMALSRUNESOBIG"
"MAXDECIMALSRUNESOBIG"
A single UTF8 character, including emoji
"¤"
3009048
A tx position in a block
5
0
Total amount of runes minted
"1000000000"
"1000000000"
Total amount of runes in circulation (max_supply - burned)
"1000000000"
Number of subunits in a super unit of runes
8
true
1727898475
"81972d23a9abaa1c6f0d96b7bccd9af905ff8a4f44ac50f2a62366f92e5a8efb"
"3caae66d4c38c46f56f12571fc518bbb36ce3ec03a4e3b6c3ed44dbee9fa9630"
a raw transaction hex
"7b22656469637473223a5b5d2c2265746368696e67223a7b2264697669736962696c697479223a33382c227072656d696e65223a313030303030303030302c2272756e65223a224d4158444543494d414c5352554e45534f424947222c2273706163657273223a302c2273796d626f6c223a6e756c6c2c227465726d73223a6e756c6c2c22747572626f223a747275657d2c226d696e74223a6e756c6c2c22706f696e746572223a317d"
false
This endpoint is used to search for Runes.\
"BIG"
Success
block number : transaction number in that block
"3009048:5"
"MAXDECIMALSRUNESOBIG"
"MAXDECIMALSRUNESOBIG"
A single UTF8 character, including emoji
"¤"
3009048
A tx position in a block
5
0
Total amount of runes minted
"1000000000"
"1000000000"
Total amount of runes in circulation (max_supply - burned)
"1000000000"
Number of subunits in a super unit of runes
8
true
1727898475
"81972d23a9abaa1c6f0d96b7bccd9af905ff8a4f44ac50f2a62366f92e5a8efb"
"3caae66d4c38c46f56f12571fc518bbb36ce3ec03a4e3b6c3ed44dbee9fa9630"
a raw transaction hex
"7b22656469637473223a5b5d2c2265746368696e67223a7b2264697669736962696c697479223a33382c227072656d696e65223a313030303030303030302c2272756e65223a224d4158444543494d414c5352554e45534f424947222c2273706163657273223a302c2273796d626f6c223a6e756c6c2c227465726d73223a6e756c6c2c22747572626f223a747275657d2c226d696e74223a6e756c6c2c22706f696e746572223a317d"
false
This endpoint is used to get the swap history of a trading pair.\
"BTC"
"MYLOVELYRUNE"
Order of the results.
"ASC"
Number of runes to return.
Page number for pagination.
Success
0
50
0
123
"buy"
"1000"
"10000"
"0.001"
BTCUSD price at the moment of a swap.
"1000"
This endpoint is used to remove liquidity from a trading pair.\
"BTC"
"MYLOVELYRUNE"
Success
"123"
2
"BTC/MYLOVELYRUNE"
"bc1p0x6psjqeawtw8zvekup2gcg8uuwejhgjfad3sp9xklmpeaq80m4qd0ly9f"
"37LHryP6Pj6Z98bQZj76YBcQ1JNKZsSXoC"
"41533"
"10000"
1000
partially signed bitcoin transaction
This endpoint is used to add liquidity to a trading pair.\
"BTC"
"MYLOVELYRUNE"
"bc1pkr9xwf5n6ugue9ra4p3quy940gl3qaaju57pvvhy5xh8xehmzh3syzdqs3"
"8f0f508a694fe6991fd6fd8be19bfec9dad34afbc5e16c2c6af1b57ee4a75f28"
"41533"
"37LHryP6Pj6Z98bQZj76YBcQ1JNKZsSXoC"
"02c64921f5c9b2c209ada61c78719eec30bebcdfc1d63ee051a68aa241ffb3190a"
"10000"
Success
"123"
2
"BTC/MYLOVELYRUNE"
"bc1p0x6psjqeawtw8zvekup2gcg8uuwejhgjfad3sp9xklmpeaq80m4qd0ly9f"
"37LHryP6Pj6Z98bQZj76YBcQ1JNKZsSXoC"
"41533"
"10000"
1000
partially signed bitcoin transaction
This endpoint is used to swap assets in a trading pair.\
"BTC"
"MYLOVELYRUNE"
Success
"123"
2
"BTC/MYLOVELYRUNE"
"bc1p0x6psjqeawtw8zvekup2gcg8uuwejhgjfad3sp9xklmpeaq80m4qd0ly9f"
"37LHryP6Pj6Z98bQZj76YBcQ1JNKZsSXoC"
"41533"
"10000"
1000
partially signed bitcoin transaction
This endpoint is used to get a list of trading pairs.\
Number of runes to return.
Filter by rune name as %NAME%. "SUPER" will match "MYSUPERRUNE", for example.
"SUPER"
Order of the results.
"ASC"
Page number for pagination.
Success
0
50
0
123
"BTC"
"Bitcoin"
"B"
8
"21000000000"
"21000000000"
"BTC"
"Bitcoin"
"B"
8
"21000000000"
"21000000000"
"1279361"
"35200000"
base_amount / quote_amount
"3634548.2954545454545454545"
2
"tb1pptp2yfl3xjvltfxwwvqnsspe60uyc0a24d90ymas4qxl8xs8rxss94quj9"
"2.751373537258053043668E-7"
"7.51373537258053043668"
"0.0170889585035029197178120051"
"62110.64"
in USD
"17088958.50"
in USD
"17088958.50"
in USD
"43725.89"
number of finalized swaps in this pool (buy+sell)
3
in base units
"1279361"
in quote units
"35200000"
This endpoint is used to list known runes.
Filter by rune name as %NAME%. "SUPER" will match "MYSUPERRUNE", for example.
"SUPER"
Specify true for pairs with liquidity, false for pairs without, or omit for all pairs.
Will return only featured runes.
Number of runes to return.
Page number for pagination.
Order of the results.
"ASC"
List of matched runes
0
50
0
123
block number : transaction number in that block
"3009048:5"
"MAXDECIMALSRUNESOBIG"
"MAXDECIMALSRUNESOBIG"
A single UTF8 character, including emoji
"¤"
3009048
A tx position in a block
5
0
Total amount of runes minted
"1000000000"
"1000000000"
Total amount of runes in circulation (max_supply - burned)
"1000000000"
Number of subunits in a super unit of runes
8
true
1727898475
"81972d23a9abaa1c6f0d96b7bccd9af905ff8a4f44ac50f2a62366f92e5a8efb"
"3caae66d4c38c46f56f12571fc518bbb36ce3ec03a4e3b6c3ed44dbee9fa9630"
a raw transaction hex
"7b22656469637473223a5b5d2c2265746368696e67223a7b2264697669736962696c697479223a33382c227072656d696e65223a313030303030303030302c2272756e65223a224d4158444543494d414c5352554e45534f424947222c2273706163657273223a302c2273796d626f6c223a6e756c6c2c227465726d73223a6e756c6c2c22747572626f223a747275657d2c226d696e74223a6e756c6c2c22706f696e746572223a317d"
false
This endpoint is used to get a trading pair.
"BTC"
"MYLOVELYRUNE"
Success
"BTC"
"Bitcoin"
"B"
8
"21000000000"
"21000000000"
"BTC"
"Bitcoin"
"B"
8
"21000000000"
"21000000000"
"1279361"
"35200000"
base_amount / quote_amount
"3634548.2954545454545454545"
2
"tb1pptp2yfl3xjvltfxwwvqnsspe60uyc0a24d90ymas4qxl8xs8rxss94quj9"
"2.751373537258053043668E-7"
"7.51373537258053043668"
"0.0170889585035029197178120051"
"62110.64"
in USD
"17088958.50"
in USD
"17088958.50"
in USD
"43725.89"
number of finalized swaps in this pool (buy+sell)
3
in base units
"1279361"
in quote units
"35200000"