XRPL Commons Selects 13 Startups for First Online Aquarium Cohort

What XRPL Commons announced for Aquarium Cohort 9

XRPL Commons announced 13 startups for its first fully online Aquarium cohort on October 13, 2026. The nine-week program supports XRP Ledger businesses through coaching and investor introductions. Completing it makes teams eligible for milestone-based grants, while product performance, customer adoption and individual funding awards remain separate questions.

Confirmed: the selection and program structure appear in XRPL Commons’ dated announcement and Bitcoin.com’s independent coverage. The official Aquarium page describes an intake aimed at teams with a working minimum viable product, or MVP, and at least one full-time founder. That starting point matters: the program is intended to help existing projects progress toward a market, rather than simply teach participants how to create a wallet.

Analysis: the most useful way to follow this cohort is to track the distance between a working demonstration and a dependable customer service. For a prospective partner, the announcement creates a manageable set of companies to examine. It does not make those companies interchangeable. A merchant checkout, an automated spending tool and a lending application need different evidence before a customer should rely on them.

Section sources[1][2][3]

Online delivery changes access; grant eligibility has conditions

The official program description offers live workshops, technical and business coaching, and XRPL expert mentorship. The October announcement places an online investor Demo Day midway through the program. Bitcoin.com corroborates that structure and reports that graduates become eligible for funding linked to milestones. No individual award amount is established by these program descriptions.

Analysis: remote delivery can remove the need to relocate for participation, but a founder still needs time to attend sessions and implement feedback. The Aquarium page explicitly expects active engagement. A sensible preparation exercise is to nominate one product problem for technical coaching and one customer problem for business coaching, then give each a demonstrable completion condition. “Improve onboarding” is vague; showing that a new user can recover from an interrupted setup is reviewable.

For founders budgeting their next release, eligibility should remain outside committed cash until an actual award and its conditions are documented. A hypothetical team might finish the program with a functioning prototype and an investor conversation but no grant agreement. Its next payroll or infrastructure commitment would still need another funding basis. Conversely, a documented milestone award would be a meaningful financing event without proving that customers will continue using the product.

Section sources[3][1][2]

XRPay and AgntPymt illustrate different payment questions

XRPL Commons identifies XRPay with merchant payments using Ripple USD, or RLUSD, and AgntPymt with authorization and governance for AI spending. Bitcoin.com independently reports those respective roles. These are descriptions of the teams’ focus, not product certifications or results from tests conducted for this article.

Analysis: consider a hypothetical merchant evaluating an XRPL checkout. The useful demonstration would connect an order to a payment, show how the seller knows the correct amount arrived, and explain what happens when the buyer pays late or asks for a refund. A successful transfer alone leaves the merchant’s operational question unfinished. The customer needs a receipt, the seller needs an order status, and support staff need a way to reconcile the two without guessing.

An AI purchasing tool needs a different demonstration. Ask the team to show an allowed purchase, a purchase outside the authorized budget, and the resulting record available to the business owner. Then change the authorization and repeat the scenario. Those are proposed acceptance exercises, not claims about AgntPymt’s current controls. Their value is that a prospective buyer can specify the behavior it requires before treating an automated payment as a completed business process.

Section sources[1][2]

Straid and Laguna put borrowing and credit evidence in focus

The selection announcement describes Straid as an application for borrowing RLUSD against XRP holdings and Laguna as infrastructure for tokenized private credit. Bitcoin.com corroborates those project categories. The shared word “credit” should not obscure the different questions a borrower and a prospective lending participant would ask.

Analysis: a borrower considering an XRP-backed loan could request a worked example covering collateral deposit, interest accrual, repayment and collateral return. The example should state its assumed prices and fees rather than borrow a market quote that will soon expire. A second scenario should explain what happens if the collateral value falls or repayment is late. This is a proposed review method; no borrowing rate, collateral threshold or liquidation behavior for Straid is established here.

For a tokenized private-credit product, the corresponding request is to identify the borrower obligation and connect it to the investor’s actual rights. A prospective participant could ask who receives repayments, which documents govern distributions and who handles a missed payment. Token records and contractual obligations should be reconciled in the explanation. Unresolved: the cohort announcement does not supply enough product terms to assess either venture’s credit quality, investor protections or suitability for a particular user.

Section sources[1][2]

A practical evidence ladder for the Aquarium’s nine weeks

Analysis: the program’s stated coaching and demonstration format suggests a useful reporting sequence: describe the starting product, document a specific change, show that change working, then establish whether someone outside the team continues to use it. Each step answers a different question. A launch announcement establishes availability; a recorded customer exercise can reveal whether the product completes the intended task; repeat usage can support a narrower claim about ongoing usefulness.

For example, a hypothetical payout startup could begin with a manual customer-support step that delays completion. Its milestone might be to make the failure state visible and allow an authorized operator to resolve it. A credible report would identify the release, explain the starting problem and show the corrected sequence using appropriately protected customer information. Counting new features would be less informative than showing that the original operational problem was resolved.

This framework also gives grant milestones a concrete role. A milestone can establish that an agreed deliverable was accepted, while a separate customer record establishes market use. An investor demonstration provides an opportunity to inspect progress, but it is not itself a signed investment. None of these proposed reporting steps is a claim about the Aquarium’s unpublished assessment rules. They are practical questions readers can use when evaluating subsequent announcements from cohort members.

Section sources[3][1][2]

What the cohort means for XRP readers and prospective users

Analysis: for XRP ecosystem readers, the selection offers a more specific development signal than an undifferentiated count of projects. It identifies teams working on customer problems and an organized support period. The potential benefit is a clearer route from development to useful applications. The limitation is that coaching can improve a team’s opportunities without resolving demand, operating costs or execution problems.

Prospective users should therefore match the next evidence request to their exposure. A merchant needs transaction and refund handling; a business authorizing automated purchases needs spending controls and records; a borrower needs understandable repayment and collateral terms. An investor needs a separate assessment of financing and product risk. Treating all these readers as one “adoption” audience would hide the very differences that determine whether a product is useful to them.

Unresolved: the selected teams’ eventual grant awards, commercial results and contribution to XRP demand are not established by admission to the program. The announcement does not justify a price forecast. The next useful disclosures would be product releases with clear scope, demonstrations that can be examined, named customer evidence where disclosure is permitted, and documented funding decisions. Those records would let readers update their view of individual companies without turning the whole cohort into a single success or failure claim.