captivecore

README

captivecore

The Captive Diamcircle-Core Server allows you to run a dedicated Diamcircle-Core instance for the purpose of ingestion. The server must be bundled with a Diamcircle Core binary.

If you run Aurora with Captive Diamcircle-Core ingestion enabled Aurora will spawn a Diamcircle-Core subprocess. Aurora's ingestion system will then stream ledgers from the subprocess via a filesystem pipe. The disadvantage of running both Aurora and the Diamcircle-Core subprocess on the same machine is it requires detailed per-process monitoring to be able to attribute potential issues (like memory leaks) to a specific service.

Now you can run Aurora and pair it with a remote Captive Diamcircle-Core instance. The Captive Diamcircle-Core Server can run on a separate machine from Aurora. The server will manage Diamcircle-Core as a subprocess and provide an HTTP API which Aurora can use remotely to stream ledgers for the purpose of ingestion.

Note that, currently, a single Captive Diamcircle-Core Server cannot be shared by multiple Aurora instances.

API

GET /latest-sequence

Fetches the latest ledger sequence available on the captive core instance.

Response:

{
	"sequence": 12345
}

GET /ledger/<sequence>

Fetches the ledger with the given sequence number from the captive core instance.

Response:

{
    "present": true,
    "ledger": "AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=="
}

POST /prepare-range

Preloads the given range of ledgers in the captive core instance.

Bounded request:

{
    "from": 123,
    "to":   150,
    "bounded": true
}

Unbounded request:

{
    "from": 123,
    "bounded": false
}

Response:

{
    "ledgerRange": {"from":  123, "bounded":  false},
    "startTime": "2020-08-31T13:29:09Z",
    "ready": true,
    "readyDuration": 1000
}

Usage

$ captivecore --help
Run the Captive Diamcircle-Core Server

Usage:
  captivecore [flags]

Flags:
      --db-url                             Aurora Postgres URL (optional) used to lookup the ledger hash for sequence numbers
      --diamcircle-core-binary-path           Path to diamcircle core binary
      --diamcircle-core-config-path           Path to diamcircle core config file
      --history-archive-urls               Comma-separated list of diamcircle history archives to connect with
      --log-level                          Minimum log severity (debug, info, warn, error) to log (default info)
      --network-passphrase string          Network passphrase of the Diamcircle network transactions should be signed for (NETWORK_PASSPHRASE) (default "Test SDF Network ; September 2015")
      --port int                           Port to listen and serve on (PORT) (default 8000)