Shard Services (Group 10)
The live shard-switch surface for preparing destination serial numbers, switching value across shards, and picking up the resulting coins.
Overview
Group 10 is the live shard-conversion family. It includes both guided flows where the RAIDA provides destination serial numbers and explicit flows where the client supplies them.
Live commands
| Code | Name | Purpose |
|---|---|---|
| 170 | switch_shard_sum | Switch into another shard using a summed proof flow. |
| 171 | pickup_coins | Collect the result of a prior shard-switch operation. |
| 172 | get_sns | Get destination serial numbers for shard conversion. |
| 174 | switch_shard_sum_with_sns | Switch shards using sum proof with caller-supplied SNs. |
| 175 | switch_shard_no_sum_with_sns | Switch shards with supplied SNs and without the sum variant. |
| Code | Minimum body size | Developer note |
|---|---|---|
| 170 | 45 bytes | Summed switch flow. |
| 171 | 43 bytes | Pickup step for completed shard switching. |
| 172 | 39 bytes | Serial-number discovery/allocation step. |
| 174 | 50 bytes | Summed flow with caller-supplied SN list. |
| 175 | 52 bytes | Explicit-SN flow without the sum variant. |
170 — switch_shard_sum
switch_shard_sum performs a shard switch using a summed proof model. It is appropriate when the client wants a compact conversion request.
Use this variant when the RAIDA should derive or manage the destination serial-number set rather than taking a fully explicit list from the client.
171 — pickup_coins
pickup_coins retrieves the output generated by a shard-switch workflow. Use it as the completion step after a successful switch request.
This is the read-side completion command for previously prepared conversion output.
172 — get_sns
get_sns returns destination serial numbers that the client can use in follow-up shard-switch operations.
Use this command when the client needs the RAIDA to allocate or reveal the destination SNs before submitting a switch request.
174 — switch_shard_sum_with_sns
switch_shard_sum_with_sns is the explicit-SN version of the summed shard-switch flow.
The caller provides the destination SN list directly instead of first asking the server for it.
175 — switch_shard_no_sum_with_sns
switch_shard_no_sum_with_sns is the explicit-SN variant for flows that do not use the sum model.
The server source documents this request/response pair directly because it is the most explicit shard-switch packet in Group 10.
Live surface note
Command 173 is intentionally absent here because it is not part of the current audited live dispatch table.