My envoy app has stopped connecting to my personal node and appears to not be connected to the Foundation servers either.
I had a recurring receive transaction not come through or update on my envoy app for over 100+ blocks, so I deleted the app and relinked my passport, which updated my utxo set.
It will not let me send any transaction saying “QR code is too big, use SD card” when consolidating utxo’s. I haven’t had any issues for the year I’ve been using passport and envoy until this recent update. All firmware on the passport is updated to 2.3.8 and envoy is on 2.0.1.
Does anyone have insight on how I might be able to regain connectivity?
Hi @ChefBTC thank you for joining our community forum!
It looks like you are describing a couple of different issues in your post. The first one is a connectivity issue, the second one is a PSBT being too big (thank you for confirming version numbers by the way!)
-
Connectivity issue: We have received similar reports of people not being able to connect to their nodes. We just found a bug where some onion SSL connection were attempted with TCP, leading to a failed tor connection. We will release a 2.0.2 with some bugfixes and updated tor repositories, including this one. In the meantime though, would you mind sharing what your setup looks like? Are you connected via tor or clearnet to your node? And when trying to connect to Foundation? If you are connecting via tor, are you using tcp or ssl? Any VPNs active or anything like that? Fee free to send the response via DMs if you don’t want to share any of this on a public forum.
-
Consolidation issue: Unfortunately there is nothing that can be done in this regard, and it is also likely this issue has nothing to do with the updates. This error comes up when you try to consolidate a really, really big PSBT (something in the order of multiple tenths of UTXOs). Trying to show such a big PSBT in a moving QR format would eat all the memory available in Passport, so in order to prevent it from freezing we just prevent the operation. One option would be to try and consolidate the UTXOs in smaller chunks using Envoy - instead of consolidating 40 UTXOs (for example), you could consolidate 10 UTXOs four times, then consolidate those four UTXOs. Another option would be to pair your Passport Core to another wallet like Sparrow wallet, build the 40 UTXO transaction there, save it to a microSD card, then put that into Passport, and ask Passport to “Sign with microSD” instead of “Sign with QR”. Unfortuately Envoy doesn’t support building transactions to a microSD card yet, though it is in our roadmap.
Hope this helps!
Thanks for the quick reply, my set up is using tcp over clearnet. No vpns active, I’m running an electrum server on an umbrel.
As far as the consolidation I tried consolidating just 2 utxos together and still get the same message of the QR code being too large.
Connectivity issue: Are you using a local 192.168.xxx.xxx type, or something like umbrel.local address?
Consolidation: That is indeed strange. What info can you provide without giving away what 2 UTXOs these are? Like:
- What’s the script type? Are they both taproot? segwit? legacy? one of each type?
- Are they outputs to a multisig setup?
- Anything odd you identify about this wallet or these UTXOs in particular? Like, do they have a strange timelock, or maybe they are non-standard, or they have weird info in the segwit area like NFTs, stamps or anything like that?
Thank you!
For the connectivity I’m using local IP address followed by the port number. tcp://192.168.x.xxx:12345
Utxo type: all the UTXOS I have in this wallet are P2WPKH (according to my mempool). None are on a multisig setup
There is no other additional conditions to these UTXOs and everything has been held by the envoy software backed by the passport.
Connectivity: Understood, thank you! We are aware that some users are having trouble with local connections like this one after the last update. We are looking into it, we are planning on releasing one or two more versions with bugfixes in the coming weeks.
UTXO: This is all interesting info, but it is a little baffling, a 2 segwit UTXO transation should not be a problem for Passport. Do you think you could screen record the dynamic QR code that Envoy is generating and Passport needs to scan, and send it to me via DM? The key is understanding why Passport complains, and for that it would be ideal to have access to the QR code it is trying to digest. Sharing this unsigned transaction would mean you let me know which 2 UTXOs you are having the problem with, so if that’s something you are not comfortable with it’s ok, don’t feel any pressure to do it. It would be the fastest way to troubleshoot it, but it is understandable not wanting to share this info for privacy reasons.
So, if you decide you don’t want to share that dynamic QR, the next thing I would suggest you would be to try and Pair your passport to Sparrow (remember there’s no phone app for this wallet, only desktop), and see if you can sign the same transaction from the qr generated by sparrow. Lmk which way you want to tackle this!
Thank you!
1 Like
I will DM you. Thanks for your help
1 Like
Hey Jack, I have a screen recording of the moving QR code but it won’t let me add it to this post. Is there a better place like telegram I can send it?