Content
@
https://ethereum.org
0 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth)
@csvensson
At @enscribe we believe in establishing a new norm for contract deployments. Currently when #smartcontracts are deployed on #Ethereum, @base, @linea and other networks, they should be verified and audited for the sake of users. But this information is not readily available to users without doing their own research. With Enscribe we want to provide users of smart contract applications with the confidence that what they are interacting with is safe — the check-mark if you will for applications. There are three components to this. The first two, verifying and auditing their are already embraced by teams, but the information is not easy to surface for users. There are three primary platforms for smart contract verifications — @SourcifyEth, @blockscout and Etherscan. If a contract is verified on one of them this should be readily surfaced for users. Hence this is something we now show in the Enscribe app. https://app.enscribe.xyz/explore/1/0xD14360D477EF49182B5141952FE67b007688725A ctd 👇
1 reply
0 recast
1 reaction
Conor Svensson (csvensson.eth)
@csvensson
We're also adding something similar for audits, which we'll be sharing more on shortly. The final piece is naming — smart contracts should be named with @ensdomains names, which is why we created Enscribe in the first place — to simplify this process. You can name your contract by heading to https://app.enscribe.xyz/nameContract. This is what we believe the post deployment workflow should be: Name, verify, audit We want this to become the gold standard for contract deployments. With this, we believe that it will enable users to quickly ascertain if contracts are safe for them to interact with them. This will not only improve #UX, but also make #Ethereum safer for all.
0 reply
0 recast
0 reaction
