# pending-children (/docs/query/pending-children)

`set_children` normally does not take effect immediately: the proposal is
parked here until `cooldown_block`, then promoted to the finalized set
that the `children` read returns. On subnets whose subtoken is not yet
enabled the cooldown is skipped and children apply immediately, so
nothing lingers here. `children` is (proportion, child\_ss58) pairs with
u64-normalized proportions, matching the `children` read.

**Category:** Delegation

## Parameters [#parameters]

| Parameter     | Type    | Description                                   |
| ------------- | ------- | --------------------------------------------- |
| `hotkey_ss58` | string  | Parent hotkey whose pending children to list. |
| `netuid`      | integer | Subnet to query.                              |

## CLI [#cli]

```bash
btcli query pending-children --hotkey <ss58|name> --netuid <integer> --json
```

## Python [#python]

Namespace method (autocomplete, signature help):

```python
import bittensor as bt

sub = bt.Subtensor()
result = sub.delegation.pending_children(hotkey_ss58="5F...", netuid=1)
```

Or dispatch by name, as an agent would:

```python
result = sub.read("pending_children", hotkey_ss58="5F...", netuid=1)
```

Async is the same surface awaited: `async with bt.Subtensor() as client:`.

## On-chain implementation [#on-chain-implementation]

* Storage [`SubtensorModule.PendingChildKeys`](/code/pallets/subtensor/src/lib.rs#L1374)

Every file is browsable under [/code](/code) exactly as built into the runtime.