ether | An R package for working with Ethereum | Cryptocurrency library

perl's -n and -p command-line switches add an implicit while (<>) {...} block around the -e code, and in addition -p prints the line at the end of each iteration. So you need to change the -p to -n and only print out the lines which match; and remove the extra and unneeded while loop. So something like

I figured it out! Apparently in order for getAmountsOut() to return a value in wei, you need to provide a value in wei.

So instead of using 50000 for amountsIn, I used ethers.utils.parseEther("50000") :

That error is clear. you do not have sufficient funds. This is how you are getting the account information:

to test locally you need to make use of mocks which can simulate having an oracle network. Because you're working locally, a Chainlink node doesn't know about your local blockchain, so you can't actually do proper VRF requests. Note you can try deploy a local Chainlink node and a local blockchain and have them talk, but it isn't fully supported yet so you may get mixed results. Anyway, as per the hardhat starter kit that you linked, you can set the defaultNetwork to be 'hardhat' in the hardhat.config.js file, then when you deploy and run the integration tests (yarn test-integration), it will use mocks to mock up the VRF node, and to test the requesting of a random number. See the test here, and the mock contracts and linktoken get deployed here

Deploying a contract and interacting with the contract are two different things.

After you deployed the contract on a blockchain, then you need a provider which is kinda a bridge to a node in that blockchain.

Found what I was looking for. First thing I did was save the DAI contract address at the top:

I solved this issue by having a payable fallback function by defining it as:

Weth is different from other token, you're not able to use swapTokensForTokens. We must use the swapEthForTokens function instead, and you have to declare the data option separately.

so in your case we need to do:

Solidity code:

Not possible by design.

A contract address is determined from the deployment transaction params. Specifically, the ethers deploy() function is using the CREATE opcode by default, so the contract address is determined from the deployer address and the deploying transaction nonce param.

But the private key to the contract address is never generated during the deployment - so it can't be returned. Just the address.

Because otherwise I can't call the transfer method on the smart contract.

Correct. If you want to transfer funds out of the contract, you need to implement a function to be able to do that.