docs: batch Router docs

balancer · Apr 15, 2024 · 3d1d789 · 3d1d789
1 parent b20fd38
commit 3d1d789
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 0 deletions.
diff --git a/docs/concepts/pools/hooks.md b/docs/concepts/pools/hooks.md
@@ -14,6 +14,7 @@ Hooks introduce a new approach to managing a pool's execution logic. They are de
 - Automatic Gauge locking
 - Sell or Buy limits
 
+## Hook requirements
 
 A hook is a codeblock that implements arbitrary logic in a pool or external contract. In order to use hooks as part of a pool's operations two steps need to be done.
 

diff --git a/docs/concepts/router/overview.md b/docs/concepts/router/overview.md
@@ -3,6 +3,11 @@ order: 0
 title: Overview
 ---
 # Router Onchain API
+
+::: info
+Interactions with Balancer via the Router require either interaction with the `Router` or `BatchRouter`. The `BatchRouter` handles batch swaps & batch queries. Placing batch functionality in a separate contract was required due to the bytecode size limit of the EVM.
+:::
+
 The Router is the recommended entrypoint for user operations. It provides functions to both query and execute `swap`, `addLiquidity` and `removeLiquidity` operations against the Balancer vault.
 [Transient Accounting](/concepts/vault/features/transient-accounting.html) enables a simple query system that ensures query functions will always return the exact same outcome as their state-changing counterpart.