Jael is the networking key infrastructure vane.
The main purpose of Jael is keeping track of Azimuth related information. For each ship, this consists of its public keys, its key revision number (or
life), its continuity breach number (or
rift) (see Life and Rift), and who the sponsor of the ship is. It also handles the local ship's private keys, keeps track of galaxy domain prefixes, and performs some boot-related tasks.
By default, Jael's primary source of information is the Gall agent
%azimuth-tracker, which (using
%eth-watcher) runs a thread that polls an Ethereum node for transactions in the Azimuth contract. It can also get updates from other ships on the network. This is always the case for moons, where it subscribes to the moon's parent's Jael for updates.
The database of PKI information that Jael maintains is used by other vanes and agents for identity validation, encryption, decryption, and other cryptographic functions. In particular, Ames (the network vane) uses the information stored in Jael to encrypt packets it sends to other ships, and to decrypt & validate packets it receives from other ships.
Jael has a few
tasks you can use to interact with it. In particular, its %public-keys task allows an agent or thread to subscribe for PKI updates for a
API Reference - The
tasks Jael takes and the
gifts it returns.
Scry Reference - The scry endpoints of Jael.
Data Types - Reference documentation of the various data types used by Jael.
Examples - Practical examples of using Jael's