Cypherpunk Rights | Privacy Crypto Advocate

[The AllFather @t_allfather]

Credit where it is due -> thanks @aszepieniec and the Neptune Cash team for the bounty on the inflation bug report.

It is always a positive sign when important security findings are treated seriously and resolved the right way, and when people can align and collaborate on important matters despite having different views on others.

For anyone interested, $XNT (@NeptunePrivacy) also has a bounty program:
https://t.co/Be00RXGbBt

We welcome all bug hunters to come over and contribute, especially with Leviathan coming.

That aside, we are happy to see people excited about Leviathan.

We will soon open the public testnet, and Leviathan is set to become the world’s first post-quantum private L2, built on top of $XNT (@NeptunePrivacy), opening the door to an entirely new realm of possibilities : DEXs, bridges, and much more.

More importantly, Leviathan stands as a proof to what a small, focused, and highly dedicated team can achieve -> results that can stand alongside those of much larger projects.

For clarity, Leviathan will run on top of XNT (@NeptunePrivacy) only, not NPT.

We are building with a long-term vision here, and this is only the beginning.

[Monero Research Lab (Unofficial) @MoneroResearchL]

Update on beta stressnet: kayabanerve completed a deeper review of the GBP fix, identifying a spec mismatch and implementing a new version that reduces the proof-size increase. Additional issues were opened on the fix repo. After weighing the low risk of further material changes to proof sizes or code paths (alpha stressnet caught issues independently of size), the team reached consensus to proceed with beta stressnet using the latest code/figures. Proposed fork date is May 6 (binaries next week after ofrnxmr's testing); the relevant table in seraphis-migration/monero #317 will be updated immediately after the meeting.

jberman: We have an interesting update to consider for beta stressnet: kayabanerve has taken a deeper pass at the GBP fix and found a mismatch to spec (kayaba would be able to speak to it best). After another pass, a new impl reduced the increase to proof sizes an estimated 25% (need to confirm the exact figures still)
kayabanerve: reduced the increase itself, not reduced the increase to just 25% relative to the old version
jberman: kayaba has also opened further issues on the GBP fix repo: https://t.co/ebRdfpTV3c
kayabanerve: I just wanted to clarify what was reduced, how. I'll let you cite any exact numbers you want, jberman
jberman: got it
jberman: kayabanerve also mentioned that there is still further back and forth to be had with CS on it, but expects it to resolve as expected with these new figures
jberman: That was also the case last week though, and we have new figures today
tevador: Can this table be updated whent he new numbers are known? seraphis-migration/monero #317
jberman: Ya I'll do it right after this meeting
tevador: Thanks
jberman: Didn't get the chance
tevador: So I guess we have also covered agenda item 5
jberman: So w.r.t beta stressnet, there is still an expected risk that there is some material change to proof sizes
jeffro256: 12500 is still probably a decent choice for reference tx size
jberman: It's an open question when exactly this GBP fix will be fully resolved
jberman: So imo, we have virtually similar info as last week, and it probably still makes sense to move forward with beta
jberman: The code is pretty much ready to proceed. We could set a date today
jeffro256: So two choices: 1) go forward with beta, knowing that the proof size on beta may be ~8% bigger than mainnet. 2) wait until we know whether or not proof sizes will change
sgp_: so beta tomorrow? /s
tevador: I'd say go forward
jberman: "knowing that the proof size on beta may be ~8% bigger than mainnet" kayabanerve has already implemented the changes, so we can use the latest
sgp_: my completely uninformed opinion is to go forward
jeffro256: Well done kayabanerve. A lot happened while I was sleeping last night ;)
rucknium: How different will the code paths be if the proof size shrinks 8%? How big is the risk that beta stressnet would materially test the "wrong" code and there would be surprises on mainnet?
jeffro256: I personally vote 1. Even if the proof size does change downwards slightly, the whole point of a stressnet is to stress
tevador: Yeah, 8% more stress testing can't hurt
jberman: Tbc, we can use the latest that implements the latest proof sizes with kayaba's expected fix fully implemented (which I'd advocate for using)
rucknium: jberman: That sounds good to me
jeffro256: So then there's two options for option 1 :): use bigger proof tx sizes (old), or 2) use smaller proof tx sizes (new)
jberman: The risk to a further change in proof size imo is to the up or down, not necessarily certain to be smaller imo
jeffro256: Fair
jberman: rucknium: Imo the code paths are not likely to be materially impacted. Alpha stressnet e.g. caught tons of different issues where a change to proof size wouldn't have made them any less likely caught
rucknium: I am OK with setting a beta stressnet start date today.
jbabb: let's please proceed to stressnet beta even if minor changes may still be necessary
jeffro256: rucknium: If the size / validation is off within a bound of 10%, the stressnet's stressing effects will overcome it either way. The only thing I could think of is some sort of a DoS bug in the new mainnet code that doesn't appear in the beta stressnet, but may be triggered in an edge case we didn't see
jbabb: these https://t.co/ebRdfpTV3c have been forwarded on and are being looked at
jberman: jeffro256 and I have discussed a proposed fork date of 2 weeks from today, May 6th. I'd also like to have ofrnxmr do a quick round of testing, and then we release binaries next week
rucknium: jberman: Sounds good to me
https://t.co/zFqfO36orB

[Cypherpunk Rights | Privacy Crypto Advocate @CypherRights]

As a proud non-user of Pornhub, I’m obviously tracking this for the financial implications 😂

USDT → USDC… wow, groundbreaking. Truly the kind of privacy upgrade that definitely won’t make anyone in D.C. nervous at all.

Honestly, if they ever switch to XMR, Congress might finally pass something unanimously, strictly in the interest of “protecting user privacy,” of course. Funny how fast principles line up when the browser history is on the line 💀

[Our Crypto Talk @ourcryptotalk]

🚨 Pornhub just dropped $USDT for $USDC

The stablecoin war is no longer theoretical.

Team USDC 🔵 Visa · Mastercard · Stripe · Shopify · BlackRock · BNY Mellon · Coinbase · Kraken · Robinhood · PayPal · Pornhub

Team USDT 🟢 Binance · Binance Pay · Tron · Bybit · OKX · HTX · Travala · AMC · Newegg · Gucci · Ferrari · Shift4 · Bitrefill · AirBaltic

USDC has the West. USDT has the rest.

[CyberSatoshi 𓆙 @XBToshi]

Monero is a hated coin.

Governments and CEXs hate it because there's no CEO to subpoena, no VC bags to dump, and absolutely zero way to trace a transaction.

Keep hating it. The math doesn't care. $XMR

[Cypherpunk Rights | Privacy Crypto Advocate @CypherRights]

For those that follow privacy protocols this latest announcement is INSANE! $XNT @NeptunePrivacy was able to win the race in implementing the Miden Protocol. Arguably the most powerful privacy protocol ever invented. 🤯 Do your own diligence on this one!

[Neptune Privacy @NeptunePrivacy]

The privacy race just changed.

Everyone has been watching Miden.

For good reason.

Backed by top-tier teams like a16z, 1kx, Hack VC, and the founders of Polygon Labs, years in the making, and one of the most anticipated launches in the space.

A zk-STARK based system designed for:
• Privacy
• Scalability
• Programmability

Right now, it’s preparing to launch as an L2 settling on Ethereum.

⸻

But there’s a bigger vision behind it.

Long term, the goal is clear:

A dedicated base layer
Purpose-built for zk-STARKs
Privacy-native
Future-proof

That part of the roadmap?

Is expected to take years.

⸻

So we asked a simple question:

What if that base layer already existed?

⸻

Introducing Leviathan.

The world’s first real-world implementation of the Miden protocol…

settled natively on Neptune Privacy.

⸻

This isn’t a fork.
It’s a natural alignment.

This is Miden’s execution layer
running on a base layer designed for it from day one.

⸻

What this unlocks:

• 100% trustless architecture
• Decentralized by default
• zk-rollup execution
• Post-quantum security (STARK-native)
• Fully private state transitions
• Programmable logic at the base layer

⸻

In other words:

The ultimate privacy stack… is now complete.

⸻

This is:

privacy → at the protocol level
privacy → at execution
privacy → at settlement

⸻

And this isn’t theoretical.

It’s already in motion with the following:

• Native wallet (in testing)
• Trustless DEX (in testing)
• Cross-chain bridge (in testing)
• Expanding DeFi stack

⸻

The Miden team built something powerful.

We didn’t want to compete with it.

We built the layer it was meant to run on.

⸻

Where Miden executes.
Neptune settles.

⸻

The next phase of privacy infrastructure isn’t coming.

It’s already here.

[Cypherpunk Rights | Privacy Crypto Advocate @CypherRights]

@koreanjewcrypto Yep looks like they officially put the hammer down, same happened to me yesterday.

[Cypherpunk Rights | Privacy Crypto Advocate @CypherRights]

Very strong day of initial trading on @MEXC for Neptune $XNT, but id be remissed if I didnt mention the irony of sending a private coin to a KYC exchange to deanonymize yourself. 🙃

[John @xmrjon]

73 exchanges delisted $monero in 2025

price went up 120%

think about what that tells you about who actually wants $xmr and why

it's not traders. traders go where the liquidity is. it's people who genuinely need financial privacy and will find a way to get it regardless

that's a different kind of demand. and it doesn't go away because a CEX pulls a listing

[Cypherpunk Rights | Privacy Crypto Advocate @CypherRights]

The market is sure liking this announcement today, up 50% $XNT

[Neptune Privacy @NeptunePrivacy]

$XNT + MEXC

[Nonlogs @nonlogs]

XMR gets delisted everywhere and the volume keeps going up. That is not a dying coin. That is a community that does not need permission.

[Cypherpunk Rights | Privacy Crypto Advocate @CypherRights]

Where's all the clowns at that say Monero will die because of CEX delistings. Get a clue! Long live the king. $XMR

[Mav @XMRVoid]

$XMR ON THE LOOSE

[Cypherpunk Rights | Privacy Crypto Advocate @CypherRights]

Can't say I disagree with Joe here, projects that don't simplify are doomed to fail.

[Joe IO @Joe_IO]

My father uses Venmo.

He would never use a privacy coin wallet that asks him to pick a node or copy a seed into a notepad.

That's the bar.

If a normal person can’t open the app and send money in 30 seconds, we’ve lost.

[Cypherpunk Rights | Privacy Crypto Advocate @CypherRights]

Zano has done a nice job building the past couple of years and the chart actually shows it.

[Zano @zano_project]

Hardfork 6 is one of the most important upgrades in Zano's history.

Gateway Addresses allow CEXes, DEXes, and bridges to integrate $ZANO using standard workflows, no custom infrastructure needed. Same privacy for users. Simple integration for services.

Also shipping:
🔹 Refined decoy selection for stronger privacy
🔹 Improved transaction uniformity

This isn't a small step. It's Zano removing the biggest barrier between privacy and mainstream adoption. 🔒

[Cypherpunk Rights | Privacy Crypto Advocate @CypherRights]

@CryptoMX__ @NeptunePrivacy Nope, keep an eye on the project. They have some even bigger news coming soon too.

[Cypherpunk Rights | Privacy Crypto Advocate @CypherRights]

Very interesting project and approach with @NeptunePrivacy $XNT. At 1 second block times, full privacy, PoW, quantum resistance, and smart contracts, this is now the fastest decentralized privacy chain in existence and soon with a full ecosystem.

This is definitely one to watch as there are also $KAS community devs involved here..

[Neptune Privacy @NeptunePrivacy]

DeFi called.
Said it needs quantum-proof privacy.

We answered.

With a complete solution.
Built for privacy, scalability, and post-quantum cryptography.

Are you ready?

Introducing our L2: Leviathan.

⸻

Block times: <1 second
TPS: >3000
100% zk-STARKs

Private.
Fully programmable.
Public Testnet: Imminent

What’s already in motion:

• $XNT as the store of value (bridged from L1) — complete
• L2 Wallet (Chrome extension) — built, testing
• ETH / Base bridge — built, testing
• Trustless web-based DEX — built, testing

What’s coming next:

• Wrapped stablecoins — in development
• Private AI (TEE) — built, expanding

⸻

Compromises: None
Competitors: None

And we’ve only just scratched the surface.
This is what DeFi was always meant to be.

[Cypherpunk Rights | Privacy Crypto Advocate @CypherRights]

@KaspaTeacher Jerry being Jerry. No one has ever taken him seriously

[Cypherpunk Rights | Privacy Crypto Advocate @CypherRights]

Private and Auditable (aka not private). Nice try.

[Brian Cohen @inthepixels]

JPMorgan Chase trying to compete with Zcash $ZEC

[Cypherpunk Rights | Privacy Crypto Advocate @CypherRights]

Completely agree with this, coins that think making compromises to get on centralized exchanges is going to drive adoption are crazy. $SAL is one of these such coins and one of the reasons true cypherpunks are avoiding it.

[John @xmrjon]

unpopular opinion: Monero adoption won't happen through exchanges

it'll happen when merchants start accepting it

@privcartcom is a Shopify plugin that lets stores take XMR (and BTC, ETH, SOL, stablecoins) with no KYC, no chargebacks, 1% flat fee, non-custodial

you keep your keys. we handle the infrastructure

this is how real adoption works.

[Monero (XMR) @monero]

Serai DEX has successfully been audited by Security Research Labs!

Serai is an innovative DEX that will offer a liquidity-pool-based trading experience for Bitcoin, Ethereum, DAI, and Monero!

[Monero Research Lab (Unofficial) @MoneroResearchL]

Important FCMP++ update: the GBP fix identified and proposed by Cypher Stack has increased FCMP++ tx sizes ~33% and 1-in verification times ~10%. Results and further thoughts are here: https://t.co/fy4OVgmQSH