To Share and +4 nLEARNs NEAR Wallet Integration Tests Note: Simulation tests are no longer actively supported. NEAR Simulator was meant to be an in-place replacement of a blockchain environment for the purpose of testing NEAR contracts. However, simulating NEAR ledger turned out to be a much more complex endeavor than was anticipated. Eventually, the …
To Share and +4 nLEARNs NEAR Wallet Unit Tests Testing contract functionality can be done through the cargo test framework. These tests will run with a mocked blockchain and will allow testing function calls directly without having to set up/deploy to a network and sign serialized transactions on this network. A common framework for tests, …
To Share and +4 nLEARNs NEAR Wallet After deploying your contract you might realize that you need to maintain it, either to fix a bug or add new functionality. Let us here guide you on how to deploy, update and finally lock your smart contract, so its code cannot change anymore. Upgrading a Contract If …
To Share and +4 nLEARNs NEAR Wallet DAO-Governed Updates When you first deploy a contract to mainnet, you will likely keep control of a Full Access key for the contract. This puts the contract in "trusted" mode, in which you and other maintainers can change it at-will (which means your users need to trust you …
To Share and +4 nLEARNs NEAR Wallet Upgrading Production Contracts When deploying new code to production contracts, you obviously can’t destroy old account state, as you do during rapid prototyping. So how to you prevent the dreaded error? Cannot deserialize the contract state. You can use a couple different approaches, depending on the complexity of …
To Share and +4 nLEARNs NEAR Wallet Migrating from Simulation Testing to Workspaces Why did we stop supporting Simulation Testing? Simulation tests were not suitable for purpose for a few reasons, namely: near-sdk-sim was hooking into parts of nearcore that were not meant to be released, in the most recent version those crates aren’t released …
