@simbachain/hardhat
Advanced tools
Hardhat plugin for deploying smart contracts to the SIMBA Chain Blocks platform.
Do you love SIMBA Chain? Do you love Hardhat? Then you're in luck! The Hardhat plugin for SIMBA Chain allows you to deploy smart contracts to your preferred blockchain through the SIMBA Blocks platform, using the same Hardhat web3 suite that you're used to developing and testing your smart contracts with. All you have to do to use the plugin is install it in your Hardhat project, compile your contracts, and then follow a few simple steps to deploy your smart contracts to chain through the Blocks platform. If you're not familiar with SIMBA's Blocks platform, it allows you to deploy smart contracts and automatically generate REST API endpoints that allow you to easily interact with your deployed smart contract.
The following are the general steps to get going with the SIMBA Chain Hardhat plugin. The rest of the documentation provides details on these and other steps.
If users want to view and/or use a boilerplate for the SIMBA Chain Truffle plugin, they can navigate to https://github.com/SIMBAChain/hardhat-plugin-template
From that URL, users can click the "Use this template" tab
If users want to view and/or use a boilerplate for the SIMBA Chain Truffle plugin, they can navigate to https://github.com/SIMBAChain/truffle-plugin-template
From that URL, users can click the "Use this template" tab
You should have a SIMBA Blocks Instance to communicate with. Additionally you must have a least one contract application created in the instance (though the plugin will direct you to create one if you do not yet have one). To create an application, open your browser, navigate to your instance and log in using your SIMBA user account. Click on your organization -> Applications and then click on the "Add" button. Follow the on screen instructions to create your application.
Next, create a directory where you want your Hardhat project to live, eg:
$ mkdir my_hardhat_project
And then cd into that project:
$ cd my_hardhat_project
Then create an npm project in that directory:
$ npm init
You can hit return/enter through the npm prompts if you'd like
NOTE: It is this level of your project (the root), where your package.json lives, where you will run your Hardhat CLI commands
You will also need to create your Hardhat TypeScript project. To do so, from the directory where your package.json now lives, run:
$ npx hardhat
For more info on starting a Hardhat project, you can follow the very brief instructions at https://hardhat.org/tutorial/creating-a-new-hardhat-project.html . Once you get to the point where you are creating your project, you will see the following graphic, below (or something similar, depending on which version Hardhat is currently on). Select "Create an advanced sample project that uses TypeScript".
888 888 888 888 888
888 888 888 888 888
888 888 888 888 888
8888888888 8888b. 888d888 .d88888 88888b. 8888b. 888888
888 888 "88b 888P" d88" 888 888 "88b "88b 888
888 888 .d888888 888 888 888 888 888 .d888888 888
888 888 888 888 888 Y88b 888 888 888 888 888 Y88b.
888 888 "Y888888 888 "Y88888 888 888 "Y888888 "Y888
👷 Welcome to Hardhat v2.9.5 👷
? What do you want to do? …
Create a basic sample project
Create an advanced sample project
❯ Create an advanced sample project that uses TypeScript
Create an empty hardhat.config.js
Quit
We suggest you just create a TypeScript Hardhat project from scratch, as instructed above. However, if you already have a hardhat project written in JavaScript, then to convert it to a TypeScript project, please follow the very brief, very clear documentation that Hardhat provides:
https://hardhat.org/guides/typescript
**Troubleshooting Notes: if instead of seeing prompts to create a hardhat project after you run $ npx hardhat, you see something like:
Hardhat version 2.9.3 Usage: hardhat [GLOBAL OPTIONS] [TASK OPTIONS] etc.....
This means that you accidentally installed Hardhat globally, which you should not do. To fix this, head to your root directory of your system (not your project), and delete your hardhat config file there (hardhat.config.ts/js). That should solve the issue; if it does not, then you will probably also find an artifacts directory and contracts directory there, as well as package.json, package-lock.json files; delete those as well.
The objects/code that this plugin is built on are contained in @simbachain/web3-suites project, but all of this is abstracted away from the developer. Though if you want a brief summary of that code, you can check out the npm publication for that project.
For installation, just run:
$ npm install @simbachain/hardhat
Then, import Simba Hardhat plugin in your Hardhat.config.ts:
import "@simbachain/hardhat";
Or if you have a Hardhat.config.js file, add a require statement:
require("./simba_hardhat");
Once you have Hardhat installed locally, you will need to create an env file in the root of your project (or you can create it in your SIMBA_HOME directory; please see Discovery of Environment Variables, but we suggest you create your env file in the root of your project, where your package.json file lives). This file can be titled any of:
If you do not want to use client credentials / non interactive commands, then the only value you need to set is your SIMBA_API_BASE_URL, which would look something like the following, but would vary, based on your environment:
SIMBA_API_BASE_URL=https://simba-dev-api.platform.simbachain.com/
If you want to use client credentials / non interactive commands, then you should also set SIMBA_AUTH_CLIENT_ID and SIMBA_AUTH_CLIENT_SECRET. So then your env file would look something like:
SIMBA_API_BASE_URL=https://simba-dev-api.platform.simbachain.com/
SIMBA_AUTH_CLIENT_ID=<your client ID for your environment>
SIMBA_AUTH_CLIENT_SECRET=<your client secret for your environment>
The most important file in your SIMBA Chain Hardhat project is your simba.json file. You DO NOT need to create and configure a simba.json file, though you will see references to simba.json in this documentation, and you will notice that this file populates in your project after you run simba commands.
NOTE regarding simba.json in your Hardhat project:
It may be tempting to just try and start a Truffle project in the same directory as a Hardhat project. Do not do this. Hardhat projects and Truffle projects should have their own simba.json files, and should live in separate directories.
Moreover, you should NOT directly manipulate your simba.json file in most cases. Any manipulation you may need to do can be done from the terminal.
Finally, run the following command to make sure everything is installed correctly:
$ npx hardhat simba help
And then you should see the following:
? Please choose which commmand you would like help with › - Use arrow-keys. Return to submit.
❯ login
export
deploy
logout
simbajson
generalprocess
loglevel
pull
viewcontracts
When it comes to setting and discovering environment variables for you project, we try to make it as simple as possible, while also allowing flexibility for users. Towards this goal, there are two main locations you can set environment variables in an env file for your project, and three different file names you can you use for your env file.
You can name your env file any one of the following:
export SIMBA_HOME=/Users/johnsmith/somedirectory
Then you can place your env file inside that directory, and the plugin will discover it.
The plugins will first look inside the root of your local project for an env file, then they will look inside SIMBA_HOME.
There are only three keys and values you need to know about
https://simba-dev-api.platform.simbachain.com/
For (2) and (3) above, you can obtain your client ID and client secret by navigating to your organisation and application in the UI, and then creating an ID and secret pair.
So as an example, in the root of your project, you would create a file called ".simbachain.env", and it would look like:
SIMBA_API_BASE_URL=https://simba-dev-api.platform.simbachain.com/
SIBMA_AUTH_CLIENT_ID=<insert your SIMBA client ID>
SIMBA_AUTH_CLIENT_SECRET=<insert your SIMBA client secret>
Please note that when running commands, you must be in the root of your project. This is where your package.json lives. If you try to run commands in a different directory, you will likely see unhandled error messages.
You do NOT need to manually compile your contracts. The SIMBA Chain Hardhat plugin will automatically compile your contracts when you export them to the SIMBA Blocks platform. However, if you would like to manually compile your contracts, first write them and save them in your /contracts/ directory. Then run:
$ npx hardhat compile
This will save your compiled contracts to your /artifacts/ directory.
The SIMBA Chain Hardhat plugin extends the tasks that are available to developers, and allows for the deployment of smart contracts by using custom defined Hardhat tasks. The following will explain what tasks are (VERY briefly), and how to use SIMBA's custom tasks.
If you're not familiar with tasks in Hardhat, the best way to think about them is: "anything you can do in Hardhat is a task." So just think of tasks as commands. The SIMBA Chain plugin simply extends what tasks are available to developers while using Hardhat. The only true additional task in the Simba Hardhat plugin is the "simba" task: the main CLI entry point task added by this plugin is the "simba" task. This task then takes a subtask as a parameter. Then, depending on the subtask selected, optional parameters can be passed. So the template CLI input for running a Simba Hardhat plugin task is:
npx hardhat simba <subtask> <optional args>
So even though we refer to tasks such as "export" and "deploy," you can't run them directly from the "npx hardhat" command: running "npx hardhat export" will throw an error, but "npx hardhat simba export" will not. This is by design, to avoid collision with Hardhat native commands, such as "help".
Below, we explain the Hardhat tasks that you will use in the SIMBA plugin to deploy your contracts. They are listed and explained in the order that you would follow to login and deploy your contracts. Then, information is provided on other tasks, such as "help" and "loglevel".
NOTE : you need to have at least one app present in the SIMBA Chain org that you try to log into. This is because, to deploy a contract, SIMBA needs to know which app you are deploying to. You can create an empty app, which is sufficient, by going to the UI, logging into your org, and creating an app there. If you try to login without an app present, then the plugin will allow you to create an app from the terminal.
Once you have configured your simba.json file, you will be able to login. the Hardhat plugin uses keycloack device login, so you will be given a URL that you can navigate to, to grant permission to your device. You will then be prompted to select the organization and application from SIMBA Chain that you wish to log into. To log in, simply run
$ npx hardhat simba login
You will then see something similar to:
simba: Please navigate to the following URI to log in: https://simba-dev-sso.platform.simbachain.com/auth/realms/simbachain/device?user_code=JPGL-RFRW
Simply navigate to the specified URL and grant permission to your device, and you will be prompted to choose your organization:
? Please pick an organisation › - Use arrow-keys. Return to submit.
❯ CarNFTs
CoffeeSupplyChain
LennysGhost
You will then be prompted to select your application, with something like:
? Please pick an application › - Use arrow-keys. Return to submit.
❯ testApp
testAppNewContracts
revisedApp
There is also a non-interactive login mode. This mode is mainly for CI/CD, but you can run this login mode like a normal login command if you have a few environment variables set, and it will use a client credentials flow for login. You will need to set
(please see Discovery of Environment Variables for directions on setting those variables)
To run login in non-interactive mode, you can run with org and app flag:
$ npx hardhat simba login --interactive false --org <myOrg> --app <myApp>
Or you can run with just the app flag, if you already have logged into an org before, and just want to switch your app:
$ npx hardhat simba login --interactive false --app <myApp>
If you already have an org and app set in simba.json, and want to use that org and app, you can just run:
$ npx hardhat simba login --interactive false
However, if you specify an org, you must specify an app. The following will throw an error:
$ npx hardhat simba login --interactive false --org <myOrg>
Once you have logged in, you will be able to export your contracts, which will save them to your organization's contracts (you can also think of this action as "importing" your contracts to Blocks). For this command, you can either run export without arguments, or with optional arguments. To export without optional arguments, run
$ npx hardhat simba export
You will then be prompted to select all of the contracts you want to export to Blocks:
? Please select all contracts you want to export. Use the Space Bar to select or un-select a contract (You can also use -> to select a contract, and <- to un-select a contract). Hit Return/Enter when you are ready to export. If you have questions on exporting libraries, then please run 'npx hardhat simba help --topic libraries' . ›
Instructions:
↑/↓: Highlight option
←/→/[space]: Toggle selection
a: Toggle all
enter/return: Complete answer
◯ CoffeeERC721
◯ CoffeeUpgradable
◯ WatchERC721
◯ WatchUpgradable
If you want to export just one specific contract, you can specify a primary contract by passing the --prm flag, followed by the contract name:
$ npx hardhat simba export --prm CoffeeERC721
There is also a non-interactive export mode. This mode is mainly for CI/CD, but it can be run just like any other export command. If you want to export all contracts that have compiled changes since the last time you exported, then you can export in non-interactive mode. Note that this will not export contracts that are strictly dependencies (eg OpenZeppelin imported contracts). To run export in non-interactive mode, run:
$ npx hardhat simba export --interactive false
After you have logged in and exported your contract, you will be able to deploy your contract. This step will generate the REST API endpoints that you can use to interact with your smart contract's methods, and save them to your organization and app. You will then be able to access those endpoints through either the SIMBA Blocks UI, or programatically through one of SIMBA's SDKs. To deploy, you have two options. First, you can run
$ npx hardhat simba deploy
If you run the above command, you will be prompted to selected which contract you want to deploy from a list of contracts you have exported. Second, you can specify the primary contract you want to deploy by running:
$ npx hardhat simba deploy --prm <contract name you want to deploy>
If your contract's constructor takes parameters, then you will see the following prompt, asking you to specify how you would like to provide the values for these parameters:
? Your constructor parameters can be input as either a single json object or one by one from prompts. Which would you prefer? › - Use arrow-keys. Return to submit.
❯ enter all params as json object
enter params one by one from prompts
Then you will be asked to specify API name, blockchain you want to deploy to, offchain storage (AWS, Azure, no storage, etc., but this depends on what you have configured for your account), and the values for your contract's constructor, based on the way you answered the last prompt above:
simba deploy: gathering info for deployment of contract CoffeeERC721
✔ Please choose an API name for contract CoffeeERC721 [^[w-]*$] … CoffeeERC721V1
✔ Please choose the blockchain to deploy to. › Quorum
✔ Please choose the storage to use. › No Storage
? Please enter any arguments for the contract as a JSON dictionary. › {"ownerName": "Brendan", "poundWeight": 13}
NOTE: regarding your API name, this just needs to be a unique name containing alphanumeric characters and/or underscores. So if your contract is called MyTokenContract, consider giving your API a name something like MyTokenContract_v1.
And just like that, your contract is deployed! If you want to view information on contract deployments you've made through the plugin, you can go to your simba.json, where you will find info similar to what's found below. So if you need to reference any information, you can find it there.
"most_recent_deployment_info": {
"address": "0x2B9d4cD4bEc9707Db7fE42d107C0F2D180B3dA45",
"deployment_id": "5b041a32-f1c4-465f-80bf-52e76379f66c",
"type": "contract"
},
"contracts_info": {
"MetadataLib": {
"design_id": "f66163a7-63de-4d8b-98d9-12e72148341f",
"address": "0x69A48097c643CD9dCDc3574F406092a95A660678",
"deployment_id": "3c860020-d762-464c-a293-25caa23c3f63",
"contract_type": "library"
},
"CoffeeERC721": {
"design_id": "025e1161-c917-45f0-8a81-42180753da9b",
"address": "0x2B9d4cD4bEc9707Db7fE42d107C0F2D180B3dA45",
"deployment_id": "5b041a32-f1c4-465f-80bf-52e76379f66c",
"contract_type": "contract"
}
}
If you want to logout, then you can do so by running
$ npx hardhat simba logout
Doing so will delete your auth token in authconfig.json
To choose a help topic from a list, run
$ npx hardhat simba help
Which will prompt you to select a help topic
? Please choose which commmand you would like help with › - Use arrow-keys. Return to submit.
❯ login
export
deploy
logout
simbajson
generalprocess
loglevel
pull
viewcontracts
Or you can pass an optional --topic flag to specify which topic you would like help with. For instance, for help with the "deploy" task, run
$ npx hardhat simba help --topic deploy
As indicated above, the available help topics are:
This command is mainly designed to be used in the CI/CD process, but it can actually be used for many things. Regarding the CI/CD use, if you use CI/CD to export your contracts in the CI/CD pipeline after you push, then you'll need to update your project's simba.json after you do a git pull. This is because the plugin relies on the "source_code" field for each contract in your simba.json's "contract_info" section to know which contracts to export. So to get the most up to date version of your exported contracts' source code in your simba.json, just run:
$ npx hardhat simba pull
In addition to pulling source code for your simba.json, you can also use the pull command to pull the most recent versions of your solidity contracts from SIMBA Chain and place them in your /contracts/ directory (or /contracts/SibmaImports/).
A brief note on file structure is worthwhile here. By default, contracts pulled from SIMBA Chain will be written to /contracts/SimbaImports/ directory. If you would like to place pulled files in the top level of your /contracts/ directory, then you can pass the --usesimbapath false flag in your call.
A note on file names is also in order. Files that are pulled from SIMBA are placed into files named after the contract name. So if you have two contracts, token1 and token2, which both originally lived in OurTokens.sol. Then both of those will end up in files named token1.sol and token2.sol. This is done becuase, currently, contracts that are pushed to SIMBA Chain sit in a flat structure, without sub-directories.
Usually, you shouldn't need to do pull contracts from SIMBA if you have git pulled, but there may be cases when, for instance, you want ALL of your most recent contracts from your SIMBA Chain organisation, even ones that weren't living in your current project. In that case, you can run:
$ npx hardhat simba pull --pullsolfiles true
This will pull all most recent contracts from your SIMBA Chain org and place them in your /contracts/SimbaImports/ folder.
If you want to place your pulled contracts in the top level of your /contracts/ directory, instead of into /contracts/SimbaImports/, then you can run:
$ npx hardhat simba pull --pullsolfiles true --usesimbapath false
If you would like to interactively choose which .sol contract files to choose, in addition to auto pulling your source code for your simba.json, you can run:
$ npx hardhat simba pull --interactive true
If you would like to skip pulling your simba.json source code (though you really should not), you can set the --pullsourcecode flag to false. For example, the following command will only pull your .sol contract files:
$ npx hardhat simba pull --pullsourcecode false --pullsolfiles true
If you would like to pull your .sol contract files interactively, while skipping your simba.json source code pull, you can run:
$ npx hardhat simba pull --pullsourcecode false --interactive true
If you want to pull a specific contract's most recently exported version, by name, from SIMBA, then you can run:
$ npx hardhat simba pull --contractname <your contract name>
If you would like to pull a specific contract version from its design_id, you can run:
$ npx hardhat simba pull --id <your contract design_id>
Contract design IDs can be referenced in your simba.json file under contracts_info -> contract name -> design_id. Contract design IDs can also be viewed by running:
npx hardhat simba viewcontracts
This command will return information pertaining to all contracts saved to your organisation on SIMBA Chain. Contract info includes: name, id, and version. For this command, just run:
$ npx hardhat simba viewcontracts
The Simba Hardhat plugin uses tslog for logging / debugging. Setting a log level through this command will set a MINIMUM log level. So for instance, if you set the log level to 'info', then logs of level SimbaConfig.log.info(...) as well as SimbaConfig.log.error(...) will be logged. Valid values for log levels are 'error', 'info', 'debug', 'silly', 'warn', 'trace', and 'fatal'. You can either run this command without any arguments, which will allow you to set a minimum log level from prompt:
$ npx hardhat simba loglevel
And you will be prompted to selected a minimum log level:
? Please choose the minimum level to set your logger to › - Use arrow-keys. Return to submit.
❯ debug
error
fatal
info
silly
trace
warn
Or you can set the specific log level from the CLI:
$ npx hardhat simba loglevel --lvl <desired log level>
If you pass an invalid log level, then the plugin defaults to "info".
A brief note here about deploying and linking libraries. You do not need to actively link libraries in this plugin. Once you have deployed your contract, SIMBA's Blocks platform handles that for you. All you need to do is make sure that if you are deploying a contractX that depends on libraryX, then first deploy libraryX. Then when you deploy contractX, the library linking will automatically be conducted by SIMBA. If you look in your simba.json after deploying a library, you will see a field for library_addresses (below) This field gets exported with other contracts, and is how SIMBA knows whether a contract needs to be linked to a library when it is deployed.
...
"library_addresses": {
"MetadataLib": "0x96E07C02A523f254E17F23Cd577f4518B0c9A855"
},
Adding libraries: If a contract that you are trying to deploy requires an external library that you did not deploy to SIMBA Chain, but you have the name and address of that library, then you can add the library by running the following command, which does not take parameters:
$ npx hardhat simba addlib
and you will then be prompted to specify the name and address of your library. If you want to specify the name and address of the library from the CLI, then you can run:
SIMBA Chain’s web3 plugins offer CI/CD support, so that when you push your git project, you automatically export all of your recently changed contracts in your project to your SIMBA Chain org. In this process, any contracts that you have made recent changes to will be compiled and exported to SIMBA Chain. If no changes have been made to your contracts, then nothing will be exported to SIMBA Chain.
To use SIMBA’s plugin's' CI/CD functionality, you will need to be working with a Hardhat project that has the SIMBA Chain Hardhat plugin installed. Please see the following for more details on installing and using our plugins:
1.Acquire a client ID and secret from SIMBA Chain for step 4 (below). You can acquire a client ID and secret from the SIMBA Chain UI, by navigating to your org, then application, and then selecting “secrets” in the upper right hand corner of the page. 2. You will need to be working with a git project that supports CI/CD. The setup for different providers varies, but the directions for getting started with CI/CD in Gitlab are here: https://docs.gitlab.com/ee/ci/quick_start/ 3. You will need to configure two protected environment variables in your git service environment:
a. SIMBA_AUTH_CLIENT_ID
b. SIMBA_AUTH_CLIENT_SECRET
4. Since these are protected variables, you will probably need to be pushing from a protected branch, regardless of your git service. 5. You will then need to create your pipeline. In Gitlab, that means creating a .gitlab-ci.yml file. Your pipeline will look different, depending on which plugin you’re using. Here is what a pipeline for gitlab would look like:
image: node:16.14.2
stages:
- install_dependencies_and_run
job_install_compile_and_run:
stage: install_dependencies_and_run
script:
- npm install
# following will use the organisation and application from your simba.json
- npx hardhat simba login --interactive false
# # if you always want to use the same org and app, then provide <org name> and <app name> below
# # but this approach only works if your 'organisation' and 'application' are set in simba.json,
# # which you can do by running 'npx hardhat simba login' before pushing
# - npx hardhat simba login --interactive false --org <org name> --app <app name>
# pull most recently changed contracts to simba.json:
- npx hardhat simba pull
- npx hardhat simba export --interactive false
The process for enabling CI/CD in your team’s workflow is very simple. We list the steps here:
$ git pull
$ npx hardhat simba pull
This command ensures that your simba.json source code for each contract is up to date. To determine which contracts need to be exported, the plugin compares the source code it finds in your simba.json to the source code it finds in compiled artifacts. If there is a difference, then the plugin knows that a contract has changed and needs to be exported. Running simba pull is necessary because in CI/CD, exporting happens in the git service environment, so there is no way for your simba.json to be updated with most recent source code during export. So what simba pull does is retrieve that source code from SIMBA Chain and write it to your simba.json
You may notice above in the pipeline that simba pull is run inside the pipeline. This is as a precaution, in case you forgot to run in your local environment. It’s never a bad idea to include simba pull in your CI/CD pipeline, but it will make the pipeline run more slowly.
modify contracts as desired within your project
compilation of contracts is optional. The Hardhat and Truffle plugins automatically compile your contracts when exported.
run git push:
$ git push
And that’s it!
So if you were to make changes to a contract called TestContractVt6, then run git push, you would see in your pipeline job logs that this contract was exported to SIMBA Chain
This command allows you to view info from your simba.json, as well as auth token (with token redacted) from authconfig.json. The command takes two optional parameters: 'field' and 'contract'. If you run the command without any parameters:
$ npx hardhat simba simbainfo
then your simba.json will be printed in its entirety.
For the 'field' parameter, you can either pass the exact name of a simba.json field (eg 'most_recent_deployment_info'), or you can pass one of the following abbreviations: 'org' for organisation info, 'app' for application info, 'deploy' for most recent deployment info, 'auth' for authProviderInfo, 'contracts' for all contracts (this would be the same as using the --contract all flag), 'web3' for web3Suite, 'baseurl' for 'baseURL', and 'authtoken' to retrieve info for your current auth credentials from authconfig.json. As an example, to retrieve most recent deployment info, you should run
$ npx hardhat simba simbainfo --field deploy
For the 'contract' parameter, you can either pass the name of a contract, eg 'MyContract,' or you can pass 'all' to view info for all of your contracts in simba.json.contracts_info. An example of this call would be
$ npx hardhat simba simbainfo --contract MyContract
This command will retrieve and print the current path to relevant directories in your project: 'artifacts', 'contracts', and 'build'. Simply run:
$ npx hardhat simba getdirs
This command allows the user to set the absolute directory path for a relevant directory in their project. Most users won't need this, but there may be cases in which you've changed your default directory for 'contracts', 'build', or 'artifacts'. This would be the case if you're using a Foundry project that has been integrated into a Hardhat project. To set a new directory path, pass the -dirname and -dirpath parameters. Valid values for dirname are 'contract', 'contracts', 'artifact', 'artifacts', and 'build'. Note that 'contract' and 'contracts' both refer to the directory named 'contracts'; and 'artifact' and 'artifacts' both refer to the directory named 'artifacts'. So for instance, to change the absolute directory path for 'build' to '/myhomedir/dev/myproject/build/', just run:
$ npx hardhat simba setdir --dirname build --dirpath /myhomedir/dev/myproject/build/
NOTE: for windows users, if the path to your new directory contains "", then please make sure you're setting with single "" and not "\". So "path\to\my\directory" instead of "path\\to\\my\\directory"
Note that if you pass 'reset' as --dirpath, then the path to the directory specified in --dirname will be reset to its default path.
This command allows the user to reset a directory path for 'build', 'contracts', or 'artifacts' to default settings for their project. To reset a directory path with this command, just pass --dirname, which can be any of 'build', 'contract', 'contracts', 'artifact', 'artifacts', or 'all'. Note that 'contract' and 'contracts' both refer to the directory named 'contracts'; and 'artifact' and 'artifacts' both refer to the directory named 'artifacts'. So for example, to reset the path to your 'artifacts' directory, just run:
$ npx hardhat simba resetdir --dirname artifacts
To reset all three of 'contracts', 'build', and 'artifacts', run:
$ npx hardhat simba resetdir --dirname all
This command allows the user to delete contract designs from their SIMBA Chain organisation. This command can be run with an optional 'id' parameter to delete a single contract, or it can be run without any parameters, which will allow the user to choose from prompts which contract designs they want to delete. To run with the 'id' parameter:
$ npx hardhat simba deletecontract --id <your contract design_id>
To run without parameters, and then choose from prompts:
$ npx hardhat simba deletecontract
FAQs
Simba Chain plugin for hardhat
The npm package @simbachain/hardhat receives a total of 10 weekly downloads. As such, @simbachain/hardhat popularity was classified as not popular.
We found that @simbachain/hardhat demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Socket's package search now displays weekly downloads for npm packages, helping developers quickly assess popularity and make more informed decisions.
Security News
A Stanford study reveals 9.5% of engineers contribute almost nothing, costing tech $90B annually, with remote work fueling the rise of "ghost engineers."
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.