HISS fee routing
userWhere $HISS creator fees go: Bankr claim into the Bankr wallet, chain-verified import, the HISS-token-side provider split, and the WETH-side treasury path.
The $HISS token trades in a Doppler-initialized WETH/HISS pool on Robinhood Chain, and its creator fees accrue to the launching Bankr account. The fee beneficiary is the Bankr wallet — the same wallet that created the flagship vault and operates the treasury. This page explains what happens to a fee claim, step by step, with no fee-beneficiary transfer and no router contract involved in the current mode.
$HISS trading fees (Doppler pool, WETH/HISS)
└─ Bankr claim → Bankr wallet 0x403bad53f39a74154a1c9a86852e443738328761
├─ WETH side → treasury operations (0% to providers by policy)
└─ HISS side → chain-verified import (dedupe by claim tx)
└─ epoch plan (deterministic, keccak plan hash)
├─ 30% provider pool → eligible vault creators (gated funding)
└─ 70% treasury-retained in the Bankr walletStep by step
- Claim. The operator claims accrued creator fees through Bankr (
bankr fees). The claim pays two assets into the Bankr wallet in one transaction: WETH and HISS. - Import. HISS imports the claim by transaction hash, verifying it on-chain first: receipt status must be success, and the amounts are decoded from the ERC-20 Transfer logs into the Bankr wallet. Claims are deduplicated by tx hash, so an import can never be counted twice. If chain logs are unavailable, recorded Bankr dashboard numbers can be imported behind an explicit source label — the artifact always says where its numbers came from.
- WETH side — treasury operations. 0% of the WETH side goes to providers, by policy. The first claim's WETH was swapped to USDG and funded the flagship HISS Vault.
- HISS side — the provider split. HISS can route a configurable portion of the claimed HISS-token side to eligible vault providers. The current policy is 30% provider / 70% treasury, computed in base units with bigint math. See provider rewards for eligibility, epochs, and gating.
- Receipts. Every step leaves an artifact: the claims file records tx hash, block, amounts, and amount source; each epoch records its plan hash and any transfer receipts. The status page and API render these artifacts unmodified.
Copy rules
Provider rewards are operational incentives, not yield or a performance claim. Surfaces describing fee routing avoid income-product vocabulary; the banned list lives in @hiss/core and is enforced by tests.