Own review alongside development
Make security review part of the team’s delivery responsibility, not an afterthought at the end of a launch.
Case 09 · Staking, tokens & NFT launches
A Web3 launchpad and gaming ecosystem with SFUND staking, tokens and NFT collections.
Seedify supports Web3 project launches, with SFUND staking giving holders access to launch opportunities. I led its blockchain developers and security reviews from 2022 to 2023. My delivery covered SFUND staking security, the GMFAM token, two NFT collections and contract release tooling.
Delivered staking security work, the GMFAM token and two NFT collections. Historical project scale: $114M+ in staking TVL covered by the work and 2,472 ETH in collection volume.
An ecosystem with staking, fungible tokens and NFT launches needs repeatable delivery and review practices across contracts with different asset and permission models.
Led the development team and owned the security review process across contract deliveries.
Worked on SFUND staking security and the GMFAM token launch.
Deployed two NFT collections and implemented CI/CD for smart contract releases.
I reviewed the SFUND staking contracts, including the behavior that protects deposited tokens and governs access to privileged operations.
SFUND staking → contract security reviewHistorical scope: $114M+ staking TVL, as recorded in my CV.I worked on the GMFAM token launch as part of the blockchain team’s delivery. The deployed token and its source can be inspected on Ethereum.
GMFAM → Ethereum contractThe public contract is linked below.I deployed two NFT collections: Seedworld Vanguards and The Mounts of Seedworld. The public collection pages show the resulting assets.
Collection contracts → deployed NFTsCollection volume is historical project scale, not personal revenue.I managed blockchain developers, owned security review and implemented CI/CD for smart contract deployments across these deliveries.
Reviewed contracts → repeatable deploymentMy role combined team leadership with implementation.Make security review part of the team’s delivery responsibility, not an afterthought at the end of a launch.
Introduce CI/CD for contract deployments to reduce manual variation between releases.
Public collection artifact associated with the ecosystem work.
Current OpenSea page for the collection identified in my engagement record.
Role and historical figures are from my CV. Public collection and token links provide ecosystem context.
TVL and collection volume refer to the historical engagement period, not current balances or personal revenue.