LuxDA Bridge/DeFi Integration

Abstract

This LP defines how bridges, teleport, and DeFi protocols integrate with LuxDA Bus.

Motivation

This specification formalizes the component design, ensuring consistent implementation across the LuxDA ecosystem.

Specification

1. Intent Namespaces

DeFi intents are posted to dedicated namespaces:

var IntentNamespaces = map[string][20]byte{
    "swap":    DeriveNamespace("lux.intent.swap.v1"),
    "bridge":  DeriveNamespace("lux.intent.bridge.v1"),
    "lend":    DeriveNamespace("lux.intent.lend.v1"),
}

2. Intent Format

type DeFiIntent struct {
    Type        IntentType
    FromChain   ChainID
    ToChain     ChainID
    FromToken   TokenID
    ToToken     TokenID
    Amount      *big.Int
    MinReceive  *big.Int
    Deadline    uint64
    Recipient   Address
    Signature   []byte
}

3. Proof Posting

Bridges post proofs of execution:

type ExecutionProof struct {
    IntentRef    [32]byte
    TxHash       [32]byte
    BlockHeight  uint64
    MerkleProof  []byte
}

4. Integration Adapters

type BridgeAdapter interface {
    PostIntent(intent *DeFiIntent) error
    WatchIntents(filter IntentFilter) (<-chan *DeFiIntent, error)
    PostProof(proof *ExecutionProof) error
}

---

LP-6496 v1.0.0 - 2026-01-02

Rationale

The design follows established patterns in the LuxDA architecture, prioritizing simplicity, security, and interoperability.

Backwards Compatibility

This specification introduces new functionality and does not modify existing protocols. It is fully backwards compatible with existing implementations.

Security Considerations

Implementations must validate all inputs, enforce access controls, and follow the security guidelines established in the LuxDA Bus specification.