How easy is it to take the open source Trezor Model T crypto hardware wallet files and manufacture your own? Or to modify or improve the design?
The Trezor is open source hardware, so Dave checks out the Github and looks at the hardware files available and imports into Eagle and KiCAD. Where to from here?
OSHW Logo generator: https://maciek134.github.io/oshw-logo-gen/
There is more hardware info here: https://github.com/trezor/trezor-firmware/blob/master/docs/hardware/model-t/index.md
Forum: https://www.eevblog.com/forum/blog/eevblog-1374-diy-trezor-crypto-hardware-wallet-part-1/
Subscribe on Library: https://lbry.tv/ @eevblog:7
EEVblog Web Site: http://www.eevblog.com
The 2nd EEVblog Channel: http://www.youtube.com/EEVblog2
EEVdiscover: https://www.youtube.com/eevdiscover
Support the EEVblog through Patreon! http://www.patreon.com/eevblog
AliExpress Affiliate: http://s.click.aliexpress.com/e/c2LRpe8g
Buy anything through that link and Dave gets a commission at no cost to you.
Donate With Bitcoin & Other Crypto Currencies!
https://www.eevblog.com/crypto-currency/
T-Shirts: http://teespring.com/stores/eevblog
#Trezor #Crypto #DIY

Hi. This is the Tresor Model T Crypto Hardware Wallet. I'm sure I've done a videos on these before and you should have a Crypto Hardware Wallet if you're into crypto because if you don't hold the keys then you don't own it. If you're relying on some software wallet or exchange wallet or something like that where you don't own hold the private keys yourself, then yeah, you might come a gutser.

So um, I use Crypto Hardware wallets. Tresor is the one I use. the one I like. I've got quite a few of them, but I just like the Tresor system.

It works. and I've got the a couple of these Model T units. I've got the model one as well, but I like the Model T. It's got the touchy feely screen.

But one of the good things I like about this is that it's actually open source. Not only open source software and firmware like the ecosystem, the application and the firmware that goes into its open source, but it's open source hardware as well. So in theory you can build one of these yourself without having to rely on the uh, supply chain and potentially get hit by supply chain men in the middle attacks. Because if you aren't aware, simply do not buy a crypto hardware wallet anywhere but the official manufacturer or one of their official authorized dealers.

Because if you do, you can get hit with like a supply chain or man in the middle attack. And the way these things work is that when they ship you well, there's a couple of methods It works. One of them is that they can like buy these and then pretend to be a deal authorized dealer and sell them. and then they can install a custom firmware on here which then can report back and steal your crypto some way like that or another way to do it is to supply you and like authentic looking uh, keyword seed sheet with the unit and then you think oh, this is my super secret key and everything But no, you do not do that If your crypto hardware wallet doesn't matter what brand it is is supplied with a uh, a pre-existing seed key, uh private key, then you're being scammed because you're supposed to generate it on the unit itself secretly and ideally on a like isolated non-internet connected uh machine like a clean uh machine so that nobody but you has the seed key for this.

The thing with your keyword seed recovery sheet is that you should treat this like cash because if anyone has that, then they don't need your tresor. They don't need your hardware wallet. They can simply use that and recover either onto another hardware wallet they uh, buy or just a software wallet. They can simply recover that in minutes and steal all of your crypto.

so you want to store that in like your safe deposit box buried in your backyard although it's paper so but yeah, maybe something more durable than that. Treat it like cash because if somebody has that, they can steal everything. so you can talk about all the security aspects of hardware wallets until the cows come home. But the fact is, they don't need this.
they can just get your seed sheet. So yeah, keep that secret squirrel. So here's the Model T and one of the things I don't like about it is the tiny little screen on. Now, I do not have big fingers, but it's like it's really hard to get in there and push these buttons.

It's really quite annoying. So I've always wanted to try and build my own Tresol Model T and potentially like improve it by maybe putting on like a bigger building a bigger compatible screen into it because I don't have to like rewrite the firmware or anything like that. I wanted to be completely firmware compatible, but have a nice bigger touchscreen. so maybe there's a compatible one that works exactly the same with the existing firmware and everything.

and then I could mount it in, maybe like a nice machined aluminium case. I could pot it and I could put on multiple Usb connectors and things like that because if your Usb port on this goes bust then well, you haven't lost your crypto. But it's just really annoying because then you got to get your seed recovery sheet and then set up a new one from scratch and that's a little time and effort. It's really annoying so you might put on multiple Usb ports.

I even had ideas of maybe adding like a second little uh, memory Lcd on there or a um, e-ink Lcd and potentially having like a power-up counter on there. So like, you can secretly know if anyone's been trying to hack in to your uh little crypto hardware wallet. So then you'll be able to know if anyone's tried to secretly hack into your hardware wallet without knowing because then it increments a counter on there. You'll know how many power-ups it's done and things like that, although they could probably implement that in the firmware in as well.

Uh, so Tresor, if you're listening. I've tweeted to this years ago, but anyway, yeah, that'd be a nice feature. Like you know, it's been powered up x amount of time. So so yeah, you never know when you might want to know how many times this has been powered up.

So yeah, that's one of the cool things about this is that it's completely open source hardware and software so that you can potentially in theory make your own and then bypass the supply chain entirely. So then you're not trusting anyone. So anyway, let's take a look at their website because when they first released this, I was disappointed that they didn't actually have the hardware files at the hardware. They didn't release the hardware files for it, and they have actually since released.

It's been a while, but haven't gotten around to it, so let's take a look. This is their Github is Page. So they've got the Tresor Firmware here, the Tresor Suite, which is the software. They transitioned from like a web based user interface to an application based user interface.

and I like it much better. Although the web one. Of course, you didn't have to install any software, it just worked from the interwebs. But yeah, that's it.
So the application is open source. I think it might be multiple. I use Windows, but might be available on multiple platforms. Uh, then they've got Connect Easy integration in third party services, account balance.

Back end: they've got a communications daemon written in Go? I don't know. But um, yeah. Like there's a very cool ecosystem surrounding the Uh Tresor here. And in terms of like being able to integrate it into other products and stuff like that.

Which is really cool, right? So let's take a look at the Github repository. We've got the Uh Tresor Sweet. Uh, Mono Repo? I don't know what that means. Look, I don't know.

I like, I don't use Github so if I use all the terminology wrong, I just don't know what I'm freaking doing. It's like I do have a Github account and I've got some stuff on there, including Dave Cad. But I just no, I'm not a github person. Uh, Tresor Firmware.

Uh, we're not really going to touch the firmware, but because you know I want to build up one of these from scratch. Design and build. Um, yeah, we're going to have to get the firmware, don't I have to compile it and everything. But I want the like the the image that I can download to my micro when I plug it on there.

so that could be an adventure in its own right. So we won't go into the uh Tresor so we won't go into the firmware. Um, Blockbook sits on api. I have no Python wrapper for the head.

I I got no idea. Micro Python Connect wallet data or data error in the Go blockchain. Yeah, we want hardware. We want hardware.

Tresor common. Don't post issues. Uh, Tresor Utxo Lib Android Uh, that's nice. Link test scenarios: Password Manager Hd Wallet No in Java No Tresor Wallet obsolete.

Do Not use uh Address Validator Tresor Hardware. There we go. Tresor Crypto Phyto 2 Test Stellar Account Viewer Okay, Anyway, there we go. We're in the hardware.

It's Uh C. It's a Gpl 3.0 license for those playing along at home. Let's go into the Tresor Hardware, shall we? And they've got. That's it.

Ah, they've got the case, the electronics, and a production test. self-test thing. Something like that. We're not really concerned with that.

Doc make photos or test results. Yeah, it's just some sort of production testing. Not too fussed about that, although you might have to use it if you build it up. probably not.

Should just be able to. Um, in theory, should you just have to take the Gerber files that they should provide and then send it to the manufacturer? Get it made by the parts based on the bomb, and then you burn the firmware? I think it's an St Arm Micro in here. So you just burn the firmware using an St programmer and Bob's your uncle? That's the theory. Anyway, so the case.

Let's have a look at the case. Uh, there are two different one ones. One's the model A one, it's the older one. but if you're going to get a tresor, I recommend it.
the Model T. It's just got the nice touchy feely in in a bigger touch screen. it's just more better. So that's version three of the tresor one.

But really. uh, Model T. So you might have to use this as a baseline to Uh design. like a custom case or something.

It's got top and bottom Scl files. That's it. Okay, last updated 11 months ago. Uh.

electronics. This is what we want. Ta-da Let's have a look at the older model one and it's got like the board, jpeg and stuff. Oh yeah, there it is.

That's the model one. I've done a tear down of that uh programmer dot board that looks like dot sketch. They look like Eagle files. Uh raspy.

What's raspy? Oh, is that a programmer? Oh, is that a raspberry Pi program? Oh, I think that's a raspberry Pi programmer. Is it? I I guess. So that's part of their programming system. I would presume.

Uh, the they've They've got a bomb. That's that's for the old one. Anyway, we want the new one because I want to do. I want to make this like a multi-part series, actually designing and making and potentially improving the tresor because it's all open source hardware.

Which is cool. So we're going to the Model T. That's it. That's it.

The board and the schematic file. Really? Where's the where's like? the project file? The Bom? Where's the like. It'll be nice. Like if you had like a pdf of the schematic and like images.

where's everything Last even put five months ago? Geez. They haven't really updated anything have they? So these look like Eagle files we're in. Yep, Eagle. Uh, version 7.7 of Eagle.

Um, it's the Xml no workers Board file is also done with Eagle 7.70 So that's it. Well, that's disappointing. That's not really. I mean it's it's open hardware.

Um, in terms of well, you know you can get the board and the schematic so we can load those into Eagle. although we can import them into a keycap, which I'll try and do here. Or we can import them into Altium. Whatever your favorite package is, you should be able to import that and then get the board manufactured.

But where are the Gerbers? Where are the Gerbers? like? You know the whole idea. The cool thing about this is that you should just be able to grab the Gerbers, upload them to whatever two dollar Pcb manufacturer you want, and get the boards for it delivered for like five bucks delivered or something. Whatever. the ridiculously low price is this week.

Um, and make your own. And then just, and, where's the bomb? Where's where's the bill of materials? The bill materials is going to be very different for this than it is from the uh, well, maybe it's like built into the schematic, but no, that's no. No, that's a thumbs down. That's a thumbs down right off the bat.

Um, for not having like a bill of materials and other stuff and there's there's uh uh, Pavel good on your Pavel. Look at that beard. He looks like a happy guy all around. Hacker working on tresor Tropic Square Knicks Os Another open source project in Prague in the Czech Republic.
Hi to all my Czech viewers. Um, so yeah, please. Um, you've got more stuff there. Please just dump it in here.

I'm sure it's not hard Anyway, I'll download those and see what we get now. One of the annoying things about Github and a trap for young players is you can't just go save link as like that because then it'll download the Html instead of the real file. So even though it will, it'll actually save it as the dot Brd file. It's actually Html and it won't work.

So yeah, you've got to like download the git thing. I don't know. Yeah and like that's another annoying thing. Like I don't even think you can like download.

can you like? You can't download this particular? There's no like this go-to file. but there's no like download zip or whatever. It's just it's stupid. I know you're supposed to like.

do the command line get pull or something rubbish like that? I don't know. But um. yeah. Anyway, here we go.

We can download Zip. Okay, so I've got the latest version of Eagley 9.6.2 It should be able to open the old ones. I don't know, I don't use Eagle, but uh yeah. let's go and we're in like Flynn.

Look at that. Beautiful. There you go. There's our it doesn't Oh dude, I didn't know Eagle opened up different windows for the schematic.

I don't know. it's been a long time since I've used it. but there you go and it looks like see, we can get our bomb from here. Potentially like I don't know how the Eagle thing works it device if they got like footprints but they don't have like links to anything.

do they like? They don't have like digi-key links or something like that. See, it'd be nice to have a bomb for this thing. Like all your generic parts and things like that, that's all like hunky-dory like oh yeah, you know your Lcs and Rs and stuff. no wackers, you can just sort of get anything.

But you know things like the Lcd and stuff like that, you got to get very specific ones there. It is. Okay, so that looks like at least they got the very specific part number. No, that might be the connector.

See, that might be the connector. I have to google that one, but that could very well be the connector, not the actual Lcd. and that, well, kind of makes sense on the schematic side of things, but that that's incredibly annoying. Most other things are being okay.

Like because that's one of the things I want is, hey, what Lcd do they use in there? Uh, have I done it? No, I don't think I've done a tear down of the Tresor Model T. I'm sure you could get the info somewhere. Someone's probably done a tear down. Get this thing made.

So ideally, maybe at the end of this video series, I'll have like a uh, a bomb. Like either a digikey or a mouse, a bomb, or an or a Jlc uh, like bomb or something like that And then the board and you can just potentially just turn key it. That would be nice if you can, just you know, hit one of those order buttons you might even be able to get. Maybe this could be a trial.
Leave a thumbs up in the comments, leave a comment down below if you want to see this. Maybe I could potentially use one of those like turnkey services perhaps. So that and then you can make it publicly, uh, available. Because this is all open source hardware.

So if I do anything with this, I've got to re-release it as open source hardware as well. I can make it publicly available so anyone in theory can just push a button and they then you get an assembled board. But then you've got to trust the manufacturer, Don't you? You've got to trust that they haven't done anything uh, sneaky bugger like. But then again, once you get the hardware, you can just like re-flash it yourself.

So that's not. You know you don't have to get a program, you can just nuke it. Um, so that's fine, so that's pretty safe. But yeah, let's know if you want me to do that.

Maybe that should be the goal of this little series. Yeah, these clamps up here. You know we've got part numbers we've got part numbers for like the fuse here and stuff and you know, so that's okay, but it's It's just not the same as having a proper bomb please Tresor. So on the Ev blogger open source hardware logo thing which is still a thing.

A lot of people, uh, use this and I think it's great. They do provide the schematics and the Pcb and they do have the mechanical Cad files firmware software but they don't have any. There's no, well, there might be design documentation I have. Well, they don't have a bill of materials so it fails at that License start use does not restrict.

uh, commercial use. so commercial use is fine, I believe. Yeah, so it's like bill of materials is like really annoying and then there's arguments over the world. B Yeah, you get the Pcb, the original file, but you don't get the Gerbers so it's like maybe I should have added like another one saying manufacturability or something like that.

Anyway, let's open up the Pcb board dot board file and bingo we're in no wackers like these are all big fat dots. What's what's going on there? I don't Once again, I don't use Eagle. Is that like an Eagle thing? or is it and they're all like, uh, they don't line up so I'm not sure what the deal is there. It's not like one is the board outline because here's your board outline.

I so don't know how to use Eagle. Um, yeah. so we've got a yellow is our board outline. no workers, so I don't know what the deal is with the other thing.

Is that an Eagle thing? or is it just something that they've done? I don't. I don't know what the deal is anyway. Um, yeah. there you go.
Oh, it's it's a four layer board. Okay, oh, I didn't think that the free version supports a four layer board. I'm pretty sure it doesn't. No, it doesn't.

Uh. two schematic sheets, two signal layers. There you go. And of course, it's a tiny board.

so it fits in the area, but only supports two signal layers, so the free version does not support. You cannot get this thing in theory. Like we should not even be able to generate the Gerbers I guess from this, so that's pretty useless. Um, so yeah.

I might try and do the import thing. I might import it into keycad. I was going to do that anyway because I don't want to use Eagle because Keycard of course, is open source. so it's more fitting to use keycad for like, an open source project like this.

Whatever. Anyway, it loads. Okay, so I've got the latest version of keycard. although there is like a version, six, beta or something.

Meh. Whatever. Let's see if we can import an Eagle Cad Electronics Model T. Can we do not? We can only just do the board import.

Okay, Oh, hang on. We did get an error message. Unsupported Eagle Layer T Test 37 converted to drawings user layer. okay, I don't know.

Restrict drill legend measures. Okay, so there were issues importing this, but we did get it. There you go. So we do have the layer details.

That's nice and don't like the blue on black. Um, there you go. They've done their layer stack up. Very nice.

Uh, it's a one one millimeter Pcb. Okay, there you go. Didn't know. Oh yeah, that makes sense in a tiny little you know, thin thing like that might not be able to fit one point because you've got to get the uh, the touchscreen and the uh, what not in there so one millimeter already.

That's a bit odd, but you know I might go for like 0.8 or because I'm going to design my own uh like you know, improved version of it, uh bigger potentially then well can be one point standard 1.6 or you know you typically go with a 0.8 You wouldn't normally go with a 1 unless you had to because it's just less common. The Tacky plan: I have no no idea what that is. Geez, that's going back Isn't it? 24th of the 7th 2018? Wow. Is it that old? Really okay.

Now it's mixing sheets. So the brown in the background there that is the uh, generated template for uh, key Cad and the blue one is for Eagle Cad. So that's yeah. that's kind of annoying isn't it? Anyway, it looks like um yeah, this has not gone well.

um it's it's got like broken nets and well it's showing broken nets and stuff. but I guess if you because it's a four layer we've got a ground and power and it's just it's not doing terrific. So yeah, that's not. You know it's not trivial to import these and to convert between one package and another.

Once again, you know if you've got more experience in, uh, like importing Eagle files in the keycap like I, I really am a complete noob at uh, keycard. Uh, let alone importing Eagle into key Cad. So yeah, and solder mask expansion? Look at that. I mean, it's just it's just none.
Look, it's just complete under under the part, under the entire part. not around the pad. Oh, that's terrible, Muriel. But those pads seem to be okay.

But yeah, no. So you've got to fix like the solder mask expansion. so you can't just like import this and then just hit generate Gerber and get it manufactured. You know it's going to be an absolute mess.

Um, let alone what's happening with all these nets. I mean, ground you might have to assign. You know, the power planes probably weren't imported properly. I don't.

You know? I like. I still don't know what all this deal up here is like. This Converted these into lines? Yeah, that's it's. going to require a lot of cleanup.

This is many hours of me to I figure out what's going on here and then B clean it up so I won't be doing that in this video. This is just making sure to see scene in part one seeing if I can import and see what was what. Very disappointed that we couldn't just get the Gerbers and just get it manufactured because I might have done that. I might have just got the got the Gerbers and then boom.

um so yeah. but I can still do that. I could generate them from Eagle I guess. Um, but yeah.

can't just you don't want to be Just be pushing generate Gerber on this. That's that's just a mess. Um, so I'm not sure what's happening with the ground and power planes and stuff. Um, so they're obviously the only not net connected things.

so they're all ground. What's like p dollars? one? Um, like I don't. I don't get it anyway. Uh, these two have nets.

I see two pet like. it just doesn't know what it's doing. So yeah, but that's common with imports. So yeah, some work required.

Generated a dot. Pretty. I don't know what a dot pretty is and then it's like loaded. All this and like I don't like.

Oh 201. What is there An 0201 part? No, there can't be Something else is like this is supposed to be the library imported library for the don't look Eagle. All these packages that's to die. That's just no, that's bad.

25 12 and then 25 12. Reefer? Like I don't. This is a mess. I'd be tempted not to even reuse that at all.

Like if I'm going to do a new one, I'd import the schematic, get the schematic, tidied it up, get the bomb tidied up, and then just generate a new board and start that from scratch because it doesn't take a long time to lay out a board like that. I mean, you know there's not a huge number of parts on it. It's not very complicated, so yeah, you know you might take the outline and stuff like that if you're going to use that and then just nuke it. Maybe you know, keep some things like like the connector in place and stuff like that, but you might want to nuke that from orbit.
Uh, it's the only way to be sure. I say we take off and nuke the entire site from orbit. It's the only way to be sure. See, here's the problem.

because there was no project. It looks like Key Cat only imports like project files and if you select just the schematic or Pcb, it wants to create like a new project directory. for the schematic and for the Pcb like separate ones. it's just I.

I don't know. I don't have enough experience with Keycap, but that seems to be a limitation. Some reason kick had shut down and it's like I just what the heck happened. Oh god no, this is a mess.

Okay, import the schematic. What? I opened the schematic and I got the Pcb. What the heck? Okay, anyway, um, yeah, that's weird. But we're in and there's our schematic.

It's done an okay job that's pretty usable. I don't know what all these words here are that is not. Uh, that is not English symbol. Ram A3.

Why is there a Ram A3 symbol under there Okay, there you go. Why is it moving the frame? Is that a keycad thing? Why like the templates moving the template with the part? That's really weird. Anyway, the part is the part. So how do can we like edit a part? Once again I don't have enough experience with head to really like know what I'm doing here unfortunately.

So once again like this is many many hours of work to get this. Like to import this from Eagle into key Cad and then get it all usable and set up the proper bill of materials. And you know keycard. Uh I believe it supports like all the data sheet links and the Bom links and stuff like that but you'd have to go through like yeah every single item.

Anyway let's do can we get a 3d view of the Pcb? see if it works? cannot determine board outline nut. So once again yeah it like it didn't import the board outline properly. so there's our there's our 3d view. So yeah that's not exactly spectacular is it? Yeah it just thinks we've got a square board.

but yeah that's all right there's no component I didn't You know it's not going to import like component models and stuff like that. Um so yeah that's not a thing. so that's is probably as good as you can expect. Oh that's what.

Okay, that's what is that. What those pads right? You know how I thought that the, uh, that the capacitors had the solder mask all the way under? It wasn't That looks like it's glue. That looks like it's a glue point. Don't know why you'd bother.

It's not a double-sided load, so you don't have to glue the components down before you reflow them. So yeah, Is that part of was that in the Eagle thing or is that part of the import? So yeah, as I assume that that's what that is without actually going and inspecting. But as I said, yeah, there's no solder mask between pins or anything like that. So yeah, you can't just import this and get it manufactured.
It's just it's no. it's not going to work, right? So that's kind of annoying. So that, uh, what do we do for part two of this video? Leave it in the comments down below. Do I spend oodles of my time trying to convert this into and tidy this up into a workable key Cad project and then try and like, make it? You know, get all the billing materials and then make it all turnkey and stuff like that.

There's probably three or four parts to just doing that video. Well, at least really. Or should part two of this just be me? Like seeing if I can just manufacture this myself, actually get one made from the supplied github, the Eagle file. so just use Eagle, Just generate the Gerbers, hopefully there's no issues there, and then send it to you know, one hung low Pcb manufacturer and get it made and then order the parts, try and get some sort of bill of materials probably manually and then, um, get it together like and then build it up and see if I can get a working tresor.

Um, should that be part two? Or do you want me to actually go down the rabbit hole of effectively learning ki Cad? Um, and because like, it's one thing to do key Cad from, you know, with very little knowledge of Key Cat. Although I'm an experienced professional Pcb designer, I'm an Altium guy, right? So very little Key Cat experience. It's one thing to actually start a board from scratch. And it's another thing to like import an Eagle file and be messed and be left with like a huge mess to try and tidy up.

It might even be easiest just to simply start from scratch, get like a physical print out of the uh of the schematic, and just manually create parts from scratch rather than try and import. Although we do have this schematic imported. but is it better just to simply? I don't know, start from scratch either. like I Maybe this Stm parts available in keycad and you know you've got the you know? I'm sure there'll be a Usb uh C connector in, you know, the parts somewhere and and things like that, so you know.

Apart from that, it's all fairly generic. There's a few oddball, uh, protection devices, uh, perhaps like Esd protection and stuff like that. But is it easy just to start from scratch? Or should you? I don't know. Am I pushing the brown stuff up a hill with a pointy stick by trying to import the Eagle files? Which is easier Anyway, I'll leave it for this video.

Please leave it in the comments down below what you think I should do with this? Because well, yeah, I don't know. Schematic seems okay, but I yeah, I don't know. I could just see a lot of hours working this. Anyway, Yeah, I think um, yeah, that that's a thumbs down for the Tresor Open Source.

You know, technically you can do it, but they don't make it easy to manufacture one of these on your own. And really, that would have been like I'd be advertising that fact. Look, if you want to buy it from us, we're safe and secure. You know, by us, it's already assembled, tested, programmed, and everything else.
But you know, if you're ultra paranoid or you just want to do it yourself? um, then here's all the Gerber files or here's you know. And here's the digikey bill of materials. Here's you know, the turnkey Jlc? uh thing. So Tresor would actually be in a much easier and simpler position to actually generate something like that.

I've got to like go through all the hard work to redo the the whole kit and caboodle. So yeah, not impressed. No bill of materials, no Gerbers, just a couple of Eagle schematic and Pcb board. Oh fail.

Anyway, hope you like that. Catch you next time you.

Avatar photo

By YTB

20 thoughts on “Eevblog #1374 – diy trezor crypto hardware wallet – part 1”
  1. Avataaar/Circle Created with python_avatars Alex Stanciu says:

    Great video showing the challenges one takes in order to build one of these "open source" projects. Will there be a part 2 coming up soon?

  2. Avataaar/Circle Created with python_avatars Arek R. says:

    I would suggest to swap this USB-C socket into easier to solder type with 2.0 interface and so no hidden pins, only around 10 pins, I'm sure trezor doesn't use 3.0 interface because there is not much data to transfer.
    I use this one in my projects: Mfr no: 918-418K2023S40001 LCSC no: C167321 it's also cheap and has through hole mechanical pins that should make it strong.

  3. Avataaar/Circle Created with python_avatars Bless You says:

    You say “nuke it.” Do you think flashing the firmware is a pretty solid protection against someone having previous physical access?

  4. Avataaar/Circle Created with python_avatars David Waddy says:

    KiCad from scratch. I think an experienced designer would progress through learning KiCad from a different direction versus how a hobbyist would. That would be interesting.

  5. Avataaar/Circle Created with python_avatars You're the best says:

    Sir where to sell out Cypto currencies like bitcoin, ether,litecoin etc help me please i have Purchased crypo but i don't know where to sell out help me please

  6. Avataaar/Circle Created with python_avatars SORLOK says:

    Would you still think there is a risk if you get the PCB made and component mounted, but do your own flashing.

  7. Avataaar/Circle Created with python_avatars BansheeHero says:

    I like this concept, Trezor like key stores are great for the future even if you use them for authentication outside of crypto. Yeah NFC yubikey exists, but still 😀

  8. Avataaar/Circle Created with python_avatars nobodybodybody says:

    Dave, on Github if browse into a specific file you can hit the "Raw" button in the upper right to download the actual file. You can also download a zip of the whole project from the top directory page by clicking the green "Code" button and then hitting the "Download ZIP" link.

  9. Avataaar/Circle Created with python_avatars Jaideep says:

    Maybe for part 2, try and redo the board on 2 layers and maybe change the form factor to something you like. Add another USB port. Remove some of the extra decoupling caps. Make it more minimal.
    Basically keeping the hardware the same but potentially making it cheaper and more redundant. I do think this could be done on 2 layers as long as you keep the USB traces short.
    Would make it much easier for amateur hobbyists to DIY their own wallet that way. Adding more decentralization I'd say.

    EDIT: On second thought, I have some free time on my hands and might actually take this up. Let me know if there's any other suggestions

  10. Avataaar/Circle Created with python_avatars TremendoussterlinghacksTech Got Me Bitcoin says:

    NOW IM ONE OF THE YOUNGEST RICH MAN IN MY STATE ALL THANKS TO INCRDIBLE HACK SOLUTION COM FOR THE 6BTC 😲🙏.

  11. Avataaar/Circle Created with python_avatars Povl Kvols says:

    Maybe not exactly as safe and secure as you'd want it to be: try searching for "trezor model t vulnerabilities"

  12. Avataaar/Circle Created with python_avatars Ross Robotics says:

    If it were me, I would use Eagle to display the schematic, then use Kicad to rebuild it. Basically, you would have Eagle on one screen and Kicad on another. Then just design the board from scratch. This method would make you learn Kicad and make your mods the way you want. If you need Gerbers from Eagle or other items/files, message me as I have the full version of Eagle (9.1.3).

  13. Avataaar/Circle Created with python_avatars Henrik Borg says:

    In KiCad you hit the B button to fill the zones and then all pads connected to those zones will be shown as connected to the zones. If you then hit Ctl-B, or is it Shift-B (not sitting by the computer now), the zones will be unfilled and the GND vias and pads will be shown as not connected.

    Don´t know why the frame was moving with the symbol for the chip. Never got that problem while importing Eagle files. Are you using a stable version or the nightly build, v5.99? v5.99 is for the upcoming v6 and there are some major changes for v6 that can cause some problems during the rewrite. The nightly builds are only for testing and debugging, not for designing PCBs, not yet.

  14. Avataaar/Circle Created with python_avatars Space Nomad says:

    Re: Where is the BOM??
    Grab a drink and some snacks, here we go:

    The schematic contains every single component type and value, the board holds the footprint for all of them. BOM is compiled by processing those schematic and board files.
    As such, putting the BOM and pictures of the schematic in the source code repository is redundant. The job of that repo is to track changes and make available your source files.
    If you put derivatives of your source code in there, now you're tracking everything twice and your clean sources are littered with binary blobs which you should really compile yourself, otherwise what's the point in sharing the source which everybody can read and understand, if everybody just grabs the binary blobs which they can't read or understand without reverse-engineering.

    GitHub is a visual tool for the Git software. Git is used to version your source code. While it supports other files, the Git software was primarily designed to handle text files only. Because software source code is just human-readable text. It's used to put metadata ("this is our release version 1.3") and to compare the exact changes between versions. This is used by developers to understand for example why the most recent version of their software release has bugs by using git to show the exact changes in the source code. You can also use this for reports to management. Git is also used to collaborate by enabling people to submit changes to your work.

    Now imagine 2 people working on this board have to generate those derivative files for each new version they release. They would need to make sure they use 100% identical settings to generate those derivative files, or the file would be entirely re-written with different content every time they generate it 1px larger or with a different font in the PDF, or compressed vs uncompressed and so on. Every time they do that, the new file is added to the repository and the old version remains intact. After all that's the most important job of your version manager, to keep track and be able to revert to earlier versions. Now imagine compiling dozens of these files. Now imagine how quickly your repository grows in size. You can and will easily end up with multiple Gigabytes instead of a few Kilobytes, just because you include derivative, redundant information that every person who actually works with your source can happily generate themselves using the development tool that you used, too. And every person who wants to work on and improve your project will have the burden to download, store and process all that unneeded crap.

    But people like Dave still want to be able to download all those derivatives with just one click, so people started putting in those files along with their actual source code and abused GitHub as a file sharing provider so they don't need to buy their own domain and webspace to publish their own website for the project and offer it as a download. And of course you then started finding Git(Hub) repositories suggested in first position when you searched for a project on Google (or DuckDuckGo, anybody?)…

    And that's wy GitHub added "Releases". That ".gitlab-ci.yml" is a script for GitLab (another visual tool just like GitHub), which automates the process of compiling and exporting those derived files. This way the developers need to install, run and maintain a server with all the development tools and put in the work to generate your output files with a script, but this gets you "reproducible builds" where all the settings and parameters used to generate your output are also part of your versioned source code. So you just tell GitHub/GitLab in the metadata that this revision is a "Release version" and all your sources get automatically compiled, packed into an archive, reproducible for anybody, downloadable on the "Releases" section of your GitHub/GitLab page. Optionally packed with more info like documentation/handbooks, digital signatures to provide trust, a changelog to notify about changes in this version, etc. Separate from your sources.

    TL;DR Instead of asking "Where is the BOM" you should ask "Where are the Releases".

  15. Avataaar/Circle Created with python_avatars Dave A says:

    I'm new to BTC if trezor when bust or the web page went down would you still be able to access your btc

  16. Avataaar/Circle Created with python_avatars Crazor says:

    What happened to preparing for a video? At least open those files and have a look around before turning on the camera. 90% of this video is "Oh I have no idea what the f* I'm doing here, look at me!". The other 10% is "Yeah maybe I should do a series on this thing, but I don't even have a clue yet what I should be doing to it". Half an hour of clueless yapping. This isn't even worth being called part 0.
    Still this could be an interesting series, waiting for the next part…

  17. Avataaar/Circle Created with python_avatars LeiserGeist says:

    On one hand, laying out the board from the schematic would make for a great educational video… On the other, it would certainly be a lot more work.

  18. Avataaar/Circle Created with python_avatars Niels Webster says:

    Turnkey would be cool! But I'm going to follow the series anyway.

    Keep it up Dave.
    Regards from the Netherlands

  19. Avataaar/Circle Created with python_avatars ꧁꧂ says:

    Why add this hardware wallet abstraction layer? Don't you think that there are any potential vulnerabilities in the hardware to software conversion process?
    Why not just use your Lastpass vault? It's right there in your browser. I can see it with my eyes. Has Lastpass every been hacked and information revealed? No. If you trust Lastpass to store all of your passwords, why not trust it to store your wallet private key?
    I don't see the point to these stupid gadgets which add another potential point of failure, aren't necessarily more secure than the Lastpass vault which you are already using to store your bank account information, and may not be compatible or supported for any unknown duration.

  20. Avataaar/Circle Created with python_avatars TheHue's SciTech says:

    Just FYI, there are (at least) two different philosophies when it comes to whether output artifacts (so, in the case of software: compiled binaries; in the case of hardware, gerber + bom files) should be included in the repo. The disadvantage of excluding them is a certain degree of inconvenience for the end user, sure, but the disadvantage of including them is that people like you will assume that the BOM, board, schematic, gerbers etc are all being kept perfectly in-sync with each other with every single commit. Not to mention merge conflicts, differences in different editor's gerber generation settings/preferences causing subtle nonsense diffs, etc. These problems do have solutions that can work to varying degrees, but still. I just point that out because with that in mind, it's not necessarily "wrong" for them to not include these artifacts, it may be more of a carefully considered compromise. Or, maybe they're indeed just lazy. I dunno. It would be nice to include a script which generated it though (as is always provided in software repos in the form of a Makefile or similar), that's where the analogy between software and hardware breaks down.

Leave a Reply

Your email address will not be published. Required fields are marked *