Shutter Network is an anti-MEV/front running solution on Ethereum using a DKG and threshold encryption, and built by @bezzenberger - PM@_brainbot. Brainbot technologies has significantly contributed to the core development of the Ethereum project from the very beginning.
1/10
The design of Shutter Network is to who needs to prevent Front-Running/ MEV can conduct transactions through its integrated terminal, which is different to our previous thread of #Flashbot. Flashbot is more for Validators, and Shutter Network is for "All" users.
2/10
Front-Running is the act of placing a transaction in a queue with the knowledge of a future transaction, and usually happens when a miner who has access to information on pending transactions. Miner can set a higher gas to place an order that would earn a profit.
3/10
In many cases, miners colluded with front-running robots for arbitrage. The most typical example is "Sandwich Attacks" which is aimed at AMM transactions. In addition, there are also front-running attacks aimed at arbitrage, liquidation transactions, flash loans, etc.
4/10
“On-chain Shutter“ serves users who need anti-front running transactions, that is, using encryption technology to hide transaction information, so that the attacker can neither determine whether the transaction is a buy or sell order, nor the token or price.
5/10
And adds it to the block, then decrypts and executes the transaction. Technical speaking, a decentralized autonomous organization (DAO) manages the system at the heart of the Shutter architecture. Its main task is to hire a set of special nodes called keypers.
6/10
The keypers generate cryptographic keys with which users encrypt their transactions. The majority of keypers are trusted to act honestly according to the protocol, while a minority can be malicious or offline.
7/10
However, distributed key generation (DKG) protocols are inefficient with many participants, so running one for each epoch is not viable. Therefore, Shutter uses a two-step process:
1. a conventional DKG process is carried out, generating the so-called eon key pair.
8/10
2. Transactions are not encrypted and decrypted with the eon keys directly, but with so-called epoch keys.
Some questions.
1. Since transactions will still be reviewed and even reordered by miners after entering the Mempool, it cannot fundamentally solve the MEV problem.
9/10
2. Threshold encryption may bring network latency. 3. Since its design is to build a proxy contract on the outer layer of the original DeFi protocol, it will directly affect the composability of the DeFi protocol.
MEV is a dynamic that allows miners to maximize their profit by determining the order of transactions on a blockchain network to their advantage. This includes arbitrarily reordering, including, or excluding transactions within a block at the expense of users.
1/12
After the Merge, rewards to miner will decrease, resulting in MEV will increase the percentage of profit for miner. Therefore, the MEV problem is getting important. Several solutions arose to mitigate these negative externalities. Most prominently, #Flashbots.
Secret Shared Validators (SSV), or Distributed Validator Technology (DVT), is the first protocol that encrypts a validator key and splits it into KeyShares. These KeyShares are distributed to non-trusting nodes run by operators, fault-tolerant for Ethereum staking.
1/5
We know that ETH 2.0 is going to change the consensus form PoW to PoS to verify transaction via staking. In order to be more decentralized, we need more nodes to participate. But if there is a node faces some security or off-line risk, the node will be penalized.