From a81a88cca0ef9e86cb613077381df19d1ba5f135 Mon Sep 17 00:00:00 2001 From: Franco Victorio Date: Tue, 2 Mar 2021 05:24:37 -0300 Subject: [PATCH] Fix mentions of buidler (#2548) (cherry picked from commit 232c355b3ab6c14b8eb6c8127376995dcba8bf3e) --- .gitignore | 2 +- contracts/proxy/README.adoc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.gitignore b/.gitignore index b79041342bb..0a62cf0b3c9 100644 --- a/.gitignore +++ b/.gitignore @@ -54,6 +54,6 @@ allFiredEvents .coverage_cache .coverage_contracts -# buidler +# hardhat cache artifacts diff --git a/contracts/proxy/README.adoc b/contracts/proxy/README.adoc index ea6bf3a389d..0a2ecdf7b56 100644 --- a/contracts/proxy/README.adoc +++ b/contracts/proxy/README.adoc @@ -13,7 +13,7 @@ An alternative upgradeability mechanism is provided in <>. This pattern, The {Clones} library provides a way to deploy minimal non-upgradeable proxies for cheap. This can be useful for applications that require deploying many instances of the same contract (for example one per user, or one per task). These instances are designed to be both cheap to deploy, and cheap to call. The drawback being that they are not upgradeable. -CAUTION: Using upgradeable proxies correctly and securely is a difficult task that requires deep knowledge of the proxy pattern, Solidity, and the EVM. Unless you want a lot of low level control, we recommend using the xref:upgrades-plugins::index.adoc[OpenZeppelin Upgrades Plugins] for Truffle and Buidler. +CAUTION: Using upgradeable proxies correctly and securely is a difficult task that requires deep knowledge of the proxy pattern, Solidity, and the EVM. Unless you want a lot of low level control, we recommend using the xref:upgrades-plugins::index.adoc[OpenZeppelin Upgrades Plugins] for Truffle and Hardhat. == Core