AIW
Arlington Asset Investment Corp. 6.625% Notes due 2023,
stock NYSE

Would love your eyes on it when the repo opens.
Actually been preparing for this. We have two tracks.
Knowledge and constraint layer has CARROT fully mapped. 4-tier key hierarchy documented, future wallet-rpc methods listed but gated, and a hard agent rule that blocks any CARROT method until hard_fork_info confirms the fork. Structurally enforced too since those methods aren't in the RPC allowlist. Server rejects them even if the agent tries.
FCMP++ has an actual test harness. Separate ports, separate data dir, second AIW instance on 3001 so mainnet on 3000 stays untouched. Executable Node test that walks the RPC compat matrix, checks hard_fork_info, verifies graceful failure on unsupported methods. JSON reports dumped per run.
Honest gap though. hard_fork_info is allowlisted but nothing polls it automatically on session start. When the fork lands I'll have to manually allow it, as it won't detect it on its own yet. That's on the list now to automate.

Would love your eyes on it when the repo opens.
Actually been preparing for this. We have two tracks.
Knowledge and constraint layer has CARROT fully mapped. 4-tier key hierarchy documented, future wallet-rpc methods listed but gated, and a hard agent rule that blocks any CARROT method until hard_fork_info confirms the fork. Structurally enforced too since those methods aren't in the RPC allowlist. Server rejects them even if the agent tries.
FCMP++ has an actual test harness. Separate ports, separate data dir, second AIW instance on 3001 so mainnet on 3000 stays untouched. Executable Node test that walks the RPC compat matrix, checks hard_fork_info, verifies graceful failure on unsupported methods. JSON reports dumped per run.
Honest gap though. hard_fork_info is allowlisted but nothing polls it automatically on session start. When the fork lands I'll have to manually allow it, as it won't detect it on its own yet. That's on the list now to automate.