What is the vault address?
The vault address is fixed before deploy. We use CREATE2. The address comes from three things. The deployer factory. A salt. And the contract code with its constructor args.
Address: 0x7a8e1CaEbBA81F41d1c3a5BDb4D2D7Cb2b75d198.
This is the planned vault address. No code has been deployed there yet. It is not a token address.
| Input | Value |
|---|---|
| Chain | 4663 |
| Factory | 0x4e59b44847b379578588920cA78FbF26c0B4956C |
| Salt | keccak256("squeeze-radar/gap-treasury/v1") |
| Explorer | Blockscout |
The file deployment/vault/address.json holds the result. It is made by pnpm vault:address. The API reads it. VAULT_ADDRESS in the env can override it.
The same code, salt, and args always give the same address. A change to any one gives a new address.
Sample
Section titled “Sample”The API returns derivation: "create2". That means the address came from the file. configured means it came from the env. unset means there is none.