Conor Svensson (csvensson.eth)
@csvensson
Once most developers start giving their #smartcontracts #ENS names, what's next for increasing trust and enhancing #Ethereum #UX for our users in a decentralised manner? There are a couple of angles we've started to explore here. The first of them is surfacing information about contract verifications against contracts, pulling data from #etherscan, @blockscout and @sourcifyeth. Our thinking being that anyone taking due care with their contract deployments should be doing this. It doesn't protect against scammers (after all anyone can do this), but at least it shows that some due care is being taken by the devs (and ensures wallets can decode any method signatures on transactions). A screenshot of our initial support for verifications is below, taken from our latest post https://enscribe.xyz/blog/contracts-verification. ctd...
1 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth)
@csvensson
We're also looking a contract audits and mechanisms to incorporate support for them in @enscribe. We'll be sharing more on this shortly. However, I'd love to hear what people here think we can do. We want us to get to a place where we have the equivalent of a TLS padlock for users of #web3 apps that provide a visual cue that can tell them if what they're interacting with is safe. It should also be done in a decentralised manner, so that whatever service is designed, can still thrive regardless of if Enscribe exists or not. What are the key metrics we can use? So far we're thinking: 1. Contract named with ENS 2. Contract verified 3. Verifiable audits against live contracts What's missing?
0 reply
0 recast
0 reaction
