Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add November 2022 Monthly Update #113

Merged
merged 4 commits into from
Nov 30, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
55 changes: 55 additions & 0 deletions docs/monthly-update/2022/11.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,55 @@
---
title: November '22
slug: /monthly-update/2022/11
---

## ink! `v4.0.0-beta` 🦑

We released the ink! [`v4.0.0-beta`](https://github.com/paritytech/ink/releases/tag/v4.0.0-beta) 🎉

The focus of this beta release was to establish the stable ABI for the final `v4.0.0`
release. It means that whilst subsequent `beta` releases may contain breaking contract
*code* changes, the ABI will remain the same so that any contract compiled and deployed
with `v4.0.0-beta` continue to be compatible with all future `v4.0.0` versions.

In order to build contracts which use ink! `v4.0.0-beta` you need to use
`cargo-contract` [`v2.0.0-beta`](https://github.com/paritytech/cargo-contract/releases/tag/v2.0.0-beta).

We also released
[`v0.22.1`](https://github.com/paritytech/substrate-contracts-node/releases/tag/v0.22.1)
of the [`substrate-contracts-node`](https://github.com/paritytech/substrate-contracts-node)., which is compatible with the
`v4.0.0-beta` release.

If you're interested in digging further, check out the relevant `CHANGELOG`s.

## Parity Retreat in Sardinia 🌞

Our team (and Parity as a whole) spent a few days enjoying the warmth and sunshine of
Sardinia.

We talked about the road towards a stable ink! `v4.0` release, improvements to the non-Rust
developer experience, and ways to improve the adoption of ink!. Keep an eye out on the
next few updates to see the fruits of these discussions.

These in-person get togethers are especially valuable bonding experience for a global
team like ours. As of this writing we're spread across eight different countries!

![Sardinia 2022](/img/monthly-update/sardinia-2022.jpg)

## Shilling at Sub0 🗣️

Alex and German had a fireside chat session at [Sub0](https://sub0.polkadot.network/), the Polkadot Developer conference.

We're still waiting for the recoding to be uploaded, and we'll share that link here when
it's available!

![Sub0 Fireside 2022](/img/monthly-update/sub0-fireside-2022.jpg)

## ink! x OpenZeppelin 🔏
The Polkadot council approved a [treasury proposal](https://polkadot.subsquare.io/council/motion/296) funding
[OpenZeppelin](https://www.openzeppelin.com/)'s review and audit of ink! and the Contracts pallet.

The tl;dr here is that OpenZeppelin will be taking a look at ink! as a language and will
give some recommendations for how to make the language safer.

We'll be sharing more about this in the upcoming weeks once the review gets started!
Binary file added static/img/monthly-update/sardinia-2022.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.