Acton Version
1.1.0 (9cf4d1f 2026-05-22)
Command
acton verify --address <> --net mainnet --dry-run
What Happened
When running acton verify, the verification backend fails to resolve import mappings defined in Acton.toml.
The project compiles successfully locally, but verification fails with:
error: Failed to import: path mapping @contracts was not registered
This suggests that the verifier is not using the import mappings from Acton.toml (or they are not being included when sources are uploaded).
Steps To Reproduce
- Create a project with an Acton.toml containing:
[import-mappings]
acton = ".acton"
contracts = "contracts/src"
gen = "gen"
tests = "contracts/tests"
wrappers = "contracts/wrappers"
- Import a contract using a mapped path, for example: (This contract was built without any error)
import "@contracts/bonding-curve/math"
- Verify the deployed contract:
acton verify --address <contract-address> --net mainnet --dry-run --wallet <wallet> --project-root ./
Expected Behavior
The verifier should recognize the import mappings defined in Acton.toml and successfully resolve imports such as:
import "@contracts/bonding-curve/math"
The contract should proceed to verification after local compilation succeeds.
Actual Output
The project compiles successfully, but verification fails during source processing:
→ Collecting source files
✓ Collected 16 source files
→ Sending sources to backend for verification
→ Using backend: https://verifier-mainnet.tonstudio.io/source
Error: Verification failed:
<project>/contracts/src/...:2:8: error: Failed to import: path mapping @contracts was not registered
2 | import "@contracts/math"
| ^^^^^^^^^^^^^^^^^
Acton Logs
Doctor Report
Project Or Input Files
No response
Environment
No response
Acton Version
1.1.0 (9cf4d1f 2026-05-22)
Command
acton verify --address <> --net mainnet --dry-run
What Happened
When running acton verify, the verification backend fails to resolve import mappings defined in Acton.toml.
The project compiles successfully locally, but verification fails with:
error: Failed to import: path mapping @contracts was not registered
This suggests that the verifier is not using the import mappings from Acton.toml (or they are not being included when sources are uploaded).
Steps To Reproduce
Expected Behavior
The verifier should recognize the import mappings defined in Acton.toml and successfully resolve imports such as:
import "@contracts/bonding-curve/math"
The contract should proceed to verification after local compilation succeeds.
Actual Output
Acton Logs
Doctor Report
Project Or Input Files
No response
Environment
No response