01 · The challenge
What needed solving
The client was launching a token where tokenomics were the core marketing story: a portion of every transfer needed to fund a treasury and a portion needed to permanently burn — but the percentages had to be tunable after launch (without redeploying), and a list of exempt addresses had to bypass fees so DEX routers and the treasury itself were not double-taxed.
02 · Our approach
How we framed the work
We started with a discovery sprint to map the user journey, business goals and real constraints. From there we wrote a fixed-scope plan: clear milestones, weekly review gates on a staging URL, and a written exit criterion for every phase. The blockchain space rewards teams that ship — not teams that plan — so we biased the engagement towards working software from week two onward.
03 · The solution
What we built
Single-file Solidity contract (deflation.sol) implementing the ERC20 standard with two independently configurable fees applied on every transfer: a tax fee routed to a treasury address, and a burn fee sent to the zero address (permanently reducing total supply). Both fees are stored in basis points (out of 10000) and adjustable post-deployment via owner-only setters. The treasury address itself is mutable. An excludeFromFee mapping lets the owner whitelist routers, the treasury, the team multisig and any contract that should not be taxed. Standard OpenZeppelin-style ownership + safe arithmetic patterns throughout.
04 · The results
What changed for the client.
Tokenomics tunable post-launch — no redeploy needed to adjust tax or burn percentages
Treasury routing keeps fee accounting on-chain and auditable
Fee exclusions prevent the double-tax footgun on DEX router interactions
Tech stack
Want a similar outcome for your business? We'd love to hear about it.