May 16, 2026

The subscribers for address and for spender are stubbed in but need a little more work to managed the statefulness (limited map of subscriptions to specific addresses). Also the subscribers for log messages and high speed events are implemented and should be complete shortly. These initially just subscribe to log messages and all events. I'll be adding a numeric flags parameter to the query string for both, where the numbers map to the desired log subscriptions and event subscriptions. Sending empty flags will therefore be equivalent to sending stop for unsubscribe. The response from registration is currently empty. These are not the same events that drive the chaser system (those carry context such as block header surrogate key). The chasers drive the above top/block/tx flow. The high speed events are much simpler and cover really anything we want, including internal diagnostics and timings. Since http is half duplex, subscribing will not result in any notification traffic until the http connection is "upgrade" to websocket. But the subscriptions remain active.