-
Notifications
You must be signed in to change notification settings - Fork 3
feat: added moonbeam to human protocol subgraph list #14
base: moonbeam
Are you sure you want to change the base?
Conversation
| "name": "counter", | ||
| "outputs": [{ "internalType": "uint256", "name": "", "type": "uint256" }], | ||
| "stateMutability": "view", | ||
| "type": "function" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's not update this file unless we need to
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed
package.json
Outdated
| "@graphprotocol/graph-cli": "0.29.2", | ||
| "@graphprotocol/graph-ts": "0.26.0" | ||
| "@graphprotocol/graph-ts": "0.26.0", | ||
| "gluegun": "^5.1.2" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we want gluegun?
package.json
Outdated
| "create-local": "graph create --node http://localhost:8020/ posix4e/humansubgraph", | ||
| "remove-local": "graph remove --node http://localhost:8020/ posix4e/humansubgraph", | ||
| "deploy-local": "graph deploy --node http://localhost:8020/ --ipfs http://localhost:5001 posix4e/humansubgraph" | ||
| "deploy": "graph deploy --node https://api.thegraph.com/deploy/ menezesphill/hmtmoonbeam", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i don't think we need to update this stuff. We probably should remove them altogether
posix4e
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have some changes in the PR
@posix4e I reverted ABIs back to the original from the main branch. Removed |
| "name": "counter", | ||
| "outputs": [{ "internalType": "uint256", "name": "", "type": "uint256" }], | ||
| "stateMutability": "view", | ||
| "type": "function" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed
ivhus
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So that indicating environment variables in a way like USER_ID=239482 USER_KEY=foobar node app.js works
ivhus
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The deploy part looks fine
Not sure about package.json and such
There's a question with humanprotocol/moonbeam (https://thegraph.com/hosted-service/subgraph/humanprotocol/moonbeam):
There was no subgraph like this, I am not sure it's going to be created automatically (only the deploy to pre-created subgraph was tested before).
Hi @ivhus, I believe package.json is ok since workflow only uses From my experience, the subgraph is not created automatically, so I believe the deployment will only take effect if the humanprotocol/moonbeam subgraph is created in advance using the foundation account. |
|
@ivhus i tagged you in the ticket so we could use a foundation controlled subgraph, like the other two production nets |
|
https://thegraph.com/hosted-service/subgraph/humanprotocol/moonbeam so I assume after the merge it should be deployed |
|
You will need to create the project
|
Confirmed, the repo has been created on The Graph. I think we are good to go. |
No description provided.