Oasis

Oasis Engineering started 2023 with a steady stream of important core protocol upgrades and feature updates. In January, the bulk of items shipped covered runtime features, Core optimizations, validator updates, and more. On top of all that, another month of consistent Mainnet and Testnet stability amidst numerous upgrades, while average daily transactions on Emerald saw a 20% boost!Keep reading for a full synopsis of Oasis Engineering’s progress during January!<h2 id="header-0">‍Wallet Updates</h2>Support for Oasis Sapphire running on Mainnet has been officially added into the <a href="https://github.com/oasisprotocol/oasis-wallet-ext/" rel="noopener noreferrer nofollow">Oasis Wallet — Browser Extension</a>! This feature was incorporated inside the <a href="https://github.com/oasisprotocol/oasis-wallet-ext/releases/tag/v1.9.0" rel="noopener noreferrer nofollow">1.9.0</a> release and is available on the <a href="https://chrome.google.com/webstore/detail/oasis-wallet/ppdadbejkmjnefldpcdjhnkpbjkikoip" rel="noopener noreferrer nofollow">Chrome Web Store</a>.In January, the <a href="https://github.com/oasisprotocol/oasis-wallet-web/" rel="noopener noreferrer nofollow">Oasis Wallet — Web</a> saw several external dependencies bumps and improved tests. In total, <a href="https://github.com/oasisprotocol/oasis-wallet-web/pulls?q&#61;is%3Apr&#43;merged%3A2023-01-01..2023-01-31&#43;" rel="noopener noreferrer nofollow">40 pull requests</a> were merged.A new release process was set up for <a href="https://github.com/oasisprotocol/cli" rel="noopener noreferrer nofollow">Oasis CLI</a>, starting with the <a href="https://github.com/oasisprotocol/cli/releases/tag/v0.1.0" rel="noopener noreferrer nofollow">0.1.0</a> release. Currently, amd64 binaries are provided for Linux and we are planning on adding MacOS builds in the near future.A new notable feature for users is a safety check for target addresses which will prevent users from sending funds to reserved addresses such as native ParaTime addresses, rewards and common pools, fee accumulators and similar (<a href="https://github.com/oasisprotocol/cli/pull/1" rel="noopener noreferrer nofollow">#123</a>). Users can override this check by passing the new — force flag.The new versions (2.5.0&#43;) of the <a href="https://github.com/Zondax/ledger-oasis" rel="noopener noreferrer nofollow">Oasis nano app for Ledger</a> include support for signing ParaTime transactions using the Ledger hardware wallet. Integration into Oasis CLI and other wallets is in progress.<h2 id="header-1">‍Network Updates</h2>Emerald, Sapphire and Cipher ParaTimes were all stable on both Mainnet and Testnet in January. No downtimes or incidents have been reported despite a number of upgrades.Here’s a rundown of what changed with Mainnet and Testnet last month.<h2 id="header-2">‍Mainnet Highlights</h2>The Oasis Core 22.2.x branch was thoroughly tested in December, so, on January 4, the non-breaking update from Oasis Core 22.1.x to Oasis Core 22.2.x branch was proposed on Mainnet. The first 22.2.x version used was <a href="https://github.com/oasisprotocol/oasis-core/releases/tag/v22.2.3" rel="noopener noreferrer nofollow">22.2.3</a> and later two additional maintenance updates were proposed — version <a href="https://github.com/oasisprotocol/oasis-core/releases/tag/v22.2.4" rel="noopener noreferrer nofollow">22.2.4</a> on January 11 and version <a href="https://github.com/oasisprotocol/oasis-core/releases/tag/v22.2.5" rel="noopener noreferrer nofollow">22.2.5</a> on January 23.On January 26, Sapphire <a href="https://github.com/oasisprotocol/sapphire-paratime/releases/tag/v0.3.1" rel="noopener noreferrer nofollow">0.3.1</a> and Cipher <a href="https://github.com/oasisprotocol/cipher-paratime/releases/tag/v2.6.2" rel="noopener noreferrer nofollow">2.6.2</a> non-breaking ParaTime upgrades were proposed on Mainnet.The average number of daily transactions on Emerald has seen a 20% boost in January (15,300 transactions compared to 12,700 in December 2022). The peak of 21,442 transactions on January 14 was also higher from the previous month — 15,929 on December 16, 2022.In the middle of January, Oasis engineering set up monitoring for Sapphire transactions. The average count was 1,125 transactions per day with a peak of 1,160 transactions on January 18.Active Oasis Mainnnet nodes as of January 31, 2023:<ul><li>120 validator nodes</li><li>6 key manager nodes</li><li>28 Cipher ParaTime compute nodes</li><li>52 Emerald ParaTime compute nodes‍</li><li>22 Sapphire ParaTime compute nodes</li></ul><h2 id="header-3">‍Testnet Highlights</h2>On January 10, Emerald 10.0.0-testnet upgrade was proposed. And on January 25, Sapphire 0.3.1-testnet and Cipher 2.6.2-testnet upgrades were proposed.From January onward, Oasis engineering will also report statistics for Emerald running on Testnet for consistency. The average number of daily transactions was 2,953 with the peak of 3,282 transactions on January 16.On January 11, Sapphire running on Testnet had a peak of 3,069 daily transactions, a 46% increase from 2,096 transactions in December 2022. Similarly, the average number of transactions increased to 2,880, up from 1,067 in December 2022.Active Oasis Testnet nodes as of January 31, 2023:<ul><li>44 validator nodes</li><li>5 key manager nodes</li><li>14 Cipher ParaTime compute nodes</li><li>32 Emerald ParaTime compute nodes‍</li><li>18 Sapphire ParaTime compute nodes</li></ul><h2 id="header-4">‍Developer Platform and ParaTime Updates</h2>In January, the <a href="https://github.com/oasisprotocol/oasis-sdk" rel="noopener noreferrer nofollow">Oasis SDK</a> repository mostly saw version bumps and polishes regarding EVM and migrated Oasis CLI. <a href="https://github.com/oasisprotocol/oasis-indexer/pulls?q&#61;is%3Apr&#43;merged%3A2023-01-01..2023-01-31&#43;" rel="noopener noreferrer nofollow">27 pull requests</a> were merged in total.On the Sapphire front, solidity precompiles for generating a keypair and signing a message using native ed25519, secp256k1 and sr25519 schemes have been added (<a href="https://github.com/oasisprotocol/sapphire-paratime/pull/80" rel="noopener noreferrer nofollow">#80</a>). The &#64;oasisprotocol/sapphire-paratime and &#64;oasisprotocol/sapphire-hardhat wrappers got a fix for intermittent errors when doing smart contract calls (<a href="https://github.com/oasisprotocol/sapphire-paratime/pull/95" rel="noopener noreferrer nofollow">#95</a>, <a href="https://github.com/oasisprotocol/sapphire-paratime/pull/101" rel="noopener noreferrer nofollow">#101</a>).Sapphire Mainnet’s endpoint is also now officially supported (<a href="https://github.com/oasisprotocol/sapphire-paratime/pull/103" rel="noopener noreferrer nofollow">#103</a>). The Metamask wrapper can now also cache signed queries for the 1st time until the browser session expires (<a href="https://github.com/oasisprotocol/sapphire-paratime/pull/100" rel="noopener noreferrer nofollow">#100</a>). This gets rid of the annoying popups each time the confidential query needs to be submitted. A total of <a href="https://github.com/oasisprotocol/sapphire-paratime/pulls?q&#61;is%3Apr&#43;merged%3A2023-01-01..2023-01-31&#43;" rel="noopener noreferrer nofollow">8 pull requests</a> were merged into the <a href="https://github.com/oasisprotocol/sapphire-paratime/" rel="noopener noreferrer nofollow">Sapphire</a> repository.All three official Oasis ParaTimes saw new maintenance releases in January. They are built on top of the new Oasis SDK version and the Oasis Core 22.2.x branch:<ul><li>Sapphire <a href="https://github.com/oasisprotocol/sapphire-paratime/releases/tag/v0.3.1-testnet" rel="noopener noreferrer nofollow">0.3.1-testnet</a> and <a href="https://github.com/oasisprotocol/sapphire-paratime/releases/tag/v0.3.1" rel="noopener noreferrer nofollow">0.3.1</a>,</li><li>Emerald <a href="https://github.com/oasisprotocol/emerald-paratime/releases/tag/v10.0.0-testnet" rel="noopener noreferrer nofollow">10.0.0-testnet</a>,</li><li>Cipher <a href="https://github.com/oasisprotocol/cipher-paratime/releases/tag/v2.6.2-testnet" rel="noopener noreferrer nofollow">2.6.2-testnet</a> and <a href="https://github.com/oasisprotocol/cipher-paratime/releases/tag/v2.6.2" rel="noopener noreferrer nofollow">2.6.2</a>.</li></ul>The <a href="https://github.com/oasisprotocol/oasis-web3-gateway/" rel="noopener noreferrer nofollow">Oasis Web3 Gateway</a> saw a number of version bumps, but no releases have been made. The dApp developers will be happy to know that a new oasisprotocol/sapphire-dev Docker image is in the final development phase which will enable localnet development and testing of Sapphire dApps. Stay tuned for the deployment in February!Work on <a href="https://github.com/oasisprotocol/oasis-indexer" rel="noopener noreferrer nofollow">Oasis Indexer</a> and <a href="https://github.com/oasisprotocol/explorer" rel="noopener noreferrer nofollow">Oasis Explorer</a> continued at a rapid pace. The indexer saw three new releases in January (<a href="https://github.com/oasisprotocol/oasis-indexer/releases/tag/v0.0.6" rel="noopener noreferrer nofollow">0.0.6</a>, <a href="https://github.com/oasisprotocol/oasis-indexer/releases/tag/v0.0.7" rel="noopener noreferrer nofollow">0.0.7</a>, <a href="https://github.com/oasisprotocol/oasis-indexer/releases/tag/v0.0.8" rel="noopener noreferrer nofollow">0.0.8</a>). It now supports account-related queries, which makes it suitable for typical wallet apps queries (<a href="https://github.com/oasisprotocol/oasis-indexer/pull/277" rel="noopener noreferrer nofollow">#277</a>). CORS support (<a href="https://github.com/oasisprotocol/oasis-indexer/pull/290" rel="noopener noreferrer nofollow">#290</a>) and transactions statistics have been added (<a href="https://github.com/oasisprotocol/oasis-indexer/pull/294" rel="noopener noreferrer nofollow">#294</a>). Adding full OpenAPI specs for the Indexer in December enabled Explorer to have a complete Golang code for endpoints now generated from the OpenAPI specs. In January, <a href="https://github.com/oasisprotocol/oasis-indexer/pulls?q&#61;is%3Apr&#43;merged%3A2023-01-01..2023-01-31&#43;" rel="noopener noreferrer nofollow">27 pull requests</a> were merged into Oasis Indexer and <a href="https://github.com/oasisprotocol/explorer/pulls?q&#61;is%3Apr&#43;merged%3A2023-01-01..2023-01-31&#43;" rel="noopener noreferrer nofollow">54 pull requests</a> were merged into the Oasis Explorer codebase.Minor updates were performed on the <a href="https://docs.oasis.io/" rel="noopener noreferrer nofollow">Oasis Docs</a>. Node operators who did not previously configure a trusted execution environment will be happy to see a new table showing <a href="https://docs.oasis.io/node/run-your-node/prerequisites/set-up-trusted-execution-environment-tee/#bios-configuration" rel="noopener noreferrer nofollow">exact BIOS settings</a> required to configure SGX on Intel CPUs. Helper buttons to add <a href="https://docs.oasis.io/dapp/sapphire/#web3-gateway" rel="noopener noreferrer nofollow">Sapphire</a> and <a href="https://docs.oasis.io/dapp/emerald/#web3-gateway" rel="noopener noreferrer nofollow">Emerald</a> Web3 endpoints to your Metamask wallet now warn you if Metamask is not detected (<a href="https://github.com/oasisprotocol/docs/pull/346" rel="noopener noreferrer nofollow">#346</a>) — previously, it just failed silently. Other updates were related to the new Oasis Core and ParaTime releases. A total of <a href="https://github.com/oasisprotocol/docs/pulls?q&#61;is%3Apr&#43;merged%3A2023-01-01..2023-01-31" rel="noopener noreferrer nofollow">10 pull requests</a> have been merged.<h2 id="header-5">‍Oasis Core Updates</h2>Two non-breaking maintenance updates for <a href="https://github.com/oasisprotocol/oasis-core/" rel="noopener noreferrer nofollow">Oasis Core</a> have been released in January: <a href="https://github.com/oasisprotocol/oasis-core/blob/v22.2.4/CHANGELOG.md" rel="noopener noreferrer nofollow">22.2.4</a> and <a href="https://github.com/oasisprotocol/oasis-core/blob/v22.2.5/CHANGELOG.md" rel="noopener noreferrer nofollow">22.2.5</a>.<ul><li>The first one introduced a fix to intermittent errors in confidential queries (<a href="https://github.com/oasisprotocol/oasis-core/issues/5123" rel="noopener noreferrer nofollow">#5123</a>), more strictness in runtime-host protocol message passing (<a href="https://github.com/oasisprotocol/oasis-core/issues/5094" rel="noopener noreferrer nofollow">#5094</a>) and wrong key-manager policy interpretation on restarts (<a href="https://github.com/oasisprotocol/oasis-core/issues/5092" rel="noopener noreferrer nofollow">#5092</a>).</li><li>The second maintenance update brought better memory management when there is a larger number of validators, compatibility fixes with the new light client which will be introduced in 23.0 (<a href="https://github.com/oasisprotocol/oasis-core/pull/5151" rel="noopener noreferrer nofollow">#5151</a>) and the new Runtime Encryption Key registry field (<a href="https://github.com/oasisprotocol/oasis-core/pull/5137" rel="noopener noreferrer nofollow">#5137</a>).</li></ul>The new versions are already deployed on <a href="https://docs.oasis.io/node/testnet/" rel="noopener noreferrer nofollow">Testnet</a>. Users are encouraged to update their nodes. The upgrade proposal on <a href="https://docs.oasis.io/node/testnet/" rel="noopener noreferrer nofollow">Mainnet</a> will follow if no major issues are found in the upcoming weeks.Besides the maintenance fixes mentioned above, a number of notable new features and bug fixes were merged into the master branch that will land in the 23.0 release:<ul><li>Support for Provisioning Certification Service v4 and a subset of <a href="https://www.intel.com/content/www/us/en/developer/articles/technical/intel-trust-domain-extensions.html" rel="noopener noreferrer nofollow">Intel Trusted Domain Extension</a> was merged (<a href="https://github.com/oasisprotocol/oasis-core/pull/5108" rel="noopener noreferrer nofollow">#5108</a>).</li><li>Minimum commission rate for validators can now be defined to avoid potentially unhealthy competition (<a href="https://github.com/oasisprotocol/oasis-core/pull/5102" rel="noopener noreferrer nofollow">#5102</a>). Currently it will remain 0 on the Mainnet but this allows for changing it in the future.</li><li>Public ParaTime keys can now be fetched using an insecure RPC channel (<a href="https://github.com/oasisprotocol/oasis-core/pull/5101" rel="noopener noreferrer nofollow">#5101</a>). This makes public keys cacheable and reduces denial of service attack surface on key managers.</li><li>Oasis node now keeps a blacklist of specific EPID GIDs in case of a compromise (<a href="https://github.com/oasisprotocol/oasis-core/pull/5113" rel="noopener noreferrer nofollow">#5113</a>).</li><li>The entity which owns and stakes a ParaTime can now be changed after it has already been registered (<a href="https://github.com/oasisprotocol/oasis-core/pull/5114" rel="noopener noreferrer nofollow">#5114</a>).</li><li>The public part of the new Runtime Encryption Key is now stored in the registry and can be used by the enclave directly to store and access encrypted data on-chain (<a href="https://github.com/oasisprotocol/oasis-core/pull/5125" rel="noopener noreferrer nofollow">#5125</a>, <a href="https://github.com/oasisprotocol/oasis-core/pull/5140" rel="noopener noreferrer nofollow">#5140</a>).</li><li>A fix for broken block verification between two trusted heights was contributed to the upstream <a href="https://github.com/informalsystems/tendermint-rs" rel="noopener noreferrer nofollow">tendermint-rs repository</a>. Oasis Core was updated to use the fixed version (<a href="https://github.com/oasisprotocol/oasis-core/pull/5134" rel="noopener noreferrer nofollow">#5134</a>).</li></ul>Check out all <a href="https://github.com/oasisprotocol/oasis-core/pulls?q&#61;is%3Apr&#43;merged%3A2023-01-01..2023-01-31&#43;" rel="noopener noreferrer nofollow">31 pull requests</a> merged in January, to see a complete list of changes.And that’s a wrap on January!Oasis Engineering is already excited to share more updates at the end of February. Until then, chat more with the Oasis team by joining us on<a href="https://discord.gg/oasisprotocol" rel="noopener noreferrer nofollow"> Discord</a> or on our<a href="https://forum.oasis.io/" rel="noopener noreferrer nofollow"> Forum</a>! And be sure to check out the newly released Oasis 2023 roadmap <a href="https://oasisprotocol.org/blog/the-oasis-2023-roadmap" rel="noopener noreferrer nofollow">here</a>.

Oasis January 2023 Engineering Update

Table of Contents

Oasis Network

Další články publikované 16. 2. 2023

Today in Crypto: 24% of New Tokens in 2022 Similar to Pump-and-Dump Schemes, Mercuryo & ConsenSys...

Unleash Your Development Potential with 5ire: Join the #BuildToEarn Campaign and Get Rewarded for...

Abu Dhabi Goes All-In on Crypto With $2 Billion Investment Program for Web3 and Blockchain Startups

“Super Start” IEO Raises 557% More Than Expected in Second Round

Crypto News of the Day: Mango Markets exploiter seeks to keep ‘bug bounty’, Blur advises NFT crea...

Not SEC But Congress Will Decide Crypto Regulation: Blockchain Association

Join our free newsletter for daily crypto updates!