Hanane Bendisari

@AvaxDevelopers yes would love that, thanks :)

@Jeux_Code Nice. You might want to check out our Builders Hub—you’ll find tools, docs, and resources all in one place. We’ve also got an active dev community if you're looking for feedback or collaboration. Let me know if you're interested, and I can share the link.

A contract with no reverts is a contract that hides its bugs. Make your contract scream when something’s wrong. Silence is where the exploits live. #Solidity #SmartContractSecurity #Foundry #Web3Dev #BuildInPublic

@AvaxDevelopers Still exploring! The protocol is fully modular and testnet-ready, so I’m considering Avalanche C-Chain, Polygon, and Arbitrum for the initial launch. Let me know if Avalanche has any preferred tooling or incentives for milestone-based escrow infra — would love to align!

@Jeux_Code Nice. Are you deploying to a specific chain or still exploring options?

require() isn’t defensive. It’s declarative. It’s how your contract defines what is not allowed. Write it like a threat model. #Solidity #SecurityMindset #SmartContracts #Web3Build #Foundry

Logic that "should never happen" is exactly what an attacker will trigger. If your contract can't handle absurd input, it's already vulnerable. #Solidity #SmartContractSecurity #Foundry #Web3Tips #BuildInPublic

Your first audit is writing tests that make you sweat. If everything passes too fast, you’re not ready. #Solidity #AuditMindset #Foundry #SmartContractTesting

Don’t try to be clever. Try to be readable. Auditors hate clever. #Solidity #CleanCode #SmartContractAudits #Web3Build

Don’t forget onlyOwner is not access control. It’s a placeholder. Build real permission layers. #SmartContracts #AccessControl #Solidity #Web3Dev

Reentrancy isn’t just about ETH. It’s about calling back anything at the wrong time. #Reentrancy #SoliditySecurity #SmartContracts #Web3Tips

@AvaxDevelopers I am. An escrow protocol with milestone based payments. Check it out 😊 github.com/HananeBendisar…

@Jeux_Code Well said. Are you working on any smart contracts right now?

No matter how clean your logic is, if your contract isn't testable — it's not trustworthy. Your tests are the real audit. Your assertions are your insurance. #Solidity #SmartContractTesting #Foundry #AuditReady #Web3Dev

Your fallback function should never do more than it has to. It’s not a feature. It’s a liability. #Solidity #Fallback #SmartContractSecurity #Web3Dev

Never trust msg.sender blindly. Proxies, relayers, and weird context will mess with you. #Solidity #SecurityTips #SmartContracts #Web3Build

The fallback function is a trap. Keep it tight, or keep it out. It’s the foot in the door for every edge case you forgot. Most contracts don’t need one. #Solidity #FallbackFunction #Web3Security #SmartContracts #BuildInPublic

Avoid magic numbers. Use constants. Use enums. Use your brain. #Solidity #CodeReadability #BestPractices #Web3Dev

Storage layout matters. Especially when you upgrade contracts. One mistake = corrupted state. #Solidity #UpgradeableContracts #Web3Security #SmartContractTips

A contract with no reverts is a contract that hides its bugs. Make your contract scream when something’s wrong. Silence is where the exploits live. #Solidity #SmartContractSecurity #Foundry #Web3Dev #BuildInPublic

“It works” ≠ “it’s safe”. Web3 is not about running code — it’s about defending logic. #Solidity #SecurityMindset #SmartContracts #Web3Dev

Gas optimization is cool. But clarity > gas. And security > both.#Solidity #GasTips #SmartContractDesign #Web3Security

If your tests only follow the happy path, they’re not tests. They’re a warm bath. #Solidity #SmartContracts #Web3Build #Foundry

Write comments for the attacker. Explain what you think is secure. Then try to break it. #SmartContractSecurity #SolidityTips #AuditMindset