Conor Svensson (csvensson.eth) pfp

Conor Svensson (csvensson.eth)

@csvensson

68 Following
38 Followers


Conor Svensson (csvensson.eth) pfp
$ETH is healthy, but smart contracts are still not user friendly. As we bring all these new users into our ecosystem, we need to stop showing them hex contract addresses. For all those new users being pulled in via the @coinbasewallet super app that has just been announced this will not be an issue. However, once these @base.base.eth users start to move beyond the boundaries of the app, they will need to see something that enables them to trust the smart contracts they're interacting with. The first part of this is ensuring we see ENS names with the smart contracts. The second is decentralised trust metrics, including if the smart contracts have been verified and audited. With all the positive momentum building about #Ethereum, let's make sure we put it to good use, and focus on giving the network and its L2s the #UX and security uplifts they deserve. The ticker is $ETH, the naming protocol is #ENS and it starts with naming smart contracts with @enscribe.
0 reply
1 recast
1 reaction

Conor Svensson (csvensson.eth) pfp
Before a user undertakes any type of transaction on #Ethereum, they should have visual information conveyed to them which tells them how safe the contract is likely to be. Multiple data sources should be used, a centralised platform is not the answer. Smart contract audits and information in blockchain explorers are the standard sources power users will look at. Regular users won't bother. This needs to be fixed. This is why developers must @enscribe_ their contracts. Users will rely on Enscribe to surface the information they need from multiple decentralised sources. Ultimately we want this to bubble up into a single icon that can provide users with a binary yes/no decision on if they should go ahead with the transaction. Effectively TLS padlock for web3. But there's lots we need to build to get there.
0 reply
0 recast
0 reaction

Conor Svensson (csvensson.eth) pfp
Sentiment around $ETH is very bullish, which is good for everyone. SharpLink Gaming keeps buying ETH further strengthening the narrative around it. Narratives capture attention, and it brings more people to the #Ethereum network as they scratch beneath the surface of this new asset class they have invested in. However, we need to do more to support these new users. Showing hexadecimal smart contract addresses and accounts for users when they try to use Ethereum will make them think this is a platform for technologists, not people. Having a good onboarding experience is so important. Whilst there are many different ways people may onboard β€” perhaps via @CoinbaseWallet or @MetaMask. When they move outside of the garden provided by these wallets, they need some familiarity with what they see. Showing a hex contract address and asking them to sign a transaction against it is not good. ctd πŸ‘‡
1 reply
1 recast
3 reactions

Conor Svensson (csvensson.eth) pfp
0 reply
0 recast
1 reaction

Conor Svensson (csvensson.eth) pfp
1 reply
1 recast
3 reactions

Conor Svensson (csvensson.eth) pfp
0 reply
0 recast
1 reaction

Conor Svensson (csvensson.eth) pfp
1 reply
1 recast
2 reactions

Conor Svensson (csvensson.eth) pfp
The #TLS protocol gave web users a way to securely share information with websites. This was a major step forward for privacy and #UX. Users became accustomed to the padlock icon when sending information to websites which made them feel safer transacting online and the underlying data was encrypted. The TLS model isn't perfect, whilst it does secure communications with websites, users have to implicitly trust the operator of the site they are interacting with. A secure connection is no good if the data is being stored in an unsecured data store. In addition, there is a degree of centralisation with TLS as it relies on Root Certificate Authorities which establish a chain of trust for issuing certificates. However, it was a major innovation as far as bringing more people online is concerned. What does the equivalent look like in #web3? ctd πŸ‘‡
1 reply
2 recasts
2 reactions

Conor Svensson (csvensson.eth) pfp
So much great builder energy at @EthCC last week. Really enjoy connecting with everyone IRL, but it's a tiring week with non-stop networking and chatting from the early morning to late evening. It was great to hear how many people are onboard with what we're doing with @enscribe. @limes.eth and the @ensdao put on a fantastic event on Wednesday night. It was super cool to connect with so many members of the #ENS ecosystem in person after chatting every week on the ecosystem calls. Also got to meet a ton of new people building for ENS and a number of the delegates. Asl always there's a ton of follow ups which need to happen, and opportunities to explore new collaborations which will keep driving the Ethereum and ENS ecosystems forward. Excited for what happens next, but also relieved we have some downtime before the next major event, @devcon later in the year!
0 reply
1 recast
4 reactions

Conor Svensson (csvensson.eth) pfp
0 reply
0 recast
2 reactions

Conor Svensson (csvensson.eth) pfp
0 reply
0 recast
0 reaction

Conor Svensson (csvensson.eth) pfp
Everyone we speak to @EthCC is onboard with our mission to make #Ethereum the safest #web3 network for users. Given that Ethereum is the global settlement layer, we believe this is a pretty important mission for its users, both current and future. Getting everyone to name their #smartcontracts with @enscribe is a start β€” imagine if users always see v3.myapp.eth instead of hex contract addresses, this is a massive win built on @ensdomains. Plus right now you get an exclusive #POAP if you're one of our early users. However, the bigger picture for us is establishing a new decentralised trust standard for user-facing smart contracts. This is what will make Ethereum apps safer for all. If you want to unpack our approach hit me up at the conference, would love to share our thinking β€” feedback has been super positive, so we believe we're on the right track.
0 reply
1 recast
3 reactions

Conor Svensson (csvensson.eth) pfp
0 reply
0 recast
2 reactions

Conor Svensson (csvensson.eth) pfp
0 reply
0 recast
1 reaction

Conor Svensson (csvensson.eth) pfp
0 reply
0 recast
0 reaction

Conor Svensson (csvensson.eth) pfp
0 reply
0 recast
0 reaction

Conor Svensson (csvensson.eth) pfp
0 reply
1 recast
3 reactions

Conor Svensson (csvensson.eth) pfp
It's an uphill battle getting people to care about #smartcontract naming with #ENS. There is no precedent for it, so no-one does it. Yet #Ethereum #UX completely sucks for users if they are shown a hex contract address. @enscribe_ is creating a new category of product for Ethereum β€” decentralised trust for smart contracts via naming and verifications. Which effectively I want to end up being the equivalent of a #TLS padlock for Ethereum apps. Being first in a category can be great, as you lead the conversation, but it's also hard as most people don't give a shit about what you're trying to do. We're not building something that will make people rich, we're building something that will make Ethereum safer and improve UX. Having, lasting positive impact in Ethereum is what matters to me, not trying to profit as much as I can from it. ctd πŸ‘‡
1 reply
1 recast
3 reactions

Conor Svensson (csvensson.eth) pfp
Hey everyone, wanted to share @enscribe with the community. With Enscribe, we're addressing a fundamental problem faced by nearly every Ethereum user: confusing and unreadable smart contract addresses. Enscribe makes it easy for developers to name their smart contracts using their #Basenames. Using the Enscribe app, available at https://app.enscribe.xyz, you can deploy new contracts with Basenames set automatically, or locate and name your already deployed contracts with them. For instance, using Enscribe we configured our own contract primary names at - v0.app.enscribe.base.eth - v0.app.enscribe.basetest.eth You can also view information about Basenames in Enscribe with the search, such as @jesse.base.eth's at https://app.enscribe.xyz/explore/8453/0x849151d7D0bF1F34b70d5caD5149D28CC2308bf1 Our mission is to eliminate hex from the user experience, and we’d love to see the Base community using their Basenames to name their contracts!
0 reply
0 recast
1 reaction

Conor Svensson (csvensson.eth) pfp
0 reply
1 recast
1 reaction