Whitepaper

Gained

An onchain fee-routing platform built for tokens launched on Robinhood Chain.

Document v1Robinhood Chain
01

Overview

Gained is an onchain fee-routing platform built for tokens launched on Robinhood Chain.

Gained allows token creators to choose where their token-generated fees are directed. The destination can be an onchain wallet, treasury, multisig, community address, creator, contributor, or an integrated social or payment destination.

LaunchTradeGenerate FeesRouteDestination

Gained provides the infrastructure that connects token activity with the destination selected by the creator.

02

The Gained Protocol

Token activity can generate a continuous stream of fees.

Gained turns that stream into a configurable payment flow. Instead of treating generated fees as something that must remain attached to the wallet that launched a token, Gained allows the creator to define a destination for those fees.

A token can therefore be configured around a specific recipient from the beginning. That recipient can be:

  • A personal wallet
  • A project treasury
  • A DAO
  • A multisig
  • A community wallet
  • A contributor
  • A creator
  • A protocol
  • A social account
  • A payment account
  • Another supported destination

Gained acts as the routing layer connecting the token's fee flow to that destination.

03

Launch on pons

Gained is designed to work with tokens launched through pons on Robinhood Chain. The launch process remains simple. A creator provides the token information, selects a fee destination, and launches through the supported launch infrastructure.

The Gained interface can provide:

  • Token name
  • Token artwork
  • Description
  • Website
  • Social links
  • Fee destination
  • Destination address or account

The defining configuration is the Fee Destination.

Once established, applicable token-generated fees can be processed according to that destination.

04

Fee Destinations

Gained is designed around flexible destinations rather than a single recipient model.

Wallets

Fees can be directed to a supported onchain wallet. This can be a personal wallet or any other address designated by the creator.

Project Treasuries

Projects can direct generated fees toward their treasury. This provides a direct onchain funding mechanism tied to token activity.

DAOs

A DAO can designate its treasury or controlled address as the fee destination.

Multisigs

Teams and organizations can route fees to a multisignature wallet.

Communities

A community can designate a shared wallet for receiving generated fees.

Contributors

Fees can be directed toward a specific contributor or collaborator.

Creators

A token can designate a creator's supported wallet or integrated account as its destination.

Protocols

Fees can be routed toward another compatible protocol or contract address.

Social Destinations

Where integrations are supported, Gained can connect fee flows to social identities and creator accounts.

Payment Destinations

Gained can support integrated payment systems where available. This can allow generated token fees to move from onchain activity into an established payment destination rather than requiring the recipient to manually manage a blockchain wallet.

Custom Destinations

Creators can specify another supported destination directly. The destination can be an onchain address or an integrated account supported by Gained.

05

The Core Flow

Gained reduces the entire process to a simple sequence.

  • 1. Launch — Create a token through the supported pons infrastructure.
  • 2. Choose — Select where the generated fees should go.
  • 3. Trade — The token becomes available for trading.
  • 4. Generate — Applicable trading activity produces fees.
  • 5. Route — Gained processes the applicable fee flow.
  • 6. Receive — The configured destination receives the routed amount.
  • 7. Verify — The distribution can be verified through the underlying blockchain transaction where applicable.
06

Fee Routing

The Gained routing layer connects a token's fee stream to its configured destination. The fundamental relationship is:

TokenTrading ActivityGenerated FeesGainedConfigured Destination

Gained does not need the destination to be the same wallet that launched the token. This separation allows creators to establish different relationships between token activity and fee recipients.

07

Destination Types

Gained treats a destination as more than simply a wallet address. A destination can represent:

  • Who receives the value
  • Where the value should be allocated

For example:

  • Token → Creator
  • Token → Treasury
  • Token → DAO
  • Token → Multisig
  • Token → Community
  • Token → Contributor
  • Token → Protocol
  • Token → X Money
  • Token → fomo
  • Token → Custom Wallet

This makes the fee destination an important part of a token's configuration.

08

Social and Payment Routing

Crypto-native users increasingly operate across wallets, social platforms, and payment systems. Gained is designed to connect these environments.

Where a supported integration exists, a creator can associate a social or payment identity with the fee destination. For example, an eligible token can have its fee destination configured toward an integrated X Money account or a fomo-linked destination.

The underlying payment mechanism depends on the integration. Gained provides the routing interface and infrastructure that connects the generated fee flow to the supported destination.

09

Onchain Settlement

Blockchain transactions remain the underlying settlement mechanism for onchain destinations.

Gained organizes the resulting activity into a clear fee lifecycle:

GeneratedProcessedRoutedReceived

This allows users to distinguish between fees produced by token activity and funds that have actually been distributed.

10

Fee Accounting

Gained provides accounting around the fee-routing process.

For each supported token, the platform can display:

  • Total fees generated
  • Fees processed
  • Fees routed
  • Current destination
  • Distribution history
  • Transaction history

For each destination, the platform can display:

  • Associated tokens
  • Incoming distributions
  • Total routed amount
  • Distribution history
  • Transaction records

This creates a transparent view of the relationship between token activity and fee distribution.

11

Dashboard

Gained provides a unified interface for monitoring fee activity.

Token Dashboard

A token page can display token information, fee destination, fee activity, routed amount, distribution history, and relevant transactions.

Destination Dashboard

A destination page can display connected tokens, incoming fees, historical distributions, and transaction records.

Activity Feed

The platform can provide a real-time view of token launches, fee activity, routing events, distributions, and new destinations.

12

Transparency

Gained is designed around verifiable fee flows. The platform distinguishes between three stages.

Generated

Fees produced through applicable token activity.

Processed

Fees recognized and processed by the routing infrastructure.

Distributed

Funds successfully routed toward the configured destination.

Where the underlying transaction is onchain, users can independently verify the resulting transfer.

13

Non-Custodial Architecture

Gained is designed as routing infrastructure rather than a custodial wallet. Users interact with the underlying blockchain and supported services through their own wallets and authorized accounts where required.

The blockchain remains responsible for onchain settlement. Gained provides the interface, routing logic, indexing, accounting, and destination coordination surrounding that settlement.

Gained does not represent ownership of the destination's assets.

14

Destination Configuration

A fee destination is associated with the token according to the permissions of the underlying launch infrastructure. The destination may be an onchain address or an integrated external destination.

Where destination changes are technically supported, the applicable permissions and authorization requirements determine whether and how a destination can be changed.

Gained does not override the underlying smart-contract permissions.

15

Protocol Fees

Gained can charge a defined protocol fee on successfully processed fee flows. The applicable fee is disclosed through the platform. The remaining amount is routed toward the configured destination.

Protocol fees and distributions are accounted for separately so that users can distinguish between:

  • Token-generated fees
  • Gained protocol fees
  • Destination distributions
16

Use Cases

Creator Monetization

A creator can designate an eligible wallet or integrated payment destination to receive fees generated by a token.

Project Funding

A project can direct its token fee flow toward its treasury.

Community Funding

A community can use a shared destination to receive and manage generated fees.

Contributor Payments

Tokens can route fees toward designated contributors or collaborators.

DAO Treasury

A DAO can designate its treasury or multisig as the destination.

Protocol Funding

A token can direct fees toward another protocol or infrastructure address.

Social Payments

Where integrations are available, token-generated fees can be connected to supported social and payment identities.

17

Security Principles

Gained is built around several core principles.

Explicit Destinations

The destination is clearly defined rather than hidden within an internal accounting system.

Onchain Verification

Onchain distributions can be independently verified through their transactions.

Non-Custodial Interaction

Users retain control of their wallets where wallet authorization is required.

Permission Awareness

Gained operates within the permissions of the underlying launch and smart-contract infrastructure.

Transparent Accounting

Generated, processed, and distributed amounts are separated within the platform.

Destination Accuracy

Users are responsible for verifying destination addresses and connected accounts before establishing a fee route.

18

Risk Considerations

Gained does not guarantee the price, liquidity, performance, or success of any token launched through or associated with the platform. Token markets can be highly volatile and assets may lose some or all of their value.

Blockchain networks, smart contracts, wallets, bridges, RPC providers, indexing systems, social platforms, payment providers, and other third-party infrastructure can experience downtime, errors, delays, or other failures.

Integrated social and payment destinations may be subject to the rules, availability, and technical limitations of their respective providers.

Fee amounts depend on applicable token activity and underlying protocol mechanics. Users are responsible for verifying token information, destination addresses, connected accounts, and transactions before interacting with the platform.

Gained provides infrastructure for fee routing and does not constitute investment, financial, tax, or legal advice.

19

Conclusion

Gained is a fee-routing layer for tokens launched on Robinhood Chain. It gives creators control over where their token-generated fees go.

The destination can be a wallet, treasury, DAO, multisig, community, contributor, protocol, creator, social account, payment account, or another supported destination.

Launch on ponsChoose a destinationGenerate feesGained routes themThe destination receives them

Gained turns token-generated fees into programmable payment flows that can move toward the destination chosen by the creator.

Note

This page is a web rendering of the Gained whitepaper. The meaning of the document has not been altered.

Back to homepage