# Segwit Ephemeral Anchors

**URL:** <https://delvingbitcoin.org/t/segwit-ephemeral-anchors/160>\
**Category:** Protocol Design\
**Created:** [November 2, 2023, 5:14pm UTC](https://delvingbitcoin.org/t/segwit-ephemeral-anchors/160 "2023-11-02T17:14:32Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![ajtowns](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/ajtowns/32/417_2.png) [@ajtowns](https://delvingbitcoin.org/u/ajtowns)\
**Post date:** [November 22, 2023, 12:06pm UTC](https://delvingbitcoin.org/t/segwit-ephemeral-anchors/160/11 "2023-11-22T12:06:37Z")

</div>

> [@sjors](#):
>
> What was wrong with a 1 byte push again?

Seems like a good question for [https://bitcoin.stackexchange.com/](https://bitcoin.stackexchange.com/) – I think segwit was originally a single push, where the first byte was the version, and the rest was the program; with that push being between 2 and 41 bytes; now the version and program are separate pushes, but rather than having the program be 1-40, it’s 2-40…

EDIT: [How could a 2 byte witness program make sense? - Bitcoin Stack Exchange](https://bitcoin.stackexchange.com/questions/110660/how-could-a-2-byte-witness-program-make-sense) suggests it’s to avoid ambiguity on how to push one-byte (OP\_1 vs 0101 etc)

---

_[View the full topic](https://delvingbitcoin.org/t/segwit-ephemeral-anchors/160)._