ETH Price: $2,186.17 (+0.32%)
Gas: 0.671 Gwei

Transaction Details

Sponsored
ads MetaMask
Open a perps trade in seconds on MetaMask Mobile Try Now!

Go long or short on 150 tokens in seconds with up to 50x leverage.

ads eToro
Crypto Trading Made Simple Buy Now!

Trusted, Multi-asset Broker with Powerful Tools for Real Traders Worldwide.

ads MoonPay
Buy Ethereum with 50% off MoonPay Fees, for your first 5 transactionsBuy Now!

T&C's apply, new users only and not for UK users.

Sponsored
ads BC.GAME
Global Football Season - First Play Protected! Play Now!

Unlock protected play and bonus up to $100! Deposit Bonus up to 1080%

ads MetaWin
Deposit & get 30% extra FREE to win $200k every week! Join Now!

Instant Withdrawals, Frictionless Signup & 1000's of Markets.

Sponsored
ads Сoins.game
100 free spins for registration. Spin now!

Everyday giveaways up to 100 ETH, Lucky Spins. Deposit BONUS 300% and Cashbacks!

ads BC.GAME
The Best ETH Casino Claim Now!

5000+ Slots & Live Casino Games, 50+cryptos. Register with Etherscan and get 760% deposit bonus. Win Big$, withdraw it fast.

ads Stake
200% Bonus, Instant Withdrawals, 100K Daily Giveaways, BEST VIP Club Claim Bonus!

20+ Cryptos, 3000+ Slots, Daily & Monthly Bonuses, Exclusive Sports Promos - Provably Fair!

Sponsored
ads BC.GAME
- The Best ETH Casino Claim Now!

5000+ Slots & Live Casino Games, 50+cryptos. Register with Etherscan and get 760% deposit bonus. Win Big$, withdraw it fast.

ads CryptoSlots
New feature: VR Slots! Play now!

Play original casino games and VR slots. Get 177% Deposit Bonus and 25 Jackpot Spins. Fast crypto withdrawals.

ads CryptoWins
$15 free + 200% Welcome Bonus | Play ETH Casino Games Claim Now!

1,200+ games, live BidCoin Auctions, huge jackpots. TRIPLE your deposit & play in 30 seconds!

Transaction Action
Transaction Hash:
0x5cc7d736298232d1a97e315c990058016a0f7297cb11d19d6a3ed339207f7171
Status:
Success
Block:
197059015409706 Block Confirmations
Timestamp:
|Confirmed within 30 secs
Sponsored:
From:
ENS Name michiganblockchain.eth
To:
0x408ED6354d4973f66138C91495F2f2FCbd8724C3 (Uniswap: Governor Bravo)
Value:
0 ETH ($0.00)
Transaction Fee:
0.00488058922664425 ETH $10.67
Gas Price:
6.696057934 Gwei (0.000000006696057934 ETH)
Ether Price:
$3,148.11 / ETH
Gas Limit & Usage by Txn:
742,780 | 728,875 (98.13%)
Gas Fees:
Base: 6.686319713 Gwei |Max: 9.397429645 Gwei |Max Priority: 0.009738221 Gwei
Burnt & Txn Savings Fees:
🔥 Burnt: 0.004873491280812875 ETH ($10.65)💸 Txn Savings: 0.001968962305855125 ETH ($4.30)
Other Attributes:
Txn Type: 2 (EIP-1559) Nonce: 358 Position In Block: 203
Input Data:
Private Note:
To access the Private Note feature, you must be Logged In
View 2 zero value Internal Transactions in Advanced view mode
ADVANCED MODE:
AA Txn Hash Method Position From Internal Txns Token Txns NFT Txns Txn Fee (ETH) Gas Limit
Transaction Receipt Event Logs
574
Address
0x408ed6354d4973f66138c91495f2f2fcbd8724c3 (Uniswap: Governor Bravo)
Name

ProposalCreated (uint256 id, address proposer, address[] targets, uint256[] values, string[] signatures, bytes[] calldatas, uint256 startBlock, uint256 endBlock, string description)View Source

Topics
  • 0 0x7d84a6263ae0d98d3329bd7b46bb4e8d6f98cd35a7adb45c274c8b7fd5ebd5e0
Data
  • id (uint256) :61
  • proposer (address) :0x13BDaE8c5F0fC40231F0E6A4ad70196F59138548
  • targets (address[]) :0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e
    0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e
  • values (uint256[]) :0
    0
  • signatures (string[]) :

  • calldatas (bytes[]) :5B0FC9C30B9638D2C5BD4528D603562A1FA1E734FE1B88E680F448D779531E9BC2B55F120000000000000000000000003B59C6D0034490093460787566DC5D6CE17F2F9C
    5B0FC9C330E9FA72B4D7D40BE0F8809D748497121D5F38EBF8700A7D2E303074E9CCF1A50000000000000000000000003B59C6D0034490093460787566DC5D6CE17F2F9C
  • startBlock (uint256) :19719041
  • endBlock (uint256) :19759361
  • description (string) :# Update Uni v3/v2 Deployment Process (March 2024) **Authors: Uniswap Accountability Committee** ## TLDR: * Today, Uniswap governance, via the timelock address, has the ability to declare a new v3/v2 deployment as official/canonical * The DAO has set a precedent for approving EVM-based deployments over the past 2 years * This proposal seeks to give the Uniswap Accountability Committee multisig agency over altering the v3-deployments.uniswap.eth & v2deployments.uniswap.eth subdomains * This will allow the Committee to edit these text records whenever a new v3/v2 deployment is complete without having to go through an onchain vote * To accommodate for this change, we are also proposing an alteration to the current deployment governance process (see “New Proposed Deployment Process” below) to increase efficiency * The DAO will retain the right to assign incentive distributions from the treasury to these deployments via an onchain vote * The DAO will maintain ownership of the primary domain, uniswap.eth, and thus have the ability to revoke the Committee's subdomain permissions through a governance vote–this assures proper checks and balances ## Background: Over the past two years, the DAO has approved numerous EVM-based deployments for Uniswap v3. There has only been one instance of a deployment proposal that did not pass the off-chain stage due to not meeting quorum: [Fantom](https://snapshot.org/#/uniswapgovernance.eth/proposal/0x98e08d94e1174b0bfa2350c616d3cf2fb8f5e56c56c03dc0ae58fd29a6b29265). We believe that this sets a precedent for optimistically acknowledging incoming EVM-based deployments as canonical. The same precedent can be set for v2 since there was a recent proposal to [deploy v2 across all target chains with v3](https://www.tally.xyz/gov/uniswap/proposal/58) in one fell swoop. The v3-deployments.uniswap.eth & v2deployments.uniswap.eth ENS subdomains act simply as records of the v3/v2 deployments that the DAO has “blessed”. From a legal as well as technical perspective, alterations to the subdomain don’t hold any weight–it’s merely a place onchain that the DAO can recognize v3/v2 deployments across various EVM chains. This way, there’s a public place to keep track of which deployments are official. Such recognition is important because it allows users and developers to ensure that the contracts they’re interacting with are representative of the real Uniswap (i.e. the Uniswap fork that has been approved by the DAO), thereby ensuring security and consistency across each fork. When the DAO currently approves deployments onchain, only the v3-deployments.uniswap.eth & v2deployments.uniswap.eth text records are being altered. The actual contract deployment is completed by a third party, like [@GFXlabs](https://gov.uniswap.org/u/gfxlabs). In fact, the deployment has to be completed prior to the onchain vote since the text record alterations requires the * The destination chain’s network number * Bridge sender contract address on mainnet associated with the deployment * UniswapV3Factory/UniswapV2Factory address on the destination chain ### Current Deployment Process: * If a chain wants to deploy Uniswap, they typically connect with either the Foundation, the Accountability Committee, a delegate, or any adjacent party * Anyone is able to author an RFC, whether it be a delegate, the destination chain themselves, or whoever else. That RFC is posted on the forum for a minimum of seven days to allow a discussion to transpire * A temperature check takes place, allowing the DAO to either approve or deny the deployment of Uni v3/v2 on the given chain * Once passed, the v3/v2 contracts are deployed on the destination chain–the deployer collaborates with an approved bridge provider if the EVM chain is not an L2 (i.e. doesn’t already have a canonical bridge) * The onchain vote takes place, recognizing the deployed contracts as official on the subdomain ## Our Proposal **We are proposing to enable the Uniswap Accountability Committee multisig to alter the subdomains as soon as a deployment’s RFC passes the 7-day discussion period–given there are no major points of contention during the RFC phase.** The RFC should give ample time to the DAO to make a decision regarding the deployment without having to partake in a 4+ week governance ordeal. And to make sure voters have a say in this process, we are including a 5-day challenge period that will be a part of the onboarding package temperature check–this will allow voters to voice their dissenting opinion regarding a deployment. Currently, the Uniswap DAO, more specifically the timelock address (0x1a9C8182C09F50C8318d769245beA52c32BE35BC) owns AND manages both subdomains. This proposal would make the Accountability Committee the manager of the subdomains. If at any time the DAO would like to alter the manager again or regain control, this can be done via an onchain vote since the timelock still owns the subdomains. ### New Proposed Deployment Process: **Step 1** * If a chain wants to deploy Uniswap, they typically connect with either the Foundation, the Accountability Committee, a delegate, or any adjacent party * Anyone is able to author an RFC, whether it be a delegate, the destination chain themselves, or whoever else. That RFC is posted on the forum for a minimum of seven days to allow a discussion to transpire * The deployer can either have the contracts deployed at this point or not–if the deployment is complete, then include the contracts in the RFC * **If no issues arise in the RFC, then the deployment will be viewed as approved, and a 5-day challenge period will be rolled into the onboarding package snapshot vote** **Step 2 (Work for the Deployer and Accountability Committee)** * If deployment hasn’t already been completed, then it must be done after the RFC phase * As soon as contracts are deployed and verified, ensuring that the bytecode of the deployed contracts matches the bytecode of the mainnet contracts, the Committee will comment on the RFC confirming that the contracts have been verified  * The Committee will then hold a temperature check to see if there’s interest in deploying incentives on the new fork–this vote also acts as the challenge period * **Once the snapshot is completed, and the vote is not subject to a majority veto, the Committee has the authority to write the relevant text to the subdomain** * The Committee will comment on the RFC confirming that the subdomain has been properly updated * An onchain vote will then take place to send the selected amount of capital to the Committee multisig for distribution on the target chain ## Technical Implementation: The onchain proposal needs to include the function calls below to grant the Accountability Committee write permissions to the subdomains. The DAO will maintain ownership of the primary domain, uniswap.eth, and thus have the ability to revoke the Committee's permissions through a governance vote and establish checks and balances. **For Uniswap v3 Subdomain:** setOwner(   node = 0x0b9638d2c5bd4528d603562a1fa1e734fe1b88e680f448d779531e9bc2b55f12,    owner = 0x3B59C6d0034490093460787566dc5D6cE17F2f9C ) **For Uniswap v2 Subdomain:** setOwner(   node = 0x30e9fa72b4d7d40be0f8809d748497121d5f38ebf8700a7d2e303074e9ccf1a5,    owner = 0x3B59C6d0034490093460787566dc5D6cE17F2f9C ) ## Next Steps: *The Accountability Committee will retroactively alter the subdomain text record for any deployments that are approved and haven't been included in the subdomains after the approval of this proposal. The Committee will also add the text for deployments that did not go through the formal governance process from the* [*Uniswap Revitalization and Growth*](https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616) *proposal.*

                

            




            

                

                    
                    

                        

                            

                                
                                    

                                        Authority
                                        
                                            Delegated Address
                                        
                                        Nonce
                                        Validity  
                                        yParity
                                        r
                                        s
                                    

                                
                                
                                    
                                
                            

                        

                        

                    

                    
                


            


            

                

                    

                        
Loading

                    

                    

                        
                    

                

            


            
            

                

                    

                        
Loading

                    

                    

                        
                    

                

            

            

            

                

                    

                        
Loading

                    

                    

                        
                    

                

            


            
        

        

        
        

            

                 
                A transaction is a cryptographically signed instruction that changes the blockchain state. Block explorers track the details of all transactions in the network. Learn more about transactions in our Knowledge Base.