Get desktop application:
View/edit binary Protocol Buffers messages
Contains the initial DKG transcripts for the subnet and materials to construct a base CUP (i.e. a CUP with no dependencies on previous CUPs or blocks). Such CUP materials can be used to construct the genesis CUP or a recovery CUP in the event of a subnet stall.
Initial non-interactive low-threshold DKG transcript
Initial non-interactive high-threshold DKG transcript
The blockchain height that the CUP should have
Block time for the CUP's block
The hash of the state that the subnet should use
A uri from which data to replace the registry local store should be downloaded
Per subnet P2P configuration Note: protoc is mangling the name P2PConfig to P2pConfig
Used in:
Number of quadruples to create in advance.
Per subnet config for advert distribution.
Used in:
The subset of peers to broadcast to, specified in percentage. This is only used when the P2P clients mark the advert as requiring best effort distribution. In future, this fixed percentage could be replaced by dynamic computation of the distribution set size, as a function of subnet size. 0 < best_effort_percentage <= 100
Per subnet P2P configuration Note: protoc is mangling the name P2PConfig to P2pConfig
Used in:
max outstanding request per peer MIN/DEFAULT/MAX 1/20/200
timeout for a outstanding request 3_000/15_000/180_000
max duplicate requests in underutilized networks 1/28/6000
maximum chunk size supported on this subnet 1024/4096/131_072
history size for receive check 1_000/5_000/30_000
period for re evaluating the priority function. 1_000/3_000/30_000
period for polling the registry for updates 1_000/3_000/30_000
period for sending a retransmission request
config for advert distribution. If this field is not specified, the feature is turned off.
Initial non-interactive DKG transcript record
Used in:
Used in:
/ The uri at which the registry store data should be retrieved. The data / must be provided as gzipped tar archive
/ A SHA-256, hex encoded hash of the contents of the data stored at the / provided URI
/ The registry version that should be used for the catch up package contents
Used in:
This feature flag controls, whether canisters of this subnet are capable of issuing threshold ecdsa signatures.
This feature flag controls whether canister execution happens in sandboxed process or not. It is disabled by default.
This feature flag controls whether canisters of this subnet are capable of performing http(s) requests to the web2.
A list of subnet ids of all subnets present in this instance of the IC.
A subnet: A logical group of nodes that run consensus
Maximum amount of bytes per message. This is a hard cap, which means ingress messages greater than the limit will be dropped.
Unit delay for blockmaker (in milliseconds).
Initial delay for notary (in milliseconds), to give time to rank-0 block propagation.
ID of the Replica version to run
The length of all DKG intervals. The DKG interval length is the number of rounds following the DKG summary.
Gossip Config
If set to yes, the subnet starts as a (new) NNS
The type of subnet.
The upper bound for the number of dealings we allow in a block.
If `true`, the subnet will be halted: it will no longer create or execute blocks.
Max number of ingress messages per block.
The maximum combined size of the ingress and xnet messages that fit into a block.
The maximum number of instructions a message can execute. See the comments in `subnet_config.rs` for more details.
The maximum number of instructions a round can execute. See the comments in `subnet_config.rs` for more details.
The maximum number of instructions an `install_code` message can execute. See the comments in `subnet_config.rs` for more details.
Information on whether a feature is supported by this subnet.
The number of canisters allowed to be created on this subnet. A value of 0 is equivalent to setting no limit. This also provides an easy way to maintain compatibility of different versions of replica and registry.
The list of public keys whose owners have "readonly" SSH access to all replicas on this subnet, in case it is necessary to perform subnet recovery.
The list of public keys whose owners have "backup" SSH access to nodes on the NNS subnet to make sure the NNS can be backed up.
ECDSA Config
Represents the type of subnet. Subnets of different type might exhibit different behavior, e.g. being more restrictive in what operations are allowed or privileged compared to other subnet types.
Used in:
A normal subnet where no restrictions are applied.
A more privileged subnet where certain restrictions are applied, like not charging for cycles or restricting who can create and install canisters on it.
A subnet type that is like application subnets but can have some additional features.