01
use-case deliverables
price feeds that don't get gamed and don't go stale.
primary pieces
Pyth push-style integration
TWAP/EMA derivative feeds
fallback oracle waterfall
deviation + staleness guards
manipulation-resistant indexes
The on-chain feed contracts of oracle systems. push-style integrations, fallback waterfall, deviation guards, TWAP derivatives — written so every revert is obvious from the trace. Price feeds that don't get gamed and don't go stale — but specifically, the smart contracts layer of it.
explicit deliverables for this use-case. additional smart contracts pieces stay in scope.
price feeds that don't get gamed and don't go stale.
contracts that hold the money our trading stacks move.
not what we built (we don't kiss-and-tell client work), but the shapes-of-the-problem we anchor scope against.
The on-chain feed contracts of oracle systems. Specifically: push-style integrations, fallback waterfall, deviation guards, TWAP derivatives — written so every revert is obvious from the trace.
Reference points we look at when scoping: Pyth Lazer, Chainlink price feed waterfall, Redstone push model. We don't copy them; they're shapes-of-the-problem.
oracle systems touches multiple disciplines. We split the work along service lines so each engagement has a single scope. If you need more than one side, we'll scope a second engagement (or a combined one) — but a single smart contracts pod is usually the right starting shape.
Book a call. 30 minutes, no NDA, no slide deck. We tell you what scope of work looks like or refer you elsewhere if we're not the right team.