Enscribe

@enscribe

27 Following

4 Followers

Conor Svensson (csvensson.eth) pfp

Conor Svensson (csvensson.eth)

When users become accustomed to seeing #ENS names against #smartcontracts in their wallets, there will be no going back. It will take time to build momentum with this change, as right now not enough people are thinking about this big #UX upgrade we can do across the #Ethereum ecosystem. But there will be an inflection point that causes it to happen. I hope it happens sooner rather than later, but there's a lot of people to get onboard here. However, until we reach that inflection point, we're not going to stop asking people to name their smart contracts. @enscribe_ is getting better by the day, and very soon we're going to unveil publicly our dedicated contract view which will help people visualise where we're headed. In the meantime, if you haven't named any smart contracts, please head to http://app.enscribe.xyz/ to name your first contract!

0 reply

2 recasts

2 reactions

Enscribe pfp

Gm, naming your contracts feels good!

0 reply

0 recast

1 reaction

Enscribe pfp

Gm! Naming contracts doesn't just help you, it also helps make #Ethereum #UX for all!

0 reply

0 recast

2 reactions

Conor Svensson (csvensson.eth) pfp

Conor Svensson (csvensson.eth)

Whilst the #ENS app is excellent for managing ENS names, we believe that the #Ethereum developer community would benefit from something that's been designed specifically for making their #smartcontracts safer and managing names associated with them. We're finding with @enscribe that we're starting to converge towards offering a smart contract management app, and there are some great new updates to this end that we'll be sharing in tomorrow's @ensdao ecosystem call.

0 reply

1 recast

1 reaction

Enscribe pfp

Gm, we believe #ENS is the best solution for naming #smartcontracts in #Ethereum and eliminating hex from the #UX.

0 reply

0 recast

2 reactions

Conor Svensson (csvensson.eth) pfp

Conor Svensson (csvensson.eth)

The premise of Enscribe remains very simple — to get developers to name their #smartcontracts. The further we go on our journey, the more opportunities we uncover to create new value for the #ENS ecosystem. To us this reinforces that we're focussing on an area currently underserved in #Ethereum. Increasing trust and improving #UX for users is our end goal. But along the way, we want to ensure that both smart contract and app developers are incentivised to use @enscribe. This is why we need to add those small moments of delight for users that make their lives easier, but also present them with information that they couldn't readily find elsewhere. For instance, this week we've identified how we can enable users to see all ENS addresses which are set to forward resolve to a smart contract. This may not be helpful for your typical end-user, but it is invaluable information for developers. ctd 👇🏻

1 reply

1 recast

1 reaction

Enscribe pfp

Gm! Build the future you want to see for #Ethereum

0 reply

0 recast

1 reaction

Conor Svensson (csvensson.eth) pfp

Conor Svensson (csvensson.eth)

Getting #smartcontracts named by developers on #Ethereum with #ENS names is the easiest #UX and security uplift we can do for our users. It's doesn't make sense that we want to see mainstream adoption of our beloved network, yet still think it's ok for users to see hex contract addresses when they transact. Hex is completely meaningless to a regular person! It's such an obvious improvement we can collectively make that everyone should be thinking about this. Change will only happen once more people builders start paying attention to this. Let's eliminate hex from the Ethereum UX, and make Ethereum the safest and most user friendly #web3 network of all! #eliminatehex #accelerateENS #justnameit

0 reply

1 recast

1 reaction

Enscribe pfp

GM! Everyone wins with #smartcontracts being named.

0 reply

0 recast

1 reaction

Conor Svensson (csvensson.eth) pfp

Conor Svensson (csvensson.eth)

Address spoofing and poisoning are very real problems for #web3 users. Last year #chainalysis highlighted how contaminated transaction histories had targeted over 82,000 wallets with users loosing tens of thousands of dollars due to these attacks. Naming wallets and #smartcontracts with #ENS names should be the default not the exception when it comes to working with #Ethereum addresses. The only way we get there is by developers and wallet providers ensuring that they all have ENS names. We have to make #Ethereum safer for its users. Eliminating spoofing and poisoning can be done if we get better and naming. If you're a developer name your smart contracts with @enscribe. If you're a wallet provider, make it easy for users to assign ENS names to their wallets. I believe we can make web3 safer for its users. But we all need to do our part. 🙏🏻

0 reply

1 recast

1 reaction

Enscribe pfp

Gm. We need to fix #smartcontract naming for the users.

0 reply

0 recast

1 reaction

Conor Svensson (csvensson.eth) pfp

Conor Svensson (csvensson.eth)

The more time we spend on @enscribe the more confident we feel that we're focusing on a problem worth solving. This blind spot of people not giving their #smartcontracts #ENS names has perpetuated throughout the #Ethereum ecosystem. Anyone we speak to about this sees that it totally makes sense. The only pushback we seem to get is that ENS names alone may not be enough of a trust signal for users to know that contracts are safe to use. That's why we also need the TLS padlock equivalent accompanying named smart contracts. Verifiable contract audits could be the solution here, but it's still a work in progress on our side. We're confident in the direction we're headed, and making Ethereum the safest blockchain of all is our goal. Getting everyone to name their smart contracts is the first step here. More will come soon after. 🫡

0 reply

1 recast

1 reaction

Enscribe pfp

Gm! We know our mission, do you know yours?

0 reply

0 recast

1 reaction

ENS DAO pfp

Weekly Roundup: A snapshot of this week’s Working Group activity—key updates, proposals, and discussions, all in one place.

1 reply

1 recast

4 reactions

Conor Svensson (csvensson.eth) pfp

Conor Svensson (csvensson.eth)

Naming #smartcontracts with #ENS is inevitable. However, we need more people to be aware of this. It's the most obvious uplift we can do for #Ethereum #UX and security we can do right now as a community. No hard forks required. No coordination or new standards required. We just need devs or anyone deploying their contracts to head to https://app.enscribe.xyz and they can easily make it happen. If you'd rather not use our app, you can also head to the @ensdomains docs at https://docs.ens.domains/web/naming-contracts/. I don't care which route you take, as long as you name that contract. I won't stop posting and @enscribe won't stop meming about this until everyone is doing it. 🫡 #namesmartcontracts #accelerateENS #justnameit

0 reply

1 recast

1 reaction

Enscribe pfp

0 reply

0 recast

2 reactions

Conor Svensson (csvensson.eth) pfp

Conor Svensson (csvensson.eth)

The alternative to naming hex smart contacts with #ENS is hiding the hex addresses from users, and letting apps such as wallets decide on the users behalf if it can be trusted. This is not ideal as it means that users are having to implicitly trust the app they are using to interact with contracts, instead of being able to decide for themselves. We're all here building and using #web3 because we believe in the importance of decentralisation, hence its important we embrace a decentralised naming protocol, rather than relying only on gatekeepers that people onboard with to curate smart contract applications for users with their own approach to naming. ENS is the best solution for decentralised naming, and we must continue to push for broader adoption throughout the #Ethereum ecosystem. This maximises choice, safety and decentralisation for users.

0 reply

1 recast

1 reaction

estmcmxci pfp

Naming Smart Contracts with ENS is becoming best practice—for both developer and user experience. @enscribe lets you name contracts at deployment, streamlining DX and improving UX by making contracts human-readable, verifiable, and safer. Here's what we learned on Commons👇 https://x.com/estmcmxci/status/1922034065513054633

1 reply

2 recasts

4 reactions

Enscribe pfp

Gm to all you #smartcontract devs out there. Have you tried naming your contracts with Enscribe yet?

0 reply

0 recast

1 reaction

Conor Svensson (csvensson.eth) pfp

Conor Svensson (csvensson.eth)

Naming #smartcontracts with #ENS names is such an obvious uplift for improving both #UX and security of the #Ethereum ecosystem, that I'm amazed more progress hasn't been made with it. It's a significant blind spot currently for our community. Once users start to see smart contracts being named, they'll come to expect this, and this will force the hands of teams when they deploy smart contracts. They'll realise that if they want their app to be taken seriously, it must have an ENS name for users be comfortable working with it. The only way we can accelerate this transition is to educate users and developers more of the benefits of this. We are taking this very seriously too with @enscribe. We've build a product that does what it needs to do well, and spent a lot of time investing in content, but we can always do more, and if we can gamify this, it makes it could make it even more fun. ctd...

1 reply

1 recast

1 reaction