Logo
Chain Engine

Chains

Create and manage saved chain definitions for the Chain Engine runtime.

Saved chains define the ordered route that runtime traffic should use.

Chain Engine Chains

Chain Fields

FieldMeaning
NameHuman-readable chain name.
NotesContext for how or why the chain was created.
TagsLabels such as harmony, manual, fallback, or stable.
Primary hopsOrdered proxy hops used for the main route.
Hop labelOptional label for readability in traffic and editing.
Fallback chain IDsOther saved chains to try when fallback is enabled and primary route fails.
Policy IDRuntime policy assigned to the chain.

Hop Order

Hop order matters. A chain like:

proxy-a -> proxy-b -> target

is not the same as:

proxy-b -> proxy-a -> target

Use Chain Tester results to preserve the working order.

Fallback Chains

Fallback chains are saved chain definitions referenced by another chain. The engine validates the fallback graph and prevents:

  • missing fallback chain references
  • fallback cycles
  • deleting a chain while it is still used as a fallback

Complete Chain Definition Fields

FieldDetail
IDStable local chain identifier.
NameHuman-readable label in lists and runtime snapshots.
NotesFree-form context for source, target, or test result notes.
TagsSearch/filter labels such as harmony, manual, fallback, stable, or country hints.
Primary hopsOrdered proxy hop list used by the primary route.
Hop proxy stringThe normalized proxy string for each hop.
Hop labelOptional label that makes traffic and editing easier to read.
Fallback chain IDsOther saved chains the runtime may try when fallback is enabled.
Policy IDPolicy assigned to the runtime route.
TimestampsCreated and updated timestamps for workspace memory.

Naming Pattern

Good chain names:

  • Harmony A US exit
  • Manual socks-http chain
  • Fallback EU route
  • Low latency chain 2 hop

Add hop labels when chains get long. They make runtime traffic easier to read later.

On this page