str4d

The main need for a non-linear-scan process like DAGSync is a map from `Nullifier` to "transaction locator". We can locate a transaction with either a `txid`, or `(block reference, tx...

I noted today that we could take a similar approach to commitments, and divide them into ranges (most likely by "number of spent notes", to keep the amount of data...

Reposting my comment from an internal thread, in response to the question "is the bloom filter approach a replacement to the nullifier approach or are they complementary?": The Bloom filter...

I was using "Bloom filter" above as a placeholder for "approximate set". There are more efficient constructions possible than Bloom filters, in particular constructions that reduce the size of the...

`man man-pages` gives the following order for these conventional or suggested sections: - `NAME` - `SYNOPSIS` - `CONFIGURATION` (Normally only in Section 4) - `DESCRIPTION` - `OPTIONS` (Normally only in...

Once I get access to a YubiKey with firmware 5.7.0+, I will add support for native age identities to `age-plugin-yubikey`, likely following the same pattern as I used for the...

This doesn't work reliably now that we are doing non-linear scanning; we don't detect spends for reverse scanning until after we've done trial decryption of the transactions they were spent...

With this change, I am able to fully resolve #2440 by adding an explicit `DefaultTTL(0)` to all of my `DSP_LINODE` sections. It would be slightly cleaner if providers could override...

> Thank you for taking the time to work on this issue. The proposed change is pretty fundamental and will require extensive discussion and testing. Yep, as expected! I will...

> I appreciate all the effort you've put into this. While this solution will work, I think there are other solutions that are more simple that will also work. I...