AGGIES LabBLOCKMINE

AGGIES Lab · Texas A&M University · Research Project

Blockchain Mining Research

Mining public blockchains for evidence. We crawl publicly accessible data across different public chains at scale and read it for signals of opportunity and threat, reporting only what the records support.

On-chain and public ecosystem data collected with provenance, normalized across chains, and derived into opportunity and threat signals with stated denominators and limits.

Research scope. The crawling pipeline and on-chain datasets are in development. No blockchain-derived dataset, figure, or finding is published on this site yet; the four intelligence modules draw on public registries only.

public chainsblocks · tx · code · eventsCrawlpublic nodes · APIsNormalizesnapshots · sha256DerivedenominatorsOpportunitiesThreatsprovenance kept per record · addresses never resolved to persons · partial coverage stated
Planned pipeline. A diagram of the method; it encodes no measured data and no chain state.

About

Why mine public blockchains?

Public blockchains publish their entire history. Every transaction, contract deployment, token transfer, and governance action on chains such as Bitcoin and Ethereum is openly readable by anyone who runs a node or queries a public endpoint. That makes them one of the largest publicly accessible records of economic and technical activity, and one of the least studied as evidence.

This program crawls that record at scale across different public chains and reads it for two kinds of signal. Opportunities, where activity, recurring failures, and gaps point to unmet needs and open problems. Threats, where exploits, concentration, and dependency expose weaknesses. Mining here means data mining of public ledgers, not operating proof-of-work hardware.

The same discipline as the rest of BLOCKMINE applies. Only publicly accessible data is collected. Every record keeps its chain, block, and retrieval time. Addresses are never resolved to individuals. A derived figure is published only with its denominator, its window, and its limits.

Focus Areas

What we are looking for

2 opportunity themes, 2 threat themes, and 2 foundations that make the signals collectable and defensible.

  1. 01
    Foundation

    Public-Chain Data Collection

    Crawling publicly accessible data from different public blockchains at scale: blocks, transactions, contract code and events, and public ecosystem records, with provenance kept for every record.

    Study questions and validity
    • Which public nodes, endpoints, and archival snapshots give complete and verifiable coverage of a chain?
    • How is block coverage measured and reported when a crawl is partial?
    • How are records de-duplicated and reconciled across sources that disagree?
    • What retrieval metadata (chain, block, endpoint, time, hash) must travel with every record?

    Coverage is reported as blocks ingested against chain height at snapshot time. Partial coverage is stated, never extrapolated.

  2. 02
    Opportunity signals

    Adoption and Activity Signals

    Where on-chain activity, contract deployment, and developer effort are growing, and which recurring failures point to unmet needs and open problems.

    Study questions and validity
    • Which categories of contracts and applications show sustained growth in deployments and use?
    • Do recurring failed or reverted transactions point to tooling or design gaps?
    • How do fee spikes and congestion windows relate to demand for specific services?
    • Which signals are robust to spam, wash activity, and automated traffic?

    An address is not a person or an organization. Activity counts are reported with the window and the filtering rules used.

  3. 03
    Opportunity signals

    Provenance and Real-World Assets

    How public ledgers are used to record provenance for physical goods, insurance, and supply chains, and where that use leaves gaps.

    Study questions and validity
    • Which provenance and traceability schemes publish records to public chains, and what do those records actually contain?
    • Where do on-chain records and off-chain documents diverge?
    • What would make a public provenance record useful to an insurer, a regulator, or a buyer?
    • Which agricultural and food supply chains have public pilots, and what did they record?

    Public records are described as posted. No private supplier relationship or commercial outcome is inferred from them.

  4. 04
    Threat signals

    Exploits and Contract Weaknesses

    On-chain traces of exploited smart contracts, drained bridges, and abandoned projects, mapped to published weakness classes.

    Study questions and validity
    • Which on-chain patterns identify an exploit event, and how are false positives controlled?
    • How do exploited contracts map to published weakness classes and to prior audits?
    • How long between deployment, first warning, and exploit?
    • What outflow can be attributed to an event in native units, and when is a USD figure defensible?

    An on-chain exploit is not a CVE unless a CVE exists. Links to the Cyber Vulnerabilities module require a defensible product or protocol match.

  5. 05
    Threat signals

    Concentration and Systemic Dependency

    How bridges, stablecoin issuers, validators, pools, and oracles concentrate value and control, and what a failure of one would propagate to.

    Study questions and validity
    • How is share of value or activity concentrated by bridge, issuer, pool, or oracle?
    • Which applications depend on a single oracle, bridge, or RPC provider?
    • How do concentration measures change across windows and chains?
    • What public evidence exists for propagation when a dependency failed?

    Concentration is not collusion. HHI is computed only over a complete denominator and withheld otherwise.

  6. 06
    Foundation

    Ethics, Legality, and Reproducibility

    Public data only, no de-anonymization of individuals, terms-of-service and rate-limit compliance, and licensed, checksummed, versioned datasets.

    Study questions and validity
    • Which collection practices respect endpoint terms of service and rate limits?
    • What rules prevent linking addresses to natural persons?
    • How are datasets licensed, versioned, and checksummed so results can be reproduced?
    • Which legal regimes govern collection and redistribution of public ledger data?

    Enacted requirements are separated from proposals and guidance. This page is not legal advice or a compliance certification.

Approach

Crawl, normalize, derive, publish

Four stages. Each step expands to inputs, outputs, assumptions, and validation. Nothing moves from Derive to Publish without review.

Datasets and pipeline

What will be measured

Published datasets and findings

None yet. Status: In development. When a dataset is released it will list the chains and block ranges covered, endpoints used, retrieval window, schema version, record counts, checksums, license, and known gaps. No blockchain-derived figure appears on this site until then.

Publications from the wider program are listed under Research and Publications.

Measurable variables (planned)

DomainVariableUnit
CoverageBlocks ingested relative to chain height at snapshotPartial coverage is reported, never extrapolated.blocks, %
ActivityTransactions and distinct active addresses per windowAn address is not a person or an organization.count/day
DeploymentNew contract deployments and verified-source shareVerification status depends on third-party explorers.count, %
FailureShare of failed or reverted transactionsFailure reasons require trace-level data.%
ExploitsIdentified exploit events and native-unit outflowsUSD values only with a timestamped price source.count, native units
ConcentrationShare of value or activity by bridge, pool, issuer, or oracleHHI needs a complete denominator; otherwise withheld.%, HHI
FeesMedian fee per transaction per windowFee markets differ by chain; not comparable without a stated basis.native units

formulas (used only with unit-validated inputs; no result when a denominator is incomplete or windows are incompatible)

coverage_fraction = blocks_ingested / chain_height_at_snapshotfailed_tx_share = failed_or_reverted_tx / total_tx_in_windowactive_addresses = count_distinct(sender_or_receiver_in_window) // addresses, not personsconcentration_hhi = sum(share_i ^ 2) // complete denominator only; otherwise withheldexploit_outflow_native = sum(outflows_from_affected_contract_in_event_window)

Team

Who is behind it

Dr. Shreyas Kumar, Principal Investigator. Professor of Practice, Department of Computer Science and Engineering, Texas A&M University, and director of AGGIES Lab.

Student researchers and collaborators will be listed here as the project team forms.

Collaborate

Interested in the project?

Students, faculty, protocol teams, insurers, and supply chain operators who want to collaborate on public blockchain data research are welcome to reach out.

shreyas.kumar@tamu.edu

Related BLOCKMINE intelligence

How the six themes relate to the four modules

Contextual research links. “Related to” does not mean proven to cause or validated as associated; an on-chain exploit is not a CVE, and concentration is not collusion.

ThemeModuleNature of link
Public-Chain Data CollectionBusiness Ideas for Open ProblemsOpen data infrastructure and indexing as venture hypotheses. hypothesis
Cyber VulnerabilitiesNode and RPC software only when a catalog entry exists. hypothesis
Adoption and Activity SignalsBusiness Ideas for Open ProblemsRecurring on-chain failures and tooling gaps as open-problem candidates. hypothesis
Supply Chain WeaknessesDependence on a few RPC providers and indexers as a software dependency. hypothesis
Provenance and Real-World AssetsSupply Chain WeaknessesPublic provenance records as one traceability input; no inferred private supplier edge. hypothesis
HealthcarePublicly posted pharmaceutical provenance records; research intelligence only. hypothesis
Exploits and Contract WeaknessesCyber VulnerabilitiesMapped to published weakness classes; an exploit is not a CVE unless one exists. hypothesis
Business Ideas for Open ProblemsAudit, monitoring, and recovery tooling gaps. hypothesis
Concentration and Systemic DependencySupply Chain WeaknessesBridge, issuer, and oracle concentration as systemic dependency. hypothesis
Cyber VulnerabilitiesSingle points of failure as attack-surface context, not exposure claims. hypothesis
Ethics, Legality, and ReproducibilityBusiness Ideas for Open ProblemsPrivacy-preserving analytics and licensed dataset tooling. hypothesis
Cyber VulnerabilitiesDisclosure norms as context for dated weakness claims. hypothesis

Original program record

Before the refocus: proof-of-work mining

Until 2026-11-08 this program studied proof-of-work mining itself. That page is preserved verbatim for the record. Its wording below is reproduced, not endorsed as the current focus.

Original overview, six topics, and four stages (captured 2026-11-07)

Studying how proof-of-work mining actually behaves: its security guarantees, its economics, and its energy footprint, measured rather than assumed.

Mining is the mechanism that secures the largest public blockchains. It converts electricity and hardware into the cost an attacker must pay to rewrite history. Yet most discussion of mining is driven by opinion rather than measurement.

This project treats mining as an engineering system worth understanding on its own terms. We look at the protocols, the hardware, the incentive structures, and the grid interactions, and we build small, instrumented experiments so that students can see the trade-offs for themselves.

Blockchain Mining is a new project at AGGIES Lab. This page will grow as the work does.

Six original topics

  1. Consensus Security. How hash power, difficulty adjustment, and block propagation shape resistance to double-spend, selfish-mining, and 51% attacks.
  2. Mining Economics. Hardware cost curves, pool reward schemes, fee markets, and the break-even points that decide where and when mining happens.
  3. Energy & the Grid. Power draw, demand response, flexible-load behavior, and what large mining loads mean for grid operators and for Texas.
  4. Mining Infrastructure Security. Firmware, pool protocols such as Stratum, remote management, and the attack surface of a modern mining operation.
  5. Hands-on Education. Lab exercises where students run a small testnet miner, read raw block headers, and measure hash rate and power on real hardware.
  6. Policy & Compliance. How emerging reporting rules, energy regulation, and cybersecurity law apply to mining operators.

Four original stages

  1. Instrument. Build a small, metered mining testbed so hash rate, power, and network behavior can be recorded precisely.
  2. Experiment. Run controlled scenarios on test networks: difficulty changes, pool switching, propagation delays, and simulated attacks.
  3. Model. Fit the measurements into security and economic models that students and partners can reason about.
  4. Publish. Share results, course material, and open tooling through AGGIES Lab.