# OpenZeppelin Contracts v3.1

**URL:** <https://forum.openzeppelin.com/t/openzeppelin-contracts-v3-1/3159>\
**Category:** Announcements\
**Created:** [June 23, 2020, 7:12pm UTC](https://forum.openzeppelin.com/t/openzeppelin-contracts-v3-1/3159 "2020-06-23T19:12:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nventuro](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/nventuro/32/8_2.png) [@nventuro](https://forum.openzeppelin.com/u/nventuro)\
**Post date:** [June 23, 2020, 7:12pm UTC](https://forum.openzeppelin.com/t/openzeppelin-contracts-v3-1/3159/1 "2020-06-23T19:12:27Z")

</div>

![4cc3a2ecb186c925df99e94f38ec2bee6c073cee](https://us1.discourse-cdn.com/flex022/uploads/zeppelin/original/2X/1/125b7f9f6595c7c1caffb13d8f6f11cd2f5c85f4.png)

We’re excited to announce the **release of OpenZeppelin Contracts v3.1** ✨

This is the first release since [v3.0, our last major release](https://forum.openzeppelin.com/t/openzeppelin-contracts-v3-0/2695). It includes the long-awaited **ERC1155 token** and helpers for **safe calls and downcasts** , as well as a number of minor improvements.

To install this release, run:

```bash
npm install --save-dev @openzeppelin/contracts

```

## ERC1155

This is a new [token standard](https://eips.ethereum.org/EIPS/eip-1155) developed by the gaming industry, focusing on gas efficiency. It’s key difference is that it is a _multi-token_ contract: a single ERC1155 can be used to represent an arbitrary number of tokens, which is very useful in applications that require many tokens by removing the high gas costs associated with deploying them. Check out our new [documentation page](https://docs.openzeppelin.com/contracts/3.x/erc1155) to learn more!.

## More Replacements for `call`

The low-level `call` primitive can be hard to use correctly and is often considered unsafe. With the addition of [`sendValue`](https://docs.openzeppelin.com/contracts/3.x/api/utils#Address-sendValue-address-payable-uint256-) in Contracts and `try-catch` in Solidity, there’s only a few scenarios in which `call` is still needed, the most troublesome one being forwarding calls.

The new [`functionCall`](https://docs.openzeppelin.com/contracts/3.x/api/utils.html#Address-functionCall-address-bytes-) helpers can forward call data to a recipient contract while imitating Solidity’s function call semantics, such as bubbling up revert reasons and rejecting calls to EOAs. We expect the addition of these functions to greatly reduce the need to rely on `call`.

## Using `SafeMath` on Small Signed Integers

We’ve expanded the scope of the [`SafeCast`](https://docs.openzeppelin.com/contracts/3.x/api/utils#SafeCast) library to also include signed integer downcasting, which allows for users that need small types (such as `int8` or `int32`) to perform checked arithmetic on them by using `SafeMath`, and then downcast the result to the intended size.

## What’s Next

Version 3.2 will likely include code for **proxy contracts** , the last big item on [our Q2 2020 Roadmap](https://github.com/OpenZeppelin/openzeppelin-contracts/issues/2207). We’re also already working on [EIP2612 for `permit` approvals in ERC20](https://github.com/ethereum/EIPs/pull/2612) and will include it in a release as soon as the EIP is finalized.

Fixed-point arithmetic was [dropped](https://github.com/OpenZeppelin/openzeppelin-contracts/issues/2265#issuecomment-639835390) after the Solidity team decided to implement native support for it (see [this issue](https://github.com/ethereum/solidity/issues/409) for some recent discussion).

---

<div class="post-metadata">

**Author:** ![abcoathup](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/abcoathup/32/415_2.png) [@abcoathup](https://forum.openzeppelin.com/u/abcoathup)\
**Post date:** [June 25, 2020, 12:36am UTC](https://forum.openzeppelin.com/t/openzeppelin-contracts-v3-1/3159/2 "2020-06-25T00:36:47Z")

</div>

OpenZeppelin Contracts Ethereum Package v3.1 should be released two weeks after OpenZeppelin Contracts v3.1.

---

<div class="post-metadata">

**Author:** ![abcoathup](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/abcoathup/32/415_2.png) [@abcoathup](https://forum.openzeppelin.com/u/abcoathup)\
**Post date:** [August 10, 2020, 4:10am UTC](https://forum.openzeppelin.com/t/openzeppelin-contracts-v3-1/3159/3 "2020-08-10T04:10:56Z")

</div>

Split this topic on August 10, 2020, 4:10am UTC

A post was split to a new topic: [Advantages of the ERC-1155 token versus ERC-721 token](https://forum.openzeppelin.com/t/advantages-of-the-erc-1155-token-versus-erc-721-token/3516)
