VEO Governance & Management

Lucid provides governance and operational management infrastructure for administering VEO markets throughout their lifecycle.

This includes:

• multisignature approval flows
• deployment permissions
• market execution controls
• pending proposal management
• market closure infrastructure
• operational governance coordination

Governance behaviour depends on how the organisation is configured during setup.

Governance Modes

VEO management supports two operational governance models:

Mode	Description
Multisignature Governance	Requires approval from multiple authorised signers
Auto-Approval Governance	Uses a designated address with direct execution permissions

These governance models determine how:

• VEOs are deployed
• VEOs are approved
• VEOs are executed
• VEOs are closed

Multisignature Governance

By default, organisations use multisignature governance for VEO management.

Under this model:

• VEO proposals require signer approval
• execution occurs only after threshold approval is reached
• market closures also require governance approval
• governance actions remain coordinated across authorised participants

Supported multisignature thresholds can include:

• 2-of-3
• 3-of-5

A single signer cannot finalise governance actions unless the required threshold is reached.

Pending VEO Management

Pending governance actions are managed through the VEO Manager module.

The VEO Manager displays:

• pending VEO proposals
• pending approvals
• executable proposals
• deployment history
• historical governance actions

This allows governance participants to monitor and coordinate VEO operations through one interface.

Executing Governance Actions

Once the required approval threshold is reached:

1. any authorised signer can execute the proposal
2. the governance action is submitted on-chain
3. the VEO state updates automatically

Governance execution can include:

• deploying VEOs
• approving VEO proposals
• closing VEO markets
• finalising pending governance actions

Auto-Approval Governance

Organisations can optionally configure a dedicated auto-approval address.

Under this model:

• governance actions execute immediately
• multisignature coordination is bypassed
• approvals are automatically authorised
• pending approval flows are skipped

This model is designed for ecosystems requiring:

• simplified operational coordination
• faster market execution
• reduced governance overhead

Closing VEO Markets

VEO markets can be closed through the configured governance infrastructure.

Depending on the governance model:

• closure may require multisignature approval
• or execute immediately through auto-approval governance

Only authorised governance participants can access market management actions.

To close a VEO market:

• Open the VEOs section.
• Locate the target VEO.
• Open the VEO detail page.
• Connect an authorised governance wallet.
• Click Close Market.
• Approve and execute the governance transaction.

If multisignature governance is enabled:

• the proposal enters the pending approval flow
• required signer approvals must be collected
• execution becomes available after threshold approval

Permission Visibility

Governance actions are only visible to authorised governance participants.

If a connected wallet does not have governance permissions:

• management controls remain hidden
• approval interfaces do not appear
• execution actions are unavailable

This ensures governance operations remain restricted to authorised participants only.

Governance Lifecycle

VEO governance infrastructure coordinates the complete operational lifecycle of a VEO market, including:

• creation
• approval
• deployment
• monitoring
• execution
• closure

All governance actions are coordinated directly through Lucid’s integrated VEO infrastructure.