token.wind

Fungible-token contract for WIND on Vexanium/Antelope.

The final contract exposes only:

• issue
• retire
• transfer
• open
• close

There is no burn, create, or new administration action. The WIND token already exists, so create is intentionally not exposed by the final contract.

Token policy

• Symbol: 8,WIND
• Maximum supply after migration: 12000000.00000000 WIND
• Existing circulating supply is preserved during migration.
• issue follows the standard Antelope flow: it increases supply only, never max_supply, credits the issuer, and transfers inline when to is not the issuer.
• retire reduces circulating supply without changing max_supply.

One-time max-supply migration

The currently deployed legacy issue increases both supply and max supply. That behavior is used once, before deploying this final build:

1. Remove all delegated accounts from token.wind@active, retaining only the owner key and token.wind@vex.code.
2. Read the current WIND supply and calculate 12,000,000 - current_supply.
3. In one atomic transaction, issue that delta to token.wind and retire the same delta.
4. Verify that circulating supply is unchanged and max supply is exactly 12000000.00000000 WIND.
5. Deploy this final contract.

No setmax action or hardcoded database mutation is used.

Build

Requires Antelope CDT 4.x (cdt-cpp):

make

The command updates token.wasm and token.abi.

Deploy

cleos -u https://api.windcrypto.com set contract \
  token.wind . token.wasm token.abi -p token.wind@active

Always verify the stat row and final ABI after deployment.