 Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
> Are you the same guy? Yes  > That's too bad. I know that whatever they are building is unofficial, but it would still be cool to see a privacy coin like Monero working within an airgapped solution like that of the Passport hardware wallet. Agreed, we'd love to see this and are working to make things like this drastically easier on a future product. > I hoped it would be Ben Sessions. A pretty popular channel when it comes to these types of software/hardware wallet reviews. But I have come across the work of Crypto Guide as well. Decent lad. He did a review when we first launched Passport Batch 2, but unfortunately there was a bit of a strange focus on common FUD rather than a product review. Would love to see him re-review it with all the changes that have happened to Passport and Envoy since then! |
|
|
|
Would be nice to have in the future releases the notification of new version at entering Envoy. I have updated mine (1.6.0 on Android) only after reading your message. Keep refining this magic app for Passport, the hardware wallet we are fond of. Already a work in progress  Was browsing around Zeus[1] Telegram group when found out a (not expected) reference to Foundation Passport in their recent alpha build (only available to sponsors): ZEUS v0.9.0-alpha1 is now rolling out to community sponsors!
This build includes:
- Watch-only account import (xpub)
- Hardware wallet / signing device support (Coldcard Q, Seedsigner, Passport Foundation etc.)
- Batch channel opens
- Batch on-chain txs
- Close channels to external addresses
- Improved payment path view
(...)
Zeus looks like a solid wallet and knowing that Passport is intended to be integrated with it just adds more options to their users (especially considering that Zeus is a Bitcoin Lighthing wallet),
[1] https://zeusln.com/Good find! We are very excited for this, and it's much more novel than "just" Passport integration into another wallet. Exciting things for those who seek to use LN in a self-sovereign way. I just came across a video of your marketing head talking with the Bitfinex team, and I heard some interesting things I wanted to mention them and ask you about it. - He was pretty secretive but said that Foundation is working on multiple new hardware devices, with plans to release them this year. Can you say something more, exclusively for the Bitcointalk community? We already know there won't be a pre-sale stage.
- How is the development going with Lightning being added to Envoy? When do you expect that to be finished, and have you thought about liquid BTC, for example?
- How far ahead is the Monero community with introducing their forked version of the Passport firmware to support the coin?
- He was pretty secretive but said that Foundation is working on multiple new hardware devices, with plans to release them this year. Can you say something more, exclusively for the Bitcointalk community? We already know there won't be a pre-sale stage.
So sorry, we like to play things pretty close to the vest and don't want to give away too much! Suffice it to say we're going to break this space open with something new in two directions  - How is the development going with Lightning being added to Envoy? When do you expect that to be finished, and have you thought about liquid BTC, for example?
Still a work in progress, but we have concrete plans of how we will tackle it from both an architecture and UX perspective and are working hard towards those goals. We won't release anything half-baked, and want to ensure that the integration is as seamless and intuitive as Lightning can be. - How far ahead is the Monero community with introducing their forked version of the Passport firmware to support the coin?
Unfortunately it seems that the effort has mostly stalled, but we're in communication with some Monero devs and trying to see how we can assist. |
|
|
|
Miniscript adoption is definitely something we're keeping a close eye on, and something we want to implement down the line but is quite complex to do it properly, especially from a UX perspective. Definitely on our radar but no firm implementation date to share at this point! |
|
|
|
@foundationdvcs : It has been a while so I wonder - Any plans on creating a European hub of Foundation to sell your current hardware offering (and perhaps setup shop for the future devices?). Probably this isn't on the list as a big priority considering the amount of resellers that you have but perhaps long term could be something that it could be interesting to explore?
We have definitely explored this in the past, but as @Pmalek mentioned it wouldn't reduce costs very much. We do have a European distributor who imports in bulk and supplies smaller resellers to bring down costs as much as we can, but international customs are still just insane. We have, however, been able to greatly reduce our shipping rates internationally recently so we can at least take some cost off for the end-user there. |
|
|
|
According to what was declared in this official video-guide Passport is capable to generate 20 child seeds, thus your willingness to have "child seed #105" would be a zeal, nothing more. Is any sense to start with #105 but not #0. BTW, when generating child-seeds Passport offers to give it a key-number (proposing "0"). I think that "0" is relevant to BIP85 child-key index. Probably it can start from not "0" index, but I'm not sure about this and reluctant to test this as generated child-keys can't be deleted and Passport advises to generate them wisely. Gotcha. That means they're not really doing BIP85. They're doing a limited version where you're locked into only using the first 20 index numbers, and I'm guessing they do some nonsense where they automatically choose which index number to give you. Sheesh. That's so stupid. The proper implementation should be: Choose an index number & choose a child seed length. That way, years from now if you lose a key & need to get it back, you just go back to the parent seed plus the index number without ever having to think about how the hardware wallet you set it up with worked. My BIP85 child seeds can be regenerated by any wallet that does BIP85 correctly. Enter the index number and choose the child seed length. We absolutely do implement BIP 85 correctly, and allow you to create a child key at any index. We intentionally start at index #0 to ensure that users who don't have complex requirements could easily find their child keys in the future if they didn't note them down somewhere by just starting at index #0 and iterating through them until they find the right one. Hopefully users would note down their index #s or use encrypted MicroSD backups to prevent needing to do that, though! Absolutely! We put a lot of time and thought into our implementation of BIP 85 called "Key Manager." We wrote a blog post detailing how exactly it works when we released the feature a few months back: All your wallets, one backup | Foundation.xyzIf you have any questions out of that I'm more than happy to help. That page DOESN'T show the steps. It just gives an overview, which is why I asked the question here: Walk me through the steps. Let's say I want to get a QR code for a 24 word child seed for BIP85 index number 105. What are the steps? I'm not going to spend over a hundred bucks on a device only to find out it's a ton of clicks & isn't more convenient than using a Blockstream Jade, which does the job though inconveniently (click click click, step step step, click click click). It does show the exact steps in both text and a GIF, but I'll detail them here for you as well Creating a new child key is as easy as New Key > 12/24/Nostr > Choose index (defaults to starting at #0, can be set to anything you'd like) > Set name > Done. If you want to then view the QR you simply select the key from the list in Key Manager > Export > Select Format (Words/Compact SeedQR/SeedQR/MicroSD) > Done. Just to be sure I explicitly setup a key at #105 to test this with no issues   Click me for GIF!All of this is 100% to BIP 85 spec, and if you have a specific need for abnormally high index #s you can do that, or if you have a need for an abnormally high number of keys you can do that (you can create 20 keys per master private key, so applying a passphrase allows for 20 more child keys). If you have any more questions I'm happy to help Meuserna, but let's please keep the tone civil and be kind to all of those in here trying to help answer your questions! |
|
|
|
Can anybody walk me through Foundation Passport's implementation of BIP85?
I want a hardware wallet that lets me load a QR with my parent seed and enter an index number & child seed length (12 or 24 words) to receive the child seed QR. Can Passport do that?
For example, let's say I need to generate a new 24 word seed for a hot wallet.
I want to be able to scan my parent seed's QR code and then choose which BIP85 index number I want to use as the child seed. Let's say I want child seed #105.
I want the device to give me a QR code for that child seed without making me jump through a ton of steps (write these words down, then write these words down, and these and these and these and confirm and confirm and and and...) Good grief. The parent seed IS the backup and I've already confirmed I have that by loading it!
...anyway... I'm trying to find a hardware wallet that makes BIP85 easy. Blockstream Jade and ColdCard do BIP85, but they make it cumbersome to use (though in fairness, I haven't seen how the ColdCard Q does BIP85 yet, but I'm not a fan of ColdCard's clunky UI. I prefer a stateless device with quick QR access to everything).
Does Foundation Passport make it easy to get child seeds, or is it still a ton of click click click click click click click click click click click click click click click click click click...?
Absolutely! We put a lot of time and thought into our implementation of BIP 85 called "Key Manager." We wrote a blog post detailing how exactly it works when we released the feature a few months back: All your wallets, one backup | Foundation.xyzIf you have any questions out of that I'm more than happy to help. |
|
|
|
We can’t wait to hear your feedback on our new site!
I love its minimalistic approach and the dark mode feature is the icing on the cake We have a HUGE week of giveaways, games, and celebrations planned for this week,
IMO, these kind of games deserve having a dedicated thread: 1 MILLION SATS hunt- I think I've found three of them so far (please don't make them harder)
BTW, I'm curious if anyone from the Philippines has tried applying to become an official reseller... 1. Dark mode was a huge focus, most of the team are dark mode maxis 2. Hmm, will have to do that for the next one! Great idea to bring that sort of thing to Bitcoin Talk as well. 3. Not that I know of, but would love to break into that market! Why choosing obscure .xyz domain? I think having separate Passport HW domain or subdomain would be a good idea. One question for you guys: Are you working on adding support for using multiple seed phrases in the same time on one device? Moe hardware wallets are supporting this, and I think it's a good idea to add it.
I had to post this here to show how ''serious'' keystone developers really are.  Few months ago they posted fake open source license for keystone firmware, and they excluded Foundation Devices and Zach Herbet! This was not open source, but they fixed it and remove that crap later. WITH THE EXPLICIT EXCLUSION OF FOUNDATION DEVICES AND ZACH HERBERT, WHO ARE STRICTLY PROHIBITED https://github.com/KeystoneHQ/keystone3-firmware/blob/d9e7f20985140e38e4cf2c9f841f8e576d90e98f/COPYING-KEYSTONE#L191. .xyz is actually becoming a very common TLD for big tech companies like Alphabet, so it's not as obscure as it can seem! There also are pretty limited domain options for a common word like "foundation" and a key goal was dropping the "devices" from the domain. 2. Do you mean storing multiple and loading them as desired? We do have a WIP feature that will allow you to load BIP 85 child seeds from Key Manager and sign from them on Passport which meets the majority of that type of need. 3. That was... an interesting and unexpected exchange  None of us had ever even talked to him but seeing someone try to wield restrictive licenses out of spite on social media was a new one for me |
|
|
|
Big news for you all today -- say hello to our new home, https://foundation.xyz 🏠
Our website and domain have served us well, but we’ve long since outgrown the “Devices” moniker. To pave the way for a new wave of freedom tech from our team, we’re launching a new site today. While we may have started as a purely hardware-focused company, we’ve grown and evolved into a freedom tech company that encompasses hardware, software and Bitcoin self-custody tools. We can’t wait to show you what we’ve planned in a HUGE 2024 that will even better reflect this! With all of this, it’s time to shift from our old https://foundationdevices.com domain to a new, improved, and more accessible https://foundation.xyz. Our website now properly reflects our design-first approach and our simple, intuitive user experiences that grow with you. A huge part of the new experience is letting you have your voice be heard, as we now feature real user feedback on every product page. Ever wondered what other Envoy or Passport users think of the experience? Wonder no longer: https://foundation.xyz/passport/Another core part of our effort has always been going above and beyond when it comes to customer support, but we never had a proper support page. All that has changed, with an entire page dedicated to contacting our support, reading FAQs, and much more. https://foundation.xyz/support/Speaking of customer support — now our Concierge white-glove service has a new home, giving you everything you need to know about it. Going from zero to self-custody has never been easier than with Passport + Concierge. https://foundation.xyz/concierge/We also have a deep passion for user education here at Foundation and wanted to better reflect that in our blog. We’ve drastically improved our blog, with better readability, better formatting, and easier navigation. Take a peek 👇 https://foundation.xyz/blog/Want to deep-dive into the specifics of our devices security model? Or simply learn more about the deep ethos of personal privacy that goes into how we design all of our products? Now you can do that at a glance on our new Security page. https://foundation.xyz/security/We can’t wait to hear your feedback on our new site! We have a HUGE week of giveaways, games, and celebrations planned for this week, so be sure to follow us on X or Nostr to be sure you don’t miss out 👀
|
|
|
|
A huge new release of Envoy just dropped!
Could I propose for the future releases a small feature , namely, the revolving order for destination and change addresses in every following transaction build by Envoy? Implementing this would mislead slightly the chainanalysis companies which use heuristics in their research, and, thus, would add to users privacy. Could you expand on what you mean here? We already rotate addresses every time you hit Receive and for every change output, even if the receive address isn't visibly used on-chain to better protect users. Is that what you're asking for, or something on top of that? |
|
|
|
Noticed only today and I think it's worth to highlight now - they fulfilled my old-date request @foundationdvcs, could I suggest a small feature to device's GUI. In the upper right corner of the screen there is a small battery icon. Is it possible to add into GUI without much pain the option to show battery percentage near that icon? Device uses lithium-ion battery and to prolong its life time it is very important to start charging procedure when it reaches certain depth of discharge. Knowing of exact battery capacity left would be highly mattered in this case.
and implemented it even by the better way: Device --> Battery --> shazam! I'm not sure what release (either 2.2.0 or 2.3.0) has brought such wonderful feature but it doesn't matter. It's over there, under the menu of Passport device. Was easy to miss in the laundry list of new features in 2.3.0 but was in there at the end, just for you You can now check the exact percentage of battery Passport has in the settings under Device > Battery. |
|
|
|
@foundationdvcs : Following this[1] discussion, is there any possibility to implement the function that allows to magnify areas within the generated QR code so that it could be easily transferred to a metal plate (for example)? Or this is seen as something that is a "nice to have feature" and not "must have" at the moment considering the development plans?
[1] https://bitcointalk.org/index.php?topic=5485622.msg63706761#msg63706761Fascinating idea! I'll raise an internal issue with the team to further discuss it, to my knowledge we haven't considered it yet but would be great for helping with steel QR backups as mentioned. |
|
|
|
Is this update actually better address formatting similar like Trezor did recently? As RickDeckard showed off, it's a new way to break up the address and use bold formatting to make it easier to verify "block by block," if you will. You can read more on the motivation and standard that was proposed by the Bitcoin Design community here: https://bitcoin.design/guide/glossary/address/#visual-formattingWe've also deployed the new address display format in Envoy as of v1.6.0 (in beta!) so that verifying addresses visually between the two is even easier!  |
|
|
|
The moment that we have been waiting has arrived - Passport version 2.3.0 is LIVE[1][2] (paging @satscraper). I'll just highlight a couple of great additions: - Full Taproot support in Passport;
- Address explorer;
- Support for verifying and displaying OP_Return;
- Creation of 12 word seed phrases (defaults to 12 word seed phrases during onboarding);
- Improved address display
The team over at Foundation keeps transmitting me a sense of responsibility and transparency within the hardware space that I find very appealing. Congratulations to everybody on the team once again.
[1] https://foundationdevices.com/2024/02/passport-version-2-3-0-is-now-live/[2] https://github.com/Foundation-Devices/passport2/releases/tag/v2.3.0Thanks so much for sharing this, Rick! We're thrilled to release this, and as you can see from the blog post it's a massive release and likely our largest to date! If any of you have questions on the release, I'm happy to answer them, and will be sure to stay on top of this thread more moving forward Edit: I've updated the version OP, and here is the quick summary for those looking for the tl;dr on v2.3.0: We’re beyond thrilled to be able to release Passport firmware v2.3.0, including full Taproot support, revamped passphrase behavior, an all-new address explorer, master seed SeedQR export, 12-word seed phrase support, 12th/24th word generation for advanced users, and native OP_RETURN message viewing and signing.
This release is one of our largest to date and includes a massive amount of new features, improvements, and bug fixes.
|
|
|
|
Update today directly from Envoy, our mobile app in just a few taps, and read the full changelog in our release notes blog post below
Is there a way for Envoy app to have support for other aigrapped hardware wallets, other than Passport? Or maybe you have the tools available for other developers to help and work on that, since everything is open source code. We plan on focusing only on Passport (and future devices) in Envoy as that allows the tightest UX pairing possible, and there are other fantastic multi-hardware wallet solutions out there like Sparrow Wallet. As you mentioned, Envoy is 100% open source so anyone could fork it and make it work with other air-gapped hardware wallets, with those supporting the same UR/animated QR standards being the easiest to implement. |
|
|
|
📷 Seamlessly switch back and forth between signing via QR and microSD
I should say that this is the most noticeable feature which empowers device to handle large transaction effectively. I have encountered in the real practice the difficulty to sign via QR the big transactions which made itself evident in the fact that the time required to complete the signing process was unbearably long (up to 10 minutes). Now, having the preliminary warning on the large transaction and opt to switch on-the-fly from QR to SD card simplifies the signing process. Tested this myself with 2.2.0 beta a few days ago. Love to hear that! We've done a lot of work to increase the size of transaction you can reasonably use QR codes for, but there is still a practical limit where it just makes more sense to use microSD, so I'm glad to hear this is already being an effective UX improvement. Even more QR improvements and transaction signing speed-ups coming in 2.3.0 as well as we've rewritten the transaction parsing from scratch to go along with Taproot. |
|
|
|
We're thrilled to get Passport v2.2.0 in your hands today 🎊 With this latest version, you can: 📷 Seamlessly switch back and forth between signing via QR and microSD 🌱 Restore from SeedQR We've also improved the user interface on Founder’s Edition and added many quality of life improvements across the board. With the number of new features we included in 2.1.0, we took this release to focus on refining our unified firmware between Founder’s Edition and Batch 2, as well as paving the way for full Taproot support in 2.3.0. Update today directly from Envoy, our mobile app in just a few taps, and read the full changelog in our release notes blog post below: https://foundationdevices.com/2024/01/passport-version-2-2-0-is-now-live/If this is your first time updating Passport or you'd like a refresher, we have docs and videos that walk you through every step of the process: https://docs.foundationdevices.com/firmware-update
|
|
|
|
An email is going out to all of those subscribed to our email list to take a brief survey, but if you purchased Passport and chose not to provide an email (for instance at a conference) please shoot us a message or reply here and we can validate your purchase and share the link directly.
Is this survey with rewards available even for people who didn't purchase Passport wallet directly from you? I found Passport locally from reseller, and I never subscribed for newsletter... well maybe I will sign up soon with temp email Absolutely! Please just send us a message and we'll set you up with the link |
|
|
|
|
