Reserve aliases in bulk

See Aliases for what an alias is and the automatic self-alias namespace reservation that mailbox create already gives you. This page covers the sithbit alias create command’s bulk form.

sithbit alias create [<alias>...] [--keypair <keypair>] [--skip-preflight] [--tx-version legacy|v1]

Creates many aliases in one invocation, packing as many CreateAlias instructions into each transaction as fit the selected format’s signed wire size and account/instruction limits. Longer lists are split into successive transactions automatically:

sithbit alias create ceo sales support billing --keypair my_wallet.json

The default format is v1. Use --tx-version legacy for the historical packet format; SITHBIT_TX_VERSION selects the format when no flag is given. Longer names can reduce the number that fit in a chunk.

For 120 distinct, 16-byte aliases, eight legacy transactions become two v1 transactions of 60 alias instructions and 3,902 signed bytes each (including the signature), measured by representative_bulk_creation_reduces_transactions. Chunk sizes vary with the alias list.

The v1_signed_wire_byte_boundary_includes_the_signature fence accepts 4,096 signed bytes and rejects 4,097; the v1_instruction_boundary_splits_without_reordering fence splits 65 instructions into chunks of 64 and one. The v1_address_boundary_splits_real_alias_instructions fence also checks the 64-address limit, including the signer, postoffice and program IDs. An item that cannot fit alone is rejected before submission, even when it follows a valid chunk.

When no aliases are given as arguments, the list is read from stdin — whitespace-separated, so one name per line works — which suits piping in a prepared file:

sithbit alias create --keypair my_wallet.json < aliases.txt

Every created alias points at the signing wallet address, exactly as alias create would — same validation, same lowercasing, same per-alias fee (see Economics) — and duplicates in the list are collapsed before submission. The delegate waiver covers the length-tiered premium fees too: reserving a 1–4 character name costs the operator only rent, which is precisely how premium short names are meant to reach the market — reserved fee-free, then sold on the marketplace or handed off at a chosen price.

Bulk-created names carry no special state: like any alias, they can later be handed to another wallet with alias transfer init — a zero-fee offer the buyer accepts, fee-waived because the delegate is the holder — or closed at any time to reclaim their rent.