invoices: multi-crypto payment support
One asset per invoice from a registry (lib/crypto_asset.rb): BTC, LTC, ETH, XMR, SOL, ALGO, USDT/USDC on ERC-20/TRC-20/BEP-20/Solana/Algorand. Migration 003 generalizes the ltc_* columns to crypto_* + crypto_coin (existing LTC invoices backfilled). QR payload adapts per asset: BIP21 amount URIs where supported, bare address for tokens with a network hint on the PDF. Default addresses come from the CRYPTO_ADDRESSES secret (JSON code=>address); LTC_ADDRESS still works as legacy.
This commit is contained in:
parent
f9c7001e7a
commit
0fbb6ee809
20 changed files with 410 additions and 143 deletions
|
|
@ -11,6 +11,9 @@ SMTP_PASSWORD=change-me
|
|||
MAIL_FROM="IE Sergei Poljanski Contact Form <me@asxp.io>"
|
||||
MAIL_TO=ie@asxp.io
|
||||
|
||||
# Optional: default Litecoin payout address prefilled into the new-invoice form.
|
||||
# Production sets this from the LTC_ADDRESS Forgejo secret; leave blank locally.
|
||||
# Optional: default crypto payout addresses prefilled into the new-invoice
|
||||
# form. JSON object, CryptoAsset code => address (codes in lib/crypto_asset.rb).
|
||||
# Production sets this from the CRYPTO_ADDRESSES Forgejo secret.
|
||||
# CRYPTO_ADDRESSES={"BTC":"bc1...","USDT-TRC20":"T..."}
|
||||
# Legacy: LTC_ADDRESS still fills the LTC default when set.
|
||||
# LTC_ADDRESS=ltc1...
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue