<p>With segwit outputs, yes. Segwit outputs do not have a witness that could get discounted.</p>
<p>With segwit inputs, in theory possibly, but in practice no. Every standard segwit input today has a non-empty witness, and thus will get a discount.</p>

CC BY-SA 4.0
2021-11-25T17:19:31.237Z
2021-11-25T17:19:31.237Z
Pieter Wuille
<p>I'm aware that for non-segwit transactions, <a href="https://bitcoin.stackexchange.com/a/89387/127763"><code>vsize</code> is always the same as <code>size</code></a>. But is it possible for a valid transaction to include <code>size</code>=<code>vsize</code> when involving segwit inputs/outputs?</p>
<p>This particular query is motivated by a need to debug an 'invalid signature' error associated with a raw transaction.</p>

<segregated-witness><transaction-weight><block-weight>
Is it possible for the `size` and `vsize` to be the same for a valid segwit (bech32) transaction?
satirn
# Is it possible for the `size` and `vsize` to be the same for a valid segwit (bech32) transaction?

(Asked by: username_0 on 2021-11-25)

I'm aware that for non-segwit transactions, [`vsize` is always the same as `size`](https://bitcoin.stackexchange.com/a/89387/127763). But is it possible for a valid transaction to include `size`=`vsize` when involving segwit inputs/outputs?

This particular query is motivated by a need to debug an 'invalid signature' error associated with a raw transaction.

**Tags:** segregated-witness, transaction-weight, block-weight


---

## 1 answers

### Answer by username_1 on 2021-11-25. Score: 5 | Accepted answer

With segwit outputs, yes. Segwit outputs do not have a witness that could get discounted.

With segwit inputs, in theory possibly, but in practice no. Every standard segwit input today has a non-empty witness, and thus will get a discount.


---

