a bit of a noob question. I'm looking to test a solidity smart contract function without waiting 6 days. It's a feature implemented that will allow me to interact with the contract and be paid X amount only after 6 days. How can test that? TIA
well it really depends on your tool set, if you are using hardhat you can write a test, that way you can easily know if that function work as intended, here to see hardhat testing and here to simulate the pass of the time you only need to know how many blocks are mined in that time to use it
Related
I'm relatively new to solidity development and coding in general, but I'd really like to try and write a program that stakes and un-stakes an NFT after 24 hours.
Some background:
I'm really into the Crypto Unicorns NFT pet collecting game right now, and there's a mini game called the "Dark Forest." The idea behind the Dark Forest mini game is pretty simple: you send your Unicorn NFT into the Dark Forest (by staking the unicorn NFT), and then after 24 hours, your unicorn comes back with items. The only thing is, you have to manually un-stake your unicorn to receive rewards, and then if you wanted to send your unicorn back in the Dark Forest a second time, you would have to do that manually as well.
Is there a way I could automate this process (un-staking, and then re-staking the unicorn NFT after 24 hours) and create some sort of "auto-staker" using solidity? Or would this automation be better handled by some other language like python or java?
Any guidance here would be awesome, as I don't really know where to start. Guidance is especially needed regarding testing the program, since I don't actually own a unicorn NFT. I'm mainly just trying to develop this quality of life program for broader Crypto Unicorns community.
Smart Contracts cant automate other Smart Contracts which is why we need central servers to do it for us.
Solutions
Use OpenZeppelin Defender - Smart Contract Automation UI
Use a node provider and create a script that listens to the stake contracts events to automate the process :>
Here is a blockchain node provider use-case code implementation github :>
https://github.com/DiverseSolutions/NodeProviderExamples
How to securely generate a random number on a smart contract using solidity from Hedera? I've been searching for an answer for a while now and looks like most of them recommend the use of Chainlink VRF?
I'm still new to this but on my limited understanding, nodes on Ethereum can somehow tamper the smart contract states or results. Since Hedera has a governing council nodes that we could somehow trust, maybe a simple generated random number from Solidity can be trusted? Or I'm getting this all wrong since I'm still learning.
Random numbers from smart contract has many use case, if someone from Hedera devs could see this thread please provide an easy solution.
To generate a verifiable random number in a solidity smart contract on Hedera, you'd do the same as you would on Ethereum or any other EVM compatible network. You could use an existing library, like vrf-solidity.
Once you have the solidity file you'd like to use you'd then compile the smart contract, add the file to Hedera, and deploy the smart contract. The steps to do so can be found in the deploy your first smart contract tutorial found on Hedera docs.
Note this HIP which introduces a native transaction type for generating random numbers and which will be available as a precompile for use in smart contracts.
https://hips.hedera.com/hip/hip-351
I'll be frank, I made a stupid mistake. In polygon network I deployed a NFT smart contract. I forgot to add withdraw function in my smart contract. Can we add this function to my smart contract that already deployed.
You can see the smart contract code in here:
https://polygonscan.com/address/0xeCd093eD38449d8d64bb015D97072BdcaA594832#code
Unfortunately, you cannot.
Upgrading smart contracts is not possible on EVM chains unless the contracts were designed for it. You can read more on the topic on Ethereum StackExchange.
I also suggest you test you minimally unit tests contracts before deploying.
Say I have a function in a Solidity smart contract that requires a certain period of time to pass before it will take some action for this example let's say one year and to properly implement a unit test for this function I need to wait one year now obviously that is impractical so my question is: Is there an easy way to manipulate the block.timestamp value inside of the hardhat development network?
For anybody looking back on this, I found the solution on this stack overflow post: https://ethereum.stackexchange.com/questions/86633/time-dependent-tests-with-hardhat
How do you make sure the contracts you defined for your software components using Design by Contract (DbC) are being tested at some point?
Shall I write unit tests for every single contract I define?
One benefit I see in DbC vs. isolated testing of single units is that I'm able to make sure the contract works between real collaborators. But how can I make sure the contracts are being tested before I rollout the software?
One way is to write a program that simulates users of your application, i.e. a bot. Startup your application with contracts enabled and have the bots exercise the app.
You can implement randomized behavior in your bots to have them exercise a larger set of use cases and edge cases.
Personally I often extend bots I write to verify performance to enable the sort of testing you're after.