Skip to content

New: add AgentMesh Trust Layer plugin (cryptographic identity for multi-agent workflows)#2060

Merged
crazywoola merged 4 commits intolanggenius:mainfrom
imran-siddique:contrib/agentmesh-trust-plugin
Feb 17, 2026
Merged

New: add AgentMesh Trust Layer plugin (cryptographic identity for multi-agent workflows)#2060
crazywoola merged 4 commits intolanggenius:mainfrom
imran-siddique:contrib/agentmesh-trust-plugin

Conversation

@imran-siddique
Copy link
Copy Markdown
Contributor

Plugin Submission Form

1. Metadata

2. Submission Type

  • New plugin submission
  • Version update for existing plugin

3. Description

AgentMesh Trust Layer provides cryptographic identity and trust verification for Dify agent workflows. It enables agents to verify each other's identity before trusting their data, check authorization for workflow steps, and maintain dynamic trust scores based on behavioral history.

4 Tools Provided:

  • verify_peer - Verify another agent's identity and capabilities using Ed25519 cryptographic signatures
  • verify_step - Check if an agent is authorized to execute a specific workflow step
  • get_identity - Get this agent's cryptographic identity (DID + public key) to share with peers
  • record_interaction - Record success/failure to dynamically update trust scores

Why This Matters:

In multi-agent workflows, agents need to verify "who" they're communicating with. This plugin provides:

  • Ed25519 cryptographic identity (DIDs)
  • Trust scoring (0.0-1.0) based on behavioral history
  • Capability-based access control
  • Full audit logging of trust decisions

Related to:

4. Checklist

  • I have read and followed the Publish to Dify Marketplace guidelines
  • I have read and comply with the Plugin Developer Agreement
  • I confirm my plugin works properly on both Dify Community Edition and Cloud Version
  • I confirm my plugin has been thoroughly tested for completeness and functionality
  • My plugin brings new value to Dify

5. Documentation Checklist

  • Step-by-step setup instructions
  • Detailed usage instructions
  • All required APIs and credentials are clearly listed
  • Connection requirements and configuration details
  • Link to the repository for the plugin source code

6. Privacy Protection Information

Data Collection

This plugin does not collect any personal user data. It operates entirely locally within the Dify environment. The only data processed:

  • Agent DIDs (generated locally via Ed25519)
  • Trust scores (stored in-memory)
  • Audit logs (stored in-memory, not persisted externally)

Privacy Policy

  • I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

Copy link
Copy Markdown
Member

@crazywoola crazywoola left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@crazywoola
Copy link
Copy Markdown
Member

Please resolve the errors in the CI.

@imran-siddique
Copy link
Copy Markdown
Contributor Author

imran-siddique commented Feb 13, 2026

@crazywoola - thank you so much! Fixed the CI errors! Updated the .difypkg\ with:

Added missing fields:

  • \meta.version: \

Please approve the workflow and if good, please help with merge!

@crazywoola
Copy link
Copy Markdown
Member

Still no good

@crazywoola
Copy link
Copy Markdown
Member

See the track here https://github.com/langgenius/dify-plugins/actions/runs/21974268190/job/63505082934?pr=2060

@imran-siddique
Copy link
Copy Markdown
Contributor Author

@crazywoola Fixed! The issue was missing extra.python fields in the YAML configuration files.

Root cause: Both the provider YAML and each tool YAML require an extra section specifying the Python source file:
yaml extra: python: source: provider/agentmesh.py # or tools/verify_peer.py etc.

Changes made:

  • Added extra.python.source to provider/agentmesh.yamlprovider/agentmesh.py
  • Added extra.python.source to tools/verify_peer.yamltools/verify_peer.py
  • Added extra.python.source to tools/verify_step.yamltools/verify_step.py
  • Added extra.python.source to tools/get_identity.yamltools/get_identity.py
  • Added extra.python.source to tools/record_interaction.yamltools/record_interaction.py
  • Rebuilt .difypkg with correct directory structure

This matches the pattern from official plugins (e.g., tools/deepl). Please re-run CI!

@imran-siddique
Copy link
Copy Markdown
Contributor Author

@crazywoola Found and fixed the actual error! 🎯

Previous CI error was:
ImportError: cannot import name 'ToolProviderCredentials' from 'dify_plugin.entities.tool'

The provider code had an unused import of ToolProviderCredentials which was removed/renamed in the latest dify_plugin SDK. Removed that import — the code never actually used it.

This push (cbe08a3): Rebuilt .difypkg with the fix. Could you please approve the CI workflow run? (It shows "action_required" since it needs maintainer approval for fork PRs.)

@imran-siddique
Copy link
Copy Markdown
Contributor Author

@crazywoola - thank you! Please help with merge. All checks have passes and no conflicst with base branch.

@crazywoola crazywoola merged commit afdac5c into langgenius:main Feb 17, 2026
1 check passed
@imran-siddique
Copy link
Copy Markdown
Contributor Author

Thank you @crazywoola for the review and merge! Really appreciate the guidance through the CI fixes.

The AgentMesh Trust Layer is now available in the Dify Marketplace -- bringing cryptographic identity (Ed25519/DIDs), trust scoring, and capability-based access control to Dify agent workflows.

Tools available:

  • verify_peer -- Verify another agent's identity and capabilities
  • verify_step -- Check authorization for workflow steps
  • get_identity -- Share this agent's cryptographic identity
  • record_interaction -- Update trust scores based on outcomes

Docs and source: https://github.com/imran-siddique/agentmesh-integrations/tree/master/dify-plugin

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.

2 participants