Skip to content

Add elizaOS plugin draft for endpoint and passport checks - #192

Draft
AgentTanuki wants to merge 2 commits into
mainfrom
codex/eliza-agent-guild
Draft

Add elizaOS plugin draft for endpoint and passport checks#192
AgentTanuki wants to merge 2 commits into
mainfrom
codex/eliza-agent-guild

Conversation

@AgentTanuki

@AgentTanuki AgentTanuki commented Sep 12, 2026

Copy link
Copy Markdown
Owner

Adds two optional elizaOS actions: observe a caller-selected public endpoint, and verify a supplied public Agent Guild passport against separately supplied issuer/subject DIDs and signed validity dates. The actions return bounded evidence through fixed Guild HTTPS routes. Configuration can restrict endpoints or issuers; neither action automatically enrolls agents, issues passports, delegates work or pays.

This is an unpublished external plugin draft in integrations/eliza-agent-guild, with a focused offline CI workflow. Its native contract was reviewed against elizaOS commit a5e06fb49c30a09f07504472c7b987dfd1775823. Native core type compatibility, loading, action discovery and live-model execution remain pending: the attempted typecheck reports the missing @elizaos/core peer. npm publication and registry submission are also pending. These source and fixture checks do not establish adoption or independent cryptographic verification.

Validation:

  • Build, source/dist byte comparison and lint pass; 36 offline tests exercise the real built handlers with substituted network responses, including direct-handler input rejection.
  • Package metadata identifies the GitHub repository and its integrations/eliza-agent-guild directory. The official npm CLI's offline archive contains exactly the intended 10 files, and every archived file matches the reviewed package bytes. No install, package publication or production probe ran.
  • Required repository npm run verify passes. Full service tests pass with JSON storage (2,183 passed, 10 skipped) and SQLite (2,184 passed, 9 skipped), with 56 deprecation warnings per lane. These local baseline checks ran against unchanged frontend/service code at 9cf6c561468e60afb77acdbddebfc5134a155e4f; opt-in live tests and other CI jobs were not rerun locally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant