Question 1

What is XDB?

Accepted Answer

XDB is the native coin of XDB CHAIN. XDB CHAIN is an independently operated open-source Layer 1 blockchain. Although it uses a Stellar-derived technology stack and is compatible with related SDKs, it does not share a ledger or governance with the public Stellar network. On this network, assets other than XDB are generally on-chain credit assets created by an issuing account; holders must first establish a trustline to indicate that they are willing to accept the issuer's asset. XDB, by contrast, is the protocol-native asset and does not require a trustline, so it serves as the unit for both fees and account reserves.

Question 2

What is XDB used for?

Accepted Answer

XDB is used directly to pay transaction operation fees and as the minimum reserve for an account and its on-chain state. For each submitted transaction, the network charges XDB according to its number of operations; creating trustlines, offers, and similar entries increases the ledger entries occupied by an account and therefore raises the reserve that must be retained. A reserve is not a consumptive fee paid to validators: when the corresponding ledger entry is deleted, the related minimum-balance requirement is released. This design gives the creation of persistent on-chain state an opportunity cost, thereby limiting cost-free ledger expansion.

Question 3

What can XDB CHAIN do?

Accepted Answer

At the protocol layer, XDB CHAIN provides capabilities to issue, transfer, and exchange assets. Issuers can create assets directly on the ledger; accounts can transfer assets between each other; and buyers and sellers can match through an on-chain order book or exchange through automated market maker liquidity pools. Path payments allow a payer to pay one asset while a recipient receives another: the system can complete conversion through up to six hops of order-book or liquidity paths, and the entire path either settles or fails. Orders, trades, and settlement results are all recorded on the ledger and can therefore be queried.

Question 4

What is XDB's maximum supply?

Accepted Answer

XDB has a fixed maximum supply of 20 billion coins. At network genesis, 100 billion XDB were created, after which 80 billion were permanently hard-burned during the initial phase; therefore, 100 billion is the genesis issuance amount, not the current maximum supply. If XDB is later transferred to a burn address whose key has permanently become unusable and cannot sign an outbound transfer, it remains as a balance on the ledger but is no longer usable. The network paper calculates total supply as “20 billion maximum supply minus the burn balance.”

Question 5

What is the difference between XDB's total supply and circulating supply?

Accepted Answer

Maximum supply, total supply, and circulating supply are different measures. The network paper defines them as follows: maximum supply is fixed at 20 billion; total supply = maximum supply − burn-address balance; circulating supply = total supply − treasury-address balance. At the observation point of August 10, 2026, the burn balance was approximately 1.264 billion and the treasury balance approximately 1.610 billion, so total supply was approximately 18.736 billion and circulating supply approximately 17.126 billion. The latter two depend on the relevant address balances and can change with new burns or changes in the treasury balance; they must not be confused with the 100 billion in the genesis-ledger field.

Question 6

How does XDB's burn mechanism work?

Accepted Answer

XDB burning centers on making tokens inaccessible: after tokens are transferred to an address whose key has permanently become unusable, no one can sign a transfer out of that address again. The network paper discloses that some branded-coin mechanisms may arrange to repurchase XDB and burn it in this way. Burning does not physically remove the balance from the genesis count of the Stellar-derived ledger, so the ledger's total_coins field may still show the 100 billion created at genesis. To assess available supply, one should examine the burn-address balance and calculate maximum supply minus that balance, rather than treat that field directly as circulating supply.

Question 7

Does XDB CHAIN operate through mining or staking?

Accepted Answer

XDB CHAIN uses the Stellar Consensus Protocol (SCP), an implementation of federated Byzantine fault tolerance, rather than proof of work or proof of stake. Each node independently declares its “quorum slices,” meaning the nodes whose agreement it requires before continuing; the network reaches agreement only when slices of different nodes overlap. This means there are no protocol-level mining rewards or requirements to stake as a validator. The key trade-off prioritizes safety over liveness: when the network is partitioned or participating nodes cannot safely reach agreement, the network is designed to pause ledger closing rather than produce conflicting histories.

Question 8

What are XDB's smallest unit and base transaction fee?

Accepted Answer

A bee is the smallest unit of XDB: 1 bee = 0.0000001 XDB, meaning XDB supports 7 decimal places. The base fee is 100 bees = 0.00001 XDB per operation. The base network fee for a transaction = the number of operations in the transaction × 100 bees; for example, a transaction containing two operations has a base fee of 200 bees. This fee differs from an account reserve: fees enter the network fee pool, while a reserve is the minimum balance an account retains for ledger state it occupies. During network congestion, the protocol fee rules in effect at that time also apply.

Question 9

Why does an XDB account need a minimum reserve?

Accepted Answer

For a new account with no additional ledger entries, the minimum balance is (2 + number of subentries) × base reserve; the base reserve observed by the network paper was 10 XDB, so a new account with no subentries must retain 20 XDB. Trustlines, offers, and data entries all increase the number of subentries and therefore the minimum balance; deleting those entries releases the corresponding reserve. This balance is neither burned nor transferred to an operator, but is XDB that the account cannot spend while maintaining that state.

Question 10

How do on-chain exchanges work on XDB CHAIN?

Accepted Answer

Offers in the on-chain order book are ledger-native limit orders matched according to price-time priority; automated market maker pools use a constant-product mechanism, with two assets in the pool jointly providing liquidity for swaps. The costs and execution conditions differ between the two methods: order books depend on quoted prices and available offers, while liquidity-pool swaps charge a 30-basis-point fee that remains in the pool, and large swaps may be affected by pool depth. Path payments can also combine these liquidity sources, but if any leg cannot meet the conditions, the entire path payment does not partially complete.

Question 11

What should I note before holding a non-native asset on XDB CHAIN?

Accepted Answer

Non-native assets are identified by a specific issuing account. Assets with the same asset code but different issuing accounts represent different assets. An account usually must first establish a trustline to the issuer before it can receive or hold that asset. Therefore, before transferring or exchanging an asset, both its code and issuing account should be verified, along with on-chain control flags set by the issuer, such as authorization, freeze, or clawback. The ledger records asset credit and control status; it does not replace the issuer's fulfillment of off-chain obligations.

Question 12

When is an XDB transaction considered complete?

Accepted Answer

In the sample of August 10, 2026, the paper records ledger-close intervals of approximately 5 to 6 seconds; once a transaction is included in a closed ledger, it is final. This consensus model does not use a confirmation window of “waiting for more blocks to reduce reorganization probability.” This does not mean every submission succeeds immediately: a transaction must still satisfy signature, balance, fee, and protocol rules and be included in a ledger. If SCP nodes cannot safely reach agreement, the network may pause; it resumes processing transactions only after agreement is restored.

XDB CHAIN (XDB) Price