If I understand correctly, Flow Port wallet https://port.onflow.org uses for Ledger account creation/discovery the https://hardware-wallet-api-mainnet.onflow.org/ service. However, it seems that this service tracks only addresses created via it.
Therefore wallets other than flow port wanting to create an account for the user's hardware wallet have no choice but to use the same service which goes against the general principle of decentralization.
Ideally, https://hardware-wallet-api-mainnet.onflow.org should be able to provide any existing address for the public key requested, not just the ones created via it, giving other wallets the freedom to create their accounts via any service they want without sacrificing interoperability with flow port.
I'm raising this issue here on @bthaile 's recommendation as this was the closest public repo we found
If I understand correctly, Flow Port wallet https://port.onflow.org uses for Ledger account creation/discovery the https://hardware-wallet-api-mainnet.onflow.org/ service. However, it seems that this service tracks only addresses created via it.
Therefore wallets other than flow port wanting to create an account for the user's hardware wallet have no choice but to use the same service which goes against the general principle of decentralization.
Ideally, https://hardware-wallet-api-mainnet.onflow.org should be able to provide any existing address for the public key requested, not just the ones created via it, giving other wallets the freedom to create their accounts via any service they want without sacrificing interoperability with flow port.
I'm raising this issue here on @bthaile 's recommendation as this was the closest public repo we found