Conor Svensson (csvensson.eth) (csvensson)

It's exciting to see how different smart contract deployments will look in the future. We have source code verification, but we don't have on-chain metadata to help projects easily tie together artifacts for releases. This is going to change very soon...

• 1 reply
• 1 recast
• 1 reaction

Interesting to see with Tempo how they're showing user transaction receipts in a way that resembles Stripe payment receipts. Question I have in my mind is if this will be adequate for users. Are they ok with seeing 0x566f…b45f as a sender? The philosophy of the @enscribe team is that these addresses must be replaced with decentralised names, akin to how ip addresses have been replaced by DNS addresses for web users. But, we could be wrong. Perhaps people will be ok with these truncated hex addresses, after all, bank accounts are numeric digits or alphanumeric in the case of SWIFT/BIC codes. My belief is that we have the capabilities to eliminate hex addresses for users with technology we have now in web3. Therefore we should do it. Sure, people may be ok with some hex in a receipt, but it's even better if the intent of the thing that that person was interacting with is in an intuitive, human readable form. ctd

• 2 replies
• 1 recast
• 1 reaction

Excited for our first big @ens_dao contract naming season announcement tomorrow. This is going to be the first of many project announcements who have fully embraced naming. 😎

• 0 replies
• 1 recast
• 1 reaction

So much good stuff happening in ENS right now: - @Celo announcing Celo names w/support from Namespace - @jamesbeck.eth discussing upcoming gTLD auctions and potential for .ens - Doma Protocol DNS integration - Contract naming season with our very own @enscribe

• 1 reply
• 2 recasts
• 4 reactions

Other than replacing hex contract addresses with ENS names, we're working to identify what is the strongest visual cue that can be used to identify if a smart contract is safe for a user. Contract audits are useful indicators of safety, but in speaking to a number of auditing firms, consensus seems to be that audits alone are not enough. Not all contract authors are as diligent as they could be apparently, so audits can risk being a false signal of safety. Other areas include social signals such as what OpenLabels initiative by @growthepie are doing (which @enscribe integrates with), which are other useful indicators. Additionally projects like SCI Domains are promising for providing trust between websites app domains and the contract infra deployed on them. ctd 👇

• 2 replies
• 2 recasts
• 4 reactions

Finding the right partner projects for us to integrate with is absolutely crucial to increase trust for Ethereum smart contracts. We're not interested in projects pumping a token, we're interested in projects that are aligned with our mission of making smart contracts on Ethereum safer for users. Hence I'm stoked to announce with our Open Labels Initiative #OLI integration from the @growthepie team, which is using #EAS behind the scenes. Like the other projects we're already integrating with such as Ethereum Follow Protocol #EFP, @Sourcify, @namehash and others we're all aligned on staying true to Ethereum's decentralisation goals (and ENS for some of us). There's even more integrations coming up, as well as further enhancing our existing integrations which I'm super excited about. If there's other projects solving meaningful problems that would align with what we're building at @enscribe my DMs are always open. 🙏

• 0 replies
• 1 recast
• 4 reactions

The rollout of L2 primary names on @ensdomains is happening. This is a significant upgrade that enables you to have your ENS names resolved on other networks including @base.base.eth, @arbitrum, @Linea, @optimism, @scrollzkp. The @enscribe team is hard at work getting this working for smart contracts, so they can be universally named via the Enscribe App. We'll be sharing more updates shortly and on the weekly @ensdao ecosystem calls if you want to learn more!

• 0 replies
• 2 recasts
• 7 reactions