Stakingverse Lukso
WarnAudited by ClawScan on May 10, 2026.
Overview
The skill matches its LUKSO staking purpose, but it needs review because it asks for a controller private key and can submit irreversible mainnet transactions without clearly declared credentials or built-in approval safeguards.
Review carefully before installing. This does not show evidence of hidden exfiltration, but it does handle a private key and can perform real LUKSO mainnet transactions. Use a limited-permission controller, verify the Stakingverse vault address independently, pin and review dependencies, and run transactions only after checking the amount, destination, network, and gas. Also note that the docs use both PRIVATE_KEY and STAKING_PRIVATE_KEY, so confirm the expected environment variable before use.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A private key that can act through the Universal Profile/KeyManager may be able to move or lock real LYX/sLYX funds if misused or if the script is modified.
The skill asks for a controller private key, and even suggests editing scripts with it. The registry metadata lists no required env vars or primary credential, so this high-impact account authority is under-declared.
Set these environment variables or edit the scripts: ... export PRIVATE_KEY="your_controller_private_key"
Do not use a main wallet key. Use a dedicated controller with minimal permissions, keep the key out of source files, and require the skill metadata to declare the credential requirement clearly.
A mistaken amount or unintended invocation could stake real LYX, and blockchain transactions are generally irreversible.
The script directly submits a mainnet KeyManager transaction with user-supplied staking value. The artifacts do not show an in-script confirmation, dry run, maximum amount check, or transaction summary before signing.
const tx = await keyManagerContract.execute(upExecuteData, { value: amountWei });Add a mandatory confirmation step that shows amount, contract address, network, gas estimate, and transaction data before signing; require explicit user approval for every state-changing transaction.
If the source or dependency changes unexpectedly, the code handling the private key could differ from what was reviewed.
The installation instructions rely on an external repository and an unpinned npm dependency, with no lockfile or install spec provided in the artifact set. This is expected for many Node scripts, but it matters more when private keys are used.
git clone https://github.com/LUKSOAgent/stakingverse-lukso-skill.git cd stakingverse-lukso-skill npm install ethers
Install only from a verified source, pin dependency versions, use a lockfile, and review the exact code before setting any private key.