That's why I've said "Bitcoin core with -txidex".
Because that was needed to be able to use getrawtransaction for txs outside of the client's wallet.
But I hadn't explained what it does and how it's applied since I thought the first option was enough and will do the same.
Topic: Zap wallet (Read 384 times)
Did you try the seed in electrum now that they support lightening?
I'll give it some thought. I used Zap because it's "out of the box" and doesn't require much in the way of tweaking the back end.
...
I was responding to a suggestion by @nc50lc.
I might see if I can read up on the docs and see if there's anything they can suggest.
Thanks everyone.
Also, I've never been able to get my core to accept the -txindex having put it before, after and also instead of a TX.
I'm not sure what you mean by this? -txindex is a commandline argument used at start-up for bitcoind/Bitcoin Core GUI. You don't pass that to bitcoin-cli or use it in an RPC call.Quote
-txindex Maintain a full transaction index, used by the getrawtransaction rpc call (default: 0)
The "used by the getrawtransaction rpc call" part means that the rpc call is using the transaction index, NOT the argument
The lncli command is to run against your lightening node not through your wallet.
Where is the node that you are connecting to? And is it a standard LND node?
I'm kind of flying blind since I have not used Zap in a while.
Did you try the seed in electrum now that they support lightening?
Sorry I can't help more.
-Dave
Where is the node that you are connecting to? And is it a standard LND node?
I'm kind of flying blind since I have not used Zap in a while.
Did you try the seed in electrum now that they support lightening?
Sorry I can't help more.
-Dave
Can you connect to the LND node that the zap wallet is working with?
You could then use
Make sure you have backed it up fully before doing this.
You might also want to open an issue on github.
Are you using Zap desktop or mobile?
-Dave
You could then use
Code:
lncli abandonchannel
to drop it from pending.Make sure you have backed it up fully before doing this.
You might also want to open an issue on github.
Are you using Zap desktop or mobile?
-Dave
Zap 0.7.2 beta desktop. (presumably the program updates as the toggle is set to yes) There's no text box to give commands, otherwise I would be able to tryout
Code:
lncli abandonchannel
- can't find a config directory or any files in said directory e2e.js / storybook.js etc.Blue wallet rejects the 24 word key, so I'm stumped where to go from here.
Can you connect to the LND node that the zap wallet is working with?
You could then use
Make sure you have backed it up fully before doing this.
You might also want to open an issue on github.
Are you using Zap desktop or mobile?
-Dave
You could then use
Code:
lncli abandonchannel
to drop it from pending.Make sure you have backed it up fully before doing this.
You might also want to open an issue on github.
Are you using Zap desktop or mobile?
-Dave
How long has it been since you sent the original TX?
A while.
Quote
How large a fee was used?
"Slow"
Quote
Odd, that the TX is no longer around unless it was sent a while ago.
Essentially, there's no way to find the RAW information even though I have the TX of the transaction to create a channel.
Quote
Has this setup ever worked in opening a channel before? (If no could be other issues)
Yes, prior to this issue I had over ten channels open.
Quote
You should probably just open another channel at this point.
I thought the same, except that's how I ended up with five channels that are "pending open".
Is there any way I can "zap wallet" in a Zap Wallet?
How do I rebroadcast TX for channel creations? I've got five of them that don't show up on the block-chain.
It would seem too much time has elapsed since the Zap TX occurred:
Code:
{
"result": null,
"error": {
"code": -5,
"message": "No such mempool or blockchain transaction. Use gettransaction for wallet transactions."
},
"id": null
}
"result": null,
"error": {
"code": -5,
"message": "No such mempool or blockchain transaction. Use gettransaction for wallet transactions."
},
"id": null
}
Also, I've never been able to get my core to accept the -txindex having put it before, after and also instead of a TX.
How long has it been since you sent the original TX?
How large a fee was used?
Odd, that the TX is no longer around unless it was sent a while ago.
Has this setup ever worked in opening a channel before? (If no could be other issues)
You should probably just open another channel at this point.
-Dave
It would seem too much time has elapsed since the Zap TX occurred:
Yeah, I figured that it will be the result.I was away when I realized and rushed to delete the post but you have already read it.
Sorry for the trouble.
The only way to re-broadcast them now is to find the RAW transaction through the client,
but since I'm not using ZAP wallet, I can't help any further.
How do I rebroadcast TX for channel creations? I've got five of them that don't show up on the block-chain.
If you have the TXID(s) of the funding transaction(s), you can use https://chainquery.com/bitcoin-cli/getrawtransaction and paste them there,or Bitcoin Core with -txindex to use the same command as the link.
You'll get the RAW transaction (in HEX) that you can use to re-broadcast using various tools like: https://blockstream.info/tx/push.
IDK if it's okay to rebroadcast an "open channel transaction" that wasn't broadcast in the first place though.
It would seem too much time has elapsed since the Zap TX occurred:
Code:
{
"result": null,
"error": {
"code": -5,
"message": "No such mempool or blockchain transaction. Use gettransaction for wallet transactions."
},
"id": null
}
"result": null,
"error": {
"code": -5,
"message": "No such mempool or blockchain transaction. Use gettransaction for wallet transactions."
},
"id": null
}
Also, I've never been able to get my core to accept the -txindex having put it before, after and also instead of a TX.
How do I rebroadcast TX for channel creations? I've got five of them that don't show up on the block-chain.
If you have the TXID(s) of the funding transaction(s), you can use https://chainquery.com/bitcoin-cli/getrawtransaction and paste them there,or Bitcoin Core with -txindex to use the same command as the link.
You'll get the RAW transaction (in HEX) that you can use to re-broadcast using various tools like: https://blockstream.info/tx/push.
IDK if it's okay to rebroadcast an "open channel transaction" that wasn't broadcast in the first place though.
How do I rebroadcast TX for channel creations? I've got five of them that don't show up on the block-chain.
But does your wallet complete/finish the syncing process? And how much time are we talking about here? Since I've been reading a lot of similar cases where they actually take up several hours just to complete the syncing process and after that one long syncing process the next ones became normal after that. Just to be sure you must see if your connection is stable or if the zap wallet is somehow being restricted by your firewall and anti-virus since this are the main culprits of having a restrictive connection on wallets.
This might be totally unrelated to this wallet but I have read about some issues in the past with other software wallets that failed to sync because the time on their PC was out of sync. Compare the time your PC displays with this source for example > https://www.timeanddate.com/time/internettime.html
Update it manually if needed, it shouldn't be out of sync by more than a few seconds max.
Update it manually if needed, it shouldn't be out of sync by more than a few seconds max.
I haven't used my Zap wallet for some time
How long is "some time"? Over a year?According to their GitHub, this was a known issue last year with version 0.2.0, and should have been fixed in an update: https://github.com/LN-Zap/zap-desktop/issues/660
If you upgrade to the latest version and its still not working, it might be an issue on their end, which has happened in the past when their servers have gone down: https://github.com/LN-Zap/zap-desktop/issues/2180
Try to download the latest release. It seems that the syncing process for older versions (especially 0.20) is not that reliable and a bit buggy.
From the picture you posted, it looks like your wallet didn't manage to connect to any peer. If it was syncing then it would show a deposit address and the progress bar!
From the picture you posted, it looks like your wallet didn't manage to connect to any peer. If it was syncing then it would show a deposit address and the progress bar!
I have never used this wallet, but as you've written, it's an obvious problem with sync. What you should do first is check which version you are using, their Android app is updated just a week ago, and I see note that some bugs are fixed. I did not check the dates of other versions, but you can check it here.
The problem may also be that something on your device is blocking synchronization, usually av/firewall settings which may change due to software updates.
The problem may also be that something on your device is blocking synchronization, usually av/firewall settings which may change due to software updates.
I haven't used my Zap wallet for some time, now whenever I try to open it (after typing the password), it's stuck on this page:
I know it's syncing but it usually doesn't take that much time. Anyone else experiencing the same problem?
I know it's syncing but it usually doesn't take that much time. Anyone else experiencing the same problem?
Jump to: