set_whitelist
Call v210 → current #4Sets the list of addresses allowed to deploy contracts.
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with set_whitelist, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: WhitelistedCreators, and finally post-dispatch where ExtrinsicSuccess is emitted and fees are settled.
Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
Click items to navigate. Pan and zoom to explore.
Used by: developers
The Big Picture
Restrict contract deployment to approved addresses during EVM bootstrap.
Use Cases
- Control deployments
- Prevent spam
- Permissioned deployment
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | new | Vec<H160> Vec | new: list of 20-byte address (Ethereum-style) |
Permissions
Origin
Unknown
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Admin/root privileges
- Valid H160 addresses
Effects
Storage Modified
Postconditions
- WhitelistedCreators updated
Code Examples
import { createClient, Binary } from "polkadot-api";
import { getWsProvider } from "polkadot-api/ws";
import { sub } from "@polkadot-api/descriptors"; // generated by: npx papi add sub -w wss://entrypoint-finney.opentensor.ai:443
const client = createClient(getWsProvider("wss://entrypoint-finney.opentensor.ai:443"));
const api = client.getTypedApi(sub);
// Build set_whitelist call (typed, named args)
const new_ = [] as [];
const tx = api.tx.EVM.set_whitelist({
new: new_,
});Runtime Info
- Pallet Index
- 22
- Call Index
- 4
- First Version
- v210
- Current Version
- v411