2023-01-04 19:55:23 +00:00
# MobyMask Watcher
2023-01-10 14:21:00 +00:00
First try the [mobymask demo in stack orchestrator ](https://github.com/cerc-io/stack-orchestrator/tree/main/app/data/stacks/mobymask ) to quickly get started. Advanced users can see [here ](/docs/README.md ) for instructions on setting up a local environment by hand.
2022-06-15 12:08:39 +00:00
## Setup
2023-01-04 19:55:23 +00:00
Run the following command to install required packages:
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
```bash
yarn & & yarn build
```
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
If the watcher is "lazy", run the server:
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
```bash
yarn server
```
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
GQL console: http://localhost:3010/graphql
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
If the watcher is "active", run the job-runner:
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
```bash
yarn job-runner
```
then the server:
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
```bash
yarn server
```
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
Next, clone the MobyMask repo and checkout this branch:
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
```bash
git clone https://github.com/cerc-io/MobyMask & & cd MobyMask
git checkout use-laconic-watcher-as-hosted-index
```
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
Install the packages:
```bash
yarn
```
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
Deploy the contract:
```bash
cd packages/hardhat
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
yarn deploy
# deploying "PhisherRegistry" (tx: 0xaebeb2e883ece1f679304ec46f5dc61ca74f9e168427268a7dfa8802195b8de0)...: deployed at 0xMobyAddress with 2306221 gas
# $ hardhat run scripts/publish.js
# ✅ Published contracts to the subgraph package.
# Done in 14.28s.
```
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
Export the address of the deployed contract to a shell variable for later use:
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
```bash
export MOBY_ADDRESS="0xMobyAddress"
```
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
Run the following GQL mutation in watcher GraphQL endpoint http://127.0.0.1:3010/graphql
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
```graphql
mutation {
watchContract(
address: "MOBY_ADDRESS"
kind: "PhisherRegistry"
checkpoint: true
)
}
```
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
Get the latest block
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
```graphql
query {
latestBlock {
hash
number
}
}
```
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
Run the following GQL query in GraphQL endpoint
```graphql
query {
isPhisher(
blockHash: "LATEST_BLOCK_HASH"
contractAddress: "MOBY_ADDRESS"
key0: "TWT:phishername"
) {
value
proof {
data
}
}
isMember(
blockHash: "LATEST_BLOCK_HASH"
contractAddress: "MOBY_ADDRESS"
key0: "TWT:membername"
) {
value
proof {
data
}
}
}
```
Run the following GQL subscription in generated watcher GraphQL endpoint:
```graphql
subscription {
onEvent {
event {
__typename
... on PhisherStatusUpdatedEvent {
entity
isPhisher
},
... on MemberStatusUpdatedEvent {
entity
isMember
}
},
block {
number
hash
}
}
}
```
Update isPhiser and isMember lists with names
```bash
yarn claimPhisher --contract $MOBY_ADDRESS --name phisherName
```
```bash
yarn claimMember --contract $MOBY_ADDRESS --name memberName
```
- The events should be visible in the subscription at GQL endpoint. Note down the event blockHash from result.
- The isMember and isPhisher lists should be indexed. Check the database (mobymask-watcher) tables `is_phisher` and `is_member` , there should be entries at the event blockHash and the value should be true. The data is indexed in `handleEvent` method in the [hooks file ](./src/hooks.ts ).
Update the the previous query with event blockHash and check isPhisher and isMember in GraphQL playground
```graphql
query {
isPhisher(
blockHash: "EVENT_BLOCK_HASH"
contractAddress: "MOBY_ADDRESS",
key0: "TWT:phishername"
) {
value
proof {
data
}
}
isMember(
blockHash: "EVENT_BLOCK_HASH"
contractAddress: "MOBY_ADDRESS",
key0: "TWT:membername"
) {
value
proof {
data
}
}
}
```
The data is fetched from watcher database as it is already indexed.
## Additional Commands
To watch a contract, run:
```bash
yarn watch:contract --address < contract-address > --kind < contract-kind > --checkpoint < true | false > --starting-block [block-number]
```
where:
- `address` : Address or identifier of the contract to be watched.
- `kind` : Kind of the contract.
- `checkpoint` : Turn checkpointing on (`true` | `false` ).
- `starting-block` : Starting block for the contract (default: `1` ).
Examples:
Watch a contract with its address and checkpointing on:
```bash
yarn watch:contract --address 0x1F78641644feB8b64642e833cE4AFE93DD6e7833 --kind ERC20 --checkpoint true
```
2022-11-25 06:01:20 +00:00
2023-01-04 19:55:23 +00:00
Watch a contract with its identifier and checkpointing on:
2022-11-25 06:01:20 +00:00
2023-01-04 19:55:23 +00:00
```bash
yarn watch:contract --address MyProtocol --kind protocol --checkpoint true
```
2022-11-25 06:01:20 +00:00
2023-01-04 19:55:23 +00:00
To fill a block range:
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
```bash
yarn fill --start-block < from-block > --end-block < to-block >
```
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
* `start-block` : Block number to start filling from.
* `end-block` : Block number till which to fill.
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
To create a checkpoint for a contract:
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
```bash
yarn checkpoint create --address < contract-address > --block-hash [block-hash]
```
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
* `address` : Address or identifier of the contract for which to create a checkpoint.
* `block-hash` : Hash of a block (in the pruned region) at which to create the checkpoint (default: latest canonical block hash).
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
To reset the watcher to a previous block number:
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
```bash
yarn reset watcher --block-number < previous-block-number >
```
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
Reset job-queue:
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
```bash
yarn reset job-queue
```
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
Reset state:
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
```bash
yarn reset state --block-number < previous-block-number >
```
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
* `block-number` : Block number to which to reset the watcher.
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
To export and import the watcher state:
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
In the source watcher, export watcher state:
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
```bash
yarn export-state --export-file [export-file-path] --block-number [snapshot-block-height]
```
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
* `export-file` : Path of file to which to export the watcher data.
* `block-number` : Block height at which to take snapshot for export.
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
In the target watcher, run job-runner:
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
```bash
yarn job-runner
```
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
Import watcher state:
2022-11-23 12:12:25 +00:00
2023-01-04 19:55:23 +00:00
```bash
yarn import-state --import-file < import-file-path >
```
2022-11-23 12:12:25 +00:00
2023-01-04 19:55:23 +00:00
* `import-file` : Path of file from which to import the watcher data.
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
Run server:
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
```bash
yarn server
```
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
To inspect a CID:
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
```bash
yarn inspect-cid --cid < cid >
```
2022-06-15 12:08:39 +00:00
2023-01-04 19:55:23 +00:00
* `cid` : CID to be inspected.