chore: docs files

OpenZeppelin · Dec 24, 2024 · e432b0d · e432b0d
1 parent f50ef5d
commit e432b0d
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 0 deletions.
diff --git a/docs/modules/ROOT/pages/erc20.adoc b/docs/modules/ROOT/pages/erc20.adoc
@@ -82,3 +82,5 @@ Additionally, there are multiple custom extensions, including:
  * xref:erc20-pausable.adoc[ERC-20 Pausable]: ability to pause token transfers.
 
  * xref:erc20-permit.adoc[ERC-20 Permit]: gasless approval of tokens (standardized as https://eips.ethereum.org/EIPS/eip-2612[`EIP-2612`]).
+
+ * xref:erc4262.adoc[ERC-4262]: standard interface for token vaults (standardized as https://eips.ethereum.org/EIPS/eip-4626[`EIP-4626`]).
diff --git a/docs/modules/ROOT/pages/erc4262.adoc b/docs/modules/ROOT/pages/erc4262.adoc
@@ -0,0 +1,3 @@
+= ERC-4262
+
+ERC4626 is an extension of ERC20 that proposes a standard interface for token vaults. This standard interface can be used by widely different contracts (including lending markets, aggregators, and intrinsically interest bearing tokens), which brings a number of subtleties. Navigating these potential issues is essential to implementing a compliant and composable token vault.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -82,3 +82,5 @@ Additionally, there are multiple custom extensions, including:
		* xref:erc20-pausable.adoc[ERC-20 Pausable]: ability to pause token transfers.

		* xref:erc20-permit.adoc[ERC-20 Permit]: gasless approval of tokens (standardized as https://eips.ethereum.org/EIPS/eip-2612[`EIP-2612`]).

		* xref:erc4262.adoc[ERC-4262]: standard interface for token vaults (standardized as https://eips.ethereum.org/EIPS/eip-4626[`EIP-4626`]).
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,3 @@
		= ERC-4262

		ERC4626 is an extension of ERC20 that proposes a standard interface for token vaults. This standard interface can be used by widely different contracts (including lending markets, aggregators, and intrinsically interest bearing tokens), which brings a number of subtleties. Navigating these potential issues is essential to implementing a compliant and composable token vault.