Conor Svensson (csvensson.eth) pfp

Conor Svensson (csvensson.eth)

@csvensson

58 Following
28 Followers
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
Well worth taking the time to read @sov's take on @base grants and how they've been so successful. Grant funding is a really tough problem in #web3 to get right, and not enough people are really providing thoughtful analysis on the subject.
0 reply
0 recast
3 reactions
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
The creation of @enscribe started with me asking the simple question, how can we provide something that's more like Heroku that enables developers to name their smart contracts at deployment. I always recall the novelty of when I first tried Heroku 10 odd years ago, seeing "quick-beetle-9451.herokuapp..." being deployed. Something similar for #smartcontract developers on #Ethereum seemed like a fun idea to explore. Our first iteration of Enscribe did exactly this — enabled developers to name their smart contracts at deployment. The thing is, developers already have their toolchains for deploying smart contracts, which made the initial proposition of Enscribe less applicable. Hence we then added the ability to name existing contracts, which enables users to name their already deployed contracts. And of course, along the way we added a Heroku name generator too which you can checkout at https://app.enscribe.xyz/nameContract. ctd 👇
1 reply
1 recast
1 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
To make things even easier for developers, we're also working on an integration with Foundry, which should be available soon. We've also realised, that there is optimised view for working with smart contracts and ENS, hence we've also added this to Enscribe. The point is the further we go with Enscribe, the more opportunities we're finding to create new valuable infrastructure to support our goal of making Ethereum safer. Whilst the idea of naming contracts appears relatively straightforward on the surface, there is more infrastructure required to make this something that everyone does by default when they deploy contracts. We don't have all the answers yet, but every day we're finding new challenges and getting better at solving them, and increasing our confidence in what we're building being positive sum for the entire #Ethereum and #ENS ecosystems. 🫡
0 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
With the @ethereumfndn's latest updates on their Protocol strategic goals, it's been great to see improving #UX as being a key pillar of this. That being said, we're in the fortunate position that we can significantly improve Ethereum UX and security right now, simply by getting developers to name their smart contracts with #ENS. No R&D or protocol upgrades are required to get us there. All it needs is for #smartcontract developers to head to https://app.enscribe.xyz/ and start naming their contracts. Once naming becomes the default behaviour, hex smart contract addresses for users will rightly start raising red flags, which would be right. Users should not be exposed to hex in the UX.
0 reply
1 recast
2 reactions
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
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
Conor Svensson (csvensson.eth)
@csvensson
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
Conor Svensson (csvensson.eth)
@csvensson
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
Conor Svensson (csvensson.eth)
@csvensson
There is no downside to naming #smartcontracts, only upside for the entire #Ethereum community. @enscribe makes it easier, and also provides information such as if contracts have been verified via services such as @sourcifyeth. We need to increase trust for our users, so please name that contract!
0 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
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
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
The english word for naming your #smartcontract with #ENS is @enscribe.
0 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
Every problem we hit, is another opportunity to make things better. We keep hitting problems and challenges which makes us confident that we're focussing on a hugely underserved area of the Ethereum and ENS ecosystems. If you want a preview of some of these cool new features, we should be presenting on the @ensdao ecosystem call on Thursday. It's a great space to see what all the builders are currently up to. 🙏🏻
0 reply
0 recast
1 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
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
Conor Svensson (csvensson.eth)
@csvensson
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
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
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
Conor Svensson (csvensson.eth)
@csvensson
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
Conor Svensson (csvensson.eth)
@csvensson
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
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
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
Conor Svensson (csvensson.eth)
@csvensson
At the moment, we're standing in the middle of the ENS village, shouting NAME YOUR SMART CONTRACTS at the top of our voices, but we need to transition to the middle of the Ethereum megacity, in the epicentre of where the entire community of developers and users hangs out and can see us broadcasting our message. Once there, the first part of our mission will be complete. However, we want to make Ethereum the safest blockchain in all of #web3 for its users, and naming smart contracts is just the first step of this journey.
0 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
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
Conor Svensson (csvensson.eth)
@csvensson
However, convincing people to take time out of their already hectic schedules is a big ask, so we're going to start creating some fun incentives in this regard. Most importantly, we want to insert ourselves into the developer workflows being used to deploy #smartcontracts. We're making great progress here and have started collaborating with a leading team to this end, but we're not ready yet to share more. In the meantime, head to https://app.enscribe.xyz/nameContract to try naming one of your smart contracts with #ENS names. @base, @lineabuiild and #ethereum mainnet all supported!
0 reply
0 recast
0 reaction