Gather, bind, resolve.
NIPPU is Finnish for a bound bundle of strands. The whole system is built around one idea: many market assets, gathered and bound into a single legible basket — with an honest line between what's declared and what's real.
Two stages you control. Two that require proof.
Input and allocation are configuration — they're always available. Purchase and distribution describe real onchain events, so NIPPU refuses to show them until a verifiable source exists.
- 01Configuration
Input
Select supported assets to include as strands in the basket.
- 02Configuration
Allocation
Assign integer weights that resolve to exactly 100%.
- 03No source
Purchase
A recorded onchain purchase — shown only when a source is connected.
- 04No source
Distribution
A recorded onchain distribution — shown only when a source is connected.
What NIPPU does
- Lets you bundle supported assets into a named basket
- Lets you shape allocation weights visually and precisely
- Enforces that weights always sum to exactly 100%
- Stores baskets locally as clearly-labeled configuration
- Records genuine local events (create, edit) in an activity ledger
- Labels every data surface with its source and freshness
What NIPPU never does
- Invent prices, yields, returns, or performance figures
- Execute trades or make any purchase on your behalf
- Claim baskets are deployed onchain when they are not
- Show fake purchase, distribution, or claim events
- Custody funds or represent a real financial position
- Provide investment advice of any kind
Designed for Robinhood Chain.
NIPPU targets Robinhood Chain (chain ID 4663). When a verified NIPPU contract and data sources are connected, onchain stages and reference pricing will populate automatically — with sources labeled throughout. Until then, the app is transparent about running on local configuration.
- Chain
- Robinhood Chain
- Chain ID
- 4663 (0x1237)
- Native token
- ETH
That's the whole model. Now bundle a basket and watch the strands resolve.
Build a basket