README.adoc 6.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145
  1. = Utilities
  2. [.readme-notice]
  3. NOTE: This document is better viewed at https://docs.openzeppelin.com/contracts/api/utils
  4. Miscellaneous contracts and libraries containing utility functions you can use to improve security, work with new data types, or safely use low-level primitives.
  5. * {Math}, {SignedMath}: Implementation of various arithmetic functions.
  6. * {SafeCast}: Checked downcasting functions to avoid silent truncation.
  7. * {ReentrancyGuard}: A modifier that can prevent reentrancy during certain functions.
  8. * {ReentrancyGuardTransient}: Variant of {ReentrancyGuard} that uses transient storage (https://eips.ethereum.org/EIPS/eip-1153[EIP-1153]).
  9. * {Pausable}: A common emergency response mechanism that can pause functionality while a remediation is pending.
  10. * {Nonces}: Utility for tracking and verifying address nonces that only increment.
  11. * {NoncesKeyed}: Alternative to {Nonces}, that support keyed nonces following https://eips.ethereum.org/EIPS/eip-4337#semi-abstracted-nonce-support[ERC-4337 specifications].
  12. * {ERC165}, {ERC165Checker}: Utilities for inspecting interfaces supported by contracts.
  13. * {BitMaps}: A simple library to manage boolean value mapped to a numerical index in an efficient way.
  14. * {EnumerableMap}: A type like Solidity's https://solidity.readthedocs.io/en/latest/types.html#mapping-types[`mapping`], but with key-value _enumeration_: this will let you know how many entries a mapping has, and iterate over them (which is not possible with `mapping`).
  15. * {EnumerableSet}: Like {EnumerableMap}, but for https://en.wikipedia.org/wiki/Set_(abstract_data_type)[sets]. Can be used to store privileged accounts, issued IDs, etc.
  16. * {DoubleEndedQueue}: An implementation of a https://en.wikipedia.org/wiki/Double-ended_queue[double ended queue] whose values can be added or removed from both sides. Useful for FIFO and LIFO structures.
  17. * {CircularBuffer}: A data structure to store the last N values pushed to it.
  18. * {Checkpoints}: A data structure to store values mapped to a strictly increasing key. Can be used for storing and accessing values over time.
  19. * {Heap}: A library that implements a https://en.wikipedia.org/wiki/Binary_heap[binary heap] in storage.
  20. * {MerkleTree}: A library with https://wikipedia.org/wiki/Merkle_Tree[Merkle Tree] data structures and helper functions.
  21. * {Create2}: Wrapper around the https://blog.openzeppelin.com/getting-the-most-out-of-create2/[`CREATE2` EVM opcode] for safe use without having to deal with low-level assembly.
  22. * {Address}: Collection of functions for overloading Solidity's https://docs.soliditylang.org/en/latest/types.html#address[`address`] type.
  23. * {Arrays}: Collection of functions that operate on https://docs.soliditylang.org/en/latest/types.html#arrays[`arrays`].
  24. * {Base64}: On-chain base64 and base64URL encoding according to https://datatracker.ietf.org/doc/html/rfc4648[RFC-4648].
  25. * {Bytes}: Common operations on bytes objects.
  26. * {Calldata}: Helpers for manipulating calldata.
  27. * {Strings}: Common operations for strings formatting.
  28. * {ShortStrings}: Library to encode (and decode) short strings into (or from) a single bytes32 slot for optimizing costs. Short strings are limited to 31 characters.
  29. * {SlotDerivation}: Methods for deriving storage slot from ERC-7201 namespaces as well as from constructions such as mapping and arrays.
  30. * {StorageSlot}: Methods for accessing specific storage slots formatted as common primitive types.
  31. * {TransientSlot}: Primitives for reading from and writing to transient storage (only value types are currently supported).
  32. * {Multicall}: Abstract contract with a utility to allow batching together multiple calls in a single transaction. Useful for allowing EOAs to perform multiple operations at once.
  33. * {Context}: A utility for abstracting the sender and calldata in the current execution context.
  34. * {Packing}: A library for packing and unpacking multiple values into bytes32
  35. * {Panic}: A library to revert with https://docs.soliditylang.org/en/v0.8.20/control-structures.html#panic-via-assert-and-error-via-require[Solidity panic codes].
  36. * {Comparators}: A library that contains comparator functions to use with the {Heap} library.
  37. * {CAIP2}, {CAIP10}: Libraries for formatting and parsing CAIP-2 and CAIP-10 identifiers.
  38. * {Memory}: A utility library to manipulate memory.
  39. * {InteroperableAddress}: Library for formatting and parsing ERC-7930 interoperable addresses.
  40. * {Blockhash}: A library for accessing historical block hashes beyond the standard 256 block limit utilizing EIP-2935's historical blockhash functionality.
  41. * {Time}: A library that provides helpers for manipulating time-related objects, including a `Delay` type.
  42. [NOTE]
  43. ====
  44. Because Solidity does not support generic types, {EnumerableMap} and {EnumerableSet} are specialized to a limited number of key-value types.
  45. ====
  46. == Math
  47. {{Math}}
  48. {{SignedMath}}
  49. {{SafeCast}}
  50. == Security
  51. {{ReentrancyGuard}}
  52. {{ReentrancyGuardTransient}}
  53. {{Pausable}}
  54. {{Nonces}}
  55. {{NoncesKeyed}}
  56. == Introspection
  57. This set of interfaces and contracts deal with https://en.wikipedia.org/wiki/Type_introspection[type introspection] of contracts, that is, examining which functions can be called on them. This is usually referred to as a contract's _interface_.
  58. Ethereum contracts have no native concept of an interface, so applications must usually simply trust they are not making an incorrect call. For trusted setups this is a non-issue, but often unknown and untrusted third-party addresses need to be interacted with. There may even not be any direct calls to them! (e.g. ERC-20 tokens may be sent to a contract that lacks a way to transfer them out of it, locking them forever). In these cases, a contract _declaring_ its interface can be very helpful in preventing errors.
  59. {{IERC165}}
  60. {{ERC165}}
  61. {{ERC165Checker}}
  62. == Data Structures
  63. {{BitMaps}}
  64. {{EnumerableMap}}
  65. {{EnumerableSet}}
  66. {{DoubleEndedQueue}}
  67. {{CircularBuffer}}
  68. {{Checkpoints}}
  69. {{Heap}}
  70. {{MerkleTree}}
  71. == Libraries
  72. {{Create2}}
  73. {{Address}}
  74. {{Arrays}}
  75. {{Base64}}
  76. {{Bytes}}
  77. {{Calldata}}
  78. {{Strings}}
  79. {{ShortStrings}}
  80. {{SlotDerivation}}
  81. {{StorageSlot}}
  82. {{TransientSlot}}
  83. {{Multicall}}
  84. {{Context}}
  85. {{Packing}}
  86. {{Panic}}
  87. {{Comparators}}
  88. {{CAIP2}}
  89. {{CAIP10}}
  90. {{Memory}}
  91. {{InteroperableAddress}}
  92. {{Blockhash}}
  93. {{Time}}