This is a FireSquid version of the sample squid showcasing EVM log indexing for substrate chains with a Frontier EVM pallete, like Astar or Moonbeam. This template indexes Moonsama token transfers over the Moonriver network and serves them via graphql API. Playground
# 1. Install dependencies
npm ci
# 2. Compile typescript files
make build
# 3. Start target Postgres database and detach
make up
# 4. Start the processor
make process
# 5. The command above will block the terminal
# being busy with fetching the chain data,
# transforming and storing it in the target database.
#
# To start the graphql server open the separate terminal
# and run
make serve
To migrate old (v5) Squids to FireSquid, follow the Migration Guide
Start development by defining the schema of the target database via schema.graphql
.
Schema definition consists of regular graphql type declarations annotated with custom directives.
Full description of schema.graphql
dialect is available here.
Mapping developers use TypeORM EntityManager
to interact with target database during data processing. All necessary entity classes are
generated by the squid framework from schema.graphql
. This is done by running npx sqd codegen
command.
All database changes are applied through migration files located at db/migrations
.
squid-typeorm-migration(1)
tool provides several commands to drive the process.
It is all TypeORM under the hood.
# Connect to database, analyze its state and generate migration to match the target schema.
# The target schema is derived from entity classes generated earlier.
# Don't forget to compile your entity classes beforehand!
npx squid-typeorm-migration generate
# Create template file for custom database changes
npx squid-typeorm-migration create
# Apply database migrations from `db/migrations`
npx squid-typeorm-migration apply
# Revert the last performed migration
npx squid-typeorm-migration revert
It is necessary to import the respective ABI definition to decode EVM logs. For Moonsama transfers we use the standard ERC721 interface, see src/abis/ERC721.json
.
To generate a type-safe facade class to decode EVM logs, use squid-evm-typegen(1)
:
npx squid-evm-typegen --abi src/abi/ERC721.json --output src/abi/erc721.ts
Squid tools assume a certain project layout.
- All compiled js files must reside in
lib
and all TypeScript sources insrc
. The layout oflib
must reflectsrc
. - All TypeORM classes must be exported by
src/model/index.ts
(lib/model
module). - Database schema must be defined in
schema.graphql
. - Database migrations must reside in
db/migrations
and must be plain js files. sqd(1)
andsquid-*(1)
executables consult.env
file for a number of environment variables.
It is possible to extend squid-graphql-server(1)
with custom
type-graphql resolvers and to add request validation.
More details will be added later.
This is alpha-quality software. Expect some bugs and incompatible changes in coming weeks.
# 1. Setup an npx alias (will work only in the local Squid folder)
alias sqd="npx sqd"
# 2. Pass your generated deployment key to CLI
sqd auth --key <your_deployment_key>
# 3. Deploy your squid
sqd squid:release <squid_name>@<squid_version> --source <github_url>\#<commit_hash>
query ExampleQuery {
zenlinkInfos {
totalTvlUSD
totalVolumeUSD
updatedDate
txCount
}
factories {
totalLiquidityETH
totalLiquidityUSD
totalVolumeETH
totalVolumeUSD
txCount
id
pairCount
}
stableSwapInfos {
id
poolCount
totalTvlUSD
totalVolumeUSD
txCount
swaps {
tvlUSD
volumeUSD
}
}
bundles {
ethPrice
}
stableSwaps {
lpToken
tokens
tvlUSD
virtualPrice
volumeUSD
id
}
zenlinkDayInfos(limit: 5, orderBy: date_DESC) {
date
dailyVolumeUSD
tvlUSD
}
stableDayData(limit: 5, orderBy: date_DESC) {
dailyVolumeUSD
date
tvlUSD
}
}