Change Details

The second key we need to encode into the QR code for the terminal output is the `ed25519` key / the device id. The way we seem to currently do this is to fetch the content OLM account and parse out the identiy keys (here we want the `ed25519`, not the `curve25519` key). Going to set @varun as blocking since I used his initial script as a starting point here Depends on D9202 Addresses [[ https://linear.app/comm/issue/ENG-4798/retrieve-the-device-id-following-key-generation | ENG-4798 ]]

The second key we need to encode into the QR code for the terminal output is the `ed25519` key / the device id. The way we seem to currently do this is to fetch the content OLM account and parse out the identity keys (here we want the `ed25519`, not the `curve25519` key). Going to set @varun as blocking since I used his initial script as a starting point here Depends on D9202 Addresses [[ https://linear.app/comm/issue/ENG-4798/retrieve-the-device-id-following-key-generation | ENG-4798 ]]

The second key we need to encode into the QR code for the terminal output is the `ed25519` key / the device id. The way we seem to currently do this is to fetch the content OLM account and parse out out the identiyty keys (here we want the `ed25519`, not the `curve25519` key). Going to set @varun as blocking since I used his initial script as a starting point here Depends on D9202 Addresses [[ https://linear.app/comm/issue/ENG-4798/retrieve-the-device-id-following-key-generation | ENG-4798 ]]