You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
usage-meter: link usage records to attestation ids across contracts #70
Metering and attestation are separate contracts with no link between them.
Usage can be recorded with no corresponding attestation, and an attestation can
exist with no usage — so an invoice cannot be traced back to the evidence that
justifies it. That traceability is the entire pitch.
What to do
Extend the usage record with an attestation_id.
Cross-contract call into audit-registry to verify the attestation exists,
is not superseded, and belongs to the claimed payer.
Reject double-metering the same attestation id.
Decide the policy for usage with no attestation: reject, or record as
unattested and price differently. Make it configurable per payer, and default
to the stricter option.
Measure the cost of the cross-contract call — if it is prohibitive, consider
verifying a batch root instead.
Acceptance criteria
Usage records carry a verified attestation reference
Double-metering the same attestation rejected
Unattested-usage policy configurable, defaulting to strict
Cross-contract call cost measured and documented
Notes
Depends on the cross-contract authorization pattern issue — get that right
before wiring contracts together, or the call becomes a privilege-escalation
path.
For context: 200+ contributions shipped across the ecosystem, clean reviews, and I contributed to this project last wave with no dropped PRs or delays.
I’ll add comprehensive tests for DatasetRegistry, LicenseRouter, and RoyaltySplitter — covering happy paths, authorization, edge cases, expiry, revocation, and failures.
Aiming for >85% coverage and cargo test --all green before PR.
Activity
Alheriii commentedon Aug 24, 2026
Hi there 👋
I’d love to pick this one up.
For context: 200+ contributions shipped across the ecosystem, clean reviews, and I contributed to this project last wave with no dropped PRs or delays.
I’ll add comprehensive tests for DatasetRegistry, LicenseRouter, and RoyaltySplitter — covering happy paths, authorization, edge cases, expiry, revocation, and failures.
Aiming for >85% coverage and cargo test --all green before PR.
Can I be assigned? Thanks!
joelpeace48-cell commentedon Aug 24, 2026
@Alheriii you are assigned, ensure all ci pipeline are green
grantfox-oss commentedon Aug 24, 2026
🦊 GrantFox — @Alheriii has been assigned to this issue as part of the Third Campaign campaign!
Next steps:
Closes #70)Good luck! Track your progress on GrantFox.
grantfox-oss commentedon Aug 24, 2026
🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!
@Alheriii's PR #84 was approved and merged by @joelpeace48-cell.
🏆 @Alheriii: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (153 total points). Track your full progress on GrantFox.
👏 Great work, @Alheriii! Keep contributing to FinesseStudioLab.