Jude Nelson
[Stacks-2.1] remove PoX sunset and cap unburnt PoX output to be a function of the last prepare phase
Another update on this: "extend PoX forever" is definitely on the table, but trying to use `(reject-pox)` to control discount-mining isn't very rigorous, or even much of a deterrent. We...
[Stacks-2.1] remove PoX sunset and cap unburnt PoX output to be a function of the last prepare phase
Okay, we've landed on a solution: * keep `reject-pox` as-is * remove the sunset The sortition weight windowing already does a good-enough job at making discount-mining very difficult and expensive...
Hey @314159265359879, thank you for reporting! Do you have any logs from what happens after the headers finish syncing? Thanks!
If the new parser is coming in 2.1 anyway, then fixing it then and there is fine by me.
Anything in dmesg? It might have been an OOM kill. That wouldn't leave a stack trace or a core dump.
Making a list: * `to-consensus-buff`: _O(n)_ in the size of the value * `from-consensus-buff`: _O(n log n)_ in the number of atoms in the type signature (caused by tuple key/value...
`from_consensus_buff` can parse a tuple, and tuple key/value pairs are stored in an ordered map (a `BTreeMap`), which means loading a Clarity value can take as long as O(n log...
So in total we need: * `replace-at?` * `AnalysisFetchContractEntry` (thanks @obycode!) * `as-contract` * Comparator functions on sequences
I think an easy win here could be to simply bound the amount of time we're allowed to spend on http traffic. We could randomize the order in which we...