Treasury rewards

From activity to holders

The proposed reward model uses a share of creator fees to acquire company-linked tokens and distribute them to eligible S&P 500 holders. Reward companies come from the S&P 500 company list. A company appearing in the catalogue does not mean its token is available.

The distribution contract and automatic operator have been implemented and tested locally, including fee claims, reward purchases and recovery after an interrupted transaction. A candidate Robinhood reward route has also passed a read-only purchase simulation. The new holder token and operator wallet are not connected, and live rewards have not been activated.

Reward funding allocation

Each round starts with a fixed budget in one supported reward token. Funding and publication happen together: the distributor must receive the exact committed amount before a round can open.

The starting reward allocation is 30% of attributable creator fees. The operator can change this percentage for future rounds; an already prepared round keeps its original budget. Zero pauses new rounds while committed allocations remain deliverable. Reward token selection, purchase routes and the operating schedule will be confirmed before activation. The prepared automatic operator can claim attributable creator fees and purchase a configured reward token through a verified route. A manual mode also accepts reward tokens already acquired by the treasury. Gas is paid separately by the wallet submitting the transactions.

Multiple rounds can distribute different company-linked tokens. Each supported reward-token address must be mapped to a company in the current constituent snapshot. The same company may have multiple tokens, each reviewed separately.

Delivery and receipts

The operator can be configured and tested before the holder token launches. After launch, its contract address is added to the local configuration; the engine verifies the creator and discovers the launch contracts automatically. It prepares a holder snapshot and allocation before funding a round. Once the allocation is published, transactions can deliver rewards directly to the committed wallets. Holders do not need to stake, connect to this website or approve a spending allowance to receive them.

Delivery works in batches of up to 50 recipients. Completed payments are skipped on retries. If a reward token blocks one recipient, that payment stays pending while other recipients can be paid. Anyone can relay an existing allocation, but cannot redirect its recipients or change its amounts.

The owner cannot edit a funded allocation or withdraw its committed tokens. Failed or undelivered allocations remain in the contract; this version has no expiry or recovery function for them. Only confirmed receipts appear in the holder report.

Eligibility and amounts

A round uses balances of the configured S&P 500 holder token at one historical block after the configured confirmation delay. The operator reconstructs transfers from deployment, reconciles total supply and checks each historical balance. The snapshot block and hash, eligibility rules and allocation are recorded in a downloadable manifest.

Zero and burn addresses, the holder-token contract and the distributor are excluded by default. Treasury, team, exchange, liquidity-pool and bonding-curve addresses must be reviewed explicitly. A configurable minimum balance is measured in the holder token’s smallest units. These settings are configuration options; the launch policy is still pending.

Holder reward = floor(round budget × eligible holder balance ÷ total eligible balance)

Amounts use integer token units. Any rounding remainder stays with the funding wallet for a later budget. Entitlements smaller than one reward-token unit produce no payment. For example, eligible balances of 70 and 30 split a 10-token budget into 7 and 3 tokens.

This is a balance-at-snapshot rule, not a minimum holding period. It does not look through exchange or pool balances to underlying users. Saving an investing draft does not establish reward eligibility.

The publisher is trusted to attest the snapshot and company-token mapping. The contract verifies the published allocation, not stock backing or the truth of the holder list. Only standard, exact-transfer, non-rebasing reward tokens are supported. Rewards do not provide company shares, dividends or a guaranteed return.