Multi-Asset FA2 Token on Tezos: Full-Cycle Development

Standard ERC-1155 on Ethereum is a proven choice for multi-asset tokens. But gas fees during peak hours reach tens of dollars per transaction, and gas limits restrict logic complexity. For projects where every cent counts, Tezos with its FA2 (TZIP-12) standard becomes a pragmatic alternative. One contract manages both fungible and non-fungible tokens, and the Michelson architecture minimizes gas costs. Gas savings reach 95% compared to Ethereum. We have developed dozens of FA2 contracts for DeFi protocols and NFT collections—here we share proven approaches.

FA2 (TZIP-12) is a standard that unifies fungible tokens and NFTs in one contract. Unlike ERC-1155, it uses granular operator management and built-in on-chain views. This simplifies integration with Tezos exchanges and marketplaces.

Why FA2 is more cost-effective than ERC-1155?

Instead of deploying one contract for ERC-20 and another for ERC-721, FA2 requires one contract with arbitrary token_id. This architectural decision saves gas during distribution and simplifies management. Here is a comparison with ERC-1155:

FA2 outperforms ERC-1155 by a factor of 10 in gas costs for a typical transfer operation. At an XTZ price of around $1, an FA2 transaction costs cents, whereas on Ethereum it costs from $5 to $50. This makes Tezos attractive for high-frequency transfers and micropayments.

How to implement multi-asset in one contract?

One contract for three token types: governance (fungible), utility (fungible), and an NFT collection (non-fungible). The key is token_id in the ledger. Use big_map for large collections to avoid paying gas for storing the entire table in memory.

In one project, we combined a governance token (token_id=0), a utility token for staking (token_id=1), and an NFT collection of 10,000 avatars (token_id=1000-10999). All in one contract. This reduced gas by 3x compared to ERC-1155 and simplified the exchange logic between tokens.

import smartpy as sp

@sp.module
def main():
    class FA2Token(
        FA2_ERRORS.Fungible,
        FA2_ERRORS.Admin,
        FA2_ERRORS.MintFungible,
        FA2_ERRORS.BurnFungible,
        sp.Contract
    ):
        def __init__(self, admin, metadata, token_metadata):
            FA2_ERRORS.Admin.__init__(self, admin)
            FA2_ERRORS.Fungible.__init__(self, {
                "ledger": sp.big_map(tkey=sp.TRecord(owner=sp.TAddress, token_id=sp.TNat), tvalue=sp.TNat),
                "operators": sp.big_map(tkey=sp.TRecord(owner=sp.TAddress, operator=sp.TAddress, token_id=sp.TNat), tvalue=sp.TUnit),
            })
            self.init_metadata("metadata", metadata)
            self.data.token_metadata = sp.big_map({0: sp.record(token_id=0, token_info=token_metadata)})
            self.data.supply = sp.big_map({0: 0})
        
        @sp.entrypoint
        def mint(self, to_, token_id, amount):
            sp.verify(sp.sender == self.data.admin, "NOT_ADMIN")
            key = sp.record(owner=to_, token_id=token_id)
            current = self.data.ledger.get(key, default=0)
            self.data.ledger[key] = current + amount
            self.data.supply[token_id] = self.data.supply.get(token_id, default=0) + amount

The standard transfer entrypoint includes built-in operator checks (see SmartPy documentation).

What does turnkey FA2 development include?

Our engineers with 10+ years of blockchain experience provide a full package:

• Smart contract code in SmartPy with unit tests (>=95% coverage).
• TZIP-16 and TZIP-21 metadata (IPFS if needed).
• Gas optimization: using big_map for ledger, minimizing storage reads.
• Integration with wallets (Temple, Kukai) via Taquito.
• Deployment guide (Ghostnet for testing, Mainnet for production).
• 2 weeks of post-launch support.

Contact us for an estimate: fill out the form on the website—we'll respond within a day.

Comparison of FA2 with the previous FA1.2 standard

FA2 is an evolution that solves the limitations of FA1.2.

Importance of auditing FA2 contracts

Even simple FA2 contracts can contain errors: reentrancy, incorrect operator handling, faulty allowances. Auditing an FA2 contract includes checking for these vulnerabilities, formal verification (SmartPy tests), and stress tests on Ghostnet. We guarantee passing audits on critical errors—this reduces the risk of fund loss and reputational damage.

Workflow

1. Discovery (2-3 days)—token specification, metadata, operators.
2. Development (1-3 weeks)—coding in SmartPy, unit tests (>=95% coverage).
3. Integration (1-2 weeks)—connecting via Taquito to Temple/Kukai.
4. Audit—check for reentrancy, gas exhaustion, formal verification.
5. Deployment—testing on Ghostnet, then Mainnet with verification on TzKT.

Estimated timelines: basic contract from 1 week, with customization up to 6 weeks. Get a consultation: describe your requirements in the form on the website—we'll calculate timelines and cost individually.

Our advantages

We have developed 30+ smart contracts on Tezos, including DeFi protocols, NFT marketplaces, and gamified projects. We guarantee: passing formal verification, no critical errors (Slither/Tezos), and full documentation. All work is done under a contract with a fixed budget.

Evaluate your project: describe your requirements in the form on the website—get timelines and budget within 1 day.

Token Development: ERC-20, Tokenomics, Vesting

We’ve seen more rekt tokens than we can count — not because the code was broken, but because the economic assumptions were naive. A token that doesn’t collapse from inflation in six months, where governance actually works, and vesting can’t be bypassed through delegation tricks — that’s real engineering. We build under that standard.

How We Avoid Common ERC-20 Pitfalls

ERC-20 standard has nine functions. Complexity starts with extensions:

ERC-20Permit (EIP-2612) — gasless approve via signature. User signs permit(owner, spender, value, deadline, v, r, s) off-chain, spender calls permit() + transferFrom() in one transaction. Removes separate approve step. Risk: signature can be intercepted — need deadline and nonce checking. We always implement EIP-712 typed structured data to prevent signature malleability.

ERC-20Votes (EIP-5805) — snapshot balances for governance. Checkpoint system stores balance history by block number. getPastVotes(address, blockNumber) returns balance at proposal creation, not current. Prevents flash loan governance: can't borrow tokens and vote in one transaction.

Rebasing tokens (stETH, Ampleforth) — balanceOf changes automatically through internal shares ratio. High integration complexity: most DeFi protocols don't work correctly with rebasing without non-rebasing wrapper. We've deployed wrappers that decouple balance from share price for Uniswap compatibility.

Fee-on-transfer tokens — percentage cut on every transfer. Breaks AMM calculations: pool receives less than expected. Uniswap v2/v3 don't support natively — needs special pair/router. We’ve built custom routers that handle fee-on-transfer tokens without reverting.

Why Tokenomics Sustainability Matters More Than Excel

Tokenomics isn't Excel table summing to 100%. It's incentive model that either works long-term or creates selling pressure killing the project.

Emission Schedule and Inflation — Fixed supply (Bitcoin model) works for store-of-value, but for utility tokens you need controlled inflation. Inflationary model (like Ethereum post-Merge) generates new tokens to incentivize participants. Key balance: emission should be <= value captured by protocol. If protocol earns $100k/month but emission is $500k/month in market value — constant selling pressure inevitable. We model these scenarios using Python simulations with cadCAD for complex systems.

Supply Distribution — No universal formula. Principle: no single entity >33% voting power at launch. Otherwise governance is fiction.

What Are the Most Critical Vesting Contract Mistakes?

Linear vesting with cliff is standard for team and investors. cliff is the period after TGE with zero availability. After cliff: linear unlock until duration. Typical implementation errors we catch in audit:

• Revocable vesting without timelock — owner can revoke immediately. Solution: revocation through multisig + governance vote with 7-day delay.
• Cliff doesn't block governance rights — with ERC-20Votes, recipient can delegate voting power from day one even if tokens aren't unlocked. We explicitly separate voting power from claim logic.
• No emergency pause — if vesting contract vulnerability discovered, need ability to pause claims. Pausable + timelock on unpause.

We’ve seen a project where the cliff was set to 0 by mistake — team could dump immediately. Our fuzz tests catch such edge cases before deployment.

Why Is Liquidity Bootstrapping Crucial for Token Launch?

Launch mechanics are critical. Three main approaches:

• Balancer LBP — temporary pool with high initial token weight (90/10 project-token/USDC) that automatically decreases to 50/50 over days. Creates downward price pressure preventing bot buys at one price. After LBP liquidity moves to permanent pool.
• Fjord Foundry — specialized platform for LBP and fair launches. Less operational overhead than direct Balancer integration.
• Uniswap v3 with limited range — add liquidity in narrow range around initial price. High capital efficiency but requires active range management.
• TWAMM — mechanics for gradual large-order sales without slippage. Implemented in FraxSwap.

LBP is 3-5x better than standard AMM listing for price discovery; we’ve seen fair launches with 50% less initial dump compared to direct Uniswap listings.

Governance Tokens and Voting Mechanics

OpenZeppelin Governor is the standard. Modular: GovernorVotes for counting, GovernorTimelockControl for timelock execution, GovernorSettings for adjustable parameters. Quorum is minimum percentage of supply for voting validity. Compound set quorum at 400k COMP (4% supply). We set quorum dynamically based on historical participation to avoid apathy or whale capture.

Flash loan governance attack — attacker borrows tokens via flash loan, delegates to self, creates proposal or votes, returns tokens. ERC-20Votes with block-based snapshot completely blocks this: must have tokens at snapshot creation moment, not voting moment.

Delegation — small holders often don't vote. Liquid delegation (like Optimism) lets delegate voting power to addresses without transfer. Critical for protocols with many passive holders.

Token Development Stack

Contracts: Solidity 0.8.x, OpenZeppelin Contracts 5.x (ERC20, ERC20Permit, ERC20Votes, Governor, TimelockController, TokenVesting).
Tokenomics audit: Python models with emission/demand simulation, cadCAD for complex systems modeling.
Deployment and management: Foundry scripts, Gnosis Safe for treasury, OpenZeppelin Defender for automation.
Analytics: Dune Analytics for on-chain metrics, Token Terminal for protocol revenue.

What’s Included in the Work (Deliverables)

• Tokenomics model with stress tests (bear market, whale exit, governance capture)
• Contract development with Foundry fuzz tests (gas optimization, reentrancy tests, overflow checks)
• Audit summary and list of edge cases covered
• Deployment scripts with Gnosis Safe admin keys
• Documentation for future upgrades and maintenance
• 30-day post-launch monitoring support

Process

1. Tokenomics design — supply model, allocation, emission schedule, vesting. Stress-test scenarios.
2. Contract development — ERC-20 + extensions, vesting, governance. Foundry fuzz tests on vesting calculations, governance thresholds.
3. Audit — special attention on governance attack vectors, vesting bypass, permit replay attacks. We use Slither and Echidna for formal verification.
4. LBP / launch — choose mechanics, set parameters, monitor first 24 hours.
5. Post-launch — monitor supply distribution via Dune, governance participation metrics, treasury management.

Timelines

• ERC-20 with permit and basic governance: 2–3 weeks
• Vesting contract with revocation and cliff: 2–4 weeks
• Full governance (Governor + Timelock + Token): 4–7 weeks
• Token + LBP + governance + vesting: 8–14 weeks

We can estimate your project within 24 hours after discussing requirements. Contact us to start the conversation — no obligation, just a technical chat about your token model. Get a detailed proposal tailored to your tokenomics and compliance needs.