Next steps

[lvaccaro]

I am brainstorming some ideas about next steps, hoping to build something useful as self-hosted node:

• bitcoin:
  [ ] support passing amount
  [ ] support unused address: track in New unused addresses #7
  [ ] support signed proofs for address or for descriptor
  [ ] add fee estimation
  [ ] notify a user when received a payment (if the server has installed mail server, or something like that)
  [ ] .. I am missing others cool stuff
• html/style:
  [ ] add dark mode
  [ ] add banner text customizable by user: useful to put links
  [ ] add linked received funds to explorer
  [ ] add sharing and copy to clipboard
• others:
  [ ] support lightning
  [ ] support liquid

[notmandatory]

I'd like to add an optional feature to get settings from env variables instead of an .ini file. Similar to the commits I was working on before using struct_opt. I prefer using env variables primarily to make my descriptor more private, but also because it's where heroku recommends putting settings. Or we could possible do both, load what we can from an .ini file and then override with env and command line parameters.

[notmandatory]

A nice to have feature would be to allow person sending btc to add a public and/or private comment with the tip, which would be associated on the server with that bitcoin address.

[thunderbiscuit]

A great use case could be to populate a donation address QR code on repositories' README files. If the readme could somehow query the API to return the latest unused address in the form of an image (or even just text), you'd basically replace the old "static donation address" setup for a dynamically generated one.

[RCasatta]

maybe we can push the bin to crates so that we can cargo install it