And what will be the difference between Arc and a centralized database? 😏
"Public" is a misleading adjective in Arc’s case because the consensus will remain in the hands of a consortium of pre-approved validators that is not open to the public.
A more accurate description would be "private" (or permissioned) and "open":
Private (permissioned) — because the consensus layer and transaction validation are controlled by a limited, permissioned set of entities. This means the network cannot be considered censorship-resistant: these validators will be subject to regulations and can be compelled to block or reverse transactions if required by their legal jurisdictions.
Open — because the infrastructure is accessible to developers: anyone can deploy smart contracts and build on the platform.
However, the openness at the application layer is undermined by the closed nature of the consensus layer: ultimately, a small group decides which transactions are valid and included in the chain. ☝
🚨 EU is closing the net on privacy 🚨
Peppol & ViDA: by 2026, all EU trade docs go through centralised hubs → tax authorities see it all. No E2E encryption, no mandatory signatures. Orders & logistics next.
Chat Control: client-side scanning kills private messaging. Once in, it can scan anything.
Key dates: Sept 12 2025, Oct 14 2025.
No citizen asked for this. Institutions + states + corporate lobbyists are pushing it.
Cypherpunks warned us in the 90s. By 2030, there will be no private channels left.
Defend encryption. Defend privacy.
Farcaster new meta just got uncovered
1. Build a popular mini-app
2. Let scammers try to build scams around it
3. Warn about the scams
4. Get a lot of engagement from people relaying the alerts
5. Big win 🚀
@jake, we love @qrcoindotfun, thank you for your vigilance 😁
Soon, you'll be able to experience what Web3 should be.
DEXES is a sovereign, privacy-first EDI infrastructure that empowers individuals and companies to send, receive, sign and timestamp business documents — securely and independently.
No third parties. No gatekeepers. Just you, your peers and public blockchain infrastructure.
Powered by Ethereum & OpenPGP
Keeping things private on the Internet is difficult but it does not have to be hard💡
Sign/Verify, Encrypt/Decrypt
These are the four operations users need to perform themselves on their own devices in order to ensure confidentiality and be able to prove or verify the origin and integrity of their electronic documents.
Doing these operations instead of end users is keeping them away from true sovereignty over the security of their communications.
Not your keys, not your coins
Not your keys, not your identity
Not your keys, not your secrets
You do not need to understand the mathematics behind it.
You do not need to be an IT professional.
You need to learn the right abstractions, have access to trustworthy tools and — most importantly — keep asking and verifying proofs.
If a system or a tool is really secure, it should be able to provide you with proofs which can be easily and independently verified by anyone at any time without needing to trust the tool itself 👇
@ethereum (1/6)
Building a decentralized EDI infrastructure on Ethereum called DEXES.
🎯 Goal
To provide a protocol and sovereign tools for individuals and companies to send, receive, sign, timestamp, and verify business documents—such as contracts, electronic invoices, financial reports, and more. Any type of electronic content is supported.
Documents can be stored encrypted (with PQC support coming soon) either on-chain or off-chain. Proofs used for auditing exchanges and verifying document integrity and origin are always stored on-chain.
Long time no see! 👋
Tough weeks ... Time for an update about DEXES 🧵
Been deep into a refactor marathon:
🔥 Dealt with the infamous stack too deep error by restructuring logic and reducing local vars.
🧠 Introduced OnChain/OffChain modes to clearly separate doc storage and transmission options.
🛑 Copies of copies now explicitly forbidden — for both simplicity and security.
🔍 Added helper view functions like isCopyOf() and rewindResponseThread() to make data retrieval smoother.
🛠️ Compilation was failing mysteriously with solc... switched to solcjs and it just worked™ (note to self: never trust your local setup).
🔁 Updated Go bindings + tests to stay in sync with the new ABI.
🖋️ Added full support for on-chain e-signature workflows and verifiable timestamping.
🛠️ Reorganize logs indexed parameters to allow grouped queries of events using grouping keys.
Time to go back building that dApp 🚀
🇧🇪 How to Make Real Belgian Fries (Frites Belges) 🇧🇪
Yes, the best fries in the world. Here's how we do it in Belgium — and what better time than now? Tomorrow is Belgian National Day! 🎉🇧🇪
🥔 What You Need:
Firm potatoes (something like Russet or Yukon Gold)
Beef fat 🐂 (traditional and key to that signature flavor!)
A fryer (or a deep pot with a thermometer)
A bit of patience 😄
Be careful with this token on @base.base.eth, likely a scam as it mimics the SOL token (logo & acronym) but it is an ERC20 token on @base.base.eth and nothing proves these tokens on @base.base.eth are truly backed by real SOL tokens on @solana
Contract address:
0x209ba0deaa26f5f95acd2110de7ce3bd01bd1258
🧠 Why DEXES is being built
Digital trust is broken.
AI can mimic anyone.
Fraud is now industrial.
And still — we lack the most basic tools to be sovereign online:
🪪 Forge and manage our digital identity
📝 Sign, timestamp and verify documents — independently
🔍 Do it all in a verifiable, durable and censorship-resistant way
For over a decade, we’ve been told: – That digital signatures need trusted brokers and legal middleware
– That email is "just fine" for business (but not for what's important)
– That your eID isn’t yours — it’s just a login
– That sending documents needs a state-approved relay
🧱 These narratives built fragile walls.
They didn’t empower us. They trapped us.
DEXES flips the script.
It’s not a SaaS. It’s a standard.
It’s not a service. It’s a right.
✅ Verifiable trust
✅ Real ownership
✅ Decentralized identity
No middleman. No lock-in.
Just tools to speak, sign, and prove — on your terms.
🎉 Shipped: Independent audit of document timestamps is now live on DEXES.
You can now verify any timestamp onchain — even without a wallet — using just the document, its hash, or a known timestamp ID.
This means anyone can check if a document was timestamped, when, and by whom, and whether the signing key was valid at that precise moment.
Let’s walk through the full audit flow 👇
📦 Shipped: Sovereign Timestamping in DEXES
You can now timestamp any document using your OpenPGP subkey — with verifiable proof anchored onchain.
✔️ Sign the hash of any file
✔️ Publish it to Ethereum (or L2)
✔️ Verify anytime, independently, using public cryptographic tools
✔️ Keep full control of your keys and visibility
The interface makes it simple.
The backend makes it resilient.
The vision stays the same: trust no authority — verify everything.
—
Let me know if you'd like to try it.
Soon to be published on IPFS 🫡
Sometimes, I wonder why I spend nights, days, weekends & holidays building Dexes feature after feature — why I left a 6-figure job to do that.
Then I remember.
I remember the nightmares as an integration engineer.
I remember fighting with legacy systems, being blocked by providers, locked in formats, or buried under acronyms like EDI, PEPPOL, DocuSign, SMTP.
I remember just wanting a way to exchange documents securely.
Without begging for API keys. Without trusting unknown backends.
Just a platform no one could ban you from — ever.
So I started building one
