@xyo-network/event-kit-actor
v2.3.5
Published
Wake publisher actor and ports for XL1 Event Kit
Readme
@xyo-network/event-kit-actor
Reference wake publisher actor and injectable ports:
- finalized head source
- publisher cursor store
- wake filters (every-block + stub schema)
- wake signer / delivery client
Environment-neutral — filesystem cursors live in @xyo-network/event-kit-node.
Signing
createAccountWakeSigner is the real D-002 signer: it builds the strict wake
Payload, computes PayloadBuilder.dataHash(event), and mints one short-lived
XL1 wallet JWT carrying that eventHash. There is no second Payload signature.
The actor requires an independent authorizationChainId and explicit source.
Its signer and durable outbox carry fromPosition/toPosition; source identity
is committed with the body and checked on recovery. createEveryBlockFilter
accepts maxPositionsPerWake and a caller-supplied canonical filterHash.
Authorization eligibility never replaces the subscription's source cursor.
- The publisher address P is pinned in configuration; construction fails when the supplied account resolves elsewhere, so a restart cannot silently adopt another derived child account.
- Every call samples a fresh
jti, so a retry of an unchanged wake reuseswakeId/eventHashunder a new token. queueIdis omitted rather than set toundefined, so the hashed object matches the receiver's JSON-decoded body.
createStubWakeSigner remains for structural tests that do not exercise crypto.
Outbox and commit order
With a PublisherOutbox wired in, each pass retries an unresolved wake before
considering new work. The order is the correctness property:
- persist the pending wake (
wakeId, range,filterHash,issuedAt); - sign — a fresh
jtievery attempt; - reject the result unless the emitted event equals the committed decision;
- deliver;
- advance the cursor;
- clear the outbox.
A crash anywhere in that window replays the same wakeId and issuedAt, so
the canonical hash is reproduced and the receiver resolves the retry to the
original receipt. issuedAt is persisted for exactly that reason: re-stamping
the clock would change eventHash and turn a duplicate into a rejected
collision.
createFilesystemPublisherOutbox in @xyo-network/event-kit-node is the
durable implementation; createMemoryPublisherOutbox is for structural tests.
The actor requires an outbox. Production Durable Delivery callers must provide
durable storage so ambiguous delivery preserves the same logical identity.
Resident runtime and evidence
The CLI's publisher run composes the persistent Node runtime: real source
readers, finalized subscription discovery, SQLite authority, bounded HTTPS
delivery, and operational probes. This actor remains its independently useful
per-subscription primitive. Local tests do not qualify credentialed hosted
delivery, Sequence, Mainnet, multi-host operation, or production readiness.
