Building secure smart contracts, DeFi protocols, ZK-ready systems, cross-chain infrastructure, and production-grade Web3 applications.
Smart contract engineer focused on secure EVM systems, DeFi infrastructure, tokenized assets, ZK-oriented development, protocol integrations, and blockchain application architecture.
Main focus areas include Solidity smart contracts, protocol security, testing, deployment workflows, upgradeable architecture, DeFi primitives, cross-chain messaging, and emerging ecosystems such as Starknet, Aztec, Noir, Move, and Sui.
- Smart contract architecture for EVM-based protocols
- DeFi, RWA, staking, vault, escrow, and tokenization systems
- ZK-oriented smart contract and circuit-adjacent development
- Cairo and Starknet smart contract development
- Aztec and Noir ecosystem exploration
- Move-based smart contract development for Sui
- Upgradeable contracts and storage-layout-safe development
- Gas-efficient Solidity implementation
- Security-focused protocol design
- Foundry and Hardhat testing workflows
- TypeScript deployment and integration scripts
- Chainlink oracle and cross-chain integrations
- Subgraph indexing with The Graph
| Area | Focus |
|---|---|
| Solidity | Smart contracts, DeFi systems, protocol architecture |
| Testing | Foundry, Hardhat, TypeScript-based test suites |
| Security | Audit readiness, access control, edge-case analysis |
| DeFi | Vaults, staking, OTC flows, tokenized assets |
| Cross-chain | Messaging, synchronization, oracle-based flows |
| ZK | Noir, Aztec, proof-oriented application logic |
| Starknet | Cairo contracts, Starknet ecosystem development |
| Move / Sui | Object-based smart contract architecture |
| Indexing | The Graph, subgraphs, blockchain analytics |
- Security first: every contract should be designed around failure modes.
- Tests are part of the architecture, not an afterthought.
- Explicit state transitions are better than hidden assumptions.
- Gas optimization should never compromise correctness.
- Upgradeability requires strict storage layout discipline.
- Production code should be readable, testable, and audit-friendly.
- Protocol logic should be simple at the interface level and strict internally.
- DeFi protocol smart contracts
- ERC20 / ERC721 / ERC1155 systems
- ERC4626-style vault logic
- OTC and escrow-based settlement flows
- Tokenized real-world asset infrastructure
- Staking and reward distribution mechanisms
- Access control and permissioned protocol logic
- Chainlink price feed integrations
- Cross-chain synchronization flows
- Subgraph indexing and blockchain analytics
- Cairo and Starknet smart contracts
- Move / Sui smart contract logic
- Noir and Aztec ecosystem research
- Smart contract testing, debugging, and audit preparation
- Secure DeFi protocol architecture
- ZK applications and privacy-preserving systems
- Starknet and Cairo development
- Aztec and Noir-based smart contract workflows
- Move-based blockchain systems
- Cross-chain infrastructure
- Tokenized real-world assets
- Smart contract security and formalized testing