I am a junior Blockchain student with a strong focus on smart contract security and testing. I have hands-on experience deploying contracts on Avalanche Fuji and building FISCO BCOS networks. My core strength is edge-case testing: I independently designed 17 boundary testing scenarios (including nonce replay, expired intents, and unauthorized payees), achieving 17 passed / 0 failed using Foundry. I am highly detail-oriented, comfortable with Linux/Python, and looking for a remote Junior Smart Contract Developer or Web3 QA internship.
| Period | Title | Company |
|---|---|---|
AgentGuard402 is an on-chain policy guardrail for x402 machine payments, built with Foundry and validated by 17 passing tests (`forge test`: 17 passed / 0 failed). It addresses a critical gap in the x402 protocol: while x402 enables AI agents to pay for resources autonomously, it has no built-in mechanism to control who an agent pays or how much it spends. The project enforces spending rules at the smart-contract level before settlement via three on-chain components: `MockUSDC3009` (an EIP-3009 test stablecoin), `AgentPolicyRegistry` (per-transaction caps, daily limits, payee allowlists, expiry, and policy status), and `PolicyVault` (fund custody with identical pre-check and execution logic). The agent never holds tokens or pays gas—it only signs EIP-712 payment intents, while a facilitator submits the transaction and an owner retains full withdrawal control. The 17 Foundry tests cover the full policy enforcement surface: exceeding per-tx caps, out-of-allowlist payees, daily limit resets, nonce replay, expired policies, impersonated signatures, amount tampering, frozen/inactive policies, and preview-vs-execution consistency. Beyond unit tests, the contracts are deployed on Avalanche Fuji (chainId 43113) with real on-chain evidence: a 16-scenario end-to-end demo comprising 4 approved payments and 12 blocked attempts, all reproducible via Snowtrace. For a full walkthrough, clone the repo and run `cd contracts && forge test` to reproduce the 17/17 pass result locally. | Independent Smart Contract Developer | Hidden |
hy do programmers prefer dark mode? Because light attracts bugs.