Track a project's contract deployment events

[ccerv1]

Describe the feature you'd like to request

Any time an EOA address deploys a contract, it should be stored as an event Any time a factory contract deploys a contract, it should be stored as an event

Describe the solution you'd like

The cumulative number of contracts deployed by a project, filterable to whether it came from an EOA or a factory

Describe alternatives you've considered

na

[ravenac95]

Just to validate @ccerv1, the EOA address in question is an OSS-Directory Project's EOA address that deploy a contract?

[ryscheng]

I think creator addresses can either create a factory or a contract

And a factory can also create a contract

[ccerv1]

@ravenac95 - I'm going to remove my name from this task.

I completed the reindexing the other day, and it worked.

The Dune queries I used are:

• Contracts
• Factories

I believe this provides the source material needed to index deployment events, but let me know if there's more needed from me.

Finally, in terms of the tagging conventions, I used:

• eoa = any EOA regardless of whether it deploys something
• creator = an EOA that should be monitored for contract deployments
• contract = any smart contract
• factory = a smart contract that should be monitored for contract deployments

@ryscheng we could refactor this to make any factory also a creator (or we could remove factory given that any contract that is also a creator would be a factory) or we could just move on ;)

[ryscheng]

sgtm, sounds like factory is redundant, we have (eoa, creator) or (contract, creator) right?

[ccerv1]

@ravenac95 here's the query for contract deploys

... and here's an approximation for factory deploys (excluding Safes)