Skip to content

Commit

Permalink
feat: add ANY_EVM semantics to deployer crawling (#1540)
Browse files Browse the repository at this point in the history
* Checks whether the oss-directory network is any_evm, includes if so
* Fix the join to join on both source and namespace
  • Loading branch information
ryscheng authored May 27, 2024
1 parent e1f317c commit 0f2c92c
Showing 1 changed file with 9 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -123,15 +123,22 @@ discovered_contracts as (
"CONTRACT" as artifact_type,
ob.project_id,
ad.contract_address as artifact_source_id,
ob.artifact_source,
ob.artifact_namespace,
ob.artifact_namespace as artifact_source,
ad.contract_address as artifact_name,
ad.contract_address as artifact_url
from ossd_blockchain as ob
inner join all_deployers as ad
on
ob.artifact_source_id = ad.deployer_address
and UPPER(ob.artifact_namespace) = UPPER(ad.artifact_namespace)
{#
We currently do not really have a notion of namespace in
oss-directory. We may need to change this when that time comes
#}
and UPPER(ob.artifact_source) in (UPPER(ad.artifact_source), "ANY_EVM")
and UPPER(ob.artifact_namespace) in (
UPPER(ad.artifact_namespace), "ANY_EVM"
)
and UPPER(ob.artifact_type) in ("EOA", "DEPLOYER", "FACTORY")
),

Expand Down

0 comments on commit 0f2c92c

Please sign in to comment.