Unmasking Coordination in Arbitrum Governance

Naive funded_by linking over-merges. A conservative policy restores interpretable structure.

run_id
loading…
chain
Arbitrum
block window
loading…
Advanced metrics (pipeline + policy + lineage)
Coverage
    Ingestion / cost
      Policy profile
        Lineage
          Concentration

            1) Problem: Naive funded_by Failure

            Historical baseline (naive funded_by policy)

            top_cluster_size
            425
            cluster_count
            321

            Shared infrastructure (routers, high-fanout funders) creates artificial connectivity, producing a giant mixed cluster.

            2) Method: Conservative Policy

            Single shared funder is not sufficient to merge.
            Require ≥2 shared funders + short-burst timing.
            Suppress service-like and high-fanout keys.

            Naive: funded_by → merge · Conservative: funded_by → gated evidence

            3) Result

            cluster_count
            -
            top_cluster_size
            -
            multi_address_clusters
            -

            The giant cluster disappears. Smaller, interpretable clusters emerge.

            4) Interactive Cluster Inspection

            selection
            cluster
            cluster_id
            -
            size / degree
            -
            gov/control
            -
            evidence types
            -
            cluster_idsizegovcontrol
            Click a cluster or graph node to inspect details.

            5) Interpretation Boundary

            This is not Sybil detection.
            This is not real-world identity attribution.
            These clusters represent coordination evidence, not claims about humans or malicious actors.