Link Box
Groups links into a named set (e.g. Key/IV/AAD) that moves together.
Overview
Groups multiple symbolic port links into a single movable card on the canvas so that related values (for example, Key, IV, and AAD) can be routed across a large workflow without long, crossing connection wires.
Unlike normal computation nodes, a LinkBox has no input ports on the canvas; instead, you bind each row of the LinkBox to any upstream node's output port in the graph. At runtime, each output port of the LinkBox forwards the exact value produced by its linked upstream source port.
When to Use
- Keeping large cryptographic workflows (such as multi-round key schedules, hybrid KEM + AEAD pipelines, or side-by-side encryption/decryption verification graphs) clean and readable without long crossing wires.
- Duplicating a grouped set of references (e.g., shared
KeyandNonce) near both the encryption stage and the decryption stage.
Parameter Configuration
LinkBox is configured by binding upstream output ports to rows in the LinkBox inspector or by creating a LinkBox from an existing node's output ports. You can rename the box title and reorder or remove linked output rows at any time.
Port I/O Specification
See Ports & Connections for general wiring rules, data type colors, and dynamic port creation.
Input Ports
This node has no input ports.
Output Ports
| Attribute | Specification |
|---|---|
| Port Nature | Dynamic / Variable Output Ports (Symbolic Links) |
| Initial Default on Canvas | Starts with 0 output ports until upstream output ports are linked into the box. |
| Port Count Range | 1 or more linked output ports. |
| Allowed Data Types | Bytes, String, Int, Bool, or Set (each port inherits the exact data type of its linked upstream output port). |
| Adding & Managing Ports | Add or remove linked upstream output ports in the LinkBox inspector or via the canvas context menu. |
| Evaluation & Ordering Rule | Each output port emits the exact runtime value of the upstream output port to which it is linked. |
Error Cases
This node has no runtime failure cases (errorProfile: none) and always succeeds for any valid typed input.
Examples
Routing Key and Nonce Across a Large Canvas without Crossing Wires
Use a LinkBox to forward Key and Nonce to a distant Decrypt node.
- Bind the
KeyandNonceupstream outputs into a LinkBox namedSession Params. - Place the LinkBox next to your AES Decrypt node and wire its
KeyandNonceoutput ports short-range.