Starknet OpenRPC specFor the latest version of the publicly maintained OpenRPC spec, see the Starknet specs GitHub repo.
Get you own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.
Parameters
message
— the message to estimate, which includes the following fields:to
— the string of the address to which the message is directed, a wallet, or a smart contract.data
— additional data to be sent with the message, usually used to invoke functions from smart contracts as a string of the hash of the method signature and encoded parameters.
block_id
— the hash of the requested block, or number (height) of the requested block, or a block tag, for the block referencing the state or call the transaction on.
Response
result
— the estimated amount of fee needed, represented as a hexadecimal string.
Use case
A practical use case forstarknet_estimateMessageFee
is to calculate the fee required for a message that interacts with a contract on Starknet. The fee is an important factor in messages, as it determines the amount of fees that need to be paid by the sender to the network for processing the message.
Deprecated feeder gateway method
The feeder gateway was deprecated on December 11, 2023. Example of the call you had to make to the feeder gateway before the deprecation:Shell
Response
200
Successful response