DODO Docs
Search
⌃K

Subgraph

DODO uses Subgraph to provide events and data related to contracts in the query chain

1.Introduction

Transaction History

  • Each OrderHistory event is triggered by a DODOProxy contract execution, if the transaction is routed to a transaction pool on the DODO platform, the events triggered by the underlying pool will be ignored to prevent duplicate logging.
  • If the transaction does not come from DODOProxy, then the transaction events triggered by the underlying pool will be logged by OrderHistory.

Trading

  • Every transaction event comes from a smart contract on the DODO platform.

Flow pool information

  • Real-time pool status tracking by Pair
  • Note that pools of type VIRTUAL are pools that do not actually exist, and are created for statistical purposes
Interface Request Endpoints The endpoints for each service are available in our open source repository

2. Usage Examples

  • Retrieve swap records
{
swaps(where:{pair:"0xc9f93163c99695c6526b799ebca2207fdf7d61ad"},first:10){
hash
from
to
fromToken{id}
toToken{id}
amountIn
amountOut
}
}
  • Query user information
{
user(id:"0x8982a82a77eaf1cd6f490b67ad982304ecc590af"){
id
txCount
tradingRewardRecieved
}
}
  • Retrieve pool status by day, hour dimension
{
pairDayDatas(first:100,orderBy:date,orderDirection:desc){
date
volumeBase
volumeQuote
feeBase
feeQuote
baseToken{
symbol
}
quoteToken{
symbol
}
}
}JSON
  • Retrieve crowdfunding pool status
{
crowdPoolingDayDatas{
date
crowdPooling {
id
creator
baseToken{
symbol
}
quoteToken{
symbol
}
}
investedQuote
investCount
newcome
poolQuote
}
}