A, perhaps more drastic, alternative that we’ve discussed would be to remove the at-block expression altogether. If we can identify alternatives for all of the use cases, this would solve the chainstate size problem and also greatly simplify the stacks-node code. The support for at-block has been a source of several bugs over the years and complicates many different areas of code. Other popular chains do not support this kind of thing, and it doesn’t seem to be a necessary feature. Thoughts?
1 Like