my-project-public

repository

loading code, commits, and activity

repositories

loading repo index

my-project-public — gitlawb

#1	{
#2	"skillId": "solana-attestation-skill",
#3	"name": "solana-attestation-skill",
#4	"description": "Operate the Solana Attestation Service verification layer vendored under /attestation — create credentials, generate schemas, issue attestations for skills/agents/plugins, verify proof hashes, and bridge OpenClawd formal-verification outputs into on-chain attestations.",
#5	"category": "solana-dev",
#6	"path": "solana-attestation-skill/SKILL.md",
#7	"url": "https://x402.wtf/api/skills/solana-attestation-skill",
#8	"tags": [
#9	"solana",
#10	"attestation",
#11	"skill"
#12	],
#13	"requiredEnv": [
#14	"SOLANA_RPC_URL",
#15	"SAS_PROGRAM_ID",
#16	"SAS_AUTHORITY_KEY"
#17	],
#18	"homepage": "https://github.com/clawdsolana/OpenClawd/tree/main/attestation",
#19	"attestation": {
#20	"status": "pending",
#21	"isFormallyVerified": false,
#22	"attestationPda": null,
#23	"verificationTimestamp": null
#24	},
#25	"markdown": "---\nname: solana-attestation-skill\ndescription: \"Operate the Solana Attestation Service verification layer vendored under /attestation — create credentials, generate schemas, issue attestations for skills/agents/plugins, verify proof hashes, and bridge OpenClawd formal-verification outputs into on-chain attestations.\"\nmetadata:\n openclaw:\n homepage: https://github.com/clawdsolana/OpenClawd/tree/main/attestation\n requires:\n env:\n - SOLANA_RPC_URL\n - SAS_PROGRAM_ID\n - SAS_AUTHORITY_KEY\n---\n\n# Solana Attestation Skill\n\nUse this skill when the task involves the vendored [`attestation/`](../../../attestation/) verification layer.\n\n## Canonical Program Addresses\n\n- SAS Program ID: `22zoJMtdu4tQc2PzL74ZUT7FrwgB1Udec8DdW4yw4BdG`\n- Token-2022 Program: `TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb`\n- Event Authority PDA: `DzSpKpST2TSyrxokMXchFz3G2yn5WEGoxzpGEUDjCX4g`\n\n## What This Skill Covers\n\n- Create and manage attestation credentials\n- Generate or update attestation schemas\n- Issue skill attestations for formal verification proofs\n- Issue agent identity attestations with vault linkage\n- Issue plugin attestations with audit proof hashes\n- Verify existing attestations and surface verifier URLs\n- Regenerate SAS IDL and clients from the vendored program\n\n## OpenClawd Schemas\n\n### Skill Attestation\n\nLayout: `[12, 32, 12, 8, 1]`\n\n```json\n{\n \"skill_id\": \"string\",\n \"verifier_pubkey\": \"Pubkey\",\n \"proof_hash\": \"string\",\n \"verification_timestamp\": \"u64\",\n \"is_formally_verified\": \"bool\"\n}\n```\n\n### Agent Identity\n\nLayout: `[12, 32, 12, 32, 1]`\n\n```json\n{\n \"agent_id\": \"string\",\n \"wallet_pubkey\": \"Pubkey\",\n \"skill_attestation\": \"string\",\n \"vault_address\": \"Pubkey\",\n \"is_vault_initialized\": \"bool\"\n}\n```\n\n### Plugin Attestation\n\nLayout: `[12, 32, 12, 34, 8, 1]`\n\n```json\n{\n \"plugin_id\": \"string\",\n \"author_pubkey\": \"Pubkey\",\n \"attestation_ref\": \"string\",\n \"audit_proof_hash\": \"ProofHash\",\n \"timestamp\": \"u64\",\n \"is_audited\": \"bool\"\n}\n```\n\n## Local Source of Truth\n\n- Program: [`attestation/program`](../../../attestation/program)\n- Core library: [`attestation/core`](../../../attestation/core)\n- Rust client: [`attestation/clients/rust`](../../../attestation/clients/rust)\n- TypeScript client: [`attestation/clients/typescript`](../../../attestation/clients/typescript)\n- IDL: [`attestation/idl/solana_attestation_service.json`](../../../attestation/idl/solana_attestation_service.json)\n- Integration tests: [`attestation/integration_tests`](../../../attestation/integration_tests)\n\n## Standard Commands\n\n```bash\ncd attestation\ncargo-build-sbf && SBF_OUT_DIR=$(pwd)/target/sbpf-solana-solana/release cargo test\n```\n\n```bash\ncd attestation\npnpm install\npnpm run generate-idl\npnpm run generate-clients\n```\n\n## QEDGen Bridge\n\nUse this flow when promoting a locally verified capability into a trustless OpenClawd attestation:\n\n1. Run the formal verification flow to produce a proof artifact.\n2. Hash the proof output with SHA-256.\n3. Create or confirm the relevant SAS schema.\n4. Issue the attestation with the resulting `proof_hash`.\n5. Record the attestation address in the skill/agent/plugin registry.\n\n## Safety Rules\n\n- Never invent a proof hash.\n- Never claim a component is formally verified without an attestation or source proof artifact.\n- Prefer mainnet verification only after devnet rehearsal.\n- Keep schema layout bytes aligned with the attested templates and registry docs.\n"
#26	}
#27

z6Mkq5mY3JWtxoxUobWcfNHm7AkRubgSWEZTkBVqZXJviFZ5/my-project-public