Angstrom Contracts

The contracts are split between "core" and "periphery". Where core is responsible for order validation & settlement, underlying AMM reward management and store for user deposits.

The periphery contracts implement the finer details of access control, as well as managing collection and distribution of node & referral fees.

• Bundle Building - What structs actually mean to the Angstrom contract & what functionality it triggers
• Payload Types - The structs that Angstrom execute method expects
• PADE Encoding - The encoding format Angstrom uses to interpret the payload in execute
• Pool Config Store
• "RAY" - What is Ray

Architecture

Methods

• execute: Entrypoint for pool update, ToB + user order processing functionality & exact make up described in bundle-building & payload-types
• deposit: Allows users to deposit funds into Angstrom for later trading (allows for gas savings vs. ERC20 with allowance usage)
• withdraw: Counterpart to deposit allows users to take back funds
• invalidateNonce: Lets users invalidate "standing orders" by marking the associated nonce as used