# Process for using AppKeys? **URL:** \ **Category:** End Devices (Nodes)\ **Created:** [August 16, 2018, 1:11am UTC](https://www.thethingsnetwork.org/forum/t/process-for-using-appkeys/16902 "2018-08-16T01:11:53Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![arjanvanb](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/arjanvanb/32/46626_2.png) [@arjanvanb](https://www.thethingsnetwork.org/forum/u/arjanvanb)\ **Post date:** [August 16, 2018, 6:30am UTC](https://www.thethingsnetwork.org/forum/t/process-for-using-appkeys/16902/2 "2018-08-16T06:30:35Z")
> [@nheinrich](#): > > Would it be better to provide what TTN provides me? I don’t think so, as like you wrote TTN allows you to set your own. TTN also allows for adding multiple AppEUIs to a single application in TTN Console; see [Registration of node with pre-configured LoRaWAN keys - #2 by arjanvanb](https://www.thethingsnetwork.org/forum/t/registration-of-node-with-pre-configured-lorawan-keys/8716/2). > [@nheinrich](#): > > convert that string of stuff (what is that format called by the way) into hex? That thing is already hex, as the prefix `0x` indicates that what you see is a hexadecimal presentation of each byte. So, `0x8E, 0x62, 0x9C, 0x1E,...` can probably be written as `0x8E629C1E...` and entered in TTN Console without the `0x` prefix. One caveat: when handling separate bytes, you need to know if it’s [LSB](https://en.wikipedia.org/wiki/Bit_numbering)-first or MSB-first, whereas `0x8E629C1E...` is really just a human-readable number for which LSB and MSB do not really apply. (When using `myVariable[16] = {0x8E, 0x62, 0x9C, 0x1E,..., }` in computer code, you force the computer to use that specific order; when using `myVariable = 0x8E629C1E...` you’re letting the compiler decide whether to use LSB or MSB when storing that human-readable value, if it provides a type that can handle such long values to start with.) --- _[View the full topic](https://www.thethingsnetwork.org/forum/t/process-for-using-appkeys/16902)._