To-do

Here's a to-do list in no particular order

1. Ask Grok to do a code overview
2. Find out why the BLE connection to the APP needs a wallet pre-load.
3. Figure out how to re-compile the APP. Grok should help.
4. Change the BLE code from using the RF-Star module to using the nRF52840 internal SoftDevice.
5. Alter the APP to accept use of this new connection. The GATT and the service UUIDs are going to change. OR figure out how to spoof the old UUIDs?
6. Add multi-currency. This will entail a bit of abstraction for the paths and PBKDF2 iterations, all the way up to completely different signing schema like Ethereum EVM chains.
7. Clone some blockchain for BitLox use. Vertcoin actually seems a good candidate as the software supposedly can mine on low-end consumer machines. This will make it so can give away some coins with each device so people can play around with them.
8. Related: make sure to include testnets for every coin possible.
9. Find a way to use a connector between BLE and node RPC ports. The end result should be that one could run their own Bitcoin (or other coin) nodes and use that as the blockchain data source.
10. Related: Dockerify the insight-wallet instances so that anyone can spin one up. Obviously this should be public domain with very complete instructions. This would be a compromise between a commercial insight instance and a pure RPC-call data source (as that could be slooooow)
11. In the APP, set up a micropayment system (using crypto itself?) for subscribing to BitLox-run insight instances. This would both support the servers (they ain't free) and give people a choice. Previous owners could be grandfathered in.
12. Find out what the "standard" is for BLE hardware wallet attachments. Write a translation layer or just move to it.
13. New wallet based on newer bitpay code. Will have to graft the hardware BLE code on. But it seems they already have Ledger stubbed out...?
14. Related to 12 - find existing wallets that are hardware signer-friendly (or curious) Stack, metamask, this Haust thing etc.
15. Code the nRF52840 USB to use HID/CDC. This would enable (possibly) to use the older Chrome wallet (only on Chromebook) OR use WebUSB. Frankly, I'm not sure it's worth the bother as I do not think USB is the growth direction for the device. Also, the most I would do to support it would be some kind of pogo-pins. I really do not want to have to have an actual USB port. It's a vector for physical abuse, and is just not really what people want.
16. Now that the hardware seems to be settled (at least the first 5.0 version), we need to whack out a prototype via EasyEDA. Previously I used EAGLE, but after AutoCAD bought them, it went to crap. Fusion360 is a waste of money and overly complicated. The previous boards were laid out in Altium, but I'm just not familiar, and literally nothing is being reused, so why go that way? KiCAD looked cool, but it did not click with me. Plus EasyEDA integrates nicely with JLCPCB.
17. Fix the keypad routine to do multistep. This has to be blindingly fast.
18. Speed up the unicode character drawing. Right now it's on the edge of acceptable (though not nearly as awful as ePaper redraw speeds). Need to implement 3.3 Read Data Bytes at Higher Speed (Read dot matrix data quickly) from GT20L16P1Y_Datasheet_EN.pdf.
19. Implement the more advanced font chip, namely the GT30L24A3W, samples of which have already been obtained. First up implement a breakout board, and if the pins are settled, include it on the prototype board.
20. Attempt to recompile the "old old" BitLox APP. There is no reason it should not work.
21. Rejigger the screen elements positioning.
22. Make the colors selectable via the APP?
23. Check if weird custom fonts/characters could be stored in EEPROM. Weird stuff that no-one has font chips for.
24. Find out availability/thickness/dims for custom Gorilla Glass®.
25. Start working out potential assembly methods. Probable: Sliding whole board+face glass into casing, then end piece levers on with a single screw fastening.
26. Waterproofing / oxidizer proofing the board at the fabricator.
27. Casing materials? Manufacturing method? CNC or die casting? 3D printing?
28. Packaging. Flat-pack is essential. Absolute minimal footprint. Zero included info; maybe a quick intro sheet. NO BATTERIES
29. Put AEM code back in.
30. Walk through ADVANCED and EXPERT setup scenarios.
31. Perhaps also have a QUICK setup mode?
32. Bring free-form message signing back. I mean, there is NO REASON you cannot do this with the address/crypto of your choice.
33. New and radical website. Maybe make it function just like a device?
34. OTA updating. THIS IS THE BIG ONE (next to manufacturability). The device MUST be able to be securely updated from the APP via BLE OTA. Even if it bricks; even if it's been wiped. Plus need a way to do this without wiping the EEPROM. Luckily looks like this is the default behavior.
35. Bitmap display from storage
36. QSPI eeprom.

HOLY HELL this is a long list.

I'll probably think of another half-dozen before I fall asleep tonight. I guess I should actually rearrange these in a ranked or grouped manner.