# 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:** 27

<div class="post-metadata">

**Author:** ![pavel.kirienko](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/pavel.kirienko/32/9_2.png) [@pavel.kirienko](https://forum.opencyphal.org/u/pavel.kirienko)\
**Post date:** [February 26, 2020, 6:37pm UTC](https://forum.opencyphal.org/t/big-endian-vs-little-endian-in-the-context-of-bit-level-encoding/428/27 "2020-02-26T18:37:07Z")

</div>

_(the conversation was completed at the dev call; the resolution is that we are switching to the CANopen format which means the bit order will be changed and the byte order will remain unchanged; the issue is [tracked in the Specification repository](https://github.com/UAVCAN/specification/issues/70))_

---

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