David Laprade

@bricesanchez @AlessioRocco Have you guys had a chance to look at this? I've had it running in production for a couple months now without issue. Anything I can do to...

@apbendi @garyghayrat Do we definitely still want this feature? Reasons we may not: * we already have the [max send](https://github.com/ScopeLift/umbra-protocol/pull/375) feature, and it is pretty similar to this in intent...

In case we do decide to move forward with this issue, [this](https://github.com/ScopeLift/umbra-protocol/tree/show-token-balances-on-send-page-dropdown-fixes-%23294) is where I left off.

FWIW, n=1, as I'm working on other send-page tickets, I kind of miss this feature now 😅

Another (all too timely) usecase for this... if a version of your frontend calls out to an address that was [recently sanctioned](https://twitter.com/tier10k/status/1556642499585785857) 😬 you'd want a way to immediately prevent...

Thanks for reporting this @fedealconada. Another data-point here. I'm working on a project that was seeing the same "could not read source code" error when I ran `forge coverage`. In...

Test failure does not appear to be related to this PR. It's also failing on `master`

> Mainnet max estimate seems a bit high Interesting. I'm really glad you checked on mainnet! I actually hadn't. (I needed to republish my keys and I was too lazy/cheap...

+1 on adding an `onError` hook. It'd be really great not to have to call `runner.run()` in a try block -- especially given how brittle some recordings can turn out...

I think all I can remember is what's in this comment: https://github.com/ScopeLift/umbra-protocol/issues/294#issuecomment-1225946597