Gregory Coppola
Gregory Coppola
We need a more specific style guide for the `stacks-blockchain` repo. There has been some confusion about what should be in the comments.
This is a feature request for *benchmarking* of Clarity2 functions. We already have Issue #1165 for benchmarking Clarity functions. However, what might lost in the shuffle is the fact that...
**Is your feature request related to a problem? Please describe.** The problem is that in the vm::docs, we now have functions, like "buff-to-int-le", that require Stacks 2.1. But, we do...
**Is your feature request related to a problem? Please describe.** From profiling experiments, it looks like there is an opportunity to save a lot of time in the inner miner...
**Is your feature request related to a problem? Please describe.** The logs currently print the time by counting epoch seconds, so it is hard to understand what time it really...
**Is your feature request related to a problem? Please describe.** _Use Case_ A key use case is: * a user wants to know why their transaction hasn't processed yet *...
**Is your feature request related to a problem? Please describe.** It is not currently possible to put a trait reference inside of an `optional` in Clarity. This led to a...
**Is your feature request related to a problem? Please describe.** Multi-dimensional data about follower mempools, including prometheus stats for: * Current size, divided by tx type * Current fee stats...
**Is your feature request related to a problem? Please describe.** https://github.com/stacks-network/stacks-blockchain/issues/3190 suggested a reactive method of debugging stalled user transactions, in which we make a new endpoint, and query this...
**Is your feature request related to a problem? Please describe.** This issue asks for better ability to verify that the mempool walk algorithm is correct. It is motivated originally by...