Transaction size & measurements
The 1,232-byte Solana packet cap and representative finalized v0 transaction sizes and compute measurements from release validation.
Solana's serialized transaction packet limit is 1,232 bytes. The SDK rejects an oversized serialization; the hosted relayer also checks the configured maximum and never accepts more than the Solana limit.
Frozen Devnet release-gate measurements
These are measurements from the 2026-10-07 Core/SDK fresh Devnet lifecycle, not a separate hosted-relayer benchmark:
| Operation | Serialized bytes | Compute units | Proof time |
|---|---|---|---|
| Shield | 661 | 89,678 | N/A |
| Private Swap A→B with change | 847 | 639,616 | 5.119 s |
| Private Swap B→A, no change | 847 | 614,188 | 5.028 s |
| Private Send (Unshield primitive) | 1,109 | 351,926 | 2.521 s |
| Unshield | 1,077 | 348,733 | 2.400 s |
| Two-output Private Swap crossing 4095→4096 | 756 | 660,935 | 4.918 s |
Every submitted SDK transaction in that run was at or below 1,232 bytes, and no tested operation exceeded its configured compute budget. Measurements reflect one frozen LUT/account shape; a different pool, recipient or archive page can change serialized size.
Hosted relayer configuration
At review time the hosted /api/v1/config response reports a 1,232-byte maximum and a 1,400,000 CU limit. Those are policy configuration values, not per-operation acceptance measurements. The endpoint returns the live public limits so clients should query it rather than assume every deployment uses the same values.
The relay response status: "submitted" means Solana RPC accepted submission. It does not mean the transaction is finalized or successful; poll transaction status.