Conversation
On-chain action audit trail (swap/bridge/mint/deploy) written to DKG Working/Shared Memory as provenance-tagged Knowledge Assets, plus decision recall via SPARQL. Preserves Hermes security model (no auto-sign, no auto-publish, Spend Governor respected). Validates 0 errors / 0 warnings.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
integrations/dkg-hermes-bridge.json— a registry entry for Hermes DKG Memory Bridge, giving the Hermes crypto agent a DKG V10 memory layer.Repo: https://github.com/kiyeps/dkg-hermes-bridge (commit pinned in entry)
What it does
Why it fits
Directly serves the bounty's "priority integration with OpenClaw, Hermes, and comparable research agents". Hermes is a multi-chain Web3 agent; giving it an immutable, queryable DKG memory layer for its on-chain decisions is exactly the agent-memory direction the program targets.
Security model preserved
Hermes's existing guardrails are untouched: user-funds-only, confirm-before-signing, Spend Governor, secret hygiene. The bridge only ADDS a memory-recording hook — it never auto-signs, never auto-publishes, and respects governor boundaries.
Round 1 scope compliance
vm/publishtool. No endorsement/voting tools.Verification
{subject,predicate,object}, no per-quad graph fieldurn:dkg:file:*/urn:dkg:extraction:*Submission metadata — final update (2026-09-08)
Tag:
cfi-dkgv10-r1Pinned commit:
1eb5b678289c4ee69bc23f09d5ef940b0aa44d0d(v0.1.2)Contributor attestation (§8a.8): I attest that this submission is my own original work (or properly licensed third-party work), and that it contains no intentional backdoors, no hidden remote-execution paths, and no undeclared network egress. — @kiyeps
Design brief: https://github.com/kiyeps/dkg-hermes-bridge/blob/main/docs/DESIGN.md
Demo: https://github.com/kiyeps/dkg-hermes-bridge/blob/main/docs/demo-transcript.txt — recorded against a live local DKG V10 node (v10.0.15, Base Sepolia testnet, context graph
openclaw-curator). Real runtime interaction: status → audit (action persisted as provenance quads) → SPARQL recall returning the stored action.Security notes (§8): Action params are hashed with a recursive canonical serializer (sorted keys, type-tagged scalars) so distinct actions can never collide onto one subject; a pre-submission review fixed a nested-object
[object Object]hash collision and hardened SPARQL literal escaping (backslash-first). Secret-shaped values are redacted before any literal leaves the process. Write authority: WM write + explicit SWM share only; no VM operations. Egress: local node only (http://127.0.0.1:9200).Maintenance commitment: Maintained by @kiyeps; support window ≥ 6 months post-merge.