@
0 reply
0 recast
0 reaction

Enscribe pfp
Enscribe
@enscribe
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
0 reaction