Broker & Subnet Lifecycle

This page explains how a broker initializes, registers, and maintains a subnet using the provided admin tools.

Subnets are broker-defined. A subnet includes the broker itself, any authorized workers, and their linked plugins. The broker is responsible for enforcing staking, access, and lifecycle rules.

Lifecycle Steps

• Start the broker with its identity configured in conf.yaml
• Stake KNS using tlp admin stake
• Link stake to the broker's identity with tlp admin link
• Submit subnet metadata with tlp admin update-subnet
• Authorize each worker identity with tlp admin authorize
• Optionally assign user credit with tlp admin credit

Each broker enforces its own policy. Timeleap only provides the tooling—usage is fully up to each subnet.

Subnets can revoke access, rotate identities, and impose slashing or uptime requirements as needed.