kamiyo-protocol

mcp
Guvenlik Denetimi
Uyari
Health Uyari
  • License — License: MIT
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Low visibility — Only 6 GitHub stars
Code Gecti
  • Code scan — Scanned 12 files during light audit, no dangerous patterns found
Permissions Gecti
  • Permissions — No dangerous permissions requested

Bu listing icin henuz AI raporu yok.

SUMMARY

Open-source Solana AI agent protocol for escrow payments, reputation, disputes, and autonomous service coordination.

README.md

KAMIYO Protocol

CI
Kani
License: MIT

KAMIYO Protocol is the core open-source repository for KAMIYO.

Kizuna is the protocol's agentic trust and settlement layer. It provides trust signals, payment verification, settlement flows, funding controls, and operator surfaces for AI agents. Reality Fork is the newest product built on top of these rails; this repository contains the underlying protocol, services, SDKs, reference applications, and the portable Reality Fork package rather than a product-only application surface.

Repository Scope

Area Purpose Primary paths
Kizuna core services Verification, settlement, funding, repayment, and operator APIs services/x402-facilitator, services/wallet-control-plane, services/api, apps/cdp-onboarding
Reality Fork Counterfactual control-room package and launch assets packages/kamiyo-reality-fork
Trust infrastructure Durable trust-event ingest, reads, replay, and service runtime services/trust-layer-service, crates/kamiyo-trust-layer
Identity and compliance Passport, mandate, and compliance surfaces packages/kamiyo-meishi, services/meishi-compliance
Agents and automation Daily cron tasks and agentic services services/kamiyo-marketing-agent, services/kamiyo-docs-agent, services/kamiyo-agent
Client and integration packages SDKs, settlement libraries, and agent-facing integrations packages/
On-chain and proof systems Solana programs, contracts, zero-knowledge components, and circuits programs/, contracts/, crates/kamiyo-zk, circuits/, noir/

Quick Start

Requirements

  • Node.js 20+
  • pnpm 9+
  • Rust stable
  • Solana CLI 2.x and Anchor CLI 0.31.x for on-chain work

Install

git clone https://github.com/mizuki0x/kamiyo-protocol.git
cd kamiyo-protocol
pnpm install

Common Commands

pnpm run build
pnpm run test
pnpm run lint:check

The root defaults target the Kizuna core workspace. For module, legacy, and on-chain commands, see BUILD.md.

Key Components

  • Reality Fork package: portable scenario and control-room package built on the protocol rails
  • x402 Facilitator: verification, settlement, funding locks, collateralized approvals, and repayment flows
  • Wallet Control Plane: mandates, linked wallets, enterprise funding limits, and collateral checks
  • Companion API: ledger, billing, integration, and protocol API surfaces
  • Trust Layer Service: durable trust-event ingest, subject-state reads, replay tooling, and Kafka-backed delivery
  • Meishi Compliance: identity and compliance services around Meishi passports
  • Marketing Agent: daily cron that drafts posts from GitHub commits and schedules them via Postiz
  • CDP Onboarding: reference operator app for Kizuna account setup and control-plane actions

Architecture

The monorepo is organized around Kizuna, the protocol's trust and settlement layer. Off-chain services in services/ expose verification, settlement, funding, and trust APIs. Client SDKs and integration packages live in packages/. On-chain components are split across Solana programs in programs/, Rust crates with the ZK and trust-layer cores in crates/, zero-knowledge circuits in circuits/ and noir/, and EVM contracts in contracts/. Reference apps and demos live in apps/ and examples/.

See ARCHITECTURE.md for the full system view.

Documentation

Service- and package-specific documentation lives alongside each component under services/, packages/, apps/, and crates/.

Contributing

Contributions are welcome. Keep changes focused, add tests for behavior changes, and update documentation when interfaces or workflows change. Start with CONTRIBUTING.md.

Support

Use GitHub Issues for bugs and feature requests. Do not open public issues for security problems; follow SECURITY.md.

License

MIT. See LICENSE.

Yorumlar (0)

Sonuc bulunamadi