wileyj

I'm more of the opinion that this could (should?) be part of the explorer vs the wallet itself. basically, a modal or something that can determine if the previous nonce...

I see the points both @Hero-Gamer and @whoabuddy are making - but let's wait for someone like @markmhx to chime in here before we get ahead of ourselves with too...

Wouldn't this be a better question to ask https://github.com/hirosystems/stacks-blockchain-api ? The data may already be there, there's just not an easy way to retrieve it currently

> Also curious if this could be achieved on a dashboard with https://stacksonchain.com > > STX Whales: https://stacksonchain.com/addressbalance Other token whales: https://stacksonchain.com/tokenwhales > > Also some further analysis on MIA:...

bump

history: because of how the explorer works, it can potentially track **millions** of paths for latency and other metrics. since we're using a pull based metrics model, every n seconds...

https://github.com/blockstack/stacks-blockchain-api/pull/502 https://github.com/blockstack/stacks-blockchain-api/blob/master/src/api/init.ts#L196-L226

with the promster library - they have some defaults set that are capping our data. https://github.com/tdeekens/promster for the sample metric, `http_request_duration_seconds_bucket` they clearly state this in the readme: ``` http_request_duration_seconds:...

> @wileyj Should I assign this issue to you? I'm not exactly sure where it stands in relation to the changes made by @fbwoolf with #491 the comment I made...

look into ways to adjust pre-release on the github release action so that it sets `pre-release` to false only when a release is tagged with the expected versioning. https://github.com/stacks-network/stacks-blockchain/pull/3199#discussion_r946800332