Conor Svensson (csvensson.eth) pfp

Conor Svensson (csvensson.eth)

@csvensson

68 Following
38 Followers
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
$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
Conor Svensson (csvensson.eth)
@csvensson
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
Conor Svensson (csvensson.eth)
@csvensson
They will be familiar with reading the DNS names which are associated with the site they are accessing, an #ENS name is a natural extension of this, which they should see against any smart contracts they interact with. Great strides are being made with ENS adoption by networks including @base.base.eth and @linea. But the tools are not there for the builders to easily name their contracts. This is one area we are addressing with Enscribe. However, we also need to ensure that the users feel safe before they sign these transactions in their wallets, and this is the other area we are razor focussed on with Enscribe — as we need decentralised trust mechanisms for smart contracts. It's not good enough having centralised services that dictate if smart contracts are "safe". If we want a decentralised network, we need decentralised services protecting our users, otherwise we end up with #web2 all over again. TLDR; name your smart contracts with ENS to improve Ethereum UX and security.
0 reply
0 recast
1 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
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
Conor Svensson (csvensson.eth)
@csvensson
I'm convinced it's only a matter of time before the idea of removing hex contract addresses from the #Ethereum user experience takes hold. To stay true to Ethereum's values, this has to be done in a decentralised way, and we are convinced that using #ENS to this end is the best route forward. If we don't eliminate hex contract addresses, users will end up relying on platforms to curate different apps, which will require islands of centralisation, where the trust shifts to the platforms instead of the creators of the DApps. Then we end up with app stores just like we have now which end up being dominated by 2-3 entities who capture the majority of the value. We must do better, and it starts with developers naming their smart contracts to facilitate a decentralised trust model for DApps.
0 reply
0 recast
1 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
Making Ethereum safer for users, especially those who are new is paramount. Even if the majority of users start their journey by onboarding with a wallet such as @MetaMask, there will come a point where they want to navigate outside of the wallet ecosystem and explore some DApps. These users will not understand hexadecimal, yet the first time they are confronted with performing a transaction, they will be shown a hexadecimal address and asked if they want to proceed with the transaction. The only indicator of trust they will see is the website upon which the site is hosted on. There will be nothing about the DApp which indicates they can trust this in our current Ethereum garden. This has to change. ctd 👇
1 reply
1 recast
3 reactions
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
Addressing this may not be as sexy as launching a new protocol or infrastructure play, but its such a crucial building block for users in web3 that I refuse to let it go. #ENS can replace those hex contract addresses with human-readable names which will make sense. In addition if we have decentralised check marks against the addresses it could come a long way in supporting users. But we need to build to get there, which we keep doing at @enscribe_. The question I have is what other teams and people here are committed to this vision of making Ethereum the safest blockchain for users?
0 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
Once devs get used to naming their smart contracts they won't look back. Users will become accustomed to this too, and they'll stop wanting to touch contracts that haven't got #ENS names setup properly. There will be snowball effect, and Ethereum #UX will be so much better.
0 reply
0 recast
1 reaction
Gramajo pfp
Gramajo
@gramajo.eth
Bullish on naming smart contracts, bots, wallets and everything in between. I just gave a name to my fully onchain gameboy photography collection with enscribe
2 replies
2 recasts
7 reactions
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
It's unlikely that we can create a truly permissionless standard for smart contracts that is safe for users, but we can ensure it's sufficiently decentralised. This I believe is the optimum of where we need to get to. If deployers of #smartcontracts can name, verify and audit their contracts, and we can capture this information from multiple sources. Approaches to naming and verification are well established against specific contract versions and audit firms share their audit reports. But there is often a disconnect between contract audits and the live version of smart contracts. This is where we have a gap that needs to be addressed. Hence we're focussing some of our efforts here with @enscribe.
0 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
We need decentralised approaches to user safety on Ethereum. There's a number of firms offering centralised services for safety, but this uses the classic web2 value capture where a singular entity ends up with too much influence over whether #web3 apps are considered safe or not. This goes against the ethos of #Ethereum, and results in users being stung by the same things that hamper them with TradFi services such as banking, where they have issues opening accounts or transacting with legitimate services. ctd 👇
1 reply
1 recast
2 reactions
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
I truly believe we need to simplify as much as possible to ensure users have a binary choice as to if a contract application is safe or not. Scores puts too much cognitive load on users, it has to be a binary decision. Whilst TLS is not exactly the same as what we're trying to achieve, it's a good proxy for the power of making users feel safe online, and we really need to find something equivalent for #Ethereum. This will ensure that it Ethereum is not only the default, but also safest decentralised network for users, which is something I believe to be of great importance to cement its foundation as the world's global settlement layer.
0 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
We have privacy protocols coming online such as @aztecnetwork which provide full privacy for users. However, at @enscribe what we want to create is something that is as powerful to users as the TLS padlock, which will tell them that the #smartcontract they are interacting is issued by the organisation or individual they believe it to have been. One part of this is to ensure teams are naming their smart contracts with @ensdomains. There are also standard procedures such as smart contract verifications via services such as @sourcifyeth that help here. Having attestations from contract audit firms would also be beneficial. But is this enough? ctd 👇
1 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
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
Conor Svensson (csvensson.eth)
@csvensson
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
Conor Svensson (csvensson.eth)
@csvensson
Although most of the time the @enscribe team are heads down building, attending events such as @EthCC are so valuable for getting feedback on what we've built, our plans for the future and finding new collaborators. We're building for the #Ethereum-centric future we believe in which is why Ethereum-focussed events like #EthCC and @devcon are so useful for our team and many others. Thank you to @jerome and your team for putting on another fabulous #EthCC, and we look forward to being back in Cannes next year! 🙏🙏🙏
0 reply
0 recast
2 reactions
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
So much positive news this last few days at @EthCC. But just because we have new institutions coming onboard, we mustn’t stop focusing on improving #UX and making #Ethereum the safest it can be for its users too. 🫡
0 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
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
Conor Svensson (csvensson.eth)
@csvensson
I'm biased as a life-long #southpark fan, but this is one subject where we should all be listening to Mr Makey, mkay. Our mission with @enscribe is to make #Ethereum the safest blockchain for users. This informs everything we do. #namethatsmartcontract
0 reply
0 recast
2 reactions
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
Day one of @EthCC and keen to connect with folk aligned with our missions: - @devtoolguild help sustain and increase coordination between devtools teams and protocol/R&D - @enscribe make Ethereum safer for users by eliminating hex contract addresses and establishing verification standards for apps Plus claim a bonus #POAP if you get your #smartcontract named with Enscribe while at EthCC.
0 reply
0 recast
1 reaction