Securely Updating SOC functionality OTA


Here we explain how Peering exchange is securing many things in the demo.

  1. Securing connection to a SOC (System On A Chip) remotely
  2. Assigning a TLS1.3 certificate, overlayed on the web side
  3. Using PXC’s secp256k1 to transmit a code change being encapsulated with TLS 1.3
  4. Sending a binary file encrypted with ed25519 and curve 25519 utilising a salt for NIST P-384 to secure the network layer
  5. Updating the SOc and flashing a blue led to confirm code change
  6. Powering up a second ESP32 SOC to allow the first ESP32 SOC to enable Blue Tooth Low Energy to activate
  7. Accessing the second chip from the phone app to receive data from the second SOC
  8. Confirming that the second SOC is activated and had the BLE activated from the first chip which was modified remotely
  9. Flashing the LED by a button the phone to confirm that we have control as a result of the activation over the air
  10. We have proved secure remote access, allowing a SOC to update a second SOC allowing local data to be transmitted to a phone over BLE