openoms
openoms
In case of autounlock implemented the YG could restart after it was stopped to make a transaction. Would need to record if YG was switched on before in the `joinin.conf`.
Display support is low priority to keep the dependencies and the extra hardware need minimal
Stepd to install an eInk display: https://github.com/openoms/joininbox/blob/master/FAQ.md#using-the-213-waveshare-e-ink-display Joininbox status screen implementation on the RaspiBlitz: https://github.com/rootzoll/raspiblitz/pull/1613 https://twitter.com/openoms/status/1312660940194828288
The other way is to create an encrypted file which is the mounted: https://github.com/JohnTroony/LUKS-OPs The advantage is that it would not need a separate encryped drive, but can be created...
This needs to be a manual guide first. Automating will be the next step.
https://github.com/armbian/build/issues/947 https://carlo-hamalainen.net/2017/03/12/raspbian-with-full-disk-encryption/
an alternative solution which better suits the joininbox environment is scheduling the `torthistx` command. Example of broadcasting a raw transaction with the Blockstream.info API via Tor an hour later: `nohup...
Thanks @nyxnor , this is great. Happy to take it as a PR. The two Tor scripts can be place to `scripts/standalone` so they don't interfere with the scripts on...
@nyxnor just these two simple scripts can be useful, no need to add anything to start.
I think TxCast is still in the experimental phase, good to keep an eye on it, but for now I'd just extend the `torthistx` command with the tor circuit renewal...