Hamza @hamza_web3dev

Solidity developer and Smart Contract Engineer. Prioritizing security. Joined January 2026

Tweets

35
Followers

5
Following

47
Likes

32

Hamza @hamza_web3dev

a month ago

@suraj_sharma14 builder

1 0 2 11 0

View Details

The fix: an epoch counter. Every time the ownership set changes (add or remove), the epoch increments. Approvals are tagged with the epoch they were made in. When executing, only approvals from the current epoch are counted. Governance change= clean slate. No stale votes survive.

0 0 0 4 0

View Details

Hamza @hamza_web3dev

a month ago

The problem: → Owner A approves a price update → Owner A gets removed →Does that approval still count? Without a fix: yes. A removed owner's vote persists — which breaks the trust model entirely. An owner added after the vote also shouldn't influence past decisions.

1 0 0 6 0

View Details

Hamza @hamza_web3dev

a month ago

The Epoch Pattern inside a MultiSig Contract What happens if an owner approves a transaction — then gets removed before it executes? This is the governance race condition I had to solve. Here's the Epoch Pattern 🧵

1 0 0 11 0

View Details

Hamza @hamza_web3dev

2 months ago

@LinaMahrouch Great idea especially with the upcomings esports worlds!

0 0 1 18 0

View Details

Hamza @hamza_web3dev

2 months ago

@imokokok27 Exactly—that’s the direction I took as well. I implemented a multisig-secured oracle for the USD/MAD rate, so every update has to be approved by multiple parties before it’s pushed on-chain. Appreciate the suggestion 🤝

1 0 0 13 0

View Details

Hamza @hamza_web3dev

2 months ago

Chainlink doesn't have a MAD/USD price feed. So I had to build a two-layer oracle system to peg a stablecoin to the Moroccan Dirham. Here's how it works 🧵

2 0 0 26 0

View Details

Hamza @hamza_web3dev

2 months ago

It's basically a lightweight Gnosis Safe — built from scratch in Solidity to understand exactly how multisig governance works under the hood. Repo: github.com/hamza-web3dev/…

0 0 0 20 0

View Details

Hamza @hamza_web3dev

2 months ago

No single address can unilaterally change the price or governance. This matters because the peg depends entirely on this feed being honest. The pattern: every sensitive operation creates a pending transaction. Owners vote. Once threshold is reached, execution happens.

1 0 0 15 0

View Details

Hamza @hamza_web3dev

2 months ago

If you need a trusted price feed with no single point of failure, you need a multisig. Here's the ownership model I built for my custom USD→MAD oracle 🧵

1 0 0 19 0

View Details

Hamza @hamza_web3dev

2 months ago

That governance problem is what I solved next. Repo: github.com/hamza-web3dev/…

0 0 0 9 0

View Details

Hamza @hamza_web3dev

2 months ago

The lesson: when your oracle dependency doesn't exist, you don't give up — you design around it. Real DeFi protocols do this all the time for exotic assets. The security question shifts from "is Chainlink reliable?" to "who controls the custom feed?"

1 0 0 16 0

View Details

Hamza @hamza_web3dev

2 months ago

Repo: github.com/hamza-web3dev/… Next: reading MakerDAO + Liquity audit reports to find what breaks in systems like this. #Solidity #DeFi #Foundry #Web3Security

0 0 0 10 0

View Details

Hamza @hamza_web3dev

2 months ago

Built following @CyfrinUpdraft 's advanced DeFi course — won't pretend otherwise. But knowing WHY the 200% ratio exists, why liquidators get a 10% bonus, why OracleLib matters — that's the real learning.

1 0 0 8 0

View Details

Hamza @hamza_web3dev

2 months ago

I built a decentralized stablecoin: WETH/WBTC collateral → mint DSC (USD-pegged). 200% collateral ratio enforced on-chain. Liquidations fully programmatic. No admin keys. Here's the 3 things that actually taught me something 🧵