akash-network / akash-network/console

[Data Request] Export of GPU bids/leases for academic research (Jan-Feb 2025)

Open
#3,165 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
264
Forks
94
Avg merge
18h 49m
Merged PRs (30d)
297

Description

Hi team,

I'm a finance PhD researcher (Bocconi University) building an event study on GPU pricing around the DeepSeek-V3 release. The hypothesis is that frontier H100 SXM5 rental prices compressed more than commodity-tier GPU prices after the shock — a clean test of the within-vendor commoditization channel.

I need historical MsgCreateBid and MsgCreateLease transactions, with the matched GPU attributes (vendor, model, RAM, interface) and pricing (uakt / uusd), for the block range ~19,800,000 to ~20,500,000 (roughly Jan 20 – Feb 10, 2025).

Public RPCs have pruned this range — the deepest free archive I could find only goes back to ~Feb 2026. Since console-api already parses bid manifests into relational tables via the bid-screening / gpu-attribute-parser pipeline, would someone with read access to the production Postgres be willing to run a one-off SQL export to CSV for that window?

I will prominently cite Akash Network and the maintainers in the paper, and I'll share the final clean panel back with the community.

Thank you!

Rubén Fernández-Fuertes
PhD candidate, Finance — Bocconi University
fernandezfuertesruben@gmail.com

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the console-api data path and the bid-screening and gpu-attribute-parser pipeline named in the request. Determine whether MsgCreateBid and MsgCreateLease records and the requested GPU attributes and pricing exist in PostgreSQL for blocks 19,800,000–20,500,000. Done means a validated CSV export for that window, subject to the required production access.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgresql, sql, typescript
Domain
data-engineering, databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.