Csongor - CJ

building word of mouth, but for machines · out of stealth soon

prev @malda_xyz

[Csongor - CJ @scsongi7]

Build for prevention.

[Malda @malda_xyz]

What’s the perfect pairing with audits?

Preventative security measures to stop malicious txns in their tracks.

This is how @phylaxsystem secures Unified Liquidity.

[Andy @andyyy]

JUST IN: BASE IS LEAVING OPTIMISM SUPERCHAIN TO BUILD THEIR OWN STACK, CITING A NEED FOR A "UNIFIED, BASE-OPERATED STACK"

BASE CHAIN HARDFORK COMING IMMINENTLY.

[Csongor - CJ @scsongi7]

5 min binary options likely poured a lot of volume into Polymarket recently...

[matze | growthepie 🥧 @web3_data]

More fees were paid on Polygon PoS than on Ethereum Mainnet 🤯

This is fully driven by Polymarket
-> see screenshots of app breakdown by fees paid

[Csongor - CJ @scsongi7]

@EvanCull @Polymarket if @Polymarket listed it odds would already be mooning probably

[Csongor - CJ @scsongi7]

The era of one size fits all frontends are soon ending...

[AK @akbuilds_]

I don’t know about others, but I’m letting Opus 4.6 design directly in Figma via Cursor.

This is starting to feel unfair.

And yeah… I just sit there and enjoy life. ❤️

[Csongor - CJ @scsongi7]

.@infinex’s new roadmap visualization is pretty neat

Quite a bit of cross-chain infra work happening there

[Csongor - CJ @scsongi7]

Difference? Pure GTM execution.

As @0xkydo pointed out: TradFi giants on stage, vApps reframed, physical hardware making the abstract tangible.

Ethereum is chasing a similar endgame but today they got outplayed in the mental model battle. Just a battle though...

Either way, another L1 just reinforces the obvious: trustless interop between them will be essential.

[Odysseus | phylax.systems @odysseas_eth]

I think that layerzero built something very special and it's amazing how they were able to get the talent and expand from interop to hardcore systems engineering

at the same time, it's not the first multi-core blockchain

it's more like how polkadot could have been if not built by a Gmbh

(would love to see ideas around semi-coherent interop that are expressed in the JAM whitepaper, adopted by layerzero)

[Csongor - CJ @scsongi7]

@0xsmallbrain Very ok

[Csongor - CJ @scsongi7]

Meme idea → Real primitives.

That’s just sometimes how DeFi evolves.

[Small Brain @0xsmallbrain]

Introducing Buy Now, Pay Maybe - a new way to buy stuff onchain

You either pay nothing... or overpay. Those who overpay cover everyone else 😏

Payments are handled transparently on @AbstractChain. Try it now (& get limited merch!) at https://t.co/1J2pSFMmNA

[Csongor - CJ @scsongi7]

@jonastheis_ @boundlesshq @Scroll_ZKP @iota Congrats! 💚

[Csongor - CJ @scsongi7]

https://t.co/4b4uQgbeXI

[Csongor - CJ @scsongi7]

Vitalik is right: trustless interop isn’t a feature, it’s a prerequisite for existence.

But the reality is bigger: multichain future is far more than just 'Ethereum and friends'.

We need trustless guarantees inbetween the entire onchain economy.

[Barna @realbarnakiss]

Ethereum is now capable of fulfilling scaling for itself. This doesn’t make L2s obsolete, this means L2s are specializing.

Chains and fragmented ecosystems will continue to exist, and interop initiatives within and oustide of Ethereum remain paramount for the success of blockchain as a whole.

We have been building with ZK to achieve our mission: laying the foundations of trustless interop.

Excited to continue to work alongside Ethereum for the betterment of the space.

[Csongor - CJ @scsongi7]

@0xEgeG I kind of did. So now you must be present for the next shoot!

[Csongor - CJ @scsongi7]

The "why" behind:

Dept. of Trustless Interop.

[Malda @malda_xyz]

It's why we build.

[Csongor - CJ @scsongi7]

Time after time, it’s clear: cross-chain must be ZK-based.

[Malda @malda_xyz]

Another $3M lost to spoofed messages.

The industry needs to move beyond simple bridge relays. A bug that ZK based infra solves by default.

We need to stop trusting the message and start verifying the proof.

[Csongor - CJ @scsongi7]

When designing architecture:

Complexity = risk
Simplicity = security

That’s why we keep protocol logic on a host chain: fewer moving parts, fewer edge cases.

[Malda @malda_xyz]

https://t.co/myrk4t1fdw

[Csongor - CJ @scsongi7]

Delivering another major upgrade to our security stack.

Audits + bug bounty are important, but preventive measures is how you stay ahead of bad actors.

We now have two independent guardrails!

[Malda @malda_xyz]

Proud to be among the first integrating @phylaxsystems’ Credible Layer.

Phylax enforces txn assertions for Malda on @LineaBuild’s sequencer.

Since the Unified Lending’s ledger lives on Linea (host chain) these security guarantees apply to all crosschain activity.

Another big step toward delivering an institution-ready product.

[Csongor - CJ @scsongi7]

@malda_xyz This is what a successful onsite looks like

[Csongor - CJ @scsongi7]

The walkaway test doesn’t stop at Ethereum or apps built on it.

It must also apply to the crosschain infra connecting L2s and mainnet.

The walkaway test for crosschain is simple:
1. Message delivery is enforced cryptographically, not socially
2. If delivery fails, users retain a permissionless escape hatch
3. Safety does not rely on coordination between chains

The Future is Unified.
The Future is Trustless.

[vitalik.eth @VitalikButerin]

Ethereum itself must pass the walkaway test.

Ethereum is meant to be a home for trustless and trust-minimized applications, whether in finance, governance or elsewhere. It must support applications that are more like tools - the hammer that once you buy it's yours - than like services that lose all functionality once the vendor loses interest in maintaining them (or worse, gets hacked or becomes value-extractive). Even when applications do have functionality that depends on a vendor, Ethereum can help reduce those dependencies as much as possible, and protect the user as much as possible in those cases where the dependencies fail.

But building such applications is not possible on a base layer which itself depends on ongoing updates from a vendor in order to continue being usable - even if that "vendor" is the all core devs process. Ethereum the blockchain must have the traits that we strive for in Ethereum's applications. Hence, Ethereum itself must pass the walkaway test.

This means that Ethereum must get to a place where we _can ossify if we want to_. We do not have to stop making changes to the protocol, but we must get to a place where Ethereum's value proposition does not strictly depend on any features that are not in the protocol already.

This includes the following:

* Full quantum-resistance. We should resist the trap of saying "let's delay quantum-resistance until the last possible moment in the name of ekeing out more efficiencies for a while longer". Individual users have that right, but the protocol should not. Being able to say "Ethereum's protocol, as it stands today, is cryptographically safe for a hundred years" is something we should strive to get to as soon as possible, and insist on as a point of pride.
* An architecture that can expand to sufficient scalability. The protocol needs to have the properties that allow it to expand to many thousands of TPS over time, most notably ZK-EVM validation and data sampling through PeerDAS. Ideally, we get to a point where further scaling is done through "parameter only" changes - and ideally _those_ changes are not BPO-style forks, but rather are made with the same validator voting mechanism we use for the gas limit.
* A state architecture that can last decades. This means deciding, and implementing, whatever form of partial statelessness and state expiry will let us feel comfortable letting Ethereum run with thousands of TPS for decades, without breaking sync or hard disk or I/O requirements. It also means future-proofing the tree and storage types to work well with this long-term environment.
* An account model that is general-purpose (this is "full account abstraction": move away from enshrined ECDSA for signature validation)
* A gas schedule that we are confident is free of DoS vulnerabilities, both for execution and for ZK-proving
* A PoS economic model that, with all we have learned over the past half decade of proof of stake in Ethereum and full decade beyond, we are confident can last and remain decentralized for decades, and supports the usefulness of ETH as trustless collateral (eg. in governance-minimized ETH-backed stablecoins)
* A block building model that we are confident will resist centralization pressure and guarantee censorship resistance even in unknown future environments

Ideally, we do the hard work over the next few years, to get to a point where in the future almost all future innovation can happen through client optimization, and get reflected in the protocol through parameter changes. Every year, we should tick off at least one of these boxes, and ideally multiple. Do the right thing once, based on knowledge of what is truly the right thing (and not compromise halfway fixes), and maximize Ethereum's technological and social robustness for the long term.

Ethereum goes hard.

This is the gwei.