Skip to workspace
Mainnet reads · Testnet actions
Mainnet dataTestnet actions
Install Freighter
Freighter is not installed

Freighter is not installed. Install the browser extension to connect a Stellar wallet. Everything on this workspace reads without one.

This workspace expects Stellar Testnet. Ryntra never receives a key, never signs on your behalf, and a signature is never a submission.

Stellar Hub Map

About Stellar Hub Map

Every module this workspace registers: 13 with a page you can open, 28 registered with the condition each one waits on. Nothing here is a link to something unbuilt. A state word on this page is workspace module maturity — it is not the Capability Registry, and it is never a public claim on its own.

Workspace

Home

  • OverviewAVAILABLEMainnet data · Testnet actionsWhat needs attention, what Stellar is doing, and what this workspace has proven.Mission control for both halves of this workspace: the mainnet network pulse, what each issuer can do to a holding, whatever currently blocks an action, and the transactions this product has actually recorded.
    Exists
    Network pulse, issuer control watch, live attention state, and the two proven testnet lifecycles.
    Missing
    Watched assets and a recent-activity list, both of which need an action store.
    Gate
    Activity — the same store both rows read from.
    Last verified
    2026-08-14
    Open
  • Attention & RecoveryAVAILABLEMainnet data · Testnet actionsEverything that is blocking, degraded or unfinished, each with its exact recovery step.Action required, caution and context, in that order. A wrong wallet network, a source that did not answer, a payment awaiting authorization, a failed transaction, a ledger that did not do what was authorized — each stating what happened, why it matters, what it affects, when it was observed and the one step that fixes it. The Overview panel and this page are the same computation, so they cannot disagree.
    Exists
    Every condition, computed from the wallet state machine, the evidence state of each read, and every stored lifecycle.
    Missing
    Conditions that need a policy to detect, because policy evaluation is not built.
    Gate
    Policies, for the rules a person defines in advance.
    Last verified
    2026-08-14
    Open

Observe

  • NetworkAVAILABLEMainnet · read onlyLedger, protocol version, fees and the reserve, read live.Stellar RPC for the ledger and the endpoint's retention window; Horizon for the base fee and base reserve. Both carry their observation time.
    Exists
    Ledger sequence, protocol version, endpoint health, retention horizon, base fee and base reserve.
    Missing
    Nothing in scope for this module.
    Gate
    None.
    Last verified
    2026-08-14
    Open
  • Assets & RWAAVAILABLEMainnet · read onlyFind an asset by its exact identity and open its passport.Search by CODE:ISSUER, plus a short list of real mainnet assets to start from. A code alone never resolves — many different assets share one.
    Exists
    Exact-identity search and the full Asset Passport over real mainnet assets, including issuer controls, holding requirements and a permanent unknowns rail.
    Missing
    Disambiguation from a bare code, which needs an indexed asset set.
    Gate
    RWA Market — the same index.
    Last verified
    2026-08-14
    Open
  • RWA & tokenized assetsAVAILABLEMainnet · read onlyTokenized treasuries, stablebonds and stablecoins side by side, issuer powers first.A curated set resolved live, not a market — Stellar has no asset index this product reads, so coverage is not claimed. Every row carries what the issuer can do to a holding before it carries supply, because on Stellar that is the fact that decides the outcome. Nothing is ranked and no note says whether an asset is good.
    Exists
    Issuer powers, holder addresses and the issuer's declared domain, read per asset at request time.
    Missing
    Coverage. Four assets is a set; a market needs an index to iterate.
    Gate
    An asset index with a source and a refresh contract.
    Last verified
    2026-08-14
    Open
  • Issuers & AnchorsAVAILABLEMainnet · read onlyThe organisations behind assets, what they can do to a holding, and what they say about themselves.One issuer at a time: account flags enforced by the network, then the issuer's own stellar.toml declaration — which carries no more authority than a company's website and is labelled that way. When the two disagree, the flags are the fact and the document is a claim.
    Exists
    Account flags, home domain, the organisation block and per-asset currency declarations, grouped by issuer.
    Missing
    Anchor deposit and withdrawal state, which is a SEP-6 or SEP-24 read this adapter does not perform, and coverage beyond the curated set.
    Gate
    One anchor integration for the anchor half; an asset index for coverage.
    Last verified
    2026-08-14
    Open
  • Markets & LiquidityPREVIEWMainnet · read onlyWhat a routing provider says a trade would do, normalized — never a route Ryntra produced.Soroswap is integrated as the SCF Integration List building block for liquidity. Its public health endpoint answers today and reports which venues its indexer covers. Everything that carries a price — quotes, pools, prices, the protocol and asset lists — answers 403 without an API key, so the quote path runs for real and renders its real refusal with the exact next step. A quote with no minimum output is refused outright.
    Exists
    The adapter, the normalized RoutePlan, the comparison, and live provider health across four indexed venues.
    Missing
    The API key that unlocks quotes, pools and prices, and a second provider to disagree with the first.
    Gate
    Register at api.soroswap.finance, generate a key, set SOROSWAP_API_KEY. No agent may create that account.
    Last verified
    2026-08-14
    Open
  • Payments & FlowsPLANNEDMainnet · read onlyWhere value actually moves on Stellar, by corridor and by asset.Payment volume, path-payment corridors and anchor flows, read from the ledger rather than from a provider's marketing. Aggregate only — this is market structure, never a person's transactions.
    Exists
    Nothing. Every figure here is an aggregation the read adapter does not perform.
    Missing
    A ledger aggregation source with a stated method, and the vocabulary that keeps holder addresses from being described as people.
    Gate
    An aggregation source whose method can be published beside its numbers.
    Last verified
    Never — nothing to verify yet.
  • DeFi & YieldGATEDMainnet · read onlyWhere an asset is used in a protocol, and what that exposes a holder to.Protocol use is a risk fact before it is an opportunity: a token deposited into a lending market inherits that market's oracle and its liquidation rules. Read and explain, never recommend or promise a yield.
    Exists
    Nothing. The Passport reserves a protocol-use section and it renders as unknown.
    Missing
    Protocol reads, which on Soroban need contract-level resolution the adapter declares out of scope.
    Gate
    Soroban contract reads, and one protocol with a stable public interface.
    Last verified
    Never — nothing to verify yet.
  • EcosystemPLANNEDWorkspaceWho is building on Stellar, and which of them this workspace can actually read.A map of the ecosystem is only useful if it says which entries Ryntra has integrated, which it has merely read about, and which it has not verified at all. Anything else is a logo wall.
    Exists
    The distinction itself, enforced elsewhere: the capability registry already separates a verified integration from a named one.
    Missing
    The surface, and a maintenance contract — an ecosystem list nobody re-reads is wrong within a quarter.
    Gate
    A source with a refresh date, so entries can go stale rather than silently rot.
    Last verified
    Never — nothing to verify yet.
  • ProvidersAVAILABLEMainnet · read onlyEvery external source this workspace depends on, and whether it answered.Stellar RPC, Horizon, Soroswap and each issuer domain, with what it is for, what it answered and what breaks without it. `Gated` is its own state and not a failure: a provider that is reachable and needs a credential this deployment does not hold is not an outage, and reporting it as one sends somebody looking for a problem that does not exist.
    Exists
    Live state for every source that builds a page here, with the exact recovery step where there is one.
    Missing
    Retained history. This is the last read rather than a record, and it says so rather than implying a trend.
    Gate
    Somewhere to retain observations — the same retention question Activity answered for actions.
    Last verified
    2026-08-14
    Open

Move

  • SendTESTNET VERIFIEDTestnet · user-signedSend an exact testnet payment, authorize it, sign it in your own wallet, and check what the ledger did.The whole lifecycle on one screen. A fingerprint is taken before the bytes leave, Freighter signs, the signed transaction is compared field by field against what was authorized, and only bytes that matched can be submitted — the submit function takes the cleared verdict rather than an XDR, so nothing else can reach the network. Then the ledger is read back independently, expected is compared against actual, and the result is a receipt whose every hash can be recomputed. Testnet only; Ryntra holds no key and no signed transaction reaches a Ryntra server.
    Exists
    The complete eight-stage lifecycle for XLM, proven by an owner-signed testnet payment that reconciled MATCHED and by a preflight that refused a doomed one before any signature.
    Missing
    Issued assets, which need destination trustline and issuer-authorization preflight before a build is honest.
    Gate
    The Move slice — issued-asset preflight, then Swap & Path Payment.
    Last verified
    2026-08-13
    Open
  • Swap & Path PaymentGATEDTestnet · user-signedStrict-send and strict-receive paths with every hop disclosed.Delivering a local-currency token is not a bank payout; offchain settlement needs an anchor. Gated on route evidence and issued-asset support.
    Exists
    The lifecycle underneath it — build, authorize, compare, submit, reconcile, receipt — is proven and asset-agnostic.
    Missing
    Route evidence to disclose, and the strict-send/strict-receive operations themselves.
    Gate
    Markets & Liquidity, so a path can be shown before it is signed.
    Last verified
    Never — nothing to verify yet.
  • CCTP BridgeGATEDMainnet · separate release gateMove a stablecoin between chains through its issuer rather than a wrapper.A burn on one chain and a mint on another, attested by the issuer — which is a different risk shape from a bridge that holds your asset. Ryntra would show the attestation and the boundary, never operate a bridge.
    Exists
    Nothing on Stellar. The lifecycle and reconciliation kernel are shared and already proven on another network.
    Missing
    Everything specific to this: the route, and first a live read confirming the protocol supports this chain pair at all.
    Gate
    Verified provider support for the exact chain pair, read from the provider's own live source — never assumed from an announcement.
    Last verified
    Never — nothing to verify yet.
  • On / Off-RampGATEDMainnet · separate release gateWhere onchain conversion ends and an anchor's responsibility begins.Ryntra does not become an anchor. It shows the provider, quote, KYC state, the exact boundary and the recovery path. Gated on an anchor integration.
    Exists
    The boundary language, which is the part most products get wrong.
    Missing
    An anchor: SEP-6 or SEP-24 deposit and withdraw, and the KYC state that comes with it.
    Gate
    One anchor integration with published terms.
    Last verified
    Never — nothing to verify yet.
  • Request PaymentPLANNEDTestnet · verificationAsk for an exact amount, with the trustline and memo already correct.Most failed Stellar payments fail for two avoidable reasons — no trustline, or a missing memo. A request that carries both turns them into the sender's preflight rather than the recipient's support ticket.
    Exists
    Both checks: destination account, trustline and authorization are already read by the Send preflight.
    Missing
    A shareable request, and somewhere for it to live between two people.
    Gate
    Somewhere to persist a request, which is the same store Activity needs.
    Last verified
    Never — nothing to verify yet.

Treasury

  • Treasury StrategyPLANNEDMainnet · read onlyIssuer concentration, duration, liquidity and oracle-freshness limits.The policy kernel that evaluates this already exists and is proven on another network. Stellar-specific rules need the asset facts to be indexed first.
    Exists
    The Guard policy kernel, with deterministic evaluation and reason codes.
    Missing
    Stellar rules to evaluate, and a portfolio to evaluate them against.
    Gate
    Stellar policy evaluation, then a connected account.
    Last verified
    Never — nothing to verify yet.
  • RWA AllocationPLANNEDMainnet · read onlyCurrent versus target exposure, by issuer, duration and liquidity.Read and plan only; it proposes and never executes. Needs a connected wallet to have a portfolio to measure.
    Exists
    Per-asset facts — issuer, model, liquidity state — resolved by the Passport.
    Missing
    Holdings, and a target to compare them against.
    Gate
    Account balance reads, then Treasury Strategy.
    Last verified
    Never — nothing to verify yet.
  • PayoutsGATEDTestnet · verificationPay one recipient repeatedly, against a policy, with a receipt each time.The payout kernel — hashing, schemas, principal registry, daily outflow ledger — exists and is source-verified on another network. Nothing about it is Stellar-specific except the settlement leg.
    Exists
    The kernel, its schemas and its golden vectors.
    Missing
    The Stellar settlement leg and its own live proof; the kernel has never moved value.
    Gate
    Recipients and Approvers, then a separately authorized live payout.
    Last verified
    Never — nothing to verify yet.
  • Batch DisbursementPLANNEDTestnet · verificationMany payments, one authorization, and one honest report of what settled.The hard part is not the sending — it is that a batch settles partially, and a surface that reports a batch as one success or one failure is lying about the middle case.
    Exists
    Per-transaction reconciliation, which is what a partial batch report is built from.
    Missing
    The batch itself, and the partial-settlement report.
    Gate
    Payouts.
    Last verified
    Never — nothing to verify yet.
  • RebalancePLANNEDMainnet · separate release gateMove an allocation back to target, with the expected effects stated first.A proposal, priced and disclosed, that a human authorizes step by step. It never executes a plan as one action, because a plan that half-executes needs each leg to be recoverable on its own.
    Exists
    Expected-versus-actual reconciliation per leg.
    Missing
    The allocation to rebalance and the routes to rebalance through.
    Gate
    RWA Allocation and Swap & Path Payment.
    Last verified
    Never — nothing to verify yet.
  • Collateral & YieldGATEDMainnet · separate release gateWhat a position earns, and what would liquidate it.Stated in that order deliberately. Yield is the reason a person opens the panel; the liquidation threshold and the oracle behind it are why they should keep it open.
    Exists
    Nothing.
    Missing
    Protocol positions, oracle reads and the liquidation model.
    Gate
    DeFi & Yield.
    Last verified
    Never — nothing to verify yet.

Control

  • Strategies & RiskPLANNEDWorkspaceThe rules you decided in advance, versioned, and what each one would have blocked.A StrategySpec is immutable once approved. Changing your mind creates a new version rather than editing the old one, so a receipt can name the exact rules that were in force.
    Exists
    The StrategySpec contract and its immutability, in the shared kernel.
    Missing
    Stellar-specific rules, and the surface to author them.
    Gate
    Stellar policy evaluation.
    Last verified
    Never — nothing to verify yet.
  • PoliciesIN BUILDWorkspaceReadable rules, immutable versions, and what each one blocks.Shared with the existing Guard policy kernel rather than reimplemented. Registered here so the Stellar surface names it rather than hiding it. Until it exists, every receipt this workspace produces carries policyVersion: null with a reason naming this module — a field absent from a receipt reads as a field removed from one.
    Exists
    The kernel, and the honest null on every Stellar receipt.
    Missing
    Stellar rules over issuer controls, trustline state, oracle freshness, concentration and size.
    Gate
    The registered policy row — the one every Stellar receipt already points at.
    Last verified
    Never — nothing to verify yet.
  • RecipientsPLANNEDTestnet · verificationAddresses you have paid before, with what is known about each one.An address book is a risk control, not a convenience: the check that matters is whether this destination exists, accepts the asset, and is the one you used last time.
    Exists
    Destination existence, trustline and authorization reads, performed per payment.
    Missing
    Anywhere to keep a recipient between payments.
    Gate
    Persistence.
    Last verified
    Never — nothing to verify yet.
  • ApproversPLANNEDWorkspaceWho may authorize what, and above which amount a second person is required.Roles that imply nothing about legal authority — the principal registry deliberately names function rather than title. Two people approving is a control; two people named on a screen is decoration.
    Exists
    The principal registry with its five non-implying roles.
    Missing
    The Stellar binding, and the surface.
    Gate
    Payouts.
    Last verified
    Never — nothing to verify yet.
  • Trustlines & PermissionsGATEDMainnet · read onlyWhat your account has authorized, and what can still be revoked.A passport states what an asset demands of any account. This states what one account has actually granted, which needs that account connected.
    Exists
    Trustline and authorization reads for any account, and the reserve each trustline locks.
    Missing
    The connected-account view, and the change operations themselves.
    Gate
    Account reads for the connected wallet.
    Last verified
    Never — nothing to verify yet.
  • AgentsGATEDMainnet · separate release gateWhat a program may do on your behalf, and what it may never do.An agent surface is only honest if the boundary is structural: no key, a scoped mandate, an explicit human authorization for anything that settles, and a kill switch that is not a preference. Registered here to name that boundary, not to promise the feature.
    Exists
    The boundary itself: authorization is a separate artifact from a signature, and this product has no key to delegate.
    Missing
    Everything else, and it is gated behind the security review the shared canon requires.
    Gate
    The registered automation gates — a bounded mandate is never a feature decision alone.
    Last verified
    Never — nothing to verify yet.
  • SettingsAVAILABLEWorkspaceYour workspace, your wallet, and what this product structurally cannot do.Workspace depth and appearance, the connected wallet and its network, which sources answer, and the boundaries — stated in one place a person can point at rather than scattered across pages.
    Exists
    Workspace and wallet state, the network and source table, and the construction boundaries.
    Missing
    Notification delivery, which needs somewhere to deliver to.
    Gate
    A notification channel with an opt-in contract.
    Last verified
    2026-08-14
    Open

Prove

  • ActivityAVAILABLETestnet · verificationEvery action this workspace prepared, and what became of it.Draft, blocked, awaiting authorization, authorized, signed, submitted, confirmed, reconciliation required, reconciled, failed — with the intent, the authorization, what the ledger recorded, whether expected matched actual, and the receipt behind each row. Kept in your browser and nowhere else: Ryntra has no account for this workspace and keeps no server-side record of anyone using it.
    Exists
    The whole lifecycle, recorded in place so one payment is one row, with a delete control and a stated cap.
    Missing
    Per-record permalinks, and export.
    Gate
    Reports, for a period with its evidence intact.
    Last verified
    2026-08-14
    Open
  • ReceiptsTESTNET VERIFIEDTestnet · verificationRecompute a receipt's hashes and read the ledger again, without trusting Ryntra.Expected versus actual, bound to one transaction. Every hash on a receipt is recomputed in your browser from the receipt's own contents, and then the ledger is read again to see whether it still agrees — a document can be internally perfect and still describe a transaction that never happened. A bare transaction hash works here too, checked against the envelope the ledger stores rather than against an authorization.
    Exists
    Hash recomputation, an independent ledger re-read, reconciliation from the ledger's own envelope, and a fee-bump refusal by name.
    Missing
    Per-receipt permalinks and a public route that needs no workspace.
    Gate
    Verifier — the same checks on a public URL.
    Last verified
    2026-08-13
    Open
  • VerifierIN BUILDTestnet · verificationAnyone can check a Ryntra receipt without a wallet and without an account.The same recomputation the Receipts page performs, on a public route: VERIFIED, NOT FOUND, TAMPERED, SUPERSEDED, or the one that matters most — transaction confirmed, authorization not proven. A receipt only a customer can verify is a customer-service tool, not evidence.
    Exists
    All of the checking. It runs today inside the workspace.
    Missing
    The public route, and per-receipt permalinks to hand somebody.
    Gate
    A public surface decision — this is the one that carries a claim.
    Last verified
    Never — nothing to verify yet.
  • JournalPLANNEDWorkspaceWhat was decided, what happened, and what that changes next time.The review half of the loop. A decision compared against its outcome produces at most a proposed next version — never an automatic change to the rules.
    Exists
    The ReviewRecord contract in the shared kernel.
    Missing
    Outcomes to review, which is Activity again.
    Gate
    Activity.
    Last verified
    Never — nothing to verify yet.
  • ReportsPLANNEDWorkspaceA period, exported, with every figure still pointing at its evidence.An export that drops provenance is a spreadsheet of numbers somebody else has to trust. Each line keeps its transaction, its receipt and its observation time.
    Exists
    Provenance on every value, which is the property an export must not lose.
    Missing
    The period, the export and the format.
    Gate
    Activity.
    Last verified
    Never — nothing to verify yet.

Build

  • DevelopersAVAILABLEWorkspaceThe read adapter, its sources and its declared boundaries.What the adapter reads, from which source, and exactly what it refuses to do.
    Exists
    Every read, its source, and the refusals — including the client that rejects sendTransaction by name.
    Missing
    A published contract with support and rate limits.
    Gate
    Data API.
    Last verified
    2026-08-14
    Open
  • Data APIPLANNEDMainnet · read onlyThe passport and its evidence as a machine-readable contract.Every read already returns a data / sources / as_of / state envelope, so the shape exists. Publishing it is a separate decision about support and rate limits.
    Exists
    The envelope, enforced by the type system rather than by convention.
    Missing
    Publication: versioning, rate limits, and a support commitment.
    Gate
    A support decision, which is a business commitment rather than an engineering one.
    Last verified
    Never — nothing to verify yet.
  • Guard APIPLANNEDWorkspaceDecision and settlement evidence for programmable money, as an API.The B2B surface over the same Evidence Kernel this workspace uses. Stellar would be one venue behind it, never a separate product.
    Exists
    The kernel, its schemas and its receipt contract, source-verified on another network.
    Missing
    The Stellar binding and the tenant boundary that a shared API requires.
    Gate
    The registered Guard platform work, and a security review before any tenant boundary ships.
    Last verified
    Never — nothing to verify yet.
  • MCPPLANNEDWorkspaceThe same evidence, readable by an assistant that cannot act on it.Read tools only. An assistant may explain, formalize, compare and review; it never supplies a missing fact, decides a policy, authorizes, signs or executes — and a read-only surface is how that boundary stays structural rather than promised.
    Exists
    The boundary, stated in the operating contract and enforced by having no key.
    Missing
    The server, and the scope decision about what an assistant may read.
    Gate
    Guard API.
    Last verified
    Never — nothing to verify yet.
  • SDKPLANNEDWorkspaceThe lifecycle and its receipt, callable from your own code.Publishing a package is a support commitment: a version somebody depends on cannot be quietly changed. Registered here, deliberately unpublished.
    Exists
    The lifecycle, typed and tested, inside this repository.
    Missing
    Packaging, versioning and the support commitment that comes with publication.
    Gate
    Guard API, then an explicit publication decision.
    Last verified
    Never — nothing to verify yet.
  • WebhooksPLANNEDWorkspaceBe told when something settled, without polling for it.Delivery is the easy half. The hard half is that a webhook consumer must be able to verify what it was told, which means the payload carries the same receipt anyone else could check.
    Exists
    The receipt, and independent verification of it.
    Missing
    Delivery, retries, and signing.
    Gate
    Guard API.
    Last verified
    Never — nothing to verify yet.
  • Usage & BillingPLANNEDWorkspaceWhat was used, what it costs, and what stays free regardless.Truth and safety are never behind a paywall: what a person can learn about an asset they hold, and whether an action is blocked, remain free of charge whatever else is metered.
    Exists
    Nothing. There is no paid path in this product.
    Missing
    Everything, and it is gated on evidence that anyone wants to pay before it is built.
    Gate
    The registered monetization gate, which requires retained willingness-to-pay evidence first.
    Last verified
    Never — nothing to verify yet.

What a state word means here

Available
A real page that reads and moves nothing.
Testnet verified
Its lifecycle ran on Stellar Testnet and reconciled, for the one operation named on the card.
Preview
Built enough to open, not proven against a live source.
In build
Active work with a registered task.
Planned
An accepted direction with no active work.
Gated
Blocked on a named condition, stated on the card.

And what an environment word means

Mainnet · read only
Real assets, issuers and ledger state. Moves nothing and needs no wallet.
Testnet · user-signed
Prepares an action you sign in your own wallet, on a network where the assets have no worth.
Testnet · verification
Checks what a testnet action actually did, without signing anything.
Mainnet · separate release gate
Would move real value. No setting in this workspace reaches it.
Workspace
Touches no network — preferences, documentation, this map.