1
0
mirror of https://github.com/CovidBraceletPrj/CovidBracelet.git synced 2024-11-13 23:18:51 +01:00
CovidBracelet/README.md

53 lines
2.2 KiB
Markdown
Raw Normal View History

2020-06-10 16:38:30 +02:00
# Covid Bracelet, compatabile to iOS and Adroid
2020-06-10 16:38:30 +02:00
**Contributions Welcome!**
## Features
2020-06-10 16:38:30 +02:00
* Sends and receives exposure beacons as specified by Google and Apple for Covid Contact Tracing
2020-06-08 11:45:02 +02:00
* Rolling, encrypted, anonymous beacons
* Compatible with Apple iOS and Android phones
2020-06-10 16:38:30 +02:00
* With rolling proximity identifiers and encrypted metadata
* Proximity identifiers and BLE addresses change every 10 minutes
* Stores own keys for 14 days
* Stores contacts of more than 5 minute duration
* Upon infection upload keys to a public database
* Retrieve keys of infections from database
2020-06-08 11:45:02 +02:00
* computes rolling proximity identifiers
* compares to stored contacts to check for exposure
2020-06-10 16:38:59 +02:00
Builds on on Zephyr OS and NRF52 BLE SOCs. Note: as we do not use the flash for key storage, this only works on nrf52480 or you can just store a very small number of keys
2020-06-10 16:38:30 +02:00
## Get Started:
We use Zepyhr master as we need a newer mbed TLS as the ones that ships with Zephyr 2.2. We are waiting for the Zepyhr 2.3 release. To build, please install Zephyr and compile via west. Note that Platform.io does not support Zephyr 2.3 rc / Zepyhr master at the current time.
2020-06-08 11:16:05 +02:00
**Note: this is a proof of concept and not ready for production**
2020-06-09 23:06:21 +02:00
## Demo Video
[![Video Demo](https://img.youtube.com/vi/tYGsFJC3LtE/0.jpg)](https://youtu.be/tYGsFJC3LtE)
## Open / Possible next steps
* extensive compatibility testing with Apple iOS and Android devices
* contininous integration testing
* set device name in Flash
* fix entropy: keys are always the same on boot up
* set scanning interval to the correct value, for now we just use the default
* set advertisement interval, correct value, for now we just use the default: should be 200-270 milliseconds
* store long-term contacts in flash
* Energy efficiency
* BLE advertisements sets
2020-06-09 14:59:42 +02:00
* Secure GATT services
* More platforms / OS?
* time sync
* firmware of the air updates (signed)
2020-06-08 11:17:03 +02:00
## TODOs Wristband
Possible platforms for real-world deployment many, as many of the cheap fitness trackers base on NRF52 or chips with similar capabilities.
However, many would need the firmware to be shipped to manufactures.
* Watch UI
* Pine Time could be good for testing
2020-06-08 11:17:03 +02:00
## TODOs App and Basestation
* extend this beyond the simple basestation
* read keys form national databases