Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Error: Calling factory deployed contract gives a 500 error
See original GitHub issueIssue Description
When trying to interact with (Contract.call) a contract that has been deployed by a factory the following request is made:
Header:
https://alpha4.starknet.io/feeder_gateway/call_contract?blockNumber=pending
Body:
{"signature":[],"contract_address":"0x03053E2e251CB67e652BAF3a3fF091F807BfDC1f01EE21Ef64180559bc0ee739","entry_point_selector":"0x361458367e696363fbcc70777d07ebbd2394e89fd0adcaf147faccd1d294d60","calldata":[]}
Producing a 500 error:
{"code": "StarkErrorCode.MALFORMED_REQUEST", "message": "{'contract_address': ['Expected hex string, got: \"0x03053E2e251CB67e652BAF3a3fF091F807BfDC1f01EE21Ef64180559bc0ee739\".']}"}
Contract:
https://goerli.voyager.online/contract/0x03053e2e251cb67e652baf3a3ff091f807bfdc1f01ee21ef64180559bc0ee739
Calling the contract without specifying the blockNumber should work? Seems by default block_number=pending is assigned to one where it cannot find the block number? Known issue in Voyager but believe the feeder_gateway has the contract info fine.
Issue Analytics
- State:
- Created 9 months ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Rather than sending them lowercase we could parse them with
toHex(toBn(...)@supsam89 closing this issue due to inactivity, feel free to reopen if any more questions arise!