proof layer
source proof
The thesis keeps market signals and fact signals attached, so a reader can inspect what supported the argument before the market moved.
@evapredicts campaign · protocol proof
public predictions need protocol proof, not louder claims.
Prediction markets already expose prices. Eva Protocol makes the argument around a price inspectable: cited signals, version history, author identity, and an anchorable record readers can revisit after the timeline moves on.
Campaign hypothesis
proof framing should attract infra-minded builders faster than another prediction-product launch post.
The best early audience for Eva is not chasing a new odds page. They care whether public forecasts can be audited later. This page turns that trust-infrastructure thesis into a measurable campaign path.
proof layer
revision proof
Material updates append to the same record instead of replacing the old take with a cleaner version after the fact.
proof layer
author proof
X identity plus wallet identity gives every thesis a record that can survive outside one social feed or screenshot thread.
proof layer
anchor proof
The protocol layer gives public market theses a timestamped artifact path before execution, trading, or reputation claims expand.
target audience
people who need forecasts to become accountable records.
prediction-market operators who want higher-quality distribution than odds screenshots
Send them to the proof record first, then measure whether they inspect records or start a thesis.
agent builders whose forecast outputs need receipts before users delegate decisions
Send them to the proof record first, then measure whether they inspect records or start a thesis.
crypto analysts turning broad market calls into reputation-bearing public records
Send them to the proof record first, then measure whether they inspect records or start a thesis.
protocol and infra buyers who care about trust rails more than another consumer feed
Send them to the proof record first, then measure whether they inspect records or start a thesis.
conversion routes
do not send every reader to the same proof step.
route
prediction-market operator
Inspect the proof thesis before the protocol pitch. The question is whether the cited sources and revisions make the take easier to trust later.
Read proof recordroute
forecast-agent builder
Open the live agent manifest, then use the MCP quickstart to see the draft-and-anchor boundary agents must respect before distribution.
Open agent manifestroute
crypto analyst
Start with one broad market thesis, attach the evidence, and keep the revision trigger visible instead of burying it in a thread.
Start thesisMetric to watch: which audience route earns the next click: proof-record reads, agent-manifest opens, MCP quickstart clicks, live-thread clicks, compose starts, or @evapredicts follows.
Campaign sequence
one protocol claim, one proof object, one measurable decision.
- Keep approved @evapredicts traffic on this page with utm_campaign=protocol_proof.
- Route the first click into the SpaceX proof record so readers inspect the object before they hear the protocol claim.
- Keep the angle only if the live thread beats softer launch copy on proof-record reads, source-library clicks, compose starts, author-record clicks, or follows.
live @evapredicts thread
make proof the public wedge, then measure the path.
The approved protocol-proof thread is live. This page now routes campaign traffic into the thread, the proof thesis, and audience-specific proof steps without claiming traction before the numbers exist.
public predictions do not need louder confidence.
they need proof objects.
what sources supported the call? what changed? who authored it? where is the record after the feed moves on?
that is the Eva Protocol wedge: market theses with cited signals, visible revisions, author identity, and anchorable evidence.
start here: https://eva.jaack.me/campaigns/protocol-proof?utm_source=x&utm_medium=social&utm_campaign=protocol_proof&utm_content=protocol_proof_post
Metric to watch: sessions with utm_campaign=protocol_proof, proof-record reads, source-library clicks, live-thread clicks, compose starts, author-record clicks, and @evapredicts follow clicks. Do not claim traction until those are measured.