You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can say this can become an experimental flag to be enabled, but could allow to provide liquidity for swaps sent privately to the daemon or to harvest for pending one in the mempool and Nostr.
Implementation possibilities
Banco Web App
The daemon serves banco web-app which is a trading form behind Tor or with https over clearnet
Nostr
Daemon derives a Nostr keys and announce the trading pairs in the Nostr profile
Daemon publishes a recurrent event with price and limits for each pair. kind TBD
Daemon subscribe to a public kind or read NIP-04 DMs for new trade requests.
he receives an address and the tap-leaf script, if accepted it can be spent even in-confirmed in a fulfill transaction
The fulfill transaction will use Ocean wallet funds to pay for BTC fees and to fund the trade, plus the daemon will add an output to claim the trade contract.
Considerations
Serving the web-app is for sure less time-consuming than implementing Nostr as transport layer
The Banco protocol does not yet fully supports blinding the trader's output.
A proper assessment of how the swap domain has to change or most likely should become a different swap/market type. Moreover better understanding of how this will impact RPC related to market management, feeder, trade history etc..
The text was updated successfully, but these errors were encountered:
https://github.com/vulpemventures/banco
We can say this can become an experimental flag to be enabled, but could allow to provide liquidity for swaps sent privately to the daemon or to harvest for pending one in the mempool and Nostr.
Implementation possibilities
Banco Web App
The daemon serves banco web-app which is a trading form behind Tor or with https over clearnet
Nostr
Daemon derives a Nostr keys and announce the trading pairs in the Nostr profile
Daemon publishes a recurrent event with price and limits for each pair. kind TBD
Daemon subscribe to a public kind or read NIP-04 DMs for new trade requests.
he receives an address and the tap-leaf script, if accepted it can be spent even in-confirmed in a fulfill transaction
The fulfill transaction will use Ocean wallet funds to pay for BTC fees and to fund the trade, plus the daemon will add an output to claim the trade contract.
Considerations
Serving the web-app is for sure less time-consuming than implementing Nostr as transport layer
The Banco protocol does not yet fully supports blinding the trader's output.
A proper assessment of how the swap domain has to change or most likely should become a different swap/market type. Moreover better understanding of how this will impact RPC related to market management, feeder, trade history etc..
The text was updated successfully, but these errors were encountered: