Instructions missing - the project cannot be run

[goldfinch-eng]

Instructions missing - the project cannot be run

[ihinsdale]

@ctindogaru Thanks for opening this issue!

In regards to your error running npm run start:local, can you confirm that you ran npm run bootstrap first?

In regards to your error running npm start:local:liquidity-mining, can you confirm that in the browser, your Metamask extension is pointing against localhost (and therefore not mainnet)? Your localhost network in Metamask needs to be configured with RPC url http://localhost:8545 to communicate with the local hardhat node, and its chain id needs to be 31337.

[ctindogaru]

It would be amazing if other folks can help you building on your product. But to be able to help, we need to be able to run the project first, so some guidance would be appreciated!

[ctindogaru]

The recommendation for npm start:local:liquidity-mining fixed the issue. Thank you so much!

However, when running npm run start:local , I'm still running into the same issue. On what network should I be when running npm run start:local? http://localhost:8545 with chain id 31337 right?

[ihinsdale]

On what network should I be when running npm run start:local? http://localhost:8545 with chain id 31337 right?

That's right. The npm start:local* commands run a local blockchain via hardhat, so you want your Metamask to point to that chain.

I have sometimes observed weird behavior like that Unhandled Rejection (Error): You must provide the json interface of the contract when instantiating a contract object. error if I have multiple Goldfinch tabs open at once, where one is for https://app.goldfinch.finance which needs Metamask to point to mainnet, and one is for http://localhost:3000 which needs Metamask to point to localhost. In that situation, it seemed like even if http://localhost:3000 was the active tab, I would have trouble switching Metamask to localhost, as if Metamask was trying to give priority to mainnet for https://app.goldfinch.finance. That problem would go away by closing the https://app.goldfinch.finance tab.

The Unhandled Rejection (Error): You must provide the json interface... error itself though sounds like the client JS is not obtaining the ABI json that it needs. When running locally, this ABI json comes from packages/protocol/deployments/all_dev.json. It is loaded by the client in getDeployments() in packages/client/src/ethereum/utils.ts.

Unfortunately I'm not able to debug this myself at the moment, as the repo HEAD runs on node v14, and I'm on an M1 Macbook Pro which needs node v16. If you are still stuck with npm run start:local, I can ask a team member to continue debugging.

But if npm run start:local:liquidity-mining works for you, you should just keep using that, as it provides a superset of the functionality of npm run start:local (specifically, it just also makes your TEST_USER address the recipient of some Merkle*Distributor grants).

[ctindogaru]

Unfortunately I'm not able to debug this myself at the moment, as the repo HEAD runs on node v14, and I'm on an M1 Macbook Pro which needs node v16. If you are still stuck with npm run start:local, I can ask a team member to continue debugging.

Same here, but using M1 with node v14 works as well.

I can ask a team member to continue debugging.

Yes please, I would appreciate that!

But if npm run start:local:liquidity-mining works for you, you should just keep using that, as it provides a superset of the functionality of npm run start:local

So start:local:liquidity-mining = start:local + more ?

[ihinsdale]

start:local:liquidity-mining = start:local + more

Yes!

Yes please, I would appreciate that!

I've pinged Warbler's on-call engineer about trying to repro.

[wbj-goldfinch]

Hey @ctindogaru are you still encountering this issue?

[ctindogaru]

We can close this for now, I've focused on smart contracts lately so didn't run into this issue anymore.