HOLDER REWARDS / WITHOUT STAKING

Hold the token.
Share the rewards.

Your holders keep their tokens. You choose the funded reward assets and snapshot schedule. The contract verifies each wallet’s share.

Keep your tokens.

No staking, deposit approval or token lock. Your balance at the snapshot determines your share.

Know the rules.

The assets, schedule and exclusions are permanent. Every holder can inspect the same commitment.

Verify your share.

Claims use proven historical balances. Anyone can relay the transaction; rewards go to the holder.

FROM A POLICY TO A PAYOUT

Here’s how it
reaches your wallet.

A reward policy is one part of the process. Funding and execution need to be in place too.

Read the full mechanics
  1. 01

    Deploy the policy.

    Choose a verified Long or Pons token, reward assets and snapshot schedule. Review the permanent rules before signing.

  2. 02

    Fund the reward assets.

    Send the selected assets to the policy. A separate fee vault and any required conversion modules must be configured before fees can fund it.

  3. 03

    Checkpoint a snapshot.

    Submit authenticated proofs for the latest due snapshot. A configured keeper can handle this; it does not happen just because the policy exists.

  4. 04

    Claim to the holder.

    Rewards go to the proven wallet. Checkpointed claims never expire, including after those tokens have been transferred.

ONE POLICY / YOUR CHOICE OF ASSETS

Something different
to share.

Choose up to four compatible coins, native ETH or tokenized-stock tokens on Robinhood Chain. Each asset is distributed separately, in proportion to eligible snapshot balances.

Selecting an asset does not buy it. The contract pays from its own funded balance and cannot pull unrelated tokens from a wallet.

Supported platforms and funding

Staking rewards are coming in a later release.

Explore the protocol library