Olas staking

Skill Jinn-Network/shared-skills/skills/olas-staking

Operate OLAS service staking safely across restake, migration, status checks, and activity-checker coordination. Public, reusable workflow without environment-specific secrets.From its SKILL.md

Install

npx -y skills add Jinn-Network/shared-skills --skill olas-staking

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.9 KB, 585 tokens by cl100k_base, as published. Nobody here has run it

OLAS Staking Operations

Reusable runbook for service staking lifecycle management.

Scope

Restake evicted services
Migrate between staking contracts
Verify staking and service state
Keep activity checker eligibility aligned

Core Concepts

Service state and staking state are different; inspect both
Evicted services can usually be unstaked and restaked without full re-registration
Contract ownership and Safe execution path determine who can call write methods
Reward availability can gate staking actions

Restake Flow (Evicted Service)

1. unstake(serviceId)
2. approve(stakingContract, serviceId) on service registry NFT
3. stake(serviceId)
4. re-verify checker eligibility

Migration Flow (Contract A -> Contract B)

1. Unstake from source
2. If required: terminate/unbond/reconfigure service bond
3. Activate and register as needed
4. Deploy or reuse multisig according to target policy
5. Approve NFT to target staking contract
6. Stake in target
7. Reconcile checker and reward settings

Status Checks

Use read calls for:

staking state by service ID
list of currently staked service IDs
service state in registry
NFT owner for service token

Treat “staked list membership + NFT ownership” as canonical confirmation.

Activity Checker Coordination

After restake or migration:

ensure service/multisig is eligible under checker rules
ensure required throughput thresholds are configured
verify eligibility with checker read methods

Safe Transaction Guidance

Route privileged staking actions through the expected Safe context
If SDK gas estimation is unreliable, use explicit gas limits and deterministic signing flow
Confirm nonce source consistency across providers

Funding Model

Plan for:

service security deposit
per-agent bond requirements
gas budget for full lifecycle actions
rewards liquidity for staking contract

Troubleshooting Patterns

GS013-style reverts: check signer context and Safe path
No rewards available: reward pool empty or not yet indexed
Manager-only reverts: wrong manager contract/address context
RPC staleness: nonce mismatch, delayed state visibility
Path-coupled scripts: env/config loaded from unintended root

Security Rules

No private key material in scripts or docs
No personal machine paths in public repositories
No operator-identifying internal wallet mapping unless intentionally public
Use placeholders for all environment-specific values

Operator Checklist

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.