# Big-endian vs. little-endian in the context of bit-level encoding

**URL:** <https://forum.opencyphal.org/t/big-endian-vs-little-endian-in-the-context-of-bit-level-encoding/428>\
**Category:** Development & Maintenance\
**Created:** [April 6, 2019, 2:29am UTC](https://forum.opencyphal.org/t/big-endian-vs-little-endian-in-the-context-of-bit-level-encoding/428 "2019-04-06T02:29:23Z")\
**Posts on this page:** 1\
**Showing post:** 28

<div class="post-metadata">

**Author:** ![polaris](https://forum.opencyphal.org/letter_avatar_proxy/v4/letter/p/7ab992/32.png) [@polaris](https://forum.opencyphal.org/u/polaris)\
**Post date:** [July 22, 2020, 9:38am UTC](https://forum.opencyphal.org/t/big-endian-vs-little-endian-in-the-context-of-bit-level-encoding/428/28 "2020-07-22T09:38:40Z")

</div>

Hello, what is the result of the discussion? I see, that the last spec (Revision 2020-07-14, page 28) is saying the byte/bit order is LSB/MSb, but the Guide ([The UAVCAN Guide](https://forum.opencyphal.org/t/the-uavcan-guide/778)) claims it must be a difference between UAVCAN v.0 and UAVCAN v.1:  
**The byte order is kept little-endian but the bits are now populated LSB-to-MSB, not the other way around**  
And UAVCAN v.0 has the same LSB/MSb order.  
How should I interpret this info?

---

_[View the full topic](https://forum.opencyphal.org/t/big-endian-vs-little-endian-in-the-context-of-bit-level-encoding/428)._
