Supra Mainnet Gas Price Adjustment — Effective 11 May 2026

Following the voting result of Supra Upgrade Proposal #3: Gas Price Adjustment, the minimum gas price on Supra Mainnet will be updated from 100 Quants to 100,000 Quants effective 11 May 2026.

Proposal details: SUP #3 Voting Result ↗

This change is important for developers, wallets, dApps, and infrastructure providers interacting with Supra Mainnet.

What Is Changing?

After the update is activated, any transaction submitted with a gas price lower than the new minimum may fail on mainnet.

What Developers Need To Do

If your application or integration uses a hardcoded gas price, it must be updated immediately.

Instead of relying on static values, applications should dynamically fetch the recommended gas price using the official RPC API:↗

This ensures your application remains compatible with future network adjustments.

Recommended Integration Approach

Developers using the Supra SDK should allow the SDK or RPC API to determine the correct gas configuration dynamically.

SDK reference: https://github.com/Entropy-Foundation/supra-l1-sdk/blob/master/src/index.ts?#L1324↗

Sample Transaction Code

const rpcUrl =
  process.env.NEXT_PUBLIC_SUPRA_RPC_VEX_URL?.replace(//rpc$/, '') ||
  'https://rpc-mainnet.supra.com'

const optionalTransactionPayloadArgs = {
  maxGas: BigInt(5000), // Adjust this parameter
}

const supraClient = await SupraClient.init(rpcUrl)

const rawTxPayload = await supraClient.createSerializedRawTxObject(
  HexString.ensure(accounts[0]),
  (await supraClient.getAccountInfo(accounts[0])).sequence_number,
  moduleAddress,
  moduleName,
  functionName,
  runTimeParams,
  params,
  optionalTransactionPayloadArgs
)

const data = Buffer.from(rawTxPayload).toString('hex')

const txHash = await provider.sendTransaction({
  data,
  from: accounts[0],
  to: moduleAddress,
  chainId: process.env.NEXT_PUBLIC_SUPRA_CHAIN_ID || '6',
  value: '',
})

Understanding Transaction Fees

Transaction fees on Supra are calculated using:

Estimated Fee = (maxGas x gasUnitPrice) / 10^8

This means the user wallet must have at least the estimated fee amount available to successfully process the transaction.

Example

If: maxGas = 5000, gasUnitPrice = 100000

• maxGas = 5000
• gasUnitPrice = 100000

Then:

Estimated Fee = (5000×100000) / 10^8

The transaction fee reserve would be: 5 SUPRA

Note: The full reserved amount is not necessarily consumed. Users are only charged for the actual gas used during execution.

How To Choose maxGas

The maxGas value should reflect the expected execution complexity of the transaction.

Recommended approach:

• Base it on the actual gas usage of your transaction
• Check previous successful transactions
• Simulate transactions whenever possible
• Add a safety buffer (~1.5× to 2×)

This helps avoid transaction failures caused by insufficient gas limits.

Important Clarification About Out of Gas Errors

Out of Gas errors occur when:

• maxGas is set too low

They do not happen because the gas price is high.

Increasing gas price affects transaction acceptance and fee estimation, while maxGas controls the execution limit available to the transaction.

Action Items For Teams

Before 11 May 2026, all teams should:

• Remove hardcoded gas price values
• Integrate dynamic gas price fetching
• Review transaction fee handling
• Validate wallet balance checks
• Test transactions on updated mainnet settings

Applications that do not update their gas handling logic may experience failed transactions after the network upgrade becomes active.