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
Seedify
Staking, tokens and NFT launches needed the same review discipline.
I led blockchain developers and the contract security review process across staking, token launches and NFT releases, while remaining hands-on with implementation and deployment.
Result
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.
My part
What I did
An ecosystem with staking, fungible tokens and NFT launches needs repeatable delivery and review practices across contracts with different asset and permission models.
01
Blockchain team leadership
Led the development team and owned the security review process across contract deliveries.
02
Staking & token work
Worked on SFUND staking security and the GMFAM token launch.
03
NFTs & release tooling
Deployed two NFT collections and implemented CI/CD for smart contract releases.
How it worksSimplified walkthrough. No live transactions.
A repeatable path from implementation to release
Product + contract design
Translate staking, token or collection requirements into explicit contract behavior and permissions.
Requirements → contract mechanicsEach asset surface has its own assumptions.Solidity + team delivery
Build the required contract components while coordinating implementation across the blockchain team.
Solidity implementationLeadership stays connected to the code being shipped.Security process
Apply contract review as part of delivery, including the paths that can affect staked assets or privileged operations.
Implementation → security reviewReview belongs in the release process.Deployment + CI/CD
Use deployment tooling and repeatable release processes to ship the contracts and collections.
Reviewed contracts → repeatable deploymentThe deployed artifact must match the reviewed delivery.Trade-offs
Decisions I made
Make releases repeatable
Introduce CI/CD for contract deployments to reduce manual variation between releases.
Links and records
See the work
Public collectionThe Mounts of Seedworld
Public collection artifact associated with the ecosystem work.
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.