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've encountered while attempting to deploy contracts on Redbelly Devnet using your platform. I'm receiving the following error message:
“Failed to deploy contract
Couldn't deploy CREATE2 factory: {"code":-32603,"message":"Internal JSON-RPC error.","data":{"code":-32000,"message":"Sender not authorised to write transactions","cause":null},"transaction":{"nonce":0,"gasPrice":...”
Here's my understanding of the issue:
ThirdWeb seems to perform a test contract deployment using its own wallet before deploying the main contract using the user's wallet.
However, Redbelly Devnet requires account verification through https:// access.devnet.redbelly.network/ before interaction.
Since ThirdWeb's test wallet isn't verified, the error occurs.
Possible Solutions:
Verify ThirdWeb's Test Wallet:
Obtain verification for the test wallet using the Redbelly link.
Skip Presumptive Deployment for Redbelly:
When Redbelly is selected as the network, directly deploy the contract using the user's wallet, bypassing presumptive deployment.
Use User Wallet for Presumptive Deployment:
Alternatively, leverage the user's wallet for presumptive deployment as well.
Urgency:
With Redbelly's mainnet launch approaching, addressing this issue promptly would significantly benefit a large number of developers.
Redbelly Network Chain Details:
Network Name: RedbellyDevNet
New RPC: https:// rbn-gcp-australia-southeast1-a-0-b-v2.devnet.redbelly.network:8545
Chain ID: 152
Currency Symbol: RBNT
Block Explorer Address: https:// explorer.devnet.redbelly.network
Thank you for your attention to this matter. I'm eager to assist in any way possible to ensure a smooth deployment experience on Redbelly Devnet.
Hey @nkrishang or @kumaryash90 could you please take a look here for the suggested fix?
Posted originally from our Discord community.
The text was updated successfully, but these errors were encountered: