Justin Berman

I made a mistake and don't believe this PR should yield a significant improvement to the scanner. I apologize. I've edited the PR description removing inaccuracies. @plowsof is still observing...

This idea was also aiming to solve for the case that the client still wants to know the daemon's height without another round trip to the daemon (not just get...

In theory it's not strictly necessary for the case described [here](https://github.com/monero-project/monero/pull/9382#issuecomment-2187704402), since there should still be one successful response (that we can use to explain the other RPC failures). But...

> what is the worst case we are trying to avoid? An example: a dev using the current API might expect a failure response when they provide too high of...

Actuaaaaally, since current behavior is to ban clients requesting a high height, there's no way anyone is justifiably relying on that behavior... I think we're justified in getting rid of...

From Stripe: > Due to current Stripe.js behavior, these warnings are expected. The warnings relate to a Google initiative to deprecate third-party cookies in Chrome. Stripe is aware of the...