Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing Liquid blinding key and not able to access L-Btc balance #304

Open
farukterzioglu opened this issue Feb 9, 2021 · 1 comment
Open

Comments

@farukterzioglu
Copy link
Contributor

I received a transaction to a confidential address generated via NBXplorer. But that amount isn't reflected to the wallet. Balance didn't change even I can see the transaction in wallet.

When I call elements-cli dumpblindingkey [CONFIDENTIAL_ADDRESS] it returns null, so probably the blinding key wasn't imported at the correct moment (maybe a temporary rpc error)

I resolved it by creating the blinding key of that confidential address and by calling elements-cli importblindingkey [CONFIDENTIAL_ADDRESS] [BLINDING_KEY]

The code I used to create blinding key;

var mainNetworkProvider = new NBXplorerNetworkProvider(NetworkType.Mainnet);
network = mainNetworkProvider.GetFromCryptoCode("LBTC");

var strategy = new DerivationStrategyFactory(network.NBitcoinNetwork).Parse("xpub....");

var blindingKey = NBXplorerNetworkProvider.LiquidNBXplorerNetwork.GenerateBlindingKey(strategy, new KeyPath("0/1")); // for address at 0/1
var hex = blindingKey.ToHex();

I resolved my issue but someone can see this issue and take this as a reference.
Or maybe we can deep dive for the reason and prevent for further occurrences, otherwise this issue can be closed.

@Kukks helped me with this in https://chat.btcpayserver.org/btcpayserver/channels/liquid

@NicolasDorier
Copy link
Member

Yeah that's probably why. We should fix it by trying again if it fails.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants