I would like to note that there is a typo in the computation. It should say 
`14,400 blocks x 12second per block = 172800 Seconds`, the suggested numbers in the call are correct though.

> This is a low risk change but high impact gain to be had on reducing friction to issuance. Please consider for fast track.

## Brief
To aid with issuance of IBTC, we should consider changing the issue deadline parameter back to original `24 Hours` value originally intended. 

## Detail
|Value|Current|Proposed|
|---|---|---|
|`issue.issuePeriod`|`14,400`|`7200`|

Currently the block time hovers around 12-13s, however assuming an optimistic 12 seconds:
```
14,400 blocks x 12second per block = 172800 Seconds
172800 seconds = 48 Hours
```
Therefore:
```
7200 block delay = 24 Hours
```

## Explanation
During some of Kintsugi's days there was high BTC network congestion. The deadline is split into issue and redeem, however so only griefing collateral is at stake (which is capped currently at writing at 0.5%) so there is no risk that decreasing this deadline will jeopardise interlay vaults. 

The benefit to be had from decreasing this deadline though, is that  any: unintended, malevolent or trollish issue requests will be rejected by the system quicker and allow for the corresponding vault collateral to be unsealed in half the time.

- The post talks about making it easier and faster to issue IBTC.
- They suggest changing a parameter to its original value of 24 hours.
- Currently, the delay is 14,400 blocks which is around 48 hours.
- Lowering the delay to 7,200 blocks will reduce the time to 24 hours.
- This change will not cause any risk to interlay vaults and will help reject any bad requests faster.

Change Issue deadline to 24hours

Brief

Detail

Explanation