The core team has released the latest version of Console 2.2.8 to production. Changes include merging the code for XOR filter fee reduction, however it has not been activated as the vote is still ongoing. For more information check the HIP.
In addition, the ability for the backend to detect “bad actors” (Hotspots that don’t send packets) was included and the team improved usability for the Console Export feature, and added a memo field for Data Credit receipts.
Full list of this sprint’s implemented features and fixes:
(Note: a closed issue does not mean the team took action, for example the issue could have been a duplicate or no longer relevant).
Open source users
Check the readme for instructions on how to use prebuilt Console images.
New open source users should follow Option 1 listed in the readme and use
docker-compose-quay.yamlas the template for their docker-compose file.
Existing open source users can update their existing docker-compose file and replace the lines for just the "console" section with the updated lines in the latest
docker-compose-quay.yamlfile. If something does not work, simply revert your changes back to the
docker-compose-quay.yamlfile an issue here.
Database migrations will still happen automatically when using the hosted Console image.
Additional technical documentation.
The team’s focus in the coming weeks (usual disclaimers apply):
- Scaling out roaming services
- LoRaWAN roaming protocol support
- Preferred Hotspot
- LoRaWAN library
- Rx delay enhancement