Nischal Sharma | nischal.eth
@nischalsh11
Followers
124
Following
216
Media
2
Statuses
85
Co-Founder @enscribe_ | Blockchain Developer @web3labs | Oper Source Maintainer @web3j and a member of @devtoolsguild
Pune
Joined June 2024
Hardhat just got smarter. Enscribe now works directly inside your Hardhat workflow so you can name contracts as easily as you deploy them. No switching tools, no extra steps, just clean developer flow. π More in post 2
1
3
10
Big new update from us β our Hardhat plugin is live. What other build tools do you need integrations with for contract naming?
Have you ever wished you could name your smart contracts with ENS names using your build tools? Now you can with the Enscribe @HardhatHQ plugin.
0
3
11
As ENS expands to more networks, @NamehashLabs helps Enscribe scale. One integration means multi-chain ENS naming stays seamless for users.
0
3
11
Smart contracts are the future of finance, be really good at reading and writing them.
15
13
141
Somethingβs cooking π A new version of the @enscribe_ contract is on the way, now with ENSIP-19 support and batch contract naming. Stay tuned! @ensdomains
1
1
9
Simplicity is the name of the game with @enscribe_. Eliminating hex contract addresses makes Ethereum safer for user and improves UX. It just needs one change in behaviour. Developers need to name their smart contracts. That's it, but the upside for Ethereum is huge.
3
5
13
318
492
2K
just got fired from Paxos. my job was to count decimal places and typecast uint256s. looking for work starting in January 2026000000000000.
190
246
4K
π¨ $PYUSD $300 Trillion Mint π¨ . @Paxos stablecoin contract accidentally minted $300 TRILLION on-chain, burned it, then minted another $300 billion. All controlled by a single EOA. We studied the incident in-depth so you don't have to. Here's what actually happened: The
At 3:12 PM EST, Paxos mistakenly minted excess PYUSD as part of an internal transfer. Paxos immediately identified the error and burned the excess PYUSD. This was an internal technical error. There is no security breach. Customer funds are safe. We have addressed the root
2
3
8
You can enhance security further using @enscribe_ by naming your contracts. So even if your Dapp is compromised, the user when signing the transaction can verify name in wallet if the contract he is trying to interact with is legit or not and belongs to correct ENS domain.
$3M was drained in May 2025 via DNS hijacking. Attackers compromised the registrar and redirected the real domain to a fake site. ENS + IPFS + Filecoin could have prevented this: β’ No registrar to hack β’ Content hash verification β’ Distributed storage Filecoin Pin launches
0
2
2
Now with @enscribe_'s @safe integration it's easier than ever to name your smart contracts. Just add Enscribe to your Safe Apps as demonstrated below.
2
5
24
Amazing to see. Which major DAO is going to be next to name their contracts? π€ Is this something we can predict on @Polymarket?
I just executed my first ENS proposal! The proposal set primary names for the ENS token, DAO wallet, and endowment. ENS is now employing best practices around naming contracts, the contracts are easier to identify, and names will resolve on sites that list them
1
6
35
Sign me, @walletconnect Just applied to play at the @Uniswap Cup β½
unicup.uniswap.org
Uniswap Cup 2025: A single-day soccer tournament, featuring your favorite teams in crypto.
0
1
1
I just executed my first ENS proposal! The proposal set primary names for the ENS token, DAO wallet, and endowment. ENS is now employing best practices around naming contracts, the contracts are easier to identify, and names will resolve on sites that list them
28
24
172
Basenames can now be your primary identity across L2s! Powered by ENSIP-19, we performed a one time migration on users' behalf, making all basenames compliant. Users don't have to act to migrate π«‘ Dev tools that support ENS integration now work with basenames too!
80
105
671
There seems to be some drama/misunderstanding around this, so let me try to clarify First of all, nobody is taking away your .eth names, ever For context: "grace period" is a 90 day period after a name expires where it kinda just sits there, giving a name owner some leeway in
more info on ENSv2 just dropped mostly dev centric info, but folks should be aware that grace period for names is going away once ENSv2 goes live
21
10
69
Make your trip to Devconnect even more worth it, and catch one of these stops on the way: π§π· @ethlatam SΓ£o Paulo: Nov 8β9 π§π· @eth_floripa Nov 11-12 π²π½ @ethereum_mexico Monterrey: Oct 30-Nov 2 π¦π· @JoinEdgeCity Patagonia: Oct 18βNov 15 π¦π· @FundingCommons Oct 24βNov 14 π¦π·
26
38
254
Amazing to see. Momentum is building around contract naming. We need other DAOs to follow suit. What say you @UniswapFND, @aave, @arbitrum, @skyecosystem, @CurveFinance, @LidoFinance?
1
5
14
Quorum reached for the proposal to set primary names for core ENS DAO contracts! β
Attention delegates! New proposal sets primary names for core ENS DAO contracts, demonstrating best practices and full use of the ENS protocol. Vote now β https://t.co/0IuRQjEGuA
4
4
29