Apr 7, 2026

I managed to complete the 8 electrum non-subscription address methods, including their rpc serialization, complex sorting, and cancellable/asynchronous behavior. Just have to write the four corresponding database queries, which are similar to the existing native queries, and then test the 8 methods, 4 queries, and 3 sorts. That'll take another day. Then it's on to the address/scripthash (basically the same) subscription/notification. I did get some work done on the address "status" optimization. I set up a copyable midstate struct that allows incremental forward updates to the confirmed aspect of the status hash. This is a stack allocated 208 bytes that can be held in the channel with each corresponding address subscription. So if you subscribe to an address with 5 million txs, we only compute that once and then just add new spend/receive txs to the hash as they occur. This might seem uncommon, but I was clicking randomly through the block explorer today and hit an address with 750,000 transactions. Chrome can't handle that amount of json, so we have to process address output enumerations differently, like by using the data or text accept type.