Mapping external AI-task receipt IDs into LLM trace/span metadata

Open
#4,340 6 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Domain
observability

Research direction

Start by reading the linked receiptid-interoperability.md document and the proposed aipou metadata fields in this issue. Compare span attributes, session metadata, linked events, and external references against the stated privacy and evidence-boundary concerns. Done means reaching a clear decision about the integration point and metadata scope.

Written by the indexing model from the issue text.

Description

I am exploring how AI Proof of Us receipts should map into LLM traces.

AIPOU creates signed MCP task receipts with hashes, nonce/replay checks, local collector signatures, and explicit evidence boundaries. It does not replace traces, and trace systems should not be responsible for validating AIPOU rewards.

For observability, the useful part may be a small external reference:

{
  "aipou.receipt_id": "0x...",
  "aipou.validation_status": "local | validated | claimed | rejected",
  "aipou.evidence_boundary": "https://github.com/0xddneto/AI-Proof-of-Us/blob/main/docs/evidence-boundaries.md"
}

Would this belong as span attributes, session metadata, a linked event, or an external reference? I am trying to keep raw prompts/outputs private and avoid noisy or misleading metadata.

Interoperability note:

https://github.com/0xddneto/AI-Proof-of-Us/blob/main/docs/receiptid-interoperability.md

Dominant language
Python
Stars
7.5k
Forks
1.2k
Avg merge
2d 6h
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from traceloop/openllmetry

All issues in traceloop/openllmetry

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.