Account Abstraction
Design that lets smart contracts act as user accounts, enabling custom validation, sponsored fees, and better UX (e.g., EIP‑4337).
Design that lets smart contracts act as user accounts, enabling custom validation, sponsored fees, and better UX (e.g., EIP‑4337).
Smart‑contract wallet enabling N‑of‑M approvals for transactions, widely used by DAOs and teams for treasury and permission management.
Framework for building blockchains in Rust with pluggable consensus, runtime pallets, and tooling, powering Polkadot parachains and standalone chains.
Smart contract programming language for the EVM, with static typing, ABI compatibility, and a large ecosystem of tooling and libraries.
Rollup that uses a base chain for data availability but validates and finalizes via its own consensus or light‑client rules rather than a smart contract on L1.
Ephemeral keys with restricted permissions used for a limited time, enabling safer automated actions without exposing the main wallet key.
Holding and controlling one’s own private keys rather than relying on a custodian; enables permissionless access but requires strong key hygiene.
Actor that scans mempools and order flow to construct profitable transaction bundles, exploiting arbitrage, liquidations, or sandwich opportunities.
MEV exploit where an attacker places a buy before and a sell after a victim’s trade to profit from induced price movement and slippage.
User‑set threshold for maximum acceptable price movement during a swap; trades revert if final price exceeds this bound.
Token representing a claim on staked assets and rewards, providing liquidity while the underlying stake remains locked (e.g., liquid staking).