I've been building a small public transparency tool for the DigiDollar lockup (dgbinsights.com — chain-verified measurement of locked collateral, companion to ddstats), and I've hit a gap in the RPC surface that I think is worth raising because it affects anyone trying to independently verify DD aggregates.
Current state (v9.26.4, tested on mainnet):
listdigidollarpositions is wallet-scoped — it returns positions in the local wallet only (returns 0 on a positionless node while getdigidollarstats reports 33 network-wide).getredemptioninfo <position_id> is also wallet-scoped ("Position not found in wallet" for any position the wallet doesn't own).getdigidollarstats returns network-wide aggregates (total collateral, active position count), which shows the node already maintains a global position index internally — there's just no RPC that lists it.
The ask: expose that existing index read-only — either a -global flag on listdigidollarpositions or a new call (getglobalpositions?), returning per position roughly what the wallet-scoped call already returns: identifier, collateral amount, mint height, unlock height, status. No consensus change, no wallet access, no new index — just a list RPC over state the node already has.
Why it matters beyond my dashboard: right now the only way to get per-position data (maturity schedules, size distributions, how much collateral unlocks when) is to scan and decode every block since activation and maintain a shadow index. That's doable — I'm building it — but it means every aggregate anyone publishes about DD is take-my-word-for-it unless the reader also builds a scanner. A one-command global view would let any node operator reproduce and audit any published DD statistic in seconds, which decentralizes trust in exactly the way DD's design intends. It would also make matured-but-unredeemed collateral visible, which keeps public "locked" figures honest over time.
Happy to help test against mainnet, write RPC docs for it, or contribute in whatever way is useful. And if there's an existing way to get this that I've missed, pointers very welcome.
I've been building a small public transparency tool for the DigiDollar lockup (dgbinsights.com — chain-verified measurement of locked collateral, companion to ddstats), and I've hit a gap in the RPC surface that I think is worth raising because it affects anyone trying to independently verify DD aggregates.
Current state (v9.26.4, tested on mainnet):
listdigidollarpositionsis wallet-scoped — it returns positions in the local wallet only (returns 0 on a positionless node whilegetdigidollarstatsreports 33 network-wide).getredemptioninfo <position_id>is also wallet-scoped ("Position not found in wallet" for any position the wallet doesn't own).getdigidollarstatsreturns network-wide aggregates (total collateral, active position count), which shows the node already maintains a global position index internally — there's just no RPC that lists it.The ask: expose that existing index read-only — either a
-globalflag onlistdigidollarpositionsor a new call (getglobalpositions?), returning per position roughly what the wallet-scoped call already returns: identifier, collateral amount, mint height, unlock height, status. No consensus change, no wallet access, no new index — just a list RPC over state the node already has.Why it matters beyond my dashboard: right now the only way to get per-position data (maturity schedules, size distributions, how much collateral unlocks when) is to scan and decode every block since activation and maintain a shadow index. That's doable — I'm building it — but it means every aggregate anyone publishes about DD is take-my-word-for-it unless the reader also builds a scanner. A one-command global view would let any node operator reproduce and audit any published DD statistic in seconds, which decentralizes trust in exactly the way DD's design intends. It would also make matured-but-unredeemed collateral visible, which keeps public "locked" figures honest over time.
Happy to help test against mainnet, write RPC docs for it, or contribute in whatever way is useful. And if there's an existing way to get this that I've missed, pointers very welcome.