Scoped keeper actions
Conversion and distribution are limited by configured contract permissions and approved routes.
Trading fees fund reward assets, distributed to eligible token holders.
Preparing for launch. The token address and first funded reward cycle have not been published.
Launch statusKeep eligible tokens in your own wallet. The standard distribution sends rewards directly, without a staking deposit.
A funded epoch records the reward pool and holder snapshot before payments begin.
These are planned settings. Final fees and reward assets depend on the deployed contracts. A target cycle does not guarantee a payout.
A configured share of token buy and sell fees funds the reward pool.
An operator converts collected fees through approved routes.
Eligible balances at a recorded block determine each allocation.
Proof-checked batches distribute the funded reward asset.
The snapshot reads token balances in eligible wallets. Connecting this site does not enroll you or change your allocation.
Rewards depend on actual fees, conversion costs, and funded epochs. There is no fixed APR or guaranteed return.
Each epoch commits an allocation root. Published snapshots can be compared with the token's transfer history.
How fees are collected, converted, and distributed.
VaultPulse is designed to turn a share of token trading fees into rewards for eligible holders. Each distribution is tied to a holder snapshot and a committed allocation.
Inspect contract configuration
Configured buys and sells route fees to the VaultPulse treasury.
A keeper uses approved assets, adapters, and routers within configured slippage limits.
The Arcus adapter converts fees into pToken vault shares or the configured reward asset.
A holder snapshot determines eligibility and allocation. A Merkle root commits the distribution.
The distributor verifies allocations before sending rewards. A separate Merkle-claim fallback requires its own configuration.
Rewards depend on collected fees, conversion outcomes, and the eligible supply at the snapshot. The target cadence is a schedule, not a guarantee of a funded distribution.
The funded reward pool is allocated in proportion to eligible snapshot balances. Integer rounding can slightly affect individual amounts. The published allocation is the record for each epoch.
Conversion and distribution are limited by configured contract permissions and approved routes.
Distribution batches are checked against the committed allocation for the epoch.
Published addresses link to the explorer, where balances and transactions can be inspected.
Reward assets, conversion routes, and privileged contract roles carry their own risks.
The standard airdrop uses eligible token balances at the snapshot block. No staking deposit or website connection is required. Connecting a wallet lets this page display your balance and recorded payment status.
The snapshot excludes configured protocol addresses, liquidity pools, the owner, and burn addresses. The operator may configure a minimum balance and additional exclusions. The final published snapshot determines the eligible supply for that epoch.
An epoch uses balances at its recorded block. Later purchases or sales do not change that committed allocation. A later snapshot can produce a different allocation.
Fifteen minutes is the target cycle, not a guaranteed payout interval. An epoch needs reward funding, a holder snapshot, and an operator to submit distribution batches. Low activity or paused operations can delay it.
No. It only means the contract has not recorded an airdrop to your wallet for that epoch. You may be waiting for a batch or absent from its allocation. The published snapshot and proofs are needed to establish eligibility.
The owner manages roles and approved routes, and can pause the distributor, close epochs, or recover treasury assets. Operators prepare snapshots and execute conversions and batches. Merkle proofs enforce a committed allocation; they do not independently prove that the operator's snapshot was correct.
Deployment status and the public address registry.
Waiting for final contract addresses.
Inspect an ERC-20 contract on Robinhood Chain.
A successful lookup confirms contract data. It is not a security audit or an endorsement.
Loading contract registry...
Loading configuration...
Verify the final contract address, token controls, and trading-fee destination.
Deploy and configure the treasury, conversion adapter, and distributors.
Check fee collection, conversion, allocation proofs, and a small reward distribution end to end.
Select a wallet to connect to Robinhood Chain.