Skip to main content
Pre-Release Documentation

This describes a pre-release version of LBAMM. Interfaces and behavior may change.

Verify the exact repository commit before building production integrations.

EIP-7702 Delegation & LBAMM Compliance

EIP-7702 enables persistent delegation of an account’s execution authority to a contract.

When an account delegates under 7702:

  • The account functions as a proxy with the delegate as its implementation
  • Delegation persists until explicitly changed
  • All calls to the account will execute with the delegate's code

LBAMM and Apptokens integrate with this model naturally to enhance the protocol's capabilities.


What EIP-7702 Can Do With LBAMM

There are many potential use cases for EIP-7702 with LBAMM including:

  • Smart order routing that fills a hop from multiple pools before proceeding to the next hop.
  • Advanced partial fills that maintain the excess token amount from each hop.
  • User accounts as transfer handlers for custom order settlement directly from the user account that holds the tokens.

Executor Model Remains Unchanged

In LBAMM:

The executor is always msg.sender.

With 7702 delegation:

  • The account remains the executor
  • Hooks retain the executor context of the actual user

No protocol changes are required to maintain the same execution guarantees.


Apptoken Enforcement Remains Intact

Apptokens rely on:

  • Token-level hooks
  • Executor visibility
  • Deterministic execution context
  • Route-aware enforcement

EIP-7702 does not weaken any of these guarantees.

Because the account remains the executor and Apptokens are delegate-aware:

  • Token hooks can restrict or allow the executor
  • Apptokens can restrict or allow the delegate code
  • Executor-based policy remains enforceable
  • Recipient restrictions remain enforceable
  • Handler restrictions remain enforceable

Delegation does not bypass enforcement.


What Does Not Change

EIP-7702 does not modify:

  • Pool math or liquidity semantics
  • Hook ordering
  • Fee ordering
  • Partial fill behavior
  • singleSwap, multiSwap, or directSwap semantics
  • multi-hop routing rules
  • Exchange fee or fee-on-top rules

All LBAMM invariants remain identical.


Summary

EIP-7702 makes accounts programmable through persistent delegation.

Within LBAMM:

  • The user remains the executor.
  • Execution semantics remain deterministic.
  • Apptoken enforcement remains fully intact.
  • No AMM invariants change.

LBAMM’s identity-based execution model is directly compatible with persistent delegation.

Limit Break

TwitterLimitBreak.comMedium

© 2026 Limit Break International, Inc. All rights reserved.

Privacy PolicyTerms of ServiceCookie PolicyDo Not Sell My Info