tgmichel
tgmichel
@crystalin RT1900, which will most likely include https://github.com/paritytech/frontier/pull/794
@AaronKutch thank you for reporting. Frontier was initially coded re-using some of the parity/open-ethereum types. On its implementation `eth_blockByNumber/Hash` return [seal_fields instead](https://github.com/ethereum/EIPs/issues/95), which aimed to provide a broader support for...
Closing, included in client [v0.25.0](https://github.com/PureStake/moonbeam/tree/v0.25.0)
I have read the CLA Document and I hereby sign the CLA
@PeterYinusa did you have a chance to look at this?
@PeterYinusa is there any additional work to do on my side to get it reviewed? Thank you.
@brad-decker Thank you, very excited to finally get this in :) and sorry it took a while, just rebased.
+1 also noticed this issue
There are some nuances in the parachain context regarding best - as described in https://github.com/paritytech/frontier/pull/423. In the above PR, a special `SyncStrategy` was introduced to prevent a different pace between...
@brad-decker the issue @seaona mentioned doesn't seem to originate in this PR, is there something I can do to help you unlock it? The logic for triggering `_onLatestBlock` and updating...