Skip to content

aip-0014.md

Latest commit

 

History

History
221 lines (164 loc) · 5.08 KB

aip-0014.md

File metadata and controls

221 lines (164 loc) · 5.08 KB
Raw

AIP-0014: Wallet and PSBT Intent Review Standard

AIP:     0014
Title:   Wallet and PSBT Intent Review Standard
Author:  Avian Network Developers
Status:  Draft
Type:    Standards Track
Category: Wallet / PSBT / User Safety
Created: 2026-06-07
Requires: AIP-0010, AIP-0011

Abstract

This AIP defines a standard format for AI-assisted wallet and PSBT intent review in the Avian ecosystem.

A wallet or external reviewer may analyze a transaction or PSBT and produce a signed intent review explaining what the transaction appears to do, what assets or AVN are moved, whether change appears present, whether ownership tokens are affected, and whether any risk signals are detected.

This AIP does not allow AI to sign transactions for users and does not make AI output a consensus rule.

Motivation

PSBT workflows are powerful but can be difficult for normal users to understand.

Avian marketplace flows, asset transfers, restricted assets, ownership tokens, and unsigned transaction creation can create confusion or mistakes. An AI-assisted intent review can help users understand what they are about to sign before they approve a transaction.

This is especially useful for:

  • Marketplace purchases
  • Marketplace listings
  • Asset creation
  • Ownership token movement
  • Restricted asset operations
  • Multi-output transactions
  • High-value AVN transfers
  • Suspicious or unusual PSBTs

Specification

1. Intent Review Object

A wallet or AI reviewer SHOULD represent a transaction or PSBT review as follows:

{
  "schema": "avian.ai.intent_review.v1",
  "chain": "avian",
  "network": "mainnet",
  "target": {
    "type": "psbt",
    "psbt_hash": "sha256-psbt",
    "txid": "optional-final-txid"
  },
  "model": {
    "model_id": "avian-psbt-reviewer-v1",
    "model_hash": "sha256-model-hash"
  },
  "summary": {
    "plain_language": "This PSBT appears to purchase asset DRAGON#001 for 1000 AVN and returns AVN change to the wallet.",
    "risk_level": "low",
    "confidence": 0.92
  },
  "effects": {
    "avn_sent": "1000.00000000",
    "avn_received": "0.50000000",
    "assets_sent": [],
    "assets_received": ["DRAGON#001"],
    "ownership_tokens_moved": [],
    "change_detected": true
  },
  "warnings": [
    {
      "code": "NEW_DESTINATION",
      "severity": "info",
      "message": "Destination address has no known previous wallet history."
    }
  ],
  "reviewer": {
    "type": "address",
    "address": "AVN_ADDRESS_OR_ID",
    "pubkey": "hex-encoded-public-key"
  },
  "created_at": "2026-06-07T00:00:00Z",
  "signature": {
    "algorithm": "secp256k1",
    "signature": "hex-encoded-signature"
  }
}

2. Risk Levels

The summary.risk_level field SHOULD use one of:

low
medium
high
critical
unknown

3. Warning Codes

Initial warning codes include:

NO_CHANGE_DETECTED
UNUSUAL_CHANGE_ADDRESS
NEW_DESTINATION
HIGH_VALUE_TRANSFER
OWNERSHIP_TOKEN_MOVED
RESTRICTED_ASSET_OPERATION
QUALIFIER_ASSET_OPERATION
UNKNOWN_ASSET_SCRIPT
UNSIGNED_INPUTS_PRESENT
PARTIAL_SIGNATURES_PRESENT
EXCESSIVE_FEE
DUST_OUTPUTS
MARKETPLACE_COUNTERPARTY_UNKNOWN
CID_UNAVAILABLE
AI_REVIEW_INCONCLUSIVE

Wallets MAY define additional warning codes.

4. Wallet Display Recommendations

Wallets SHOULD display a clear transaction summary before signing.

Recommended display fields:

AVN sent
AVN received
AVN fee
assets sent
assets received
ownership tokens moved
change output status
destination addresses
risk level
warnings
model ID
review timestamp

The wallet SHOULD clearly state that the AI review is advisory.

5. Signing Restrictions

AI systems MUST NOT sign wallet transactions unless explicitly implemented as a separate user-authorized signing system.

This AIP defines review and explanation only.

6. PSBT Handling

Reviewers SHOULD analyze the PSBT without modifying it.

If a reviewer normalizes, decodes, or extracts data from the PSBT, the input hash MUST refer to the original PSBT bytes.

7. Consensus

This AIP introduces no consensus changes.

A transaction remains valid or invalid only according to Avian consensus rules, regardless of the AI review.

Rationale

Users need understandable explanations of what they are signing.

AI can help translate complex transaction structure into plain language, but it must remain advisory and verifiable.

Backwards Compatibility

This AIP is fully backwards compatible.

Existing PSBTs and transactions remain unchanged.

Security Considerations

A malicious or incorrect review could mislead users.

Wallets SHOULD avoid hiding raw transaction details behind AI summaries. The user SHOULD still have access to deterministic transaction details.

Applications SHOULD display:

  • Whether the review was local or remote
  • Model ID
  • Reviewer identity
  • Timestamp
  • PSBT hash
  • Risk warnings
  • Whether the review was signed

AI summaries SHOULD NOT override deterministic wallet validation.

Future Work

Future AIPs may define:

  • Standard PSBT extraction format
  • Local-only wallet review mode
  • Multi-reviewer PSBT attestations
  • Marketplace-specific review profiles
  • Post-quantum reviewer signatures