Account for the full route
The execution design considers fees, royalties, and funding requirements when evaluating a route.
Solana NFT execution
Arby is building a cross-marketplace execution workflow for Solana NFTs—connecting available listings with funded demand, checking route conditions, and keeping a clear record of each outcome.
In development Private operator workflow
Example states, not live marketplace data.
Listing
Marketplace A
Example NFT #024
Asset available
Funded demand
Marketplace B
Example NFT #024
Eligible offer
Route checks
Execution record
MatchMatch an available asset with eligible funded demand.
The workflow
A coordinated process for evaluating an order route before execution and understanding what happened afterward.
Monitor supported listing and offer sources for relevant assets and available demand.
Identify compatible listing-and-offer routes, including whether the demand is funded and the asset is eligible.
Check fees, royalties, funding, and route compatibility before attempting a supported execution path.
Track the observed outcome and reconcile execution records against resulting asset and balance changes.
This describes the intended workflow; live route support depends on venue access and validation.
Execution design
Arby remains in development. Integration access, live route validation, and end-to-end operational readiness are still being established.
The local implementation uses integer-lamport accounting, a narrowly scoped Rust execution guard, receipt verification, and a durable PostgreSQL ledger. These mechanisms do not establish live route support or release readiness.
The underlying strategy evaluates NFT arbitrage routes with an executable exit. Initial acquisitions require a supported paired buy-and-exit transaction; an unsupported composition remains unavailable.
The execution design considers fees, royalties, and funding requirements when evaluating a route.
Supported paths are checked against explicit execution conditions before submission. Atomic composition is a route-specific capability, not a universal guarantee.
Execution records and reconciliation are designed to make resulting fills, asset movements, and balance changes easier to inspect.
Marketplace integrations
Arby is designed around venue-specific integrations that bring listings, funded offers, and execution requirements into a consistent evaluation process. Support is assessed route by route.
In development
Marketplace and AMM routes are part of the local implementation. Live route validation remains.
Integration development
Solana access and route compatibility remain subject to confirmation.
Under evaluation
Native Solana order execution remains unverified.
Independent project. Marketplace references do not imply partnership or endorsement.
Magic Eden access requirements include direct listings, funded offers and MMM pools, with atomic composition where supported and final-message cosigning where required. Each path needs compatible instruction, funding, fee and signing evidence before activation.
Get in touch to discuss Solana integrations, execution compatibility, and the Arby workflow.
A little more context
Arby is a private Solana NFT execution project focused on matching available listings with funded demand across supported marketplace routes. Its intended workflow covers route evaluation, execution, and outcome reconciliation.
Arby is currently in development and is not offered as a public trading service.
Integration work is assessed by marketplace and execution path. The integration section reflects the current project stage; listed venues should not be read as a promise of live support.