Closed Philogy closed 10 months ago
Hi Philippe, thanks for jumping on this and taking the time to report the issue. The reponse of the node that you are using seems to not have a result
field. I'll take a closer look but in the meantime, try out this public node instead: https://eth.public-rpc.com
Ok, I see what the problem is, the node seems to be picky about the request not specifying the Content-Type
header. It should be easy to fix.
I created a fix that will be in the next release: https://github.com/ethereum/fe/pull/952 Thanks again for reporting, please use another JSON-RPC provider such as https://eth.public-rpc.com/ in the meantime.
What is wrong?
Following the simple dao blog post I installed fe via brew (
fe -V
=>fe 0.26.0
) and tried to run the command to verify the contract:Whereby I ran this in the
fe_contracts
directory of the https://github.com/cburgdorf/simple_dao/ repo on tagSimpleDAOBountyDeployment
(also doesn't work on master). My RPC seems perfect functional with me able to retrieve both contract code (tested viacast code <addr>
) and the current block number. I was using the publichttps://eth.llamarpc.com
endpoint for reference.Full error from running the command: