Content
@
https://ethereum.org
0 reply
0 recast
0 reaction
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)
@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
