ZERΘ MΛXX

Building q-safe proof systems, signatures & agent tools · ZKΘ ∈ 𝔽ₚ
Built B20SCAN on @base & @twothirdsfun on @inconetwork & @fermah_atlas

[ZERΘ MΛXX @0maxxdev]

@snwdnnn This is preIPO, not token

[ZERΘ MΛXX @0maxxdev]

@deepsundar @Polymarket This is IPO, not token

[ZERΘ MΛXX @0maxxdev]

In July, Utexo's CTO gave a window for USDT on Bitcoin: end of summer to mid-September. Careful to call it realistic, not committed.

That window has passed. No consumer launch.

If that's all you were watching for, nothing happened. It's the wrong thing to watch - because a B2B rollout has no launch day. It has an accumulation of places the thing can appear. And over exactly those weeks, three got nailed down.

→ Tether's own Wallet Development Kit now ships a Lightning module for RGB assets, built by Utexo. Teaching a Lightning node to carry RGB used to be every wallet team's problem. Now it's done once and inherited.

→ UniSat is named as the next launch partner - a million weekly actives. Here's the strange part: their users live on Ordinals and Runes, where every asset is publicly inspectable. They're about to meet one that isn't. Fastest education in client-side validation ever, or a lot of confused support tickets.

→ Solv, with $2B in reserves, for atomic BTC↔USDT swaps and yield on native rails. No wrappers, no bridges.

That last one changes the character of the thing. A rail that only moves money is a rail. Once it swaps assets and pays yield, you have the beginnings of finance on Bitcoin that doesn't route through someone else's chain.

Three doors, three separate bets: on developers, on a borrowed audience, on balance sheets. None of them needs an announcement to be judged - each is checkable on its own.

Field note №11, built as a horizontal walk through all three:

https://t.co/X50xze66vb

One sour note in the record: Utexo's X account was briefly accessed without authorisation this month. They do not and will never promote tokens. Anticipation is exactly what phishing likes.

cc @utexocom

[ZERΘ MΛXX @0maxxdev]

A field in a real Primus attestation was committed with SHA256 instead of revealed. I recovered it in 0.66 seconds.

The attestation is an OKX BTC-USDT ticker, produced by the official zkTLS Playground and signed by the production attestor. Three fields were resolved out of the response. Two were revealed as strings. The third went through SHA256.

The committed one was the last traded price. A blind sweep of every price from 0.0 to 200000.0 at one decimal is two million candidates. It landed on guess 775,305, not even halfway through the range.

Then the part that actually matters. The two fields published in the clear beside it were the bid and the ask: 77530.4 and 77530.5. Search outward from the midpoint and the answer arrives in three guesses. Not three seconds. Three hashes. The neighbours gave away the secret.

This is not a break in SHA256 and it is not specific to zkTLS. It is the oldest property of commitments: a hash hides exactly as much as the value had to begin with. For a price it costs nothing, prices are public anyway. But the operation does not know what kind of number you handed it, and neither does the field name.

Chapter 04 runs the search in your browser, measures your own machine's rate, and uses it to price the rest:

A credit score, 3 milliseconds.
A date of birth in the last century, 153 milliseconds.
An account balance to the cent under 100k, 42 seconds.
A 16 byte random salt, longer than the universe has existed.

That last row is the fix, and the page runs it too: the same sweep against a salted commitment, two million guesses, nothing. Commit to the value with a salt, keep the salt, publish it when you reveal.

One boundary I want to state plainly. I have not checked whether any Primus documentation promises confidentiality for this operation, and the page does not claim it does. What is shown is mechanical: a hash, its preimage, and a stopwatch.

Selective disclosure is the feature that invites you to hide a number. If the value matters, salt it. If you cannot, reveal it and know that you did.

https://t.co/FYzHWqbqDw

Community work, not affiliated with @primus_labs.

[ZERΘ MΛXX @0maxxdev]

This is actually a fun experiment. I’m less interested in one lucky run and more in whether Jev can keep making good calls over time when every decision is public

[Raul Rivas @raulrivas99]

Can AI beat the S&P 500?

I built PnL Bench to find out, starting with Jev.

- 503 stocks.
- 10 picks.
- $10k budget.
- Hourly market-session reviews. Public decisions.

More prediction models and trading strategies coming soon.

Who wins: Jev or the S&P 500?
Link below

[ZERΘ MΛXX @0maxxdev]

Just a respectful suggestion to the @ritualfnd team after reading through the tokenomics.

I like a lot about the $RITUAL design, but I think the 0.5% launch allocation for the existing community deserves another look.

The 13.5% reserved for future network incentives is meant for future participation, so it doesn’t really reward the people who were already here early.

Personally, I think moving 1.5% from that bucket to the launch community allocation would create a much better balance - 2% for the current community at launch, with no change to total supply and no additional dilution.

Early Infernet operators, builders and long-time community members supported Ritual before mainnet, before liquidity, and before there was any certainty the network would succeed.

Future incentives are important, of course. I just think the people who helped Ritual get to this point should receive a more meaningful share at launch as well.

If the allocations aren’t completely final yet, I hope the team will at least consider it.

[ZERΘ MΛXX @0maxxdev]

@AlbertMacGloan Listing on CEX?

[ZERΘ MΛXX @0maxxdev]

Looks like @Apple is already quietly preparing for the post-quantum world. Instead of replacing the old cryptography overnight, they’re combining it with ML-DSA. That’s probably what the real PQC transition will look like - gradual, hybrid, and mostly invisible to users.

[Danno Ferrin @shemnon]

Turns out Apple's reference image crypto is a hybrid RSA-3072 and ML-DSA-87 signature.

The -87 ML-DSA signature is in the strongest security category for a standardized Post-Quantum DSA. About as strong as a 512-bit ECC signature, if we ignore the whole quantum computer thing.

[ZERΘ MΛXX @0maxxdev]

@SarthakCt 2% is something that can restore the faith and love of the community

[ZERΘ MΛXX @0maxxdev]

@fydbullish @ritualfnd Real heroes are not born, they become

[ZERΘ MΛXX @0maxxdev]

@ADHAMSROUR19 @ritualnet Thank you, friend, for raising the topic. Many people are afraid to express it for fear of losing their role. 2% I think is a good idea that will be very positively perceived by the community

[ZERΘ MΛXX @0maxxdev]

@hypercars10000 @RobinhoodCrypto Here for the special trailer edit 🏎️ Now I just need a Hypercar parked in my wallet. Would love a WL spot!

Wallet: 0x771388495F34d21C5574FeFc04cd1D5811E00aDa

[ZERΘ MΛXX @0maxxdev]

@InfoTanoy @ritualnet @ritualfnd @joshsimenhoff @0xMadScientist @Jez_Cryptoz It's just the use of free labour, not the tokenomics of a strong project

[ZERΘ MΛXX @0maxxdev]

@SarthakCt Absolutely, I see only enthusiastic shouts about Tokenomics, no one will say an extra word. But what will they say if they don't get anything?

[ZERΘ MΛXX @0maxxdev]

@biennyqt @ritualnet @ritualfnd For fun bro, for fun

[ZERΘ MΛXX @0maxxdev]

@rifal19988 @joshsimenhoff @cryptooflashh @dunken9718 @0xMadScientist @ritualfnd Few people will get anything, haha

[ZERΘ MΛXX @0maxxdev]

Got my ticket for early access to Bread wallet on Miden mainnet 🍞

Self-custodial, with privacy baked in.

https://t.co/fsNZLrPv7v

[ZERΘ MΛXX @0maxxdev]

@biennyqt @ritualnet @ritualfnd Well, they're apparently collecting the reaction of the community, and since you're posting joyful posts, they'll leave it like that

[ZERΘ MΛXX @0maxxdev]

@prmakk @ritualnet @ritualfnd There was such a Shardeum project, Ritual began to remind me of it