From a468828000c52a7c45fe38886998dc2440405e2b Mon Sep 17 00:00:00 2001
From: Theo <theo@noreply.org>
Date: Mon, 31 Jul 2023 02:12:57 -0700
Subject: [PATCH] Add info about deployed contract

---
 README.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/README.md b/README.md
index dab51a1..361d0a0 100644
--- a/README.md
+++ b/README.md
@@ -33,6 +33,10 @@ or
 npm run test:linux
 ```
 
+### Contracts
+
+Proposal deployed contract: [etherscan link](https://etherscan.io/address/0x86d5f637f7cc0e55334439d0495de3b7daa62baa#code)
+
 ### Verification
 
 Since the proposal code can be confusing because it relies on numerous specifications and EIPs, users can use scripts to verify the correctness of the data, see the output in the corresponding files, and insert the code directly into Solidity, comparing it with the existing code in the proposal (there should be no discrepancies be).