Conor Svensson (csvensson.eth) pfp

Conor Svensson (csvensson.eth)

@csvensson

56 Following
29 Followers
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
We're also looking a contract audits and mechanisms to incorporate support for them in @enscribe. We'll be sharing more on this shortly. However, I'd love to hear what people here think we can do. We want us to get to a place where we have the equivalent of a TLS padlock for users of #web3 apps that provide a visual cue that can tell them if what they're interacting with is safe. It should also be done in a decentralised manner, so that whatever service is designed, can still thrive regardless of if Enscribe exists or not. What are the key metrics we can use? So far we're thinking: 1. Contract named with ENS 2. Contract verified 3. Verifiable audits against live contracts What's missing?
0 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
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
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
We're mission driven with @enscribe, hence it's important we see more #smartcontracts being given #ENS names over time. At the current time a tiny (<0.1%) of smart contracts are being given ENS names. Getting to 1% would be an amazing improvement. We believe longer term 5-10% is a good target, as this is closer to the proportion of smart contracts that have been verified by services such as @sourcifyeth. Public dashboards via @dune.eth will help here. I did experiment with this previously, but they still need further tweaking for accuracy. https://dune.com/csvensson/ens-contract-naming We want to deliver impact with Enscribe, and ensuring we can measure that impact to #Ethereum is critical to our mission. 🫡
0 reply
0 recast
1 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
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
Conor Svensson (csvensson.eth)
@csvensson
1/ Increasing trust and improving the #UX for users of Ethereum, by eliminating hex contract addresses and replacing them with #ENS names and trusted verifications with @enscribe. 2/ Something launching soon focussed on brining dev tooling together within the ecosystem, which dtg.wtf gives you a hint about...🤫 Price moves make many people happy, but seeing more apps and real users will make everyone happier. The Big Lebowski is one of my favourite movies btw.
0 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
Price is leading the #ETH narrative today, which is good to see following all the FUD that X has been full of this past year. This doesn't change the fact that we can't move away from our core goals for #Ethereum. Since 2016 I've been trying to contribute as best I can. Some of these initiatives have been more successful than others, but nothing changes my conviction in the technology and our community, which is what keeps me here. Personal highlights of this journey include: ctd...
1 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
- Back in 2016 built a mining rig to contribute to the decentralisation of the network - Created #Web3j which is now almost 9 years old and still going strong https://github.com/web3j/web3j. - Launched web3labs.com to build infra for #Ethereum - Spent 3 years with @entethalliance and their members on their client specification work - Wrote a book about blockchain —http://amzn.to/3DO4ZL5 - Transitioned to staking to support #themerge - Created @chainlens blockchain explorer - Recently launched @enscribe I keep building because I believe in Ethereum — it's the new internet/the world's global settlement layer/the Linux of our generation/etc.... I'm now focussed on two mission-driven initiatives. ctd...
1 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
Secondly there's those who simply don't have faith in web3 due to the prevalence of scams. They need ways to have confidence in the apps they're working with. Kind of like trust scores, but we need something that doesn't burden users with additional cognitive load when deciding on whether to accept a transaction or not. A trust score means different things to different users. Is a 75% score safe? Or should I only accept 99%? It's too vague. Better is a binary indicator that means it it either should be safe to transact with an app or not. Just like the #TLS padlock used in #web2. We want to appeal to both classes of user, and we're building for both 🛠️.
0 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
I believe UX and trust in #web3 apps are intertwined. We're in a place where there's two types of users we need to onboard. Firstly in those who need a simple, intuitive UX when working with apps. Showing hex to these users (such as a contract address) is really bad, and there's no reason why they should be exposed to this. They will likely be familiar with web addresses, so an #ENS name is somewhat intuitive for them, and sends a trust signal. ctd...
1 reply
0 recast
1 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
Secondly there's those who simply don't have faith in web3 due to the prevalence of scams. They need ways to have confidence in the apps they're working with. Kind of like trust scores, but we need something that doesn't burden users with additional cognitive load when deciding on whether to accept a transaction or not. A trust score means different things to different users. Is a 75% score safe? Or should I only accept 99%? It's too vague. Better is a binary indicator that means it it either should be safe to transact with an app or not. Just like the #TLS padlock used in #web2. We want to appeal to both classes of user, and we're building for both 🛠️.
0 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
With @enscribe we're working on changing #smartcontract developer behaviour. We want naming contracts to be as natural to the development process as the deployment itself. Our starting point with Enscribe has been to build a UI to enable #ENS users to easily name their contracts. But we know that isn't enough for developers who use dev tools such as Foundry to deploy their contracts. That's why we're working on dev tool integrations for our service, to ensure that we can ensure we reach the developers and build pipelines performing the contract deployments. Getting to the source of contract deployments is core to our mission. #AccelerateENS #namesmartcontracts
0 reply
1 recast
1 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
2/ The next step from here is the creation of trusted verifications where users can easily see additional steps taken by the contract deployers to ensure they're safe for their users. Everyone is talking about improving the safety and #UX of #web3, but not enough people are focussing on what we can do right now to achieve this, instead of chasing the next big upgrade or infra project. It's not to say that those things are bad, but our industry is disproportionally focussed on these future things, in part because they typically come with nice token models, and also so much of web3 is inhabited by technologists. And we love shiny new things.
1 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
3/ If we make Ethereum safer, it's more appealing to real users. The whole #crypto and web3 industries are currently tarnished in the eyes of everyday people, due to the prevalence of scams, rug pulls and bad actors. We need to change this to bring more people onto the next generation of the internet, and it all starts with using what we already have available to make things safer for our users.
0 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
1/ I truly believe that's there's a lot of work we can do right now to make #Ethereum and its ecosystem safer for users. Naming smart contracts with @enscribe is the first step in this direction. It's a no-brainer that we should all be referring to #smartcontracts by their #ENS names instead of hex contract addresses.
1 reply
0 recast
1 reaction
Enscribe pfp
Enscribe
@enscribe
We believe #ethereum #wallet #ux needs to change. Users shouldn’t be exposed to contract addresses. Enscribe solves this with @ensdomains. Come join our community if you’re passionate about fixing this 👉 https://discord.gg/8QUMMdS5GY
0 reply
1 recast
2 reactions
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
@dwr.eth a couple of my team based in Romania and India are facing real issues joining Farcaster. Hitting in app purchases not supported during the signup flow. Anyone there that can assist?
0 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
Slight delay on our part, but @chainlens explorer is now here and sharing updates on all the killer features we’re shipping 🚀
0 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
Loved learning about @acetcg today at #EDCON2024. The team have done a fantastic job of capturing the heroes, villains, memes and more from #web3 into a TCG format. Excited to play!!!
0 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
This is something David Deutsch discussed in his book The Beginning of Infinity — Chapter 10 A Dream of Socrates
0 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
I hate every time I get given new 2FA recovery codes as it means printing out multiple copies that then have to be secured in different physical locations. Digital security is such a hassle.
0 reply
0 recast
0 reaction