Matt Luongo
Matt Luongo
Note this goes for sending ETH, ERC-20s, and any transaction construction really... including if a dApp built the tx.
@Shadowfiend ideas here? This solution is ikrsome... maybe we need some sort of tx request subscription from the frontend?
Good with this as long as we're coming back to cover the tech debt later. Onward!
@EvelinaBuiciag do you have a timeline on integration completion? We're thinking this can be merged + released after Arbitrum and Optimism go out, and we can find a way to...
> Now the meaty one. IMO @0xDaedalus's point about collisions means this whole code path should be disconnected from enrichment until we've implemented the additional bits you've described @mhluongo. Initially...
All of that is a UI concern though. This PR doesn't include an interface that suggests this information should be trusted as correct — it gives us the information necessary...
Moving this back to draft and giving it a rethink.
This works in `main`, though I don't think we should close it until the frontend shows non-EIP1559 gas controls as well.
Between this and derivation paths, we should have everything we need in the tech tree for RSK... except an Alchemy alternative!
The styling is off on Chromium 