VRE

Trust is a resource. VRE is how you earn it. On-chain proof of who won. @solana | @colosseum |

[VRE @voutcomeengine]

On-chain proof of who won on @solana.

Every raffle asks you to trust the backend.
VRE closes that gap.

Commit → replay from tx sig → MATCH / OK

Building something that picks winners?
https://t.co/X7NbkTwtAx

@OnSwig @multisig @worldnetwork @metaplex
#Solana #Colosseum

[VRE @voutcomeengine]

@NanoCommando 100%! I have Mac and steamdeck, could I play on them?

[VRE @voutcomeengine]

Thanks fam 🙏 Yeah, VRE is part of the Frontier Hackathon.

The program I submitted is small and frozen on purpose. I don't touch it so it stays stable for judging. It's live on devnet: commit the rules and participant list on-chain, resolve, and anyone can replay and verify the result from a tx signature. API, npm SDK and an embeddable widget are all there.

Since submission I've kept building on separate isolated programs, without touching the judged one, and actively testing on devnet. Optimized small draws, added medium and large-scale ones, and pushed it to 100k+ participants. Right now I'm adding randomness nobody can manipulate, and starting VRE Civic as a separate product, verifiable voting for elections and governance.

Honestly I'm not stopping at the hackathon. I genuinely love this and want to take it all the way. Let's connect on DM 🤝

P.S. https://t.co/u5nDnf20ue - you can touch hackathon partner api with ready-to-check cases
https://t.co/p7J7HmpGe5 - showcase for judges

[VRE @voutcomeengine]

Whatever the @colosseum results turn out to be, working on randomness strengthening for VRE.

The old way: the operator picks a "random" seed. It's replay-verifiable, but the operator could in theory grind it to favor a winner. Fine for low-stakes, not for real money.

The new way: randomness comes from future Solana blocks hash no one can predict or fake, bound to a frozen participant list. Still fully replayable by anyone, but now nobody can steer the result, not even us.

Verifiable was never enough on its own. It has to be unmanipulable too.

#solana #security #hackathon #colosseum #building #VRE #randomness

[VRE @voutcomeengine]

@1z11_ no, u can't.

[VRE @voutcomeengine]

What's the most broken part of DAO governance?

[VRE @voutcomeengine]

Building toward verifiable voting, genuinely curious where it hurts most.

[VRE @voutcomeengine]

@Cryptnow_io Good job! Love it.

[VRE @voutcomeengine]

Same view on tokens honestly. VRE's whole pitch is "don't trust me, replay it yourself." The second you bolt a speculative token onto a trust product, you undercut the one thing you're selling. A token only earns its place if there's something that actually can't be verified deterministically, and our core is the opposite of that. So it's revenue and real usage first, token never just to raise.

[VRE @voutcomeengine]

Same view on tokens honestly. VRE's whole pitch is "don't trust me, replay it yourself." The second you bolt a speculative token onto a trust product, you undercut the one thing you're selling. A token only earns its place if there's something that actually can't be verified deterministically, and our core is the opposite of that. So it's revenue and real usage first, token never just to raise.

[VRE @voutcomeengine]

@Cryptnow_io GM!

[VRE @voutcomeengine]

@JelleoLabs @maskaradio @Copenhagen0x @toly really fast! good job!🫶

[VRE @voutcomeengine]

Ran my own Solana program through @JelleoLabs' security scanner. 24 findings, went through each one, and they all checked out (canonical bumps from init, PDAs validated by derivation + owner + discriminator). Fast, readable, genuinely good tool.

@toly called it "super helpful" and I get why. Credit to @Copenhagen0x for building it right.

The bigger point: we're entering an era where a lot of code is written by AI agents. Security can't be a one-time audit anymore. It has to be continuous and verifiable, so anyone can check that the code was actually checked.

That's the same principle VRE is built on, just one layer down. Jelleo makes the code provable, VRE makes the outcome provable. Trust you can check beats trust you assume.

#solana #colosseum #hackathon #security

[VRE @voutcomeengine]

Use it @colosseum fellas!

[Jelleo @JelleoLabs]

https://t.co/6MF4ISUSaY

[VRE @voutcomeengine]

@uzproof @solana_sailor My Codex think just like this!

[VRE @voutcomeengine]

@chrislutzxy Verifiable Outcome Engine.
Commit the rules and participant list on-chain before the draw. Resolve. Get a Solana signature. Anyone can replay and verify the result independently from public RPC — no trust required.

[VRE @voutcomeengine]

@maskaradio

[VRE @voutcomeengine]

GM sir. Genuinely curious what felt most broken to you in DAO voting. The counting itself, the lack of an audit trail, not being able to verify your own vote landed? Trying to pin down where the trust actually breaks.

Asking because I've started sketching the architecture for exactly this with VRE (verifiable outcomes) Civic. Commit the rules and the final encrypted ballot set first, then anyone can replay the count and verify the result. Voting is the long game but the core is there.

What's your read on where it breaks? It would be very helpful. Thanks.