Pi Lanningham

Looks like the relevant commit is here: https://github.com/DefinitelyTyped/DefinitelyTyped/commit/f34693c881c286ebdf2a33d25542b009f8e4f297#diff-825aab95db5570e43fc04346c6b2971e

Last version that worked, for anyone coming across this issue: "@types/chrome": "0.0.96", I personally don't depend on anything changed since then, but I'm sure it'll become a problem for people...

:eyes: Bumping on this again?

> @Quantumplation what is your opinion in how to (avoid) configuring this? Also, you might have an opinion on: > > how are phantom tokens observable by clients if they're...

> > As for the snapshots, they could still be a part of the snapshots so long as it was understood that they were part of an ephemeral state that...

As you pointed out in private, this is achievable by turning off pruning, but doing so across the entire network would blow out memory / db, I'm assuming :P

Was it an intentional decision somewhere to sort transactions in this way? I.e. is there a good reason why this was done, or is it just an accident of the...

Note that Sundae would benefit dramatically from these bitwise operations; In particular, because transaction inputs get re-ordered, we need to provide an "indexing set" in the redeemer; but because of...

@michaelpj I can provide some psuedocode for what i'm doing now, how many execution units that costs, and some psuedocode for how I was thinking of using bitwise operators, but...

Hopefully the above is at least somewhat helpful to you :sweat_smile: On an unrelated note, it's really the O(n) list indexing that is absolutely wrecking performance everywhere. If we had...