Casey Rodarmor

I was thinking that the simplest way to support alignment may be: - Only support aligning byte slices. Push doing deserialization from aligned byte slices to the user. - Only...

I had an idea for at least [a slight improvement in DHT privacy](https://twitter.com/rodarmor/status/1559066612732375040), and was curious if you've encountered anything similar. I was thinking about it in the context of...

This is no longer a problem, retrying in #820 means that we continue even if we get an error. However, this is still happening, and the pattern is so regular...

This is low priority, since it's not actually causing any problems, so pushing it back to the production inscriptions milestone.

> The updater writes to the database every 5000 blocks, but the 34 is a mystery. Maybe, not so much of a mystery. The MPSC channel that the background block...

I suspect latest master is particularly bad here, because of #1166, so flushes are taking a lot longer, so we're more likely to hit the timeout.

> [10f8469](https://github.com/casey/ord/commit/10f8469a09f601d2ae4939a2d74b0f607782a26b) is the first bad commit This definitely seems like a bad bisect. That commit is super harmless.

One concern with surfacing the inscription number right now is that inscription numbers depend on knowing all inscriptions before a given inscription, and when we update the protocol, there will...

I think this ship has sailed in the sense that people are attached to the existing inscription numbers, so in true Bitcoin fashion, we now how to work around our...

We might also be able to support this easily simply by making the transaction checks more liberal. The idea would be to move checks that we're sending inscriptions to the...