Conor Svensson (csvensson.eth) pfp

Conor Svensson (csvensson.eth)

@csvensson

58 Following
27 Followers
Conor Svensson (csvensson.eth) pfp
0 reply
1 recast
1 reaction
Conor Svensson (csvensson.eth) pfp
Our mission at Enscribe is to make #Ethereum the safest blockchain for users. Getting #ENS names in front of users instead of hex contract addresses will be a huge step in the right direction for this. It's such an obvious upgrade, that I constantly find myself astounded that more people aren't prioritising this. People put up with the current #Ethereum #UX because they're either technologists, speculators or libertarians. Users outside of this camp will not come to accept hex addresses anywhere in the user experience. Especially as it exposes them to security issues such as address spoofing or poisoning attacks. We must do better. DNS names helped normalise access to web site, ENS will help normalise access to web3 apps. The other option is centralised services which hide smart contract addresses from users, but if we're ok with that, why are we building #web3?
0 reply
1 recast
1 reaction
Conor Svensson (csvensson.eth) pfp
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
1 reaction
Conor Svensson (csvensson.eth) pfp
0 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
0 reply
1 recast
1 reaction
Conor Svensson (csvensson.eth) pfp
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
Conor Svensson (csvensson.eth) pfp
0 reply
1 recast
1 reaction
Conor Svensson (csvensson.eth) pfp
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
Conor Svensson (csvensson.eth) pfp
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
0 reaction
Conor Svensson (csvensson.eth) pfp
0 reply
1 recast
1 reaction
Conor Svensson (csvensson.eth) pfp
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
Conor Svensson (csvensson.eth) pfp
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
Conor Svensson (csvensson.eth) pfp
1 reply
1 recast
1 reaction
Conor Svensson (csvensson.eth) pfp
0 reply
1 recast
2 reactions
Conor Svensson (csvensson.eth) pfp
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
1 recast
2 reactions
Conor Svensson (csvensson.eth) pfp
0 reply
0 recast
1 reaction
Conor Svensson (csvensson.eth) pfp
With @enscribe we believe in building solutions that are valuable for the end users of #Ethereum. To reach these users we need to create compelling reasons for developers to utilise our infrastructure. Naming #smartcontracts with #ENS names is win/win for developers and users. Developers can use ENS names to refer to their various contract deployments, and users get to see a name crafted by the deployer of the smart contract that conveys some meaning about the intent of the contract instead of a meaningless hex address. This is the first goal for Enscribe, to see this ENS names for smart contracts come to fruition. The second goal is to further increase trust through decentralised verifications. More is coming on this soon. In the meantime, please start naming your smart contracts using the Enscribe app. https://app.enscribe.xyz/nameContract
0 reply
2 recasts
1 reaction
Conor Svensson (csvensson.eth) pfp
1 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
1 reply
0 recast
1 reaction
Conor Svensson (csvensson.eth) pfp
0 reply
1 recast
1 reaction