Enscribe pfp

Enscribe

@enscribe

29 Following
7 Followers
Enscribe pfp
Enscribe
@enscribe
Gm fam. Remember hex is for machines not people.
0 reply
1 recast
2 reactions
Enscribe pfp
Enscribe
@enscribe
Gm fam. Remember hex is for machines not people.
0 reply
1 recast
2 reactions
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
Naming #smartcontracts is so satisfying. When you start seeing smart contracts with #ENS names, you can't unsee it. You question why everyone else isn't doing this when it makes #Ethereum apps so much better. Name that contract! app.enscribe.xyz
0 reply
1 recast
3 reactions
Enscribe pfp
Enscribe
@enscribe
Gm to everyone trying to make #Ethereum safer for our users. One of Enscribe's goals is to eliminate contract address spoofing.
0 reply
0 recast
2 reactions
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
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
4 reactions
Enscribe pfp
Enscribe
@enscribe
GM to all the #ENS users and builders!
0 reply
0 recast
2 reactions
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
#smartcontract audits are a critical service provided by a number of providers. However, they are not on-chain. A couple of years ago #ERC7512 https://eips.ethereum.org/EIPS/eip-7512 was proposed as a way to provide this by a number of firms including @osec, @chain-security, @openzeppelin, @hatsfinance and others. However, we're still not seeing them. I'd love to know what some of the stumbling blocks were here, as its an area that we'd love to incorporate support into @enscribe. Alongside naming and contract verifications we believe ready access audits about specific deployed contracts are the missing piece of the puzzle for making apps even safer for users on #Ethereum. Would love to converse more about this either here or at @ethcc IRL if anyone wants to? 🙏
0 reply
1 recast
1 reaction
Enscribe pfp
Enscribe
@enscribe
☀️ GM!
0 reply
0 recast
1 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
This is our end goal. Of course our solution needs to be sufficiently decentralised too, but we need to solve the usability problem for users first. When people look at what we're building it makes complete sense to them, the challenge is getting the attention of the masses when you're not trying to hype a token. We want to build hype around our solution that will set new standards that make #Ethereum safer for all of its users, ensuring it is not only the leading blockchain network for apps, but also the safest. These things can happen, we just need to ensure more people are aware of our mission, and that they don't get distracted by the next shiny protocol on the horizon. We're building for #Ethereum and it's users, and everyday the team wakes up feeling excited for this future. 🫡
0 reply
1 recast
1 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
Simplify, simplify, simplify. Every time we ship a new feature to @enscribe_, how can we simplify it to be useful for #Ethereum users, not developers. So much infrastructure for Ethereum still caters for a technical audience. This is not good enough for mainstream adoption. We're a highly technical team, so are default is to start with the technical solution that we want to see. But we need to abstract away this complexity, and ultimately end up with a visual cue that anyone can understand. We want to get to having the equivalent of a #TLS padlock for users, which along with the #ENS name gives them enough confidence that the app they're interacting with is legit. ctd 👇
1 reply
1 recast
1 reaction
Enscribe pfp
Enscribe
@enscribe
GM GM Get that sweet feeling of seeing your #smartcontract with an #ENS name.
0 reply
0 recast
1 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
Name, verify, audit. If we can get developers and projects performing each of these tasks for deployed #smartcontracts we have an opportunity to improve #UX and make #Ethereum safer for users. When users start seeing this information associated with a contract before they interact with it, it helps them have confidence that what they're dealing with is safe. How much better would it be to see something like this to check a contract, before you do that transaction?
0 reply
0 recast
0 reaction
Enscribe pfp
Enscribe
@enscribe
GM #ENS fam!!!
0 reply
0 recast
1 reaction
Enscribe pfp
Enscribe
@enscribe
GM to all the #Ethereum users out there!
0 reply
0 recast
1 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
With @EthCC on the horizon, the @enscribe team is pumped about having loads of IRL conversations with the #Ethereum community. We'll have great new announcements in the run up, but DM me if you want to chat on contract naming with #ENS or how we can make smart contract apps safer for users. We want to ensure that Ethereum is the safest #web3 ecosystem for users, whilst staying true to its decentralised promises. There are 3 core tenants to achieving this for smart contracts following deployment: 1. Name your smart contract with an #ENS name 2. Verify your smart contract with a service such as @SourcifyEth or a block explorer 3. Provide audit data to your users If all smart contract apps can comply with each of these we believe web3 starts to become safer, whilst also improving #UX. It is win/win for us all with technology that is available right now. Enscribe simply pulls it together to make it easier for developers to do. 🫡
0 reply
1 recast
2 reactions
Enscribe pfp
Enscribe
@enscribe
GM GM GM. Don't forget about your users! They'd definitely prefer to see #smartcontracts with #ENS names over hex addresses.
0 reply
0 recast
1 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
All contracts should have have ENS names. This is our thesis at @enscribe. We want to make it as easy as possible for developers and users to name contracts. Any barriers we encounter along the way are: 1. Validation that we're focussing on a problem worth solving. 2. Stretching the team to find ways to address these barriers. Case in point. There are limitations in the ENS protocol with respect to being able to resolve contract names just from their address. We want to see this fixed for @namechain, so we've started engaging with the community on this point specifically. https://discuss.ens.domains/t/approaches-to-support-setting-primary-names-for-all-contracts/20919 #Web3 is still being built, which is what makes it so much fun to be a part of. There's tons of opportunities to find ways to contribute to it. You just need to go deep to find that area. For us its enabling #smartcontract naming with #ENS and increasing trust for users but keeping it decentralised. What do you want to see solved? 🫡
0 reply
1 recast
2 reactions
Enscribe pfp
Enscribe
@enscribe
GM GM GM GM GM GM GM GM Having #smartcontracts named is inevitable. Don't wait to start naming your contracts.
0 reply
0 recast
1 reaction
Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
Setting a primary name is the gold standard for #smartcontract naming with #ENS. This enables app such as wallets to take a hex contract address and convert it into its ENS name. However, it's not possible currently to set primary names for all smart contracts. This is documented in the @ensdomains docs at https://docs.ens.domains/web/naming-contracts/. This shortcoming is an area that the @enscribe_ team wants to help address, and Nischal from the team has created a post outlining some of our thoughts here https://discuss.ens.domains/t/approaches-to-support-setting-primary-names-for-all-contracts/20919/2. The #ENS community being who they are, have already provided some useful feedback, and we had a really great discussion on the @ensdao ecosystem call yesterday on this. ctd 👇
1 reply
1 recast
2 reactions
Enscribe pfp
Enscribe
@enscribe
GM Fam! Don't stop now, keep naming those #smartcontracts. https://app.enscribe.xyz
0 reply
0 recast
2 reactions