FilOzone / FilOzone/filecoin-pay-explorer

feat(explorer): service metric cards on the service page

Open
#464 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
TypeScript
Stars
3
Forks
7
Avg merge
5d 14h
Merged PRs (30d)
47

Description

### Description

Above the rails/dataset content, show four cards for the payer/operator pair: recurring spend per month, one-time ops spend, account-level runway, and locked deposit. Locked deposit copy states the deposit returns on terminate.

Spend and locked come from the pair's rails, pricing from `getServicePrice()`, runway from account funds and lockup rate. These were already real (not `PocChip`) in the POC branch; this is porting them onto #409's page.

### Additional context

Parent: #460. Depends on #409. Not a Warm Storage-only feature, but the one-time ops split only means something for FWSS today.

Merges alone: cards read from rails and contract calls that exist today; no new subgraph dependency.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the service page from #409 and inspect how its rails and contract calls expose payer/operator data. Check the existing getServicePrice(), account funds, and lockup rate sources. Done means four cards show recurring monthly spend, one-time ops spend, account-level runway, and locked deposit, with the stated termination copy.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
blockchain, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
64/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.