wileyj

@kantai is this possible in the config or via restarting the process? or is this something that is stored in the local db ?

@hstove something like this **should** work i think: https://github.com/blockstack/subdomain-registrar/commit/0b091b1f521af8f540960a4f74b915bfaa71c88b

do you have a partition for `/tmp` of a specific size?

i think you have a few options here, but the easiest solutions are platform specific. you may increase that tmpfs size if you want to keep more test data, mount...

@jbencin in the interest of prioritizing nakamoto work - can we put this in draft, or even delete (for now) and create an issue to track this after 3.0 is...

understood. I'm just anticipating downstream conflicts that would require some refactoring. let's pick this up after 3.0 On Fri, May 10, 2024 at 16:54 Jeff Bencin ***@***.***> wrote: > @wileyj...

what about PR'ing the expected conflicts here to reduce the friction? are they things that shouldn't be included in a point release?

#4760 @hstove is it feasible to have a PR addressing this for next week?

> Is `id-header-hash` still meaningful on the stacks block level as the stack chain does not fork anymore on that level? very good question - @obycode any insight here?

> Should we point the change here to the main branch now to include the changes? that probably makes the most sense and can be done without any change from...