Brice
> @obycode those timestamps are GMT? No, those logs were in EST, so they matched with when the tx was actually mined. It's still unclear to me why that transaction...
> a related point is that I think miner reward maturation _also_ should follow `tenure-height` rather than `block-height` Is there any advantage to adding a new `tenure-height`, versus just using...
I agree, (2) is not a good solution. (1) seems like a viable option to me.
I'd argue that the **correct** solution is to leave `block-height` as-is, returning the chain length, and then require any contracts to adapt to the new timing of blocks, but practically,...
The decision in the SIP is: > The protocol described in this document would have Stacks blocks occur at a much greater frequency than in the past. Many contracts rely...
After posting that link, I also noticed that the `#try` fragment identifier is not working to jump to that location on the page.
If someone has time to work on this soon, it could be very helpful for 2.3 debugging with stacks-devnet-js. My guess is that it should be relatively easy.
If someone has time to work on this soon, it could be very helpful for 3.0 debugging with stacks-devnet-js. My guess is that it should be relatively easy.
I believe the main missing component needed to implement this would be maintaining the comments in the AST. There is currently no data structure to hold comments, so they are...