corridor-in-a-box

Overview

corridor-in-a-box is an open, manifest-driven engine for Stellar SEP-31 cross-border corridors. A corridor is configuration, not code: the engine runs quote → comply → settle → reconcile → recover over any standards-compliant anchor pair, and adding a new corridor is a new *.corridor.yaml file — not a fork.

No smart contract required. SEP-31 is off-chain orchestration of a single native Stellar payment (the settle leg).

The three boundaries

  1. engine ↔ manifest — the engine contains no corridor-specific strings. Corridor #2 is a YAML file, not a code change.
  2. engine ↔ adapters — the engine knows only the AnchorAdapter interface; every standards-compliant anchor shares one adapter.
  3. router seam — the open repo ships a RouteResolver interface plus two resolvers: StaticRouteResolver (trust the manifest) and RegistryRouteResolver (require a fresh on-chain attestation). A health-/rate-weighted resolver could be supplied as a separate proprietary component, but none is included or injected today. The interface is an extension seam, not evidence that such a component exists.