Community Listing Requirements

What Communities Need To Get Listed

The listing process is intentionally lightweight. AquaVaults already has the platform infrastructure — the swapper, fee routing, widget system, and participation layer are all built. Communities do not need to build any of that. They need to provide the information that places them inside it.

There is no custom development required, no technical integration project, and no complex onboarding process to navigate. The setup comes down to three things: basic community information, a registered community treasury wallet, and optional Jupiter referral accounts. Communities can start participating in the ecosystem as soon as those pieces are in place.

Basic Community Information

Communities provide the information that represents them inside the AquaVaults ecosystem. This is how members find and recognize the community in the selector, and how the community presents itself to the broader platform.

Referral Accounts — Optional Routing Enhancement

When users select a community other than AquaVaults and the platform fee is above 0%, routed platform fees direct the community's share toward their registered community treasury wallet. Jupiter referral accounts are an optional additional routing layer — they provide token-specific routing paths that expand coverage and can help communities structure their fee destinations with greater granularity.

A Jupiter referral account is a standard Solana account created through Jupiter's referral system. Once created, a community's referral account address is registered with AquaVaults, and the fee routing system can direct community-eligible portions of platform fees toward it when swaps occur with that community selected.

Community Treasury Wallets

Communities register their treasury wallet addresses as part of the listing configuration. These are the core routing destinations for community-directed platform fees — serving all Solana swap activity not covered by a configured Jupiter referral account, and all EVM swap activity.

These wallets are community-controlled addresses — AquaVaults does not take custody of them. They serve as registered routing destinations within the platform configuration.

Why The Setup Matters

The listing configuration is not just administrative. It is what connects a community to the infrastructure that makes ongoing participation possible.

A properly configured listing allows a community to participate fully in the AquaVaults ecosystem — including community fee routing, custom deep link campaigns, Swap Widget integration, AutoSwap coordination, and Co-op Mining Rig participation tied to community selection and recurring engagement.

The setup is simple because the infrastructure is already built. Communities are not building a new system — they are connecting into one that already exists and is already running. The listing configuration is the handshake between a community and that infrastructure.

Getting those pieces in place from the start gives communities access to the full ecosystem from day one rather than needing to come back and configure things later when they are ready to run their first campaign.

Communities Can Start Small

Nothing about the listing process requires a community to have everything figured out before it starts. A small but active community with a clear identity and engaged members is exactly the kind of community AquaVaults is designed for. The platform does not require large teams, extensive infrastructure, or an established track record of on-chain activity.

A community can list with a basic setup — name, bio, logo, one or two social links, a treasury wallet — and immediately become available for community-directed fee routing when users select them on the platform. They can add Jupiter referral accounts when they want to extend their routing infrastructure with additional token-specific paths. They can introduce the Swap Widget to their community when they want to run a campaign. They can build toward AutoSwap coordination and Rig participation over time as their members become familiar with the platform.

The ecosystem meets communities where they are. The infrastructure scales with their participation — communities do not need to scale their participation to fit the infrastructure.

Joining The Ecosystem

Getting listed is a beginning, not a formality. A community that adds a logo and a name to a selector page has set up a presence. A community that actively directs its members, runs campaigns, coordinates Rig participation, and uses the Swap Widget on their own site has built something much more substantial — a recurring participation structure that strengthens over time through consistent engagement.

The difference between those two outcomes is not a technical configuration. It is whether the community actively organizes around the infrastructure AquaVaults provides, or treats the listing as something passive after setup.

The communities that get the most from the platform are the ones that show up consistently — that give their members recurring reasons to participate, that run campaigns with structure and follow-through, and that use AquaVaults as a layer of their community identity rather than a one-time experiment.

AquaVaults works best when active communities participate consistently over time. That is what the listing is the first step toward.