📊 Merchant Gas Spending Dashboard API

[mijinummi]

📌 Overview

Businesses and merchants require visibility into their gas expenditures to monitor costs and optimize transaction strategies. Without structured reporting, tracking multi-chain spending is inefficient and error-prone.

This task introduces a Merchant Gas Spending Dashboard API that aggregates gas usage and provides detailed breakdowns per chain for actionable business insights.

---

🎯 Objective

Build an API that:

• Aggregates gas spending for merchants on a monthly basis
• Provides detailed breakdowns by chain and transaction type
• Supports multi-chain and multi-wallet tracking
• Enables reporting for financial planning and cost optimization

---

🛠 Scope of Work

1️⃣ Monthly Spending Aggregation

• Collect historical gas usage for merchant wallets:
  • Base fee and priority fee per transaction
  • Gas used per transaction
  • Transaction timestamp
• Aggregate data by month
• Compute total gas cost in ETH / native token and USD equivalent

---

2️⃣ Chain-Level Breakdown

• Provide per-chain gas spending summaries
• Include metrics such as:
  • Number of transactions
  • Average gas per transaction
  • Total gas consumed
• Optionally, include breakdown by transaction type (e.g., transfer, swap, contract call)

---

3️⃣ API Endpoints

Expose endpoints for merchant reporting:
GET /dashboard/gas-spending?merchantId=&month=
GET /dashboard/gas-spending/:merchantId/detail

Requirements:

• Input validation (merchant ID, month format)
• Multi-chain aggregation support
• Pagination for detailed transaction views
• JSON response structured for easy front-end visualization

Example response:

{
  "merchantId": "1234",
  "month": "2026-02",
  "totalGasETH": "12.45",
  "totalGasUSD": "4,980.50",
  "chains": [
    {
      "chainId": 1,
      "chainName": "Ethereum",
      "gasETH": "8.12",
      "gasUSD": "3,250.30",
      "transactions": 120
    },
    {
      "chainId": 56,
      "chainName": "BSC",
      "gasETH": "4.33",
      "gasUSD": "1,730.20",
      "transactions": 80
    }
  ]
}

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[mftee]

@mftee has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I am a fullstack software developer with multiple years experience in the industry. I can deliver on this issue in a few hours.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @mftee to this issue.

[drips-wave]

Congratulations, @mftee! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @mftee: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are issued when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊