# Paused contract: burn() behaviour before/after 0.6.0

**URL:** <https://forum.openzeppelin.com/t/paused-contract-burn-behaviour-before-after-0-6-0/2373>\
**Category:** Contracts\
**Created:** [February 26, 2020, 2:00pm UTC](https://forum.openzeppelin.com/t/paused-contract-burn-behaviour-before-after-0-6-0/2373 "2020-02-26T14:00:41Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [February 27, 2020, 8:01am UTC](https://forum.openzeppelin.com/t/paused-contract-burn-behaviour-before-after-0-6-0/2373/2 "2020-02-27T08:01:34Z")

</div>

Hi @jmahhh,

Welcome to the community 👋

Yes, that is how it appears to me.  
In OpenZeppelin Contracts 2.5 burning wasn’t impacted by Pausable, whilst in OpenZeppelin Contracts 3.0 burning is impacted by Pausable.

Is this a problem?

[OpenZeppelin Contracts v2.5](https://forum.openzeppelin.com/t/openzeppelin-contracts-v2-5/2155) (Solidity 0.5)

> <https://github.com/OpenZeppelin/openzeppelin-contracts/blob/release-v2.5.0/contracts/token/ERC20/ERC20Pausable.sol>

[OpenZeppelin Contracts v3.0 beta release](https://forum.openzeppelin.com/t/openzeppelin-contracts-v3-0-beta-release/2256) (Solidity 0.6)

> <https://github.com/OpenZeppelin/openzeppelin-contracts/blob/v3.0.0-beta.0/contracts/token/ERC20/ERC20Pausable.sol#L22>

> <https://github.com/OpenZeppelin/openzeppelin-contracts/blob/v3.0.0-beta.0/contracts/token/ERC20/ERC20.sol#L195>

---

_[View the full topic](https://forum.openzeppelin.com/t/paused-contract-burn-behaviour-before-after-0-6-0/2373)._