How JuniorShot Is Built.
The settlement path, the oracle stack, the money path and the failure modes. Written so a technical reviewer can evaluate it in one pass.
Settlement Path.
- 01Round opensStakes enter the pool, capped per wallet.
- 02LockStaking closes, then the strike price is read, so no late information edge exists.
- 03Oracle readsMedian of five independent feeds at the settle timestamp.
- 04Contract settlesWinners split the losing pool pro rata, minus a flat public rake of 3 percent, published before you stake.
- 05Rake takenThe rake splits at settlement per the published waterfall: Backstop share, operations share, retained margin. The split is on-chain and changes only with 30 days' notice.
Collateral And Settlement.
Users stake any supported asset. Assets convert at deposit. Every pool settles in a single denomination. Odds are never split. There is exactly one pool per market regardless of which assets were staked. Payouts return in the asset each user staked, and odds are identical for all participants.
Separate pools per currency would fragment liquidity and split odds. One shared unit avoids that, which matters most in long tail markets where depth is thin.
Oracle Stack.
Markets resolve from deterministic, pre-declared sources only. Median of five independent feeds at the settle timestamp. Median beats average, because one corrupted feed cannot drag the result. The three candidate feeds are Chainlink, Pyth and RedStone, subject to availability on the launch chain.
A divergence beyond tolerance or a stale feed triggers a void with full refunds and zero rake. There is no discretionary override.
Asset reference rates, used to convert stakes in all supported assets into pool units, come from the same independent feed discipline. If an asset rate is stale or divergent, new stakes in that asset are blocked rather than settled at a bad rate. Existing pool balances are unaffected because they are already denominated in units.
AI may propose a market. Only a deterministic, pre-declared feed may resolve it. No model, and no human committee, decides an outcome.
Money Path.
Custody Of Bitcoin And Stablecoins
Items marked AT LAUNCH are the intended design and are not final until the launch review and the CertiK final report.
What Happens When Things Break.
| Scenario | Behaviour |
|---|---|
| Oracle feed goes stale | Round voids, full refund, zero rake. |
| Feeds disagree beyond tolerance | Round voids, full refund, zero rake. |
| Pool is empty or one sided | Round voids, stakes returned. |
| Asset rate feed stale or divergent | New stakes in that asset are blocked. Existing pool and settlement are unaffected because the pool is already denominated in units. |
| Keeper fails to settle on time | Settlement retries, incident posted to Status. |
| Emergency | Documented emergency policy, see Governance. |
Where It Runs.
Launching on Hemi, an EVM layer that inherits Bitcoin security via Proof of Proof.
Contracts immutable at deployment. No admin override on settled results or the rake waterfall.
CertiK assessment in progress.