This subgraph aims to allow anyone to query data for the Loopring Exchange v2, with support for L2 blocks, transactions, accounts, pools, tokens, pairs and aggregations of trade volumes by token and pair on a weekly and daily basis.
The schema file contains documentation of most of the fields for almost all of the available entities.
The Proxy entity contains data about the upgradable proxy, such as the current implementation (Exchange entity), all past implementations, as well as a count of all blocks processed across all implementations.
This entity represents implementations of the exchange. It's a simple entity with the address of said implementation as it's ID, a link to the proxy (to be able to derive the past implementations list on the Proxy entity), and a list of all tokens registered when that implementation was active.
The Token entity contains the classic metadata found on any ERC20 (name, symbol, decimals) as well as the address of said token contract, the total traded volume (denominated in it's own token value), and the daily and weekly entities created for said token. Its ID is equal to the internal ID within the Loopring exchange.
The Pair entity represents a pair of two tokens. There is only a single Pair entity for a pair of two tokens, since it's ID is standardized in the following manner <LOWEST Token ID>-<HIGHEST Token ID>.
This entity contains trade volume data, latest price of each token in the pair (denominated on the other token), daily and weekly data aggregations, as well as a list of all the trades involving said pair.
The Account interface is implemented by the following entities: User, Pool and ProtocolAccount. Since users and pools are all identified by account IDs within the loopring data, they share some similarities, so we wanted to represent them in a similar way, but still keep them as unique entities.
Both User and Pool entities have a unique ID within loopring, which is used as the ID for the entities, and that ID is linked to the address, which the entity also tracks.
These entities also have a list of all the AccountTokenBalance entities that a User or Pool has, and they also keep track of the last transaction where the entity was updated and the transaction it was created at.
ProtocolAccount is a special singleton entity that keeps track of all AccountTokenBalance entities that the protocol has, for when protocolFees start being collected.
This entity reprensents the balance of a particular Token, that a particular Account has.
Aside from links to the relevant Token and Account, and a balance field, this entity also has a list of all the Transaction entities that modified it.
This entity reprensents a "unique" Non-Fungible Token (or NFT). It can be either an ERC1155 or ERC721 NFT.
This entity reprensents a particular NFT slot for a given Account.
In Loopring, NFTs are "stored" in slots for each account, and they support NFT balances (in case it's an ERC1155).
Each slot is a combination of the Account.id and Token.id that was passed in the transaction where the AccountNFTSlot was created. Only Token.id >= 32768 are valid for NFT slots.
The Block entity represents a single L2 block on the Loopring exchange.
It contains L1 metadata for the block (gasLimit, timestamp, L1 block height when the block was included, etc), as well as L2 metadata, like blockType, blockSize, blockVersion, operator that handled the block, etc.
It also contains the raw data represented as a hex string, parsed block data, like the fee maker and taker bips, and a list of all the parsed transactions from said block of raw data.
The Transaction interface is implemented by entities that represent all the transaction types available in the Loopring exchange:
- AccountUpdate
- AmmUpdate
- SignatureVerification
- Deposit
- Withdrawal
- Transfer
- Add
- Remove
- OrderbookTrade
- Swap
- WithdrawalNFT
- TransferNFT
- TradeNFT
- SwapNFT
- MintNFT
- DataNFT
The interface only defines the commmon points, which is only a reference to the Block entity where the transaction was created, the raw L2 data expressed as a hex string, and also a list of all the AccountTokenBalance entities that the transaction modified (useful for the transactions lists on said entity).
Each of the implementations contains type specific parsed data from the raw L2 data. For more information, you can check the schema file, which has all relevant fields documented.
There's also a parallel interface called TransactionNFT, which makes sure to include the nfts and slots fields, so that NonFungibleToken entities can have a list of transactions that included them, for ease of use.
There are specific entities that aggregate AccountTokenBalance, Token and Pair data on a daily and weekly basis.
PairDailyData and PairWeeklyData aggregate data for the Pair entity such as trade volume and token price (high, low, open, close).
TokenDailyData and TokenWeeklyData aggregate data for the Token entity, in particular the trade volume.
AccountTokenBalanceDailyData and AccountTokenBalanceWeeklyData aggregate data for the AccountTokenBalance entity, in particular the balances for each of the Token entities that and Account has.
All daily/weekly aggregation entities have fields to reference the day/week start and end, as well as the day/week "number". This number is relative to the Loopring exchange v2 launch, since we needed to define a start point for all daily/weekly aggregation entities.
If there's not activity for a Token or Pair within a day/week, there won't be an entity available for that day, and all values can be safely assumed as 0. We don't include these "null" entities since if there's no activity, there's no event to hook to and create the entity for that day/week.
Get all token balances for an account with its account ID
{
accountTokenBalances(where: {account: "<ACCOUNT-ID>"}) {
id
token {
id
}
account {
id
}
balance
}
}Get all account token balances for a specific token
{
accountTokenBalances(where: {token: "<TOKEN-ID>"}) {
id
token {
id
}
account {
id
}
balance
}
}Get all swaps for a particular account ID
{
swaps(where: {account: "<ACCOUNT-ID>"}) {
account {
id
}
pool {
id
}
tokenA {
symbol
decimals
}
tokenB {
symbol
decimals
}
fillSA
fillSB
feeA
feeB
id
tokenAPrice
tokenBPrice
}
}Get all orderbook trades for a particular account ID (no need to do 2 queries, we can do it on a single one now with account_contains:["<ACCOUNT-ID>"])
{
orderbookTrades(where:{accounts_contains:["<ACCOUNT-ID>"]}) {
accountA {
id
}
accountB {
id
}
accounts {
id
}
tokenA {
symbol
decimals
}
tokenB {
symbol
decimals
}
fillSA
fillSB
feeA
feeB
id
tokenAPrice
tokenBPrice
}
}
Get pair daily data for ETH-LRC pair (0-1) ordered by dayNumber (ascending)
{
pairDailyDatas(where:{pair:"0-1"}, orderBy: dayNumber, orderDirection: asc) {
pair {
token0 {
id
symbol
}
token1 {
id
symbol
}
}
dayStart
dayEnd
dayNumber
token0PriceLow
token1PriceLow
token0PriceHigh
token1PriceHigh
token0PriceOpen
token1PriceOpen
token0PriceClose
token1PriceClose
tradedVolumeToken0
tradedVolumeToken1
}
}