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
I propose adding a config that allows users to pass in a method for calculating appropriate Solana priority fees to set per transaction. Passing in a method allows integrators to customize how they calculate this, including:
using Solana RPC getRecentPriorityFees to estimate based on past priority fees
using Helius getPriorityFeeEstimate to lean on an external service to estimate appropriate priority fees
The text was updated successfully, but these errors were encountered:
I've looked into this and know generally how to get it done. however, it depends on #1698 merging first, which enables to add non-JSON-serializable things functions into the integration config. as of right now, because Connect only supports a stringified JSON config, we literally can't do this.
* set priority fee for solana transactions
* always set compute unit limit & price
* set fee to 75th percentile of recent fees paid
* include mintAddress
* fix try/catch
Description and context
Solana transactions require setting a priority fee to land transactions during periods of high congestion.
See:
I propose adding a config that allows users to pass in a method for calculating appropriate Solana priority fees to set per transaction. Passing in a method allows integrators to customize how they calculate this, including:
getRecentPriorityFees
to estimate based on past priority feesgetPriorityFeeEstimate
to lean on an external service to estimate appropriate priority feesThe text was updated successfully, but these errors were encountered: