RIVO

Solana launchpad in the works. Building post-quantum provenance, locked liquidity, shielded payments and more token pairings. Pre-launch. No token yet.

[RIVO @RivoTechnology]

Building RIVO, a Solana launchpad focused on verifiable rules and clearer information.

What we’re building:
• Post-quantum creator verification
• A 5% cap on recorded creator-wallet buys
• Locked liquidity after graduation
• Trader alerts—you decide whether to follow a trade

Still in development. No token.
Security audit and legal review before launch.

Proof before promises. Follow along as we build.

[RIVO @RivoTechnology]

5. Legal review: planned
Terms, disclosures, and how the platform works.
6. Launch 🚀 when it's built and reviewers outside the team have had their say.

Next from us: the review scope and build attestations (commit, tag, toolchain), both planned, not shipped.

[RIVO @RivoTechnology]

Late night at RIVO. The roadmap is live: https://t.co/C6FAahLXOn

We're two full-time college students building this, with one more person helping. We're shipping updates as fast as we can.

[RIVO @RivoTechnology]

3. Shielded payments: in design. Privacy features will be tested end to end and reviewed before launch.
4. Independent review: planned. Our hash-based post-quantum provenance code will go to reviewers outside the team. Reviewers aren't chosen yet.

[RIVO @RivoTechnology]

@Algorand Ghosts we can't help with. The quantum part we're working on 🎃

[Algorand @Algorand]

Ghosts can’t break your encryption. Quantum computers might.

Happy Halloween from the network with 3.5M post-quantum transactions and counting… 🎃

[RIVO @RivoTechnology]

Agreed on both. Attestations will name the source commit, tag and toolchain so anyone can rebuild and compare hashes. Matching hashes prove the build, not the review, which is why the review scope gets published separately, covering what was checked and by whom. The roadmap is just the first thing we're putting out. Wrote that wrong in the previous reply my apologies.

[RIVO @RivoTechnology]

RIVO build update 🛠️

Since our last post:
• Closed 5 findings from our latest security review
• Full local test suite passing, including 45/45 post-quantum tests

Next up: independent reproducible builds, so anyone can verify the code we ship.

What we're building toward:
• Post-quantum creator provenance (in development)
• Bonding curve to locked liquidity (in development)
• Shielded payments (in research)
• Expanded token pairings (on the roadmap)

Still pre-launch. Nothing is deployed to mainnet and nothing has been audited. No RIVO token exists.

[RIVO @RivoTechnology]

@__spekulator__ Yes. Both the review scope and the build attestations will be public, so you can see what was checked and verify the hashes yourself. We're starting with the public roadmap.

[RIVO @RivoTechnology]

@__spekulator__ Public roadmap should be done tomorrow!

[RIVO @RivoTechnology]

Exactly right, and it's why reproducible builds come next. We're lining up independent reviewers for the builds, and separately we're in talks with one of the original designers of the hash-based signature schemes our post-quantum work builds on, to review our construction. We'll share who's reviewing and where the hashes get posted before anything ships.

[RIVO @RivoTechnology]

@__spekulator__ Yes we believe in transparency and are working to show yall what we are building towards.

[RIVO @RivoTechnology]

RIVO update 🛠️

• Creator fees on curve trades are working in local testing.
• An optional email sign-up wallet is in design, with non-custodial control as a core requirement.
• Security review is ongoing ahead of launch.
• Multi-chain support is on the roadmap after launch.

Still in development. No token yet. Heads down, building carefully.

[RIVO @RivoTechnology]

RIVO build update: another round of offline security self-tests today on our post-quantum creator verification work. Building carefully, testing as we go, and taking the time to get it right.

Still in development. No token launched.

[RIVO @RivoTechnology]

Heads down on RIVO 🔧

Today: fork tests, deeper security reviews, and clearer evidence behind our post-quantum creator verification.

We’re building a Solana launchpad with verification at its core. Shielded payments and expanded pairing options are still in design.

Shipping waits until the audit gate clears.

[RIVO @RivoTechnology]

@__spekulator__ Yes, the preview already shows that exact breakdown: the base fee per signature, the priority fee based on the requested compute limit × CU price, and the total. I’m taking your feedback seriously—just clarifying that this is already implemented.

[RIVO @RivoTechnology]

The deeper I got into quantum cryptography, the more I wanted to turn that research into something useful.

I’m building a Solana launchpad with a long-term goal: give creators a place to launch and give users clearer, verifiable rules around what they’re buying into.

That starts with the fundamentals:
🔒 Permanently locked liquidity after graduation
⚖️ Capped developer buys and fee limits enforced on-chain
🛡️ A roadmap for post-quantum creator identity that links a launch to its creator

The launchpad is the foundation. From there, I want to build out stronger creator verification and explore private payments where they make sense.

Those pieces are at different stages. Core development and fork testing are underway. PQ identity is moving toward a fork-only prototype and security review. Private payments remain research-only.

And to be clear: PQ creator identity would protect specific proofs of authorship. It would not make Solana or every token on the platform “quantum-proof.”

My commitment goes beyond getting a site online. It means maintaining the product, testing assumptions, addressing security findings, and sharing progress—including what needs more work. I want people to be able to look back through these updates and see a product taking shape.

No token launch until the site is live. I’m here to build something that earns a reason to stick around.

[RIVO @RivoTechnology]

Yep—Solana handles this differently from EVM. The network fee is a base fee, currently 5,000 lamports per signature, plus any priority fee. That priority fee is based on the compute limit requested, even if the transaction uses less.

Our planned preview will show the exact network fee before signing, with a clear notice: “Charged even if the transaction is processed but fails.” A transaction that never lands isn’t charged.

[RIVO @RivoTechnology]

Yes—the proposed preview accounts for fees on failed transactions too. If a transaction fails, its state changes are rolled back, but the network fee (base plus priority) is still charged. We show that separately as “paid even if this transaction fails,” so a reverted state diff doesn’t suggest that failure costs nothing.

That’s the proposed behavior in the draft spec, still under security review and not live yet.

[RIVO @RivoTechnology]

Today on RIVO: putting our post-quantum signature design under independent scrutiny. 🔍

We’re reaching out to cryptographers to review the hash-based signatures behind our proposed post-quantum creator verification. We’re asking them to assess:

• How our designs compare with published standards
• What security margin they actually provide
• Whether either design has weaknesses that rule it out

We want a clear go or no-go on both candidates—including our preferred design. Solana on-chain feasibility and implementation will be reviewed separately.

No reviewers are confirmed yet. Security fixes continue, and new features remain paused pending the required reviews.

Proof before promises. 🛠️