Add Assetiko assets to decentralized platforms. Add Assetiko assets to decentralized platforms.

Integrate in four steps.

How Assetiko assets fit into network applications.

Assetiko assets are tokenized products with network-specific issuer accounts, public metadata and product-specific documentation. A platform integrating an Assetiko asset should treat its code, network, issuer account, product page, TOML file, supported pair and risk disclosure as one verified information set.

Integrate native Stellar XAUa deliberately.

XAUa is issued natively on Stellar as the asset tuple XAUa:GB2I4YQVCMSKOFRAQYPRNLMCTGMO7OKHQ4YOBSDJ77BG2MYZYNET27YE. It is part of the same Assetiko Gold product and consolidated reserve framework as native XRPL XAUa, but it remains a distinct network asset with its own trustline, authorization, liquidity and transaction mechanics.

Copyconst XAUaStellar = {
  code: "XAUa",
  issuer: "GB2I4YQVCMSKOFRAQYPRNLMCTGMO7OKHQ4YOBSDJ77BG2MYZYNET27YE",
  network: "stellar-public",
  metadata: "https://gold.assetiko.com/.well-known/stellar.toml"
};

const assetId = `${XAUaStellar.code}:${XAUaStellar.issuer}`;
// Verify the exact code and issuer before creating a trustline or quote.

USDV is the primary quote layer.

Assetiko uses USDV as the prime pairing asset for its XRPL product markets. USDV is a permissioned asset. Integrators should expect trust-line authorization, compliance controls, issuer-side rules and possible transfer restrictions to affect routing and execution.

Copyexport const USDV = {
  currency: "USDV",
  issuer: "rfffsukWALJB1PXYk7H8xkR6UJUDT8nMJE",
  role: "prime_quote_asset",
  permissioned: true
};

Use explicit pathfinding for RLUSD or USDC entry routes.

Applications can support users who hold RLUSD or USDC by explicitly routing through USDV into Assetiko assets, where liquidity exists and the user satisfies the required trust-line and compliance conditions.

Copyimport xrpl from "xrpl";

const client = new xrpl.Client("wss://xrplcluster.com");
await client.connect();

const user = "rUSER_RECEIVING_ACCOUNT";

const RLUSD = {
  currency: "RLUSD",
  issuer: "VERIFY_OFFICIAL_RLUSD_ISSUER"
};

const USDV = {
  currency: "USDV",
  issuer: "rfffsukWALJB1PXYk7H8xkR6UJUDT8nMJE"
};

const ASPX = {
  currency: "ASPX",
  issuer: "rE63VEywx9eX2mWgfLWNRBf7JDdKtTS27R"
};

const quote = await client.request({
  command: "ripple_path_find",
  source_account: user,
  destination_account: user,
  destination_amount: {
    currency: ASPX.currency,
    issuer: ASPX.issuer,
    value: "1"
  },
  send_max: {
    currency: RLUSD.currency,
    issuer: RLUSD.issuer,
    value: "100"
  }
});

const route = quote.result.alternatives?.[0];
if (!route) throw new Error("No executable path found");

const payment = {
  TransactionType: "Payment",
  Account: user,
  Destination: user,
  Amount: {
    currency: ASPX.currency,
    issuer: ASPX.issuer,
    value: "1"
  },
  SendMax: route.source_amount,
  Paths: route.paths_computed
};

// Submit with the user's wallet after showing route, issuer and slippage.

Production integrations should test whether their wallet flow supports path-based same-account delivery. Where it does not, use the platform's supported XRPL DEX execution pattern, still preserving the explicit route and issuer checks.

Prepare users before execution.

XRPL issued assets require trust lines. Permissioned assets may also require issuer authorization. Your interface should detect missing trust lines, frozen trust lines, authorization failures and insufficient limits before opening a swap or exposure flow.

Copyconst trustSet = {
  TransactionType: "TrustSet",
  Account: user,
  LimitAmount: {
    currency: "ASPX",
    issuer: "rE63VEywx9eX2mWgfLWNRBf7JDdKtTS27R",
    value: "1000000"
  }
};

Current Assetiko assets.

Use TOML files as the public metadata layer.

Each product subdomain may publish network-specific TOML metadata containing accounts, currency metadata, issuer metadata, token metadata and links. Applications should cache responses, refresh them regularly and treat any network or issuer mismatch as a blocking condition.

Copyconst tomlUrls = {
  ASPX: "https://aspx.assetiko.com/.well-known/xrp-ledger.toml",
  ANDX: "https://andx.assetiko.com/.well-known/xrp-ledger.toml",
  ASEM: "https://asem.assetiko.com/.well-known/xrp-ledger.toml",
  ADEF: "https://adef.assetiko.com/.well-known/xrp-ledger.toml",
  AENG: "https://aeng.assetiko.com/.well-known/xrp-ledger.toml",
  AEMX: "https://aemx.assetiko.com/.well-known/xrp-ledger.toml",
  XAUa_XRPL: "https://gold.assetiko.com/.well-known/xrp-ledger.toml",
  XAUa_STELLAR: "https://gold.assetiko.com/.well-known/stellar.toml",
  NEXF: "https://nexf.assetiko.com/.well-known/xrp-ledger.toml"
};

Show route-aware prices.

Assetiko product pages may display market-derived prices. Developer platforms should show the price implied by the selected network and route, the prime USDV pair, liquidity depth, slippage, issuer, destination amount and fees. Never blend network prices without disclosing the method, and do not present non-USDV entry quotes as official Assetiko prices unless the route explicitly passes through USDV.

Handle failure states clearly.

Before enabling Assetiko assets in production.

• Verify token issuer accounts against product pages and TOML files.
• Verify USDV issuer metadata and permissioning requirements.
• Display product terms, risk disclosures and supported pair information.
• Use route-specific quotes with explicit pathfinding for RLUSD or USDC entry assets.
• Detect missing trust lines, authorization failures, frozen lines and insufficient limits.
• Show slippage, destination amount, source amount, issuer accounts and route hops before signing.
• Cache metadata with a refresh policy and block execution on mismatch.
• Keep logs for route, issuer and transaction diagnostics.