I am fascinated by making a swap utility utilizing HTLCs. The consumer connects their pockets to the frontend, locations an order, and the backend matches the order with a maker and creates the HTLC transaction. The consumer’s UTXOs are used as inputs to fund the transaction, and the only non-change output is the one with the HTLC because the unlocking script. The circulate would look much like the one depicted right here:
Nonetheless, I do not need the backend to should do the coin choice and determine which UTXOs are optimum to fund the transaction. From my understanding, usually the walletcreatefundedpsbt RPC technique would try this for you, however on this case the pockets in query is the consumer’s pockets. Is there an equal manner I can do coin choice for another person’s pockets?
I am fascinated by making a swap utility utilizing HTLCs. The consumer connects their pockets to the frontend, locations an order, and the backend matches the order with a maker and creates the HTLC transaction. The consumer’s UTXOs are used as inputs to fund the transaction, and the only non-change output is the one with the HTLC because the unlocking script. The circulate would look much like the one depicted right here:
Nonetheless, I do not need the backend to should do the coin choice and determine which UTXOs are optimum to fund the transaction. From my understanding, usually the walletcreatefundedpsbt RPC technique would try this for you, however on this case the pockets in query is the consumer’s pockets. Is there an equal manner I can do coin choice for another person’s pockets?
