search

LedgerHQ / lib-ledger-core

MIT License
79 stars 83 forks source link

cannot find LedgerAPI blockexplorer implementation #324

Open rootSig opened 5 years ago

rootSig commented 5 years ago

Hi @EricLarch @btchip @KhalilBellakrid @pollastri-pierre

We are using Ledger's lib-ledger-core and C++ / Qt to build a trustless P2P exchange based on HTLCs with an integrated multi-currency wallet.

Our integration was smooth until we discovered that lib-ledger-core's WalletPool used for creating wallets (BTC, ETH, XRP, XMR) seems to query your server infrastructure, such as eth-mainnet.explorers.dev.aws.ledger.fr.

We can see that WalletPool is using the websocket protocol with Ledger API and references to LedgerApiBitcoinLikeBlockchainObserver & LedgerApiEthereumLikeBlockchainExplorer. Unfortunately, we are unable to find any further references to Ledger API, its source code or live server instances which we can query.

Our goal is to setup a multi-currency wallet utilizing lib-ledger-core. Could you kindly advise us where we could find LedgerApi's block explorer and self-host it? Are there alternatives in case your explorer is closed-sourced?

Btw we also stumbled upon these tasks: https://github.com/LedgerHQ/lib-ledger-core/projects/10#card-13905293, https://github.com/LedgerHQ/lib-ledger-core/projects/10#card-13905295 - do you still plan to work on them, and do you deem them feasible?

In the event that the answer is yes, we can try to work on a PR into lib-ledger-core to communicate with bitcoind/geth nodes directly, eventually getting rid of LedgerAPI's hosted blockexplorer instances, and/or making this approach an alternative to using LedgerAPI servers.

KhalilBellakrid commented 5 years ago

Sorry for the late answer but we've been pretty busy those last days ! We are happy to see that you rely on lib-ledger-core to build your wallet but concerning the explorers they are still close source, we plan in the future to change that of course but I can’t give you an ETA since we have other priorities right now, as Pierre suggested you could implement support for a third party explorer and use it, regarding the websocket it is not mandatory in that case you will have to trigger synchronization from your side (which is kind of flow that Ledger Live is following). If you need more details let's discuss that on the Slack Dev.