Determine GA scope

[BigLep]

Done Criteria

Engineering team understand the GA scope and has created the corresponding GitHub issues. Engineering team can get there is they have a verbal description or visual/mockup that covers:

1. What should a user see when they go to pay.filecoiin.cloud?
   • I assume we want some "metrics". Are those metrics the current value as numbers or historical values in a time-series graph or table?
2. What navigation options are available?
3. What does a user see when they click on any of those navigation options?
4. Is there any extra information that the current pay.filecoin.cloud is displaying that should be removed?
5. Requirements for the subgraph exposure/access (i.e., public or proxy) Setup how we're exposing our subgraph to pay.filecoin.cloud #87

Notes

1. PM discussion happening in https://linear.app/filoz/project/enable-filecoin-pay-console-to-be-a-usable-tool-and-data-source-3da962a03d40/overview

[BigLep]

2026-01-16 conversation with @timfong888: we'll be able to see what GA scope is supposed to look like in Tim's prototype set to "GA mode". He is doing this work in timfong888/filecoin-pay-console#42

Beyond dashboard capabilities for the working group to see filecion pay usage, we also need to account for the "console" functionality (e.g., https://pay.filecoin.cloud/console).

Engineering will away either:

1. A visual or written spec of what's needed for the GA site OR
2. Bulletted list of additions/removals/fixes to the current pay.filecoin.cloud we need to make
   so we can make an engineering plan.

I assume we'll have clarity here the first half of next week (week of 2026-01-19).

[timfong888]

GA requirements:

1. Active Wallets
2. USDFC Settled
3. Burned (need more detail to understand what and how)
4. Churned Wallets (all rails status = Terminated)

[timfong888]

FilOzone/filecoin-pay#251 is the associated for Auction work

[BigLep]

@timfong888 : thanks. Two other questions:

1. Any requirements for the "console" portion?
2. To make sure there is no confusion, the items in Determine GA scope #77 (comment) are just the current values, not time-series graphs.
3. Does anything else in pay.filecoin.cloud need to be removed, or is it ok for it to live as-is as long as the above items are included?

[BigLep]

To try and be really clear about what engineering needs here: a verbal description or visual/mockup that covers:

1. What should a user see when they go to pay.filecoiin.cloud?
   • I assume we want some "metrics". Are those metrics the current value as numbers or historical values in a time-series graph or table?
2. What navigation options are available?
3. What does a user see when they click on any of those navigation options?
   • Please make clear if their is a "console" / "connect your wallet" option and whether the current implementation at https://pay.filecoin.cloud/console is good enough
4. Is there any extra information that the current pay.filecoin.cloud is displaying that should be removed?