You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
within the gas tracking branch, we have implemented a transaction entity that interacts with the optimism gas oracle to return all of the necessary data fields to calculate the gas cost of the transaction. currently, the l1_gas_used by the transaction is underestimated by ~1% on average. from my best guess, this is a problem with how we are passing in the transaction data to the contract function.
the oracle contract function being called can be found here.
an example of interacting with the oracle contract can be found in the optimism sdk here
the current convention used for passing transaction data to the function can be found here
without the serialize function of the ethers package, we are restricted to using the ethereum class in graph-ts
The text was updated successfully, but these errors were encountered:
i really liked the idea of a big subgraph that collected and formatted every piece of data you could want and was written in a very modular way (writing each entity in its own file (?) and other good stuff) that could be forked and used as boilerplate for any type of rubicon-related subgraph you could encounter (im talking about you future messari orderbook template). but, this goes against our event-driven lifestyle at the moment.
within the gas tracking branch, we have implemented a transaction entity that interacts with the optimism gas oracle to return all of the necessary data fields to calculate the gas cost of the transaction. currently, the
l1_gas_used
by the transaction is underestimated by ~1% on average. from my best guess, this is a problem with how we are passing in the transaction data to the contract function.the oracle contract function being called can be found here.
an example of interacting with the oracle contract can be found in the optimism sdk here
the current convention used for passing transaction data to the function can be found here
without the
serialize
function of the ethers package, we are restricted to using theethereum class in graph-ts
The text was updated successfully, but these errors were encountered: