<p>Nope. The contents of the script itself are used to actual generate the Policy ID. Once you mint something under that policy ID it's impossible to make a change.</p>

CC BY-SA 4.0
2022-01-19T17:28:25.993Z
2022-01-19T17:28:25.993Z
Tygar Pool
<p>It's possible to create a policy which can no longer be used to mint/burn after a given slot. The following object in a <code>policy.script</code> handles that:</p>
<pre><code>{
      &quot;type&quot;: &quot;before&quot;,
      &quot;slot&quot;: &lt;insert slot here&gt;
}
</code></pre>
<p>What if, however, one does not include this block (no <code>before</code> object in script) but eventually wants to lock the policy to prevent future burning/minting? Is this possible?</p>

<native-assets><policy>
ad-hoc policy lock
# ad-hoc policy lock

(Asked by: username_0 on 2022-01-19)

It's possible to create a policy which can no longer be used to mint/burn after a given slot. The following object in a policy.script handles that:
{
      "type": "before",
      "slot": 
}

What if, however, one does not include this block (no before object in script) but eventually wants to lock the policy to prevent future burning/minting? Is this possible?

**Tags:** native-assets, policy

---

## 1 answers

### Answer by username_1 on 2022-01-19. Score: 1

Nope. The contents of the script itself are used to actual generate the Policy ID. Once you mint something under that policy ID it's impossible to make a change.


---

