Self-taught Smart Contract Developer focused on Solidity, EVM-compatible blockchains, and building transparent, security-conscious on-chain systems.
I enjoy designing smart contracts where permissions, incentives, and fund flows are explicit and verifiable. My main focus is learning through hands-on projects, writing tests with Foundry, and improving contract design and security.
A Solidity-based DAO governance and treasury protocol built with Foundry. It explores how a community can manage shared funds through transparent, token-weighted governance rather than relying on a single trusted operator.
- Governance: proposal creation, token-weighted voting, quorum checks, and proposal execution.
- Treasury: ETH deposits and withdrawals authorized through governance.
- Governance token: ERC-20 with Permit, pausing, and role-based access control.
- Merkle airdrop: proof-based token distribution with protection against duplicate claims.
- Testing: Foundry test suites for core contract behavior.
This is an active learning project. Its current design has limitations that would need further review before production use, including real-time token-balance voting rather than historical voting snapshots.
A modular smart contract factory exploring building blocks for transparent and responsible financial applications.
- Modular contract deployment and reusable components.
- Profit-sharing, asset-financing, and custody-oriented modules.
- Solidity development and testing with Foundry.
- Sura-Chain — an on-chain voting system exploring candidate validation and one-vote-per-address rules.
- My ERC-20 Token — explore my repositories for token-contract practice and testing.
- ClassFund — a class fund management project.
- Smart contracts: Solidity, ERC-20, access control, custom errors, events, governance and treasury patterns.
- Development & testing: Foundry (Forge, Cast, Anvil), unit testing, fuzz testing fundamentals, debugging.
- Libraries: OpenZeppelin Contracts.
- Blockchain fundamentals: Ethereum, EVM-compatible chains, transactions, gas, and contract security concepts.
- Additional tools: Git, GitHub, JavaScript, TypeScript.
- Prefer explicit permissions and clearly defined trust assumptions.
- Use tests to validate expected behavior and edge cases.
- Treat security as an ongoing process of threat modeling, review, and iteration—not a claim that a contract is automatically secure.
- Portfolio: saftanasdalihin-site.vercel.app
- LinkedIn: linkedin.com/in/saftanasdalihin
- X: @saftanasdalihin
I’m open to junior smart contract opportunities, internships, and collaborative Web3 projects.
Building transparent systems, one contract and test at a time.