Smart Contract Engineer | Great architecture is clear. I design the system, secure the logic, and explain the 'why'. Send me a DM.
Joined August 2022
- Tweets 1,098
- Following 127
- Followers 252
- Likes 1,438
346 Photos and videos
Pinned Tweet
1 Dec 2025
Smart contracts handle real value. If the math is wrong, the money vanishes.
Most tutorials teach you syntax. They don't teach you solvency.
I spent the last few weeks building a decentralized, algorithmic stablecoin from scratch.
Here is the engineering journey behind the code. 👇
4
2
41
1,470
Jun 1
Recently, I have been using the @contractdotdev workflow to test my smart contracts against live mainnet state.
It completely removes the usual infrastructure friction, and this quick demo video explains exactly how it works.
youtu.be/tkB2h38yrWw
@kenny_io
1
6
54
Jun 1
PS: There is some background noise in the video, and my editing skills are... let's just say I'm much better at writing Solidity. 😄
Go ahead and enjoy the video.
1
2
12
Jun 1
For those who prefer reading over trying to ignore my background noise, I wrote a full technical breakdown of this exact workflow here:
dev.to/binnadev/smart-contra…
@NeeleshW3
2
19
May 31
PS: There is some background noise in the video, and my editing skills are... let's just say I'm much better at writing Solidity. 😄
Go ahead and enjoy the video.
1
1
4
May 31
For those who prefer reading over trying to ignore my background noise, I wrote a full technical breakdown of this exact workflow here: dev.to/binnadev/smart-contra…
1
8
May 25
If you spend enough time in the tech space, you will eventually hear the word "DevRel".
They speak at conferences, write tutorials, and the community usually seems to love them.
But what exactly do they do? Is it just marketing for coders? Is it just customer support?
👇🏾
1
1
3
47
May 24
Smart contracts turned the blockchain into a trust-minimized execution layer. We write them with extreme care because immutability is unforgiving.
But writing secure code is only half the battle. The other half? Fighting your testing infrastructure. 🧵👇
1
3
70
May 24
What if there was a workflow that completely eliminated this friction?
✅ Zero Faucet fatigue
✅ Zero 3rd-party RPC setups
✅ Zero mock contract simulations
✅ Seamless mainnet state & Chainlink integration
It sounds too good to be true.
1
1
32
May 24
I don't want you to just take my word for it.
I wrote a full technical breakdown on how to adopt this workflow and instantly improve your development lifecycle.
Stop fighting infrastructure. Read the full journey here:
🔗 dev.to/binnadev/smart-contra…
1
19
May 1
A few days ago, I thought about something simple:
If three people count money together, you trust the result more than if one person counts it alone.
Not because people are perfect but because agreement reduces error.
That idea shaped my work this week. 🧵
1
6
46
May 1
Now that the foundation is built and unit tests are done, the next step is invariant testing.
In simple terms
an invariant is a rule that must always stay true no matter what happens
For example
no matter how many times people confirm payments
no matter the order they sign
1
3
22
May 1
...the system must never accept the same payment twice
and it must never move funds without enough approvals
Invariant testing is me trying to break those rules on purpose
from every angle possible
to prove that they cannot be broken
1
2
20
Apr 29
The full breakdown is here for anyone who wants to understand what production-grade security actually looks like: dev.to/binnadev/series/39005
👇
Apr 29
I published the entire engineering process in a five-part series.
From UUPS proxies to audit-ready threat models. The contract is deployed and verified on Polygon mainnet.
The full five-part engineering breakdown is on dev.to: dev.to/binnadev/series/39005
1
3
102
Apr 29
A green test suite on a broken smart contract is worse than no tests at all.
It gives you false confidence while holding real money.
Most tutorials teach you to write isolated functions.
1
6
41
Apr 29
A vulnerable kiosk dispenses cash before marking the receipt as used. Reentrancy works the same way.
If you understand the "refund kiosk glitch", you know why updating your database before dispensing the cash is the only way to prevent reentrancy attacks.
1
1
16
Apr 29
I published the entire engineering process in a five-part series.
From UUPS proxies to audit-ready threat models. The contract is deployed and verified on Polygon mainnet.
The full five-part engineering breakdown is on dev.to: dev.to/binnadev/series/39005
1
134