Yore Coprocessor

$YORE is live! verifiable historical-state coprocessor for solana. read the chain's past, and trust the answer with one on-chain proof. ca: DK89Yxx4yPWoMRZxLck3pYUqatbyUNKNj1Hcu1SPpump site: yorecoprocessor.com github: github.com/zaydenholloway… follow: @YoreCoprocessor read the past, trust the proof.

on evm, coprocessors that read the chain's past are a proven category. axiom, herodotus, lagrange, brevis already do it there. solana has nothing like it. no native, trustless way to read its own history. yore fills that gap, built for solana from day one.

every yore answer is paid only if it's verified. a wrong proof or a missed deadline gets the prover's stake slashed. honest work pays. fake work burns.

the first yore demo is one query on devnet: prove a wallet's balance at any past slot, end to end. small loop, but it's the whole engine running.

100% of the dev fee goes to the @pumpfun account linked to this github. no hidden wallet. the same identity that ships the code collects the fees and funds the build. github: github.com/zaydenholloway proof, not promises.

our supply is locked now: app.streamflow.finance/contract/solan…

everything in yore rests on one thing: a commitment to solana's past. yore takes the account state at each slot, hashes it into a single root (a merkle root), and anchors that root on-chain. after that, any historical fact can be proven against the root with a short cryptographic path. no archive to trust, just a hash that has to match.

yore ships in phases, starting small and getting more trustless each step: phase 0: devnet demo, one query, zk proof, full loop. phase 1: more query types and the cheap optimistic path. phase 2: open prover market with staking and slashing on mainnet. phase 3: decentralized archives, so no single provider holds the history. phase 4: open registry and an sdk for any team to plug in. evm already has coprocessors like this. solana doesn't. yore is built for solana from the ground up.

new on the site: a merkle proof inspector. pick any wallet and see the full proof path. the leaf, its sibling hashes (sorted-pair keccak), every fold up the tree, up to the root. then it lands on the exact committed root stored on-chain. they match, hash for hash. no checkmark to trust. you read the cryptography yourself.

once solana can prove its own past, the build surface opens up: airdrops that prove you held the token, with no trusted snapshot. defi oracles with time-weighted prices and retroactive solvency checks. governance and rewards based on how long you held, not just how much. on-chain credit that reads a wallet's real history. game points that turn past actions into verified facts. one primitive, a lot of apps.

Three months in the Incubator > three years figuring it out alone – 3 months of hands-on mentorship from Solana OGs IRL in NYC – Weekly workshops, office hours, and 1:1s – Demo day in front of the ecosystem's top VCs and builders Apply now for Cohort 5.

5/ this is the same principle behind every serious prover market. yore points it at the one thing solana can't do for itself: read its own past.

4/ because checking is cheap and objective, the network can pay only for answers it has verified. provers lock collateral worth at least 10x the max payout, so cheating always loses money.

1/ one idea holds yore together: producing a historical answer is expensive, checking it is cheap.

query the past. build a sample query, point it at any slot, and hit submit. you'll watch the prover loop run end to end: request, compute, prove, verify, settle. go try it: yorecoprocessor.com

yore answers a question two ways and picks the right one per query. zk: the prover proves the math is correct, checked on-chain instantly. best for high-value reads like liquidations and big airdrops. optimistic: the prover posts the answer with a bond. cheap and fast, with a short window for anyone to challenge a lie. by default it stays cheap and upgrades to a zk proof when the stakes are high.

@99_Bollish no, simply because that's how it is.

@YoreCoprocessor So you post tweets like this right after launching your coin to discourage people from buying, so you can bundle more supply yourself or something? 😆

yore runs a historical read in four steps: 1. a program asks a question about the past. 2. a prover computes the answer from solana's history. 3. the prover attaches a proof of correct work. 4. an on-chain verifier checks that proof in one call. producing the answer is heavy. checking it is cheap. that gap is the whole point.