Olas Staking

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

1. GS013-style reverts: check signer context and Safe path
2. No rewards available: reward pool empty or not yet indexed
3. Manager-only reverts: wrong manager contract/address context
4. RPC staleness: nonce mismatch, delayed state visibility
5. 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

• Staking state verified
• Service state verified
• Eligibility checker verified
• Reward path verified
• Monitoring updated