diff --git a/website/pages/en/deploying/hosted-service.mdx b/website/pages/en/deploying/hosted-service.mdx index 2e6093531110..79301caedc92 100644 --- a/website/pages/en/deploying/hosted-service.mdx +++ b/website/pages/en/deploying/hosted-service.mdx @@ -46,6 +46,18 @@ graph init --from-example --product hosted-service / The example subgraph is based on the Gravity contract by Dani Grant that manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated. The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events. Continue on to the [subgraph manifest](/developing/creating-a-subgraph#the-subgraph-manifest) to better understand which events from your smart contracts to pay attention to, mappings, and more. + +### From a Proxy Contract + +To build a subgraph tailored for monitoring a Proxy contract, initialize the subgraph by specifying the address of the implementation contract. Once the initialization process is concluded, the last step involves updating the network name in the subgraph.yaml file to the address of the Proxy contract. You can use the command below. + +```sh +graph init \ + --product hosted-service + --from-contract \ + / [] +``` + ## Supported Networks on the hosted service You can find the list of the supported networks [Here](/developing/supported-networks).