OpenChainGraph Suite · ART-532 · CCP-Core Clearing Primitives

Client Porting Check

Checks whether a client's cleared positions and collateral are portable to a backup clearing member, given the porting window, position and collateral completeness, and backup-member consent status you declare. An empty position set, a missed porting window, and a not-yet-consented backup member each resolve to a distinct, defined not-portable outcome rather than a generic failure. A portable verdict is an evaluation of the snapshot you declared. It is not a guarantee that porting will in fact occur, and this tool does not itself move any position or collateral.

Declared snapshot, not a live feed No-positions and window-missed kept distinct from a consent gap Single-run, stateless
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
⚠ This tool does not pull a client's positions, collateral, or a backup member's consent decision itself. You declare all three and it computes once when you press the button, stores nothing, runs on no schedule, and retains nothing. Clause: PFMI Principle 14 (Segregation and Portability) · 17 CFR 240.15c3-3a.
Porting event

The demo figures below are synthetic and already loaded, so you can press Run without entering anything of your own.

Positions
Collateral
Rejected inputs
Rationale
    Execution Hash (SHA-256)
    What this does not do

    It does not pull a client's positions or collateral, execute a transfer, or bind a backup clearing member to accept a port. Consent status is a fact you declare about a decision made elsewhere. A portable verdict is not a guarantee that porting will in fact occur, and it is not a determination that any party has breached PFMI Principle 14 or SEC Rule 15c3-3a.

    Related

    This node evaluates the porting leg of a defaulting-member event. Sibling CCP-core nodes cover the default-fund waterfall, Cover-2 fund sizing, cross-CCP disclosure comparison, and the margin-call lifecycle that this node can follow when a call is not met within its declared SLA window.