queries.graphql

"""
These are typical queries that I think would be used to extract data for a front-end similar to: https://merge.tina.cafe/9

In general, for the leaderboard query and onwards, I just had issues copying them in and troubleshooting through syntax issues. So they seemed to be invalid queries atm.
"""

############

"2022-03-14_Update1Checks-NFTs"

"""
Showcases, in this order:
1. mergeExample: where mass NFTs have been merged into token 23106, 2. burnedExample: where mass NFT has been merged/burned into another one, 3. noMergeExample: where nothing has happened, 4. currentAlpha, 5. yellowExample, 6. redExample, 7. blueExample
"""

{
  mergeExample: nft(id: "23106") {
    id
    owner {
      id
    }
    massValue
    massSize
    color
    tier
    mergeCount
    isAlpha
    mergedInto
    mergeTimes
    absorbedNFTs
  }
  burnedExample: nft(id: "17325") {
    id
    owner {
      id
    }
    massValue
    massSize
    color
    tier
    mergeCount
    isAlpha
    mergedInto
    mergeTimes
    absorbedNFTs
  }
  noMergeExample: nft(id: "7705") {
    id
    owner {
      id
    }
    massValue
    massSize
    color
    tier
    mergeCount
    isAlpha
    mergedInto
    mergeTimes
    absorbedNFTs
  }
  currentAlpha: nft(id: "1") {
    id
    owner {
      id
    }
    massValue
    massSize
    color
    tier
    mergeCount
    isAlpha
    mergedInto
    mergeTimes
    absorbedNFTs
  }
  yellowExample: nft(id: "70") {
    id
    owner {
      id
    }
    massValue
    massSize
    color
    tier
    mergeCount
    isAlpha
    mergedInto
    mergeTimes
    absorbedNFTs
  }
  redExample: nft(id: "2") {
    id
    owner {
      id
    }
    massValue
    massSize
    color
    tier
    mergeCount
    isAlpha
    mergedInto
    mergeTimes
    absorbedNFTs
  }
  blueExample: nft(id: "12") {
    id
    owner {
      id
    }
    massValue
    massSize
    color
    tier
    mergeCount
    isAlpha
    mergedInto
    mergeTimes
    absorbedNFTs
  }
}

###########

"Query: 2022-03-14_#1_AddressZero&Nifty"

"""
Showcases address(0) and Nifty Gateway Omnibus User entities
NOTE: not sure why NiftyGateway's tokenIds are all multiples of 10 or so it seems.
TODO: whitelist is not a field that I update yet.
"""
{
  AddressZero: user(id: "0x0000000000000000000000000000000000000000") {
    id
    mergeNFTs {
      id
    }
    whitelist
  }

  NiftyGateway: user(id: "0xe052113bd7d7700d623414a0a4585bcae754e9d5") {
    id
    mergeNFTs {
      id
    }
    whitelist
  }
}

############

"""
Simple Queries
"""
{
  NFT(first: 5) {
    id
    owner {
      id
    }
    massValue
    massSize
    color
    tier
    mergeCount
    isAlpha
    mergedInto
    mergeTimes
    absorbedNFTs
  }
}

#############

"""
Leaderboard Query: pulling information for mass leaderboard based off of value or massCount usually
"""
{
  nfts(first: 100, orderBy: massSize, orderDirection: desc, where: { merged_not(true)}) {T
    id
    owner {
      id
    }
    massValue
    massSize
    color
    tier
    mergeCount
    isAlpha
    mergedInto
    mergeTimes
    absorbedNFTs
  }
}

"""
User Query: check to see what NFT a user has, and its details... TODO: when the front-end (hypothetical) queries for user data for a person's connected HD wallet (and thus public address)... does their front end take that and input it as an input parameter into a graphQL query to the subgraph? **DK and I talked about this and it is do-able. To be done later.
"""
{
  User(id: <userAddressAsHexString>) {
    id
    mergeNFTs #Don't know if we need to specify more, of I guess that's the great thing, the front end can just poke deeper into the NFT dataset?
    whitelist
  }
}

"""
User Query Option 2: if the above doesn't work, I guess the front-end (hypothetical) just queries for all the Users that have populated entities. In that case, they would just query everything at the current block and use that data in their own database?
"""
{
  User(first: 100, orderBy: mergeNFTs.massSize, orderDirection: desc, where: { mergeNFTs.merged_not(true)}){
    id
    mergeNFTs #Don't know if we need to specify more, of I guess that's the great thing, the front end can just poke deeper into the NFT dataset?
    whitelist
  }
}