Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Comprehensive LUKSO blockchain knowledge base for AI agents. Makes any agent a LUKSO expert — covering all LSP standards (LSP0-LSP28), Universal Profiles, sm...
Comprehensive LUKSO blockchain knowledge base for AI agents. Makes any agent a LUKSO expert — covering all LSP standards (LSP0-LSP28), Universal Profiles, sm...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Complete knowledge base for building on LUKSO — the blockchain for creative economies, digital identity, and new social standards.
Chain ID: 42 (mainnet) / 4201 (testnet) Native token: LYX Consensus: Proof of Stake (32 LYX per validator) EVM compatible: Yes, unmodified Ethereum execution layer Unique: Universal Profiles (smart contract accounts) instead of EOAs Founder: Fabian Vogelsteller (also created ERC-20 and ERC-725)
LUKSO extends Ethereum with LSP standards (LUKSO Standard Proposals) that enable: Smart accounts (Universal Profiles) with built-in permissions, metadata, and social features Flexible tokens (LSP7/LSP8) with safety features like force parameter and universal receiver hooks Gasless transactions via relay service (LSP25) On-chain social graph via followers system (LSP26) Profile customization via The Grid (LSP28)
Universal Profile (LSP0/ERC725Account) ├── KeyManager (LSP6) — permission layer │ ├── Controllers — addresses with specific permissions │ └── Allowed calls/addresses — fine-grained access control ├── Profile Data (LSP3) — name, description, avatar, links ├── Universal Receiver (LSP1) — hooks for incoming transactions ├── Owned Assets (LSP5) — registry of tokens/NFTs owned ├── Issued Assets (LSP12) — registry of tokens/NFTs created └── The Grid (LSP28) — customizable profile layout
Load these based on what you need:
Complete reference for ALL LSP standards (LSP0-LSP28+). Includes interfaces, function signatures, and implementation details. Read when working with any specific LSP or needing to understand the standards architecture.
Practical code examples and implementation guides. Covers UP creation, token operations, permissions, gasless transactions, and common pitfalls. Read when writing code or debugging LUKSO-specific issues.
Projects, team, community channels, grants, and chain infrastructure. Read when answering ecosystem questions or looking for project information.
Deployed contract addresses, GitHub repositories, NPM packages, and API endpoints. Read when looking up addresses, ABIs, or integration endpoints.
ContractAddressLSP26 Follower System0xf01103E5a9909Fc0DBe8166dA7085e0285daDDcAEnvio GraphQLhttps://envio.lukso-mainnet.universal.tech/v1/graphql Full address list in references/contracts-and-repos.md
# Envio GraphQL query { Profile(where: {name: {_eq: "username"}}) { id name } }
query { Profile_aggregate { aggregate { count } } }
const LSP26 = "0xf01103E5a9909Fc0DBe8166dA7085e0285daDDcA"; const calldata = lsp26Contract.methods.follow(targetAddress).encodeABI(); await universalProfile.methods.execute(0, LSP26, 0, calldata).send({from: controller});
force parameter (LSP7/LSP8): Set to true to send tokens to any address. Set to false (default) to only send to UPs with a Universal Receiver — prevents accidental sends to EOAs or contracts that can't handle them. LSP6 Permissions: Permissions are bitmask-based. Common mistake: granting CALL permission but forgetting EXECUTE_RELAY_CALL for gasless transactions. ERC725Y data encoding: Use @erc725/erc725.js for encoding — manual encoding is error-prone, especially for VerifiableURI and array types. Gas estimation: UP transactions go through KeyManager proxy, so gas estimates can be off. Add 20-30% buffer.
Docs: https://docs.lukso.tech GitHub: https://github.com/lukso-network Medium: https://medium.com/lukso Discord: https://discord.gg/lukso Testnet faucet: https://faucet.testnet.lukso.network
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.