Upala subgraph

Clients

Requests from DB (repo)

When writing data:

• Get pool manager for the pool address
• Get scoreBundle timestamp by hash

When reading data (housekeeping):

• Get array of deleted roots since [latestDeletedRootTimestamp]
• Get array of base score updates since [latestBaseScoreUpdateTimestamp]

Requests from group manager (repo)

• When updating scores "is this bundleHash deleted"
• When updating base score "what is the current base score for the pool address"
• TBD Commitments

Requests from multipassport (repo)

When populating multipassport:

• Get UpalaID for the provided address (search owners and delegates of the ID)
• Get owner and delegates for the Upala ID"
• Get pool metadata by address
• Get poolType (poolFactoryAddress) by pool address
• Get pool balance by pool address todo
• Get pool base score by pool address todo

Requests from unique-human-lib (repo)

• Get approved pools for the dapp address
• Get delegates by Upala ID
• Get poolType (poolFactoryAddress) by pool address
• Get pool balance by pool address todo
• Get pool base score by pool address todo

Housekeeping

Data needed for the subgraph itself.

All spawned pools are registered in Upala.sol with an emitted event in order to create Data source templates for the subgraph. Same for DApps Same for poolFactories

Monitored contracts

• Upala
• Pool and pool factory
• DApp lib and example DApp
• DAI