npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@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 reuses wakeId/eventHash under a new token.
  • queueId is omitted rather than set to undefined, 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:

  1. persist the pending wake (wakeId, range, filterHash, issuedAt);
  2. sign — a fresh jti every attempt;
  3. reject the result unless the emitted event equals the committed decision;
  4. deliver;
  5. advance the cursor;
  6. 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.