-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use filecoin test chain not hardhat #6
Comments
|
We need to enable Currently getting a permission error, probably need to do this https://lotus.filecoin.io/reference/basics/api-access/ |
Note: I’m assuming we’re using a restartable devnet from this [branch](#7)
# Update this with token you generated from before
chainauthtoken = "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJBbGxvdyI6WyJyZWFkIiwid3JpdGUiLCJzaWduIiwiYWRtaW4iXX0.PyJt3GZtJrLu-bs_3Kmy1VrFpcGoCZEZ8JhX-YWQ4Pc"
# This is the default RPC endpoint for the lotus daemon
chainurl = "ws://127.0.0.1:1234/rpc/v1"
Found chain id: 31415926
panic: failed to estimate gas: CallWithGas failed: call raw get actor: resolution lookup failed (t410f6op5nzi2vwepn5gonk4ie4tzz773sitggxp4hiy): resolve address t410f6op5nzi2vwepn5gonk4ie4tzz773sitggxp4hiy: actor not found
goroutine 1 [running]:
main.main()
/Users/lagap/code/go-nitro/scripts/start-rpc-servers.go:60 +0x444
exit status 2 Note:
|
Currently we rely on spinning up a seperate instance of hardhat for nitro-rpc-client, we're not actually communicating with the filecoin test chain that gets started with a the
devnet
command.I'm not sure if the filecoin test chain exposes an EVM-comptable JSON-RPC API, but we should investigate and use it, if it exists.
The text was updated successfully, but these errors were encountered: