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.
- 02Freeze windowEntries lock before the outcome window so no late information edge exists.
- 03Oracle readsTwo independent price feeds are averaged at the settle timestamp.
- 04Contract settlesWinners split the losing pool pro rata, minus a 3 percent rake.
- 05Rake routesThe rake goes to a JBTC buyback function that cannot be redirected.
Collateral And Settlement.
Users stake any supported asset: USDT, USDC, BTC or JBTC. Amounts convert at an oracle rate into a single pool accounting unit. 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. Two independent feeds are averaged at the settle timestamp.
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 USDT, USDC, BTC and JBTC stakes 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.
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 fee route.
CertiK assessment in progress.