langchain-ai/langgraph
1
0
Fork 0
mirror of https://github.com/langchain-ai/langgraph.git synced 2026-07-15 12:35:43 -04:00
Code Issues 314 Packages Projects Releases 17 Wiki Activity

Idea: optional proof-of-delivery receipts for agent runs (claw2claw wrapper) #1137

New Issue
Closed
opened 2026-02-20 17:43:12 -05:00 by yindo · 3 comments
yindo commented 2026-02-20 17:43:12 -05:00
Owner
Copy Link
Copy Source

Originally created by @jacobtop-tcg on GitHub (Feb 5, 2026).

Quick idea for LangGraph examples: add an optional hook that mints a verifiable receipt (proof link with result preview/download) for each run.

Minimal wrapper (Python): https://github.com/jacobtop-tcg/claw2claw-receipt-wrapper
Gist: https://gist.github.com/jacobtop-tcg/97f8a1ecb25822d252eb5790736adb4f

This would let users share an auditable link for agent deliverables, and optionally verify payment (USDC on Base) later.

If you want, I can draft a PR against one example.

Originally created by @jacobtop-tcg on GitHub (Feb 5, 2026). Quick idea for LangGraph examples: add an optional hook that mints a verifiable receipt (proof link with result preview/download) for each run. Minimal wrapper (Python): https://github.com/jacobtop-tcg/claw2claw-receipt-wrapper Gist: https://gist.github.com/jacobtop-tcg/97f8a1ecb25822d252eb5790736adb4f This would let users share an auditable link for agent deliverables, and optionally verify payment (USDC on Base) later. If you want, I can draft a PR against one example.
yindo closed this issue 2026-02-20 17:43:12 -05:00
yindo commented 2026-02-20 17:43:13 -05:00
Author
Owner
Copy Link
Copy Source

@metawake commented on GitHub (Feb 5, 2026):

Interesting to see this pop up here too! (Saw your PydanticAI issue as well.)

I've been working on something adjacent with Work Ledger
(github.com/metawake/work-ledger) - focused on recording full graph
executions for replay and diff, rather than just output receipts.

Use case: graph fails in prod → export the run → replay locally without
API calls → diff against a working version to find what broke.

Already has a LangGraph wrapper: ledger.wrap(graph).

These approaches could complement each other- your receipts for
verification, run recording for debugging. Curious what the LangGraph
team thinks about observability hooks in general.

@metawake commented on GitHub (Feb 5, 2026): Interesting to see this pop up here too! (Saw your PydanticAI issue as well.) I've been working on something adjacent with Work Ledger (github.com/metawake/work-ledger) - focused on recording full graph executions for replay and diff, rather than just output receipts. Use case: graph fails in prod → export the run → replay locally without API calls → diff against a working version to find what broke. Already has a LangGraph wrapper: `ledger.wrap(graph)`. These approaches could complement each other- your receipts for verification, run recording for debugging. Curious what the LangGraph team thinks about observability hooks in general.
yindo commented 2026-02-20 17:43:13 -05:00
Author
Owner
Copy Link
Copy Source

@jacobtop-tcg commented on GitHub (Feb 5, 2026):

Nice — Work Ledger looks complementary. Receipts = verifiable proof-of-delivery (shareable URL + signature/hash checks). Work Ledger = full-run recording for replay/diff.\n\nI’d love to integrate: emit a claw2claw receipt at the end of a run, and optionally attach a pointer to a Work Ledger run export as an artifact (so a proof links to a reproducible debug trace).\n\nIf you’re open: I can draft a tiny example PR in this repo showing an optional hook that (a) records via work-ledger if configured, (b) mints a receipt with the final output + links.

@jacobtop-tcg commented on GitHub (Feb 5, 2026): Nice — Work Ledger looks complementary. Receipts = *verifiable proof-of-delivery* (shareable URL + signature/hash checks). Work Ledger = *full-run recording for replay/diff*.\n\nI’d love to integrate: emit a claw2claw receipt at the end of a run, and optionally attach a pointer to a Work Ledger run export as an artifact (so a proof links to a reproducible debug trace).\n\nIf you’re open: I can draft a tiny example PR in this repo showing an optional hook that (a) records via work-ledger if configured, (b) mints a receipt with the final output + links.
yindo commented 2026-02-20 17:43:13 -05:00
Author
Owner
Copy Link
Copy Source

@hinthornw commented on GitHub (Feb 6, 2026):

We aren't interested at this time.

@hinthornw commented on GitHub (Feb 6, 2026): We aren't interested at this time.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
agents
awaiting author revision
bug
change
chat models
checkpointer
ci
code quality
code quality
dependencies
documentation
drawing
duplicate
enhancement
good first issue
help wanted
invalid
maintainer
meta
missing information
not maintained by langchain
open-swe-auto
open-swe-max
open-swe-max-auto
pending
performance
pull-request
Mirrored from GitHub Pull Request
 question
requires design
sdk
server
stale
studio
tests
type checking
usage question
v0.5
v1.1
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/langgraph#1137
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?