The HyperdriveFactory emits a Deployed event that can be used to get a list of all of the Hyperdrive pools deployed by a given factory. As of right now, there isn't a single address that can be used to traverse through the factories and get a list of all of the Hyperdrive pools tracked by the Element DAO.
We're in a good position to build a Hyperdrive Registry as all that really remains to be done is to create a registry contract that wraps the Hyperdrive factories and stores an array of factory addresses (or a richer data-structure with more metadata). The best approach may be to re-architect the factories and deployers so that a single registry contract can serve all Hyperdrive deployment needs, which would also solve the problem.
The
HyperdriveFactory
emits aDeployed
event that can be used to get a list of all of the Hyperdrive pools deployed by a given factory. As of right now, there isn't a single address that can be used to traverse through the factories and get a list of all of the Hyperdrive pools tracked by the Element DAO.We're in a good position to build a Hyperdrive Registry as all that really remains to be done is to create a registry contract that wraps the Hyperdrive factories and stores an array of factory addresses (or a richer data-structure with more metadata). The best approach may be to re-architect the factories and deployers so that a single registry contract can serve all Hyperdrive deployment needs, which would also solve the problem.