Changelog
what changed, when.

011.0.0

Current 2026-09 · first release · pubspec.yaml version: 1.0.0+1

Included

• Build: six steps (job, identity, extensions, authorities, consequences, review) ending in an unsigned Token-2022 create-mint transaction.
• Seven presets: Membership, Licence, Loyalty points, API credits, Pass / ticket, Reward token, Whitelist token. Every change away from a preset is named with its consequence.
• Eight extension tiles: Transfer fee, Mint close authority, Default account state: frozen, Non-transferable, Interest bearing, Permanent delegate, Transfer hook, Metadata on the mint.
• Consequences report across nine surfaces, with protocol facts and unverified venue policy kept apart.
• Console: Overview, Holders, Issue, Revoke (burn and reclaim), Expiry, Approvals (freeze and thaw), Fees (harvest and withdraw), Authorities (renounce with a typed phrase), Compatibility, Audit trail.
• Settings: network and mainnet gate, your RPC endpoints in the OS keystore, priority fee and compute units, jobs, vocabulary, branding, maintenance mode, published configuration, venue-check register, effective configuration.
• Non-custodial: the app holds no key and signs nothing; enforced by test/no_signing_in_product_test.dart.
• Keyless: no API key or RPC URL in the package.
• On-chain proofs in DOCS/proofs/: all seven presets created and read back, the fee, freeze and delegate flows, the delegate limits and the mainnet simulation gate, against the same Token-2022 program devnet runs.
• Command-line builder: tool/build_mint_transaction.dart prints an unsigned create-mint transaction for checking with other tools.
• Platforms: web, macOS, Android, iOS. 260 automated tests; flutter analyze reports no issues.

Known limitations

• Maintenance mode also hides Settings; turning it off needs the app's stored data cleared (details).
• devnet_rpc_url and mainnet_rpc_url in the settings document are read but not used.
• Support email, website, documentation and terms links are shown in Settings only.
• Settings, venue checks and the audit trail are stored per device.
• No Windows or Linux build.

02Updating

When a new version is released, download it from your CodeCanyon Downloads page. Then:

1. Keep your changes in GitCommit your own version first, so you can compare.
2. Compare and mergeUnzip the new version next to yours and merge the changes, keeping your bundle ID, name and icons.
3. Check

   flutter pub get
   flutter analyze
   flutter test

4. Settings carry overSettings and endpoints are stored on the device, not in the code, so a rebuilt app on the same device keeps them as long as the bundle ID and web address stay the same.