@pro100skm I did this deployment on Apothem , I did it twice
First time : I did it from the latest block count , but it only indexed one / two records.
Second time: 35252497 This block count, It's now indexing data when checked after certain intervals.
Deployment : graph-node-apothem.yodaplus.net:80...
No, doesn't work. At least returns empty data.
This is libs that I use for compile and build subgraph. Are they ok?
"@graphprotocol/graph-cli": "^0.21.0","@graphprotocol/graph-ts": "^0.20.0",
"@openzeppelin/contracts": "^4.6.0",
"@openzeppelin/subgraphs": "^0.1.7-1"
@pro100skm Can you try redeploying it? I have deployed a subgraph on mainnet to query the ERC721 which seems to work fine.
graph-node.yodaplus.net:8000/subgr...
I have used this repo to deploy it.
github.com/wighawag/eip721-subgraph
Which subgraph are you using? Do you have the github link?
github.com/pro100skm/test-subgraph
@pro100skm Getting some compilation erros
xdc.dev/uploads/articles/qx5bp3it3...
@pro100skm I did this deployment on
Apothem, I did it twiceFirst time : I did it from the latest block count , but it only indexed one / two records.
Second time: 35252497 This block count, It's now indexing data when checked after certain intervals.
Deployment : graph-node-apothem.yodaplus.net:80...
apothem is great, but we have a problem with mainnet graphql