Evidence
What you can verify in Laisen.
The product keeps the key facts in view: provider, model, wallet, chain, contract addresses, transaction hashes, and execution history.
- Provider
- GMI Cloud
- Inference runs through GMI Cloud.
- Model
- GLM-5
- GLM-5 handles package and mandate generation.
- Tool calls
- Signal, scheduling, and ledger steps
- Each call shows a status and a short detail.
- Wallet + chain
- MetaMask on Base Sepolia
- Wallet connection and network state stay visible.
- Deployment
- Token and protocol addresses
- Contract addresses appear after deployment.
- Schema
- Pending, valid, fallback, failed
- Payload health is checked before the run continues.
- Fallback
- Safe mode and hard-stop states
- Failure paths stay visible instead of disappearing into logs.
- History
- Time-ordered activity log
- Each run appends a readable event trail.
Fallback
Failure states stay explicit.
Standard
Normal path with live signal, deploy, and release.
Safe mode
Cached inputs keep the run moving when live infrastructure is unavailable.
Failure test
A deliberate hard stop shows how the product surfaces failure.
Activity
Execution history explains what just happened.
01
Mission saved
The run begins with a stored mission.
02
Wallet ready
The wallet and chain are checked before deployment.
03
Contracts deployed
Deployment adds contract addresses and transaction hashes.
04
Mandate released
The signer either releases or rejects the next step.
05
Execution updated
The log continues as execution advances, pauses, redirects, or completes.
Next step
Open the runtime.
The runtime page combines live state with wallet and chain actions.