Rohit Solia

[Rohit Solia @rohit_solia]

@GooglePixel_US You used cheap glue while making this watch and now asking for $200 to repair it. Guess I trusted wrong brand!

[Rohit Solia @rohit_solia]

@vfsglobalcare Any progress on this matter?

[Rohit Solia @rohit_solia]

@VFSGlobal @vfsglobalcare cc @IndianEmbassyUS @cgihou It's been 4 months since my application USAH05184N25 was canceled, and I am still waiting for the refund. Could you please provide an update on the status and expected timeline for processing the refund?

[ً @lightclients]

EIP-8037 is scheduled for Glamsterdam and will increase the gas cost of creating new accounts and writing to new storage slots by 5-8x.

What protocols have hard-coded expectations about state gas costs? What is at risk of breaking?

[Rohit Solia @rohit_solia]

@vfsglobalcare Thanks! I've provided everything you've asked in DM, hope it gets resolved soon.

[Rohit Solia @rohit_solia]

@vfsglobalcare Sent.

[Rohit Solia @rohit_solia]

Alpha, MIT-licensed. Issues and feedback very welcome.

npm i -D hardhat-upgrades-validator@alpha

📦 https://t.co/I8ee5ZZxUk
💻 https://t.co/O9cglZMKJj

[Rohit Solia @rohit_solia]

@OpenZeppelin's `hardhat-upgrades` is the gold standard for proxy upgrade safety.

It doesn't work with hardhat-deploy v2.

So I built `hardhat-upgrades-validator`, a @HardhatHQ v3 plugin that fills the gap.

🧵

[Rohit Solia @rohit_solia]

Big thanks to @wighawag . He's open to consuming this directly inside `rocketh/proxy`, which would mean hardhat-deploy v2 users get upgrade safety by default, with zero manual wiring.

That kind of integration is the whole point.

[Turshija @turshija]

I got completely owned by the most sophisticated hack I've ever encountered.

I'm a developer. I know what scams look like.
This didn't look like one.

🧵

[Odyssey Finance @OdysseyFi]

https://t.co/pJJpLjgGVe

[Immunefi @immunefi]

Immunefi platform early access customer announcement: @VesperFi.

Vesper provides a platform for easy-to-use Decentralized Finance (DeFi) products, and they have more than 50 audits to their name.

Great to be working closely with a project that takes security seriously.

Welcome aboard!

[ronan.eth @wighawag]

Releasing purgatory

a local Ethereum mempool proxy

let you debug transaction flow - pending, not-found, included....

✅Gas price filtering
✅Web dashboard
✅REST API

npm i purgatory
anvil | hardhat node --port 8546
purgatory --rpc-url http://localhost:8546 -p 8545

[vitalik.eth @VitalikButerin]

Now, account abstraction.

We have been talking about account abstraction ever since early 2016, see the original EIP-86: https://t.co/E4xJymAxiH

Now, we finally have EIP-8141 ( https://t.co/YD9nIpsxcC ), an omnibus that wraps up and solves every remaining problem that AA was intended to address (plus more). Let's talk again about what it does.

The concept, "Frame Transactions", is about as simple as you can get while still being highly general purpose. A transaction is N calls, which can read each other's calldata, and which have the ability to authorize a sender and authorize a gas payer. At the protocol layer, *that's it*.

Now, let's see how to use it.

First, a "normal transaction from a normal account" (eg. a multisig, or an account with changeable keys, or with a quantum-resistant signature scheme). This would have two frames:

* Validation (check the signature, and return using the ACCEPT opcode with flags set to signal approval of sender and of gas payment)
* Execution

You could have multiple execution frames, atomic operations (eg. approve then spend) become trivial now.

If the account does not exist yet, then you prepend another frame, "Deployment", which calls a proxy to create the contract (EIP-7997 https://t.co/sIQrtJDXLt is good for this, as it would also let the contract address reliably be consistent across chains).

Now, suppose you want to pay gas in RAI. You use a paymaster contract, which is a special-purpose onchain DEX that provides the ETH in real time. The tx frames are:

* Deployment [if needed]
* Validation (ACCEPT approves sender only, not gas payment)
* Paymaster validation (paymaster checks that the immediate next op sends enough RAI to the paymaster and that the final op exists)
* Send RAI to the paymaster
* Execution [can be multiple]
* Paymaster refunds unused RAI, and converts to ETH

Basically the same thing that is done in existing sponsored transactions mechanisms, but with no intermediaries required (!!!!). Intermediary minimization is a core principle of non-ugly cypherpunk ethereum: maximize what you can do even if all the world's infrastructure except the ethereum chain itself goes down.

Now, privacy protocols. Two strategies here. First, we can have a paymaster contract, which checks for a valid ZK-SNARK and pays for gas if it sees one. Second, we could add 2D nonces (see https://t.co/1cRegaXpHM ), which allow an individual account to function as a privacy protocol, and receive txs in parallel from many users.

Basically, the mechanism is extremely flexible, and solves for all the use cases. But is it safe? At the onchain level, yes, obviously so: a tx is only valid to include if it contains a validation frame that returns ACCEPT with the flag to pay gas. The more challenging question is at the mempool level.

If a tx contains a first frame which calls into 10000 accounts and rejects if any of them have different values, this cannot be broadcasted safely. But all of the examples above can. There is a similar notion here to "standard transactions" in bitcoin, where the chain itself only enforces a very limited set of rules, but there are more rules at the mempool layer.

There are specific rulesets (eg. "validation frame must come before execution frames, and cannot call out to outside contracts") that are known to be safe, but are limited. For paymasters, there has been deep thought about a staking mechanism to limit DoS attacks in a very general-purpose way. Realistically, when 8141 is rolled out, the mempool rules will be very conservative, and there will be a second optional more aggressive mempool. The former will expand over time.

For privacy protocol users, this means that we can completely remove "public broadcasters" that are the source of massive UX pain in railgun/PP/TC, and replace them with a general-purpose public mempool.

For quantum-resistant signatures, we also have to solve one more problem: efficiency. Here's are posts about the ideas we have for that: https://t.co/xzG3Jp7Yky https://t.co/WikL7gJ5qg

AA is also highly complementary with FOCIL: FOCIL ensures rapid inclusion guarantees for transactions, and AA ensures that all of the more complex operations people want to make actually can be made directly as first-class transactions.

Another interesting topic is EOA compatibility in 8141. This is being discussed, in principle it is possible, so all accounts incl existing ones can be put into the same framework and gain the ability to do batch operations, transaction sponsorship, etc, all as first-class transactions that fully benefit from FOCIL.

Finally, after over a decade of research and refinement of these techniques, this all looks possible to make happen within a year (Hegota fork).
https://t.co/p7XOgId5NN

[ronan.eth @wighawag]

🚀 hardhat-deploy 2.0 is here!

A complete rewrite built for Hardhat 3.x that makes #ethereum #smartcontracts deployment easier than ever

Write deploy scripts in plain TypeScript/javascript. Get Hot Reload, Reproducible deployments and easy export + many more features!

🧵thread

[Peter Girnus 🦅 @gothburz]

Last quarter I rolled out Microsoft Copilot to 4,000 employees.

$30 per seat per month.

$1.4 million annually.

I called it "digital transformation."

The board loved that phrase.

They approved it in eleven minutes.

No one asked what it would actually do.

Including me.

I told everyone it would "10x productivity."

That's not a real number.

But it sounds like one.

HR asked how we'd measure the 10x.

I said we'd "leverage analytics dashboards."

They stopped asking.

Three months later I checked the usage reports.

47 people had opened it.

12 had used it more than once.

One of them was me.

I used it to summarize an email I could have read in 30 seconds.

It took 45 seconds.

Plus the time it took to fix the hallucinations.

But I called it a "pilot success."

Success means the pilot didn't visibly fail.

The CFO asked about ROI.

I showed him a graph.

The graph went up and to the right.

It measured "AI enablement."

I made that metric up.

He nodded approvingly.

We're "AI-enabled" now.

I don't know what that means.

But it's in our investor deck.

A senior developer asked why we didn't use Claude or ChatGPT.

I said we needed "enterprise-grade security."

He asked what that meant.

I said "compliance."

He asked which compliance.

I said "all of them."

He looked skeptical.

I scheduled him for a "career development conversation."

He stopped asking questions.

Microsoft sent a case study team.

They wanted to feature us as a success story.

I told them we "saved 40,000 hours."

I calculated that number by multiplying employees by a number I made up.

They didn't verify it.

They never do.

Now we're on Microsoft's website.

"Global enterprise achieves 40,000 hours of productivity gains with Copilot."

The CEO shared it on LinkedIn.

He got 3,000 likes.

He's never used Copilot.

None of the executives have.

We have an exemption.

"Strategic focus requires minimal digital distraction."

I wrote that policy.

The licenses renew next month.

I'm requesting an expansion.

5,000 more seats.

We haven't used the first 4,000.

But this time we'll "drive adoption."

Adoption means mandatory training.

Training means a 45-minute webinar no one watches.

But completion will be tracked.

Completion is a metric.

Metrics go in dashboards.

Dashboards go in board presentations.

Board presentations get me promoted.

I'll be SVP by Q3.

I still don't know what Copilot does.

But I know what it's for.

It's for showing we're "investing in AI."

Investment means spending.

Spending means commitment.

Commitment means we're serious about the future.

The future is whatever I say it is.

As long as the graph goes up and to the right.