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 attempted to deploy a contract and received the following message:
Error estimating transaction fee. Response 400: Bad Request. Attempted to fetch http://localhost:3999/v2/fees/transaction and failed with the message: ""
Solution
It would be great for the API to send a better description than an empty string
Underlying Issue
The actual issue was that my contract name was too long
The text was updated successfully, but these errors were encountered:
thanks for the contribution! though im not sure how much sense it makes to couple the estimateTransaction call with too much information about contract payloads, cc @janniks
Hmm, yeah we should give better error messages. I'll check if the API is returning actual information.
janniks
added
bug
Unwanted or unintended logic causing harm
and removed
feature
Brand new functionality. New pages, workflows, endpoints, etc.
labels
Mar 4, 2024
Problem
I attempted to deploy a contract and received the following message:
Solution
It would be great for the API to send a better description than an empty string
Underlying Issue
The actual issue was that my contract name was too long
The text was updated successfully, but these errors were encountered: