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
currently your receipt doesnt expose the values "type" and "effectiveGasPrice". We use effectiveGasPrice in one of our bots to multiply it with "gasUsed" to get the actually spend SMR amount (and then convert it to $, to show the $ cost of a transaction).
To be fully complient it would be nice of you add those 2 values to your list. In your case they are currently both static.
effectiveGasPrice : QUANTITY - The sum of the base fee and tip paid per unit of gas.
type: QUANTITY - integer of the transaction type, 0x0 for legacy transactions, 0x1 for access list types, 0x2 for dynamic fees.
So in your case effectiveGasPrice would be 1000 GWEI (so 1000 * 10^9) as hex string, and type would be "0x0"
As at some point more protocols and dApps from other chains will come to shimmer you should try to be as complient as possible with the EVM standard, so that they can migrate without having to make alot of adjustments "just for Shimmer".
The text was updated successfully, but these errors were encountered:
r.EffectiveGasPrice
and r.Type instead of the static values, if you fill these value correctly, but i am not a GO developer so it is hard for me to read that code (first time I see GO)
As stated in the official documentation:
https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_gettransactionreceipt
currently your receipt doesnt expose the values "type" and "effectiveGasPrice". We use effectiveGasPrice in one of our bots to multiply it with "gasUsed" to get the actually spend SMR amount (and then convert it to $, to show the $ cost of a transaction).
To be fully complient it would be nice of you add those 2 values to your list. In your case they are currently both static.
So in your case effectiveGasPrice would be 1000 GWEI (so 1000 * 10^9) as hex string, and type would be "0x0"
As at some point more protocols and dApps from other chains will come to shimmer you should try to be as complient as possible with the EVM standard, so that they can migrate without having to make alot of adjustments "just for Shimmer".
The text was updated successfully, but these errors were encountered: