Skip to content

Release Notes

Note: We expect to issue one major upgrade of the Oasis Devnet per quarter. In addition to new features and experiences, some of these upgrades may require us to reset the Devnet's state. We will be sure to provide you with ample time and instructions to ensure this affects your own work on the Devnet as little as possible.

Q1 2019 Devnet Upgrade (2/21/19)

  1. New: Contract auto-expiration: Store data however long (or short) you want. Storing data on a blockchain network can be expensive—especially when you’re using large datasets for a limited amount of time (think: ML training sets). As data lovers ourselves, we feel you! That’s why we’ve added auto-expiration, a feature that lets you set time limits for how long contracts and their associated data are stored on the network. Pay less for gas on the network, and spend more on the data you actually need.

  2. New: Oasis Storage API for Rust smart contracts. We also have an all-new Oasis Storage API designed to make storing data easier for smart contracts developed in Rust. This API allows you to create and use large byte arrays for greater flexibility when storing and retrieving data. We will continue to support previous storage APIs as well.

  3. State Wipe to Enable Devnet Upgrade: In order to enable our new Storage API we conducted a state wipe of the Oasis Devnet on Thursday, February 21 at 8:00 am PT. As a part of this upgrade we cleared all data stored on the Devnet. Your account will need to be funded and all relevant contracts will need to be re-deployed. See below for specific instructions.

Migration instructions

  • All users will need to reset their wallet and request new funds from the faucet.

    • For MetaMask, see here for instructions
    • For Truffle, run truffle migrate --reset
  • Developers will need to upgrade all Oasis-related dependencies in their projects:

  • Developers should download the latest version of Contract Kit:

    docker pull oasislabs/contract-kit

  • Developers using an earlier version of web3c.js must replace all uses of web3c.confidential with web3c.oasis. (We have renamed the namespace in the library. web3c.eth remains the same for backwards-compatibility.)