Skip to content

Commit

Permalink
Add doc entry for "Verifying Deployments on BscScan"
Browse files Browse the repository at this point in the history
  • Loading branch information
jbargu committed Feb 17, 2021
1 parent 9e2d018 commit 4285465
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/deploy.rst
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@ The following actions WILL remove locally stored deployment data within your pro

To restore a deleted :func:`ProjectContract <brownie.network.contract.ProjectContract>` instance, or generate one for a deployment that was handled outside of Brownie, use the :func:`ContractContainer.at <ContractContainer.at>` method.

Verifying Deployments on Etherscan
Verifying Deployments on Etherscan/BscScan
==========================================

Brownie features automatic source code verification for solidity contracts on all networks supported by etherscan. To verify a contract while deploying it, add the ``publish_source=True`` argument:
Expand Down Expand Up @@ -119,4 +119,4 @@ If you need deployment artifacts on a development network, set :attr:`dev_deploy
These temporary deployment artifacts and the corresponding entries in :ref:`the deployment map<persistence>` will be removed whenever you (re-) load a project or connect, disconnect, revert or reset your local network.

If you use a development network that is not started by brownie - for example an external instance of ganache - the deployment artifacts will not be deleted when disconnecting from that network.
However, the network will be reset and the deployment artifacts deleted when you connect to such a network with brownie.
However, the network will be reset and the deployment artifacts deleted when you connect to such a network with brownie.

0 comments on commit 4285465

Please sign in to comment.