The details, documented.
How the product is funded, how rewards move, and what is connected today.
Current status
Portfolio balances and reward-delivery history come from verified live reads for the connected wallet. Before connection, the app asks you to connect. A failed request displays an error rather than substituting sample data. An empty verified result is shown as empty.
Robinhood mainnet
The application targets Robinhood Chain, an EVM-compatible network with ETH for gas. Official network documentation is the source for these settings.
The public RPC is rate-limited. A production provider endpoint should be configured for reliable service.
The intended reward lifecycle
Pending
A real purchase event has been detected and attributed to an eligible user. Detection alone is not approval or payment.
Confirmed
The merchant has approved the commission. Rebate still waits for settlement before spending the reward funds.
Invested
The conversion succeeded and Stock Tokens were delivered. In the intended live ledger, this status must link to the actual transaction and not merely a submitted request.
Reversals before investment must be recorded. A unique reward identifier prevents the same settlement being processed twice. This merchant purchase lifecycle is not connected today; verified onchain delivery receipts are separate records.
Merchant-funded, explained
The planned rewards model uses a disclosed portion of a settled merchant commission to fund the user reward. Rebate would retain a disclosed share of that commission.
Reward rates, the commission split, rounding, conversion costs, and eligibility must be disclosed for each verified live offer. No live merchant offers, fixed reward rates, or estimated reward amounts are shown today.
AutoRebate and Brand-to-Stock
Allocation preferences use whole-number percentages totaling exactly 100%. They are chosen by you and stored on this device. Saving a preference does not place an order, buy tokens, rebalance a wallet, or activate rewards.
A listed ticker does not guarantee instrument availability. Live support must be checked against the official asset catalog and applicable eligibility requirements before execution.
Brand-to-Stock is conditional on the merchant and instrument being supported. If it is unavailable, the chosen allocation would be the fallback. Changes apply to future rewards and do not rebalance existing holdings. Brand-to-Stock is not active today.
What a Stock Token represents
Robinhood describes its Stock Tokens as tokenised debt securities issued by Robinhood Assets (Jersey) Limited. They provide economic exposure to an underlying security without legal or beneficial rights in the underlying issuer. They are not direct shares.
The app resolves official contract addresses from the RHJ asset catalog. A matching name or ticker alone is not sufficient. Live indicative values apply the asset’s current corporate-action multiplier to the raw underlying bid.
Availability and eligibility depend on issuer terms and jurisdiction. Review Robinhood’s Stock Token documentation and the applicable instrument terms.
Settlement contracts
The configured Rebate settlement contract is 0xc2b1fa4c8888742ac1196710dfcd2db4bc7ae0e4.
The settlement design delivers supported ERC-20 rewards from an authorized operator to a recipient, recording a unique reward ID. It does not mint Robinhood Stock Tokens, obtain merchant commissions, or manufacture investment returns. The operator remains responsible for valid purchase evidence, funding, and eligible recipients.
The settlement console checks ownership, funding, allowance, token precision, and duplicate reward IDs. Exact token approvals and deliveries are separate wallet-confirmed actions. A delivery receipt proves the transfer, not the preceding merchant approval or stock purchase.
Verified history requires a matching mined creation transaction and its exact block, verified against the configured contract address and current deployed code. Older receipts load through bounded pages tied to one confirmed snapshot. The app labels history as partial until every consecutive block range back to deployment has been verified. A failed page clears the accumulated view. This on-demand reader is not a persistent production indexer.
What connects the whole flow
Production purchase-to-portfolio operation requires an active merchant/affiliate or card-linked provider, verified and replay-protected purchase events, a persistent user ledger, settled commission funds, an eligible execution venue, and funded onchain delivery. Those services cannot be supplied by wallet connection alone.
No private keys are needed in the browser build. Wallet actions are presented through the user’s wallet. No user analytics have been added.