Enscribe pfp

Enscribe

@enscribe

35 Following
12 Followers


Enscribe pfp
Enscribe
@enscribe
🌈 GM GMGMGMGM Name that #smartcontract https://app.enscribe.xyz
0 reply
0 recast
1 reaction

Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
$ETH is healthy, but smart contracts are still not user friendly. As we bring all these new users into our ecosystem, we need to stop showing them hex contract addresses. For all those new users being pulled in via the @coinbasewallet super app that has just been announced this will not be an issue. However, once these @base.base.eth users start to move beyond the boundaries of the app, they will need to see something that enables them to trust the smart contracts they're interacting with. The first part of this is ensuring we see ENS names with the smart contracts. The second is decentralised trust metrics, including if the smart contracts have been verified and audited. With all the positive momentum building about #Ethereum, let's make sure we put it to good use, and focus on giving the network and its L2s the #UX and security uplifts they deserve. The ticker is $ETH, the naming protocol is #ENS and it starts with naming smart contracts with @enscribe.
0 reply
1 recast
1 reaction

Enscribe pfp
Enscribe
@enscribe
gm 🫑 If you name your #smart contract with Enscribe, you help eliminate address spoofing and poisoning attacks.
0 reply
0 recast
4 reactions

Enscribe pfp
Enscribe
@enscribe
GM Enscribe is here to fix #smartcontract naming on Ethereum and @base.base.eth. We shouldn't put up with hex contract addresses.
0 reply
2 recasts
5 reactions

Enscribe pfp
Enscribe
@enscribe
GM Enscribe is here to fix #smartcontract naming on Ethereum and @base.base.eth. We shouldn't put up with hex contract addresses.
0 reply
2 recasts
5 reactions

Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
Sentiment around $ETH is very bullish, which is good for everyone. SharpLink Gaming keeps buying ETH further strengthening the narrative around it. Narratives capture attention, and it brings more people to the #Ethereum network as they scratch beneath the surface of this new asset class they have invested in. However, we need to do more to support these new users. Showing hexadecimal smart contract addresses and accounts for users when they try to use Ethereum will make them think this is a platform for technologists, not people. Having a good onboarding experience is so important. Whilst there are many different ways people may onboard β€” perhaps via @CoinbaseWallet or @MetaMask. When they move outside of the garden provided by these wallets, they need some familiarity with what they see. Showing a hex contract address and asking them to sign a transaction against it is not good. ctd πŸ‘‡
1 reply
1 recast
3 reactions

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

Enscribe pfp
Enscribe
@enscribe
GM GM GM GM How are users able to spot scam addresses when all they are shown is hex? Name those smart contracts with your #basenames.
0 reply
0 recast
2 reactions

Enscribe pfp
Enscribe
@enscribe
🌈 GM! πŸ¦„ We won't stop until developers are naming their #smartcontracts
0 reply
0 recast
1 reaction

Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
Making Ethereum safer for users, especially those who are new is paramount. Even if the majority of users start their journey by onboarding with a wallet such as @MetaMask, there will come a point where they want to navigate outside of the wallet ecosystem and explore some DApps. These users will not understand hexadecimal, yet the first time they are confronted with performing a transaction, they will be shown a hexadecimal address and asked if they want to proceed with the transaction. The only indicator of trust they will see is the website upon which the site is hosted on. There will be nothing about the DApp which indicates they can trust this in our current Ethereum garden. This has to change. ctd πŸ‘‡
1 reply
1 recast
3 reactions

Enscribe pfp
Enscribe
@enscribe
GM! Build the future you want to see for @base.base.eth. One day we'll look back on showing hex #smartcontract addresses and question what we were thinking back in 2025.
0 reply
0 recast
1 reaction

Enscribe pfp
Enscribe
@enscribe
We're here to get everyone naming their smart contracts. Would love to see what a @clanker integration could look like.
1 reply
0 recast
0 reaction

Enscribe pfp
Enscribe
@enscribe
GM. Keep based and naming those #smartcontracts on @base.base.eth. Claim an early adopter #POAP whilst you're at it. https://app.enscribe.xyz
0 reply
1 recast
2 reactions

Gramajo pfp
Gramajo
@gramajo.eth
Bullish on naming smart contracts, bots, wallets and everything in between. I just gave a name to my fully onchain gameboy photography collection with enscribe
2 replies
2 recasts
7 reactions

Enscribe pfp
Enscribe
@enscribe
πŸ‘‹ Have no fear, Enscribe is here
0 reply
0 recast
0 reaction

Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
We need decentralised approaches to user safety on Ethereum. There's a number of firms offering centralised services for safety, but this uses the classic web2 value capture where a singular entity ends up with too much influence over whether #web3 apps are considered safe or not. This goes against the ethos of #Ethereum, and results in users being stung by the same things that hamper them with TradFi services such as banking, where they have issues opening accounts or transacting with legitimate services. ctd πŸ‘‡
1 reply
1 recast
2 reactions

Enscribe pfp
Enscribe
@enscribe
✨ Gm everyone ✨
0 reply
0 recast
1 reaction

Conor Svensson (csvensson.eth) pfp
Conor Svensson (csvensson.eth)
@csvensson
The #TLS protocol gave web users a way to securely share information with websites. This was a major step forward for privacy and #UX. Users became accustomed to the padlock icon when sending information to websites which made them feel safer transacting online and the underlying data was encrypted. The TLS model isn't perfect, whilst it does secure communications with websites, users have to implicitly trust the operator of the site they are interacting with. A secure connection is no good if the data is being stored in an unsecured data store. In addition, there is a degree of centralisation with TLS as it relies on Root Certificate Authorities which establish a chain of trust for issuing certificates. However, it was a major innovation as far as bringing more people online is concerned. What does the equivalent look like in #web3? ctd πŸ‘‡
1 reply
2 recasts
2 reactions

Enscribe pfp
Enscribe
@enscribe
GM GM GM #ENS and #Ethereum fam!
0 reply
0 recast
1 reaction

Enscribe pfp
Enscribe
@enscribe
It was all hands to the deck last week making sure our EFP integration was ready for @EthCC. Want to know why this was a no-brainer to add it to Enscribe? Read on πŸ‘€ https://www.enscribe.xyz/blog/efp-in-enscribe
0 reply
0 recast
0 reaction