shield-checkReliability & Safety

Public guidance on verification, execution modes, and safe usage expectations.

Solenvus is designed to make skill usage more understandable and less ambiguous.

This section explains the main signals users should rely on.

Verification signals

Some skills include a verification flag.

This indicates that the skill has been confirmed against mainnet conditions.

Users should prefer verified skills when reliability matters most.

Execution modes

Solenvus supports three execution modes:

  • mock

  • real

  • hybrid

Mock

Use this when you want to inspect shape and logic without live execution risk.

Real

Use this when you need live protocol data or real execution behavior.

Hybrid

Use this when you want current market context with safer simulated execution.

Before running a skill

Users should review:

  • Protocol

  • Action type

  • Verification state

  • Live test support

  • Battle support when comparison matters

Use public trust signals

The platform exposes several user-facing signals to reduce guesswork:

  • Trust score

  • Speed score

  • Battle score

  • Docs score

  • Protocol status

  • Activity history

Safe documentation policy

This documentation only includes information that is appropriate for end users.

Sensitive operational details, private configuration, and internal-only controls are intentionally excluded.

Last updated