I think the mempool is going to be one of the next blockchain module where we will see a lot of innovation.

Encrypted mempools, side-pools, app-specific mempools, custom appchain mempools, ... read all about it below!
First, at the base layer, with @project_shutter and Flashbots SUAVE building encrypted mempools.
But we'll also see the rise of new "side pools", for instance to support account abstraction via EIP-4337.

The 4337 mempool broadcasts "user operations" instead of traditional transactions, which are later bundled and posted on-chain by bundlers.
See the EIP (eips.ethereum.org/EIPS/eip-4337) and this thread by @VitalikButerin which explains the possibilities and remaining problems:
EIP-4337 needs a "general" mempool.

I think we will also see the emergence of app-specific mempools.
In fact, this already exists, for instance in @CoWSwap.

These mempools allow doing some pre-processing, matching, and aggregation in the mempool directly. For instance, CoWSwap matches buy and sell orders off-chain in order to minimize slippage.
Quick sidebar: CoWSwap is really cool because this matching is itself decentralized, a competition between "batch builders" to get the best price for users. See this great talk by @AnnaMSGeorge for more details:
Often, the possibilities offered by these app-specific mempools hinges of the notion of "intent": the users sign-off on *what* they want accomplished, not *how* they want it accomplished.
Specialized actors then monitor the mempool and try to fullfill these intents as well as possible.

For CoWSwap, this is done through order matching.
But you could go a lot more generic! You could imagine a system where an intent would grant specific permissions (e.g. unlock assets), but the transaction would revert if the specified conditions are not fullfilled by the end of the transaction.
If I understand correctly, @anomanetwork is trying to build such a system. But you don't necessarily need a whole new system to do this. There is a TON of innovation that can be driven via a new mempool module + smart contracts on EVM chains.
For instance, I could sign an intent that says: on a budget of 1 $ETH, I want to purchase any three #motorheadz NFTs, to be carried out within the next 3 hours.
If a "builder" finds a way to carry the trade, he can use my signed intent to unlock the ETH, purchase the NFTs, and transfer them to me!
Another example: optimistic game resolution. Player trade a series of intents, representing game moves. If everybody respects the rules, it's only necessary to post a single transaction on-chain, representing the agreed-upon result of the game.
But if a player tries to cheat, you could use the intents (representing the game history) to build a proof of cheating on-chain.

If the intents are traded privately, this is a solution reminiscent of state channels.
If the intents are broadcasted in the mempool, mempool watchers can act as referees, and mount a proof of cheating on behalf of the player that has been wronged.
These app-specific mempools can of course be integrated in app-specific chains!

And of course, it's my dearly held opinion that all app-chains should be app-specific *rollups* with Ethereum as their settlement layer!
This is of course where I plug the #OPStack, our initiative at OP Labs to build a modular rollup stack where it is easy to mix and match parts!
Bedrock (next mainnet release) is the foundation, but we want to push the easy of customization to the max, and offer a wide selection of open-source modules!
But we'll need help to do this. If you want to build on the OP Stack, work on new modules, and help push forward the future of blockchain tech and modularity, don't hesitate to be in touch!

DMs are open!
smh I forgot to number this tweet thread :D

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with (🔴✨) Norswap 🏴‍☠️

(🔴✨) Norswap 🏴‍☠️ Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @norswap

Nov 9
1/43 🧵 How do you shuffle a deck of cards on the blockchain?
How do you draw a card without revealing it to your opponent?
2/ Shuffling a deck is easy if anybody can see the new ordering (just use the Fisher-Yates algorithm for instance).

Of course, in most games, you want to ordering to remain hidden from both players!
3/ Instead we need to approach the problem from a different angle: the deck won't be pre-shuffled, we will just randomize card draws.

Let's assume at first everyone will be able to see the drawn card.
Read 43 tweets
Jun 7
1/54🧵 Thread on @VelodromeFi and why it's a superior system for incentivizing liquidity.
@VelodromeFi 2/ Liquidity is super important for project tokens. A lack of liquidity makes the token price too volatile. It also prevents investors for exiting, which makes them wary to invest in the first place.
@VelodromeFi 3/ (And more cynically, such a liquidity pool also doubles as another use case for the token, to prevent excessive selling.)
Read 56 tweets
Jun 2
1/40/ Some technical notes on $OP airdrop #1 from yesterday. 🧵
2/ Obviously, it was a bumpy ride. We ran into a few different things that I think people will be interested to hear about though.
3/ Important disclaimers:

This is only my recollection / perspective on events. Not anything official or authoritative. I don't speak for OP Labs nor Optimism.

The official retrospective we will put out will have much more details, but I hope this gives you a taste.
Read 42 tweets
Jun 1
There are a lot of take-aways from yesterday's airdrop for Optimism, which you'll hear from me or others soon.

But I think there's a good take-away for dapps too:

> Any serious dapp should run its own nodes. <
Consider that a dapp running its own nodes would have seen 0 disruption from the JSON-RPC endpoints overload yesterday.
A simpler solution is to at least have a private endpoint with a node provider.

This wouldn't have sufficed to avoid all disruptions yesterday, as node providers were very briefly underprovisioned in terms of total capacity!
Read 4 tweets
Mar 11
With the Cannon bug bounty out, it's time for me to take my best stab at describing what it is, and how it works.

Cannon is our next-gen EVM-equivalent fault proof system. It's what will keep your funds secure when you use Optimism. Read to know more!
You can read the unrolled version of this thread here: typefully.com/norswap/GyqpjNs
1/44 What to expect?

- Recap on optimistic rollups / fault proofs
- Short history of fault proofs at Optimism
- Most thorough explanation of Cannon (fault proofs?) to ever grace Twitter — quite technical, but approachable
- My longest twitter thread to date

LET'S FUCKING GO
Read 47 tweets
Mar 10
‧͙⁺˚*・༓☾ ✨ Norswap's Thread of Things ✨ ☽༓・*˚⁺‧͙
⭕ Optimistic Rollups vs ZK Rollups
Read 7 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(