Build finalizer python script #13

New issue

Open

opened 2026-05-01 13:02:23 +00:00 by NakataModem · 1 comment

NakataModem commented

2026-05-01 13:02:23 +00:00

Owner

Finalizer purpose:

monero > check deposit statuses until it's finalized (just call /check endpoint periodically, maybe once in 5 minutes) -> then - if deposit is completed, just set used monero wallet address to be re-used (is_available to TRUE)
litecoin > check deposit statuses until it's finalized, same as monero, but with one critical difference: if payment is succeeded - DON'T set address available (to be reused).
because address must not be touched until it's output is spent (UTXO consolidated on withdrawal) -> SO re-use logic for successful deposit addresses is in withdrawal module - when user spends coins from these addresses - then it sets is_available to TRUE - because coins are spent from this address - and also keep_track is set to FALSE after output is spent

(btw actually we can track unspent UTXOs by looking at confirmed statuses + is_available - false. ) so actually no need to add keep_track? though it can add explicitness. so better do it.

Finalizer purpose: - monero > check deposit statuses until it's finalized (just call /check endpoint periodically, maybe once in 5 minutes) -> then - if deposit is completed, just set used monero wallet address to be re-used (is_available to TRUE) - litecoin > check deposit statuses until it's finalized, same as monero, but with one critical difference: if payment is succeeded - DON'T set address available (to be reused). because address must not be touched until it's output is spent (UTXO consolidated on withdrawal) -> SO re-use logic for `successful` deposit addresses is in `withdrawal module` - when user spends coins from these addresses - then it sets is_available to TRUE - because coins are spent from this address - and also keep_track is set to FALSE after `output` is spent (btw actually we can track unspent UTXOs by looking at `confirmed` statuses + `is_available` - false. ) so actually no need to add keep_track? though it can add explicitness. so better do it.