idex-contracts-whistler VS hardhat

Whistler includes a wallet exit mechanism, which allows users to withdraw funds in the case IDEX is offline or maliciously censoring withdrawals. Calling exitWallet initiates the exit process, which prevents the wallet from subsequent deposits, trades, or normal withdrawals. Wallet exits are a two-step process as defined in controls.

That's it for the first part ! Then we will use Hardhat to deploy our Solidity Contract on the Polygon testnet, and then overload our mintNFT() function with the actual minting. If you want to see the Part 2 quickly, give us some love and we will execute ! ❤️❤️❤️

To keep things simple and visible (in case you cant deploy), we will use Sepolia testnet blockchain and Hardhat as development environment, so to configure hardhat to use sepolia we need to add the following configuration to the hardhat.config.js file:

The documentation has no mention of Trezor wallet support. According to this GitHub issue I could try out this Frame application, but I was wondering if there was a simpler solution that didn't require installing some 3rd party application.

I have two skipped tests because at the time of writing this article events firing doesn't work properly in the latest version. Link to the github issue

Hardhat

Other options include Remix (an IDE), ChainIDE, Anchor (for Solana), Hardhat, and lots of others. Web3 dev environments have come a long way in a short time, and there’s probably something out there for whatever you need.

Hardhat allows developers to build, test, and deploy smart contracts and dApps using a variety of tools and libraries. With over 114K users on GitHub and an active Discord community, Hardhat is a hugely popular framework for dApp developers. Much of its popularity can be attributed to its rich list of features, flexibility and the Hardhat Ethereum Virtual Machine for testing and debugging smart contracts.

The hardhat-ethers plugin adds the ethers.js library to the Hardhat node, making it possible to use its functionalities. It's possible to use it to deploy the contract, but since our goal is to create transactions, we can also add some code to do that as well.

Also learning how to use one of these development environments instead of Remix is necessary: 1. Hardhat: https://hardhat.org 2. Foundry: https://github.com/foundry-rs/foundry

Easy for devs — The zkEVM supports most popular tools out of the box. You can build, test, debug, and deploy your smart contracts with Hardhat, Infura, Truffle, etc. All the tools you use now, you can keep using. And there is already a bridge to move tokens onto and off the network.