To get the most out of your Goldsky setup and ensure smooth performance and scalability, follow these recommended practices:
Only include ABI entries relevant to the events you plan to index. This reduces noise and improves decoding accuracy.
Avoid syncing from block 0 unless absolutely necessary. Set a reasonable startBlock to speed up syncing and reduce resource usage.
Structure your entities based on your app’s business model. Use clear and semantic naming like UserPrediction, Matchday, or RewardClaim.
Index only the events and fields you truly need. This keeps response times fast and subgraph costs low.
If your contract is upgraded or schema changes, create a new subgraph version rather than modifying the live one. This ensures continuity and reliability.
Watch for decoding failures, unexpected null fields, or schema mismatches in the Goldsky dashboard. Fix issues early to avoid gaps in data.
Use Goldsky’s CLI or APIs to automate schema deployment as part of your app’s continuous deployment pipeline.