lukso-expert_skill

This skill makes any agent a LUKSO expert by providing in-depth guidance on LSP standards, Universal Profiles, and related tooling.
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill lukso-expert

  • _meta.json280 B
  • SKILL.md5.2 KB

Overview

This skill provides a comprehensive LUKSO blockchain knowledge base that turns any agent into a LUKSO expert. It covers all LSP standards (LSP0–LSP28), Universal Profiles, token standards (LSP7/LSP8), KeyManager permissions, gasless relays, The Grid, and developer tooling. It is optimized for practical guidance, contract references, and debugging LUKSO-specific issues.

How this skill works

The skill inspects LUKSO-specific protocols, standards, and common developer patterns to generate precise answers, code snippets, and configuration tips. It retrieves canonical facts (chain IDs, contract addresses, GraphQL endpoints), decodes common pitfalls (permissions bitmasks, encoding errors, force parameter semantics), and suggests concrete fixes and commands. It maps developer needs to the right LSP reference, example code, or ecosystem resource.

When to use it

  • Building smart contracts, dApps, or integrations on LUKSO
  • Creating or managing Universal Profiles (permissions, metadata, data keys)
  • Deploying or interacting with LSP7/LSP8 tokens and NFT flows
  • Setting up or troubleshooting gasless relay transactions (LSP25)
  • Managing KeyManager permissions and access control (LSP6)
  • Working with The Grid (LSP28), followers (LSP26), or any LSP standard

Best practices

  • Prefer @erc725/erc725.js for ERC725Y data encoding to avoid manual errors
  • Always validate LSP6 permissions bitmasks; test combinations in a staging UP before mainnet
  • When sending LSP7/LSP8 tokens, decide force=true only when intended to bypass Universal Receiver checks
  • Add a 20–30% gas buffer for UP transactions routed through KeyManager proxies
  • Use Envio GraphQL endpoints for reliable profile lookups and indexing
  • Keep a canonical list of deployed contract addresses and ABIs for your target network

Example use cases

  • Create a Universal Profile, set profile metadata (LSP3), and assign controllers via KeyManager (LSP6)
  • Implement an LSP8 NFT contract and integrate Universal Receiver hooks for safe transfers
  • Configure a gasless relay flow using LSP25 and ensure EXECUTE_RELAY_CALL permission is granted
  • Resolve usernames to UP addresses via Envio GraphQL and fetch owned assets (LSP5)
  • Debug token transfer failures by checking force parameter and Universal Receiver implementation

FAQ

Mainnet uses chain ID 42, testnet 4201, and the native token is LYX.

Why are token transfers failing to EOAs?

By default LSP7/LSP8 require Universal Receiver support; set force=true to bypass, or ensure recipient implements a Universal Receiver.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
lukso-expert skill by openclaw/skills | VeilStrat