About the service
I write smart contracts in TEAL / PyTeal for the Algorand blockchain — from simple stateless signatures to full stateful applications. TEAL is bytecode executed by the Algorand virtual machine (AVM); PyTeal is a Python framework that generates it. I'm proficient in both tools, so your logic turns out compact, cheap to execute and protected against classical errors.
What I can build:
— ASA tokens: creation, configuration, clawback, freeze and reserve roles, opt-in and transfer restrictions.
— Stateful contracts (applications) with global and local state, box storage and careful protection of updates or deletion.
— Groups of atomic transactions that link payments, asset movements and application calls so everything settles together or not at all.
— Escrow, vesting, staking, auctions, vaults and simple DeFi primitives.
Each contract I deliver with commented PyTeal source, compiled TEAL, deployment scripts (Python SDK or algokit) and a test suite that runs in a local sandbox or on TestNet. I check for typical vulnerabilities: rekey and close-remainder-to abuse, unchecked fee and sender fields, group size assumptions and re-entrance in inner transactions. You get a brief description of on-chain logic so your team can maintain it. Describe the needed behavior — and I'll correctly port it to the AVM.
What I can build:
— ASA tokens: creation, configuration, clawback, freeze and reserve roles, opt-in and transfer restrictions.
— Stateful contracts (applications) with global and local state, box storage and careful protection of updates or deletion.
— Groups of atomic transactions that link payments, asset movements and application calls so everything settles together or not at all.
— Escrow, vesting, staking, auctions, vaults and simple DeFi primitives.
Each contract I deliver with commented PyTeal source, compiled TEAL, deployment scripts (Python SDK or algokit) and a test suite that runs in a local sandbox or on TestNet. I check for typical vulnerabilities: rekey and close-remainder-to abuse, unchecked fee and sender fields, group size assumptions and re-entrance in inner transactions. You get a brief description of on-chain logic so your team can maintain it. Describe the needed behavior — and I'll correctly port it to the AVM.
