... There is kinda currently no way to pass this data back to Shakedex easily.
The best fix may be actually a change in Shakedex, either adding a custom Context argument for getCoin() or maybe being able to pass a nodeClient object (which could include our API call for getCoin()) as opposed to just passing an IP address + api key.
For now, all attempts to fill an auction with SPV will simply fail. We might want to make it clear in the UI that shakedex + SPV is a bad combo, for now...
The Shakedex swapProof module expects the nodeClient to be able to
getCoin()
: https://github.com/kurumiimari/shakedex/blob/744387a5e6cf2499e4becc78618babc5bf173e5e/src/swapProof.js#L99-L102The nodeClient is part of the shakedex
Context
object which only expects the IP address and API key for the full node's HTTP API: https://github.com/kurumiimari/shakedex/blob/744387a5e6cf2499e4becc78618babc5bf173e5e/src/context.js#L11-L12Even though in SPV mode, Bob is already configured to make
getCoin()
requests from the hosted server...https://github.com/kyokan/bob-wallet/blob/6f3f93bf202740f27cda1b46684d78e94ae68a96/app/background/node/service.js#L491-L496
... There is kinda currently no way to pass this data back to Shakedex easily.
The best fix may be actually a change in Shakedex, either adding a custom Context argument for
getCoin()
or maybe being able to pass anodeClient
object (which could include our API call forgetCoin()
) as opposed to just passing an IP address + api key.For now, all attempts to fill an auction with SPV will simply fail. We might want to make it clear in the UI that shakedex + SPV is a bad combo, for now...