First-party data, pulled not pushed
Pyth’s design choice is its identity: prices come first-party from the firms that MAKE markets — exchanges, trading firms — rather than from third-party reporters, and consumers pull updates on demand instead of paying for a constant push. That makes it cheap where blockspace is dear and fast where it counts, which is why it spread through the ecosystems where speed is the product.
The dependency is the value case
An oracle is load-bearing plumbing: lending markets liquidate on its numbers, perp venues mark to it, structured products settle on it. The bet in PYTH is the same shape as GRT’s — a work-adjacent token over a metered service — with a sharper edge: oracle failures are not degraded service, they are cascading liquidations. Criticality cuts both ways; it justifies the dependency premium and concentrates the tail.
Token mechanics, standard issue
Around that core sits a conventional modern launch: governance rights, staking for data integrity, and a large supply vesting on the usual calendar. The plumbing story is exceptional; the float story is not.
Reading it
Adoption breadth — how many protocols mark against it — is the fundamental; unlocks are the supply tape; funding reads the leverage. And any oracle incident anywhere reprices the whole category at once, PYTH included.