See Luvion in use
Choose an operation to see how a team submits an exact intent, reviews it, obtains approvals and high-threshold authorization, and prepares evidence for handoff. These short recordings use the actual Luvion client and local APIs, with synthetic test data.
Interactive configuration example
Follow the receive-configuration walkthrough and interactive demo. This separate example includes scheduling and execution on an isolated local chain. The recordings below retain their own authorization and handoff scope.
Risk parameter change
Follow a test WETH LTV change from 80% to 75% through approval, authorization and simulation.
Import the exact LTV package: 80% to 75%, with all other parameters unchanged.
What these recordings demonstrate
- Separate responsibilities: request creation, technical review, business approvals and authorization are distinct steps.
- Exact operation binding: the target, recipient, amount or parameter belongs to a specific request, rather than a general permission to act.
- Reviewable evidence: the workflow retains authorization and simulation evidence for review and, where shown, transaction handoff.
Recording scope
These are controlled, non-production demonstrations, not live customer deployments or proof of production readiness. Workflow recordings do not broadcast transactions; handoff does not mean execution.
The 22-of-33 FROST setup uses local key shares. It is not a network of 33 independently operated nodes. Business approvals and threshold signing are separate controls.
The upgrade recording stops at authorization, without a connected execution Gate. RWA examples do not verify legal ownership, reserves, KYC or offchain settlement. The bridge-admin example only uses a local test contract, not cross-chain message verification. Per-request amount controls are not cumulative spending limits.
Recorded separately in English and Chinese, with matching interface labels, fonts and captions. Chinese labels use a recording-only presentation layer; API behavior and authorization checks are unchanged. All videos are silent. Login, role switching and native browser confirmation dialogs are omitted; the resulting workflow states are real.
Mandatory protection additionally requires an accepted execution enforcement point and closure of bypass routes. See Security boundary and Current implementation status.
Try one workflow with us
Start with one operation, one test environment and agreed acceptance criteria. Explore the design-partner pilot.