WEBVTT 00:01.070 --> 00:04.930 The Mineratopia guest segment is sponsored by Cake Wallet. 00:05.310 --> 00:10.790 Store, send, receive, and exchange your Minera and Bitcoin safely on iOS and Android 2. 00:11.210 --> 00:14.490 Cake Wallet is open source and you always control your own keys. 00:18.110 --> 00:19.070 Alright, alright. 00:19.970 --> 00:23.610 Hello, what's going on? Brindle Abdullah, what's going on guys? 00:23.630 --> 00:25.030 Is my microphone working okay? 00:26.090 --> 00:26.990 Yeah, you're pretty good. 00:27.590 --> 00:28.070 Okay, good. 00:29.330 --> 00:31.490 Best I can do it for an hour, so... 00:31.490 --> 00:33.550 No, we'll take it. We'll take it. It's not bad. 00:33.630 --> 00:33.970 Alright, alright. 00:34.110 --> 00:34.710 Brindle, how you doing? 00:35.370 --> 00:36.990 How bad? Yeah. Can you hear me? 00:37.610 --> 00:39.730 Yeah, yeah, it's good. You guys are both good. 00:40.310 --> 00:40.490 Alright. 00:42.730 --> 00:48.250 Um, so Minero Nodo guys, what do we got? Everybody's on the edge of their seats. 00:48.810 --> 00:51.170 They've been on their seats for months now. 00:51.570 --> 00:54.210 You can tell anytime in a day now. In a day, in a day. 00:54.830 --> 00:55.830 Yeah, we're doing our best. 00:56.290 --> 00:58.970 It's currently going through basically the final PC. 00:59.750 --> 01:00.990 It's been a lot, guys. 01:01.110 --> 01:04.990 I'm just going to say what we're out here in the public, you know, behind the scenes. 01:05.650 --> 01:09.290 I could be quite cruel at times, so I apologize to them. 01:09.310 --> 01:10.890 No, I fully understand it, man. 01:11.110 --> 01:14.170 I know they're working their freaking asses off. 01:14.990 --> 01:20.030 I have nothing that I can do other than tell them, fix this, fix this. 01:21.730 --> 01:24.070 But yeah, they're doing a fantastic job. 01:24.070 --> 01:29.910 And like I said, on the outset, while there have been delays due to fabrication reasons, 01:30.630 --> 01:33.830 we haven't been sitting on their hands or they haven't been sitting on their hands since 01:33.830 --> 01:40.670 they've been adding other features, fixing the bugs that we were noticing. 01:41.610 --> 01:44.450 So there's been improvements and developments in the software. 01:44.810 --> 01:47.170 So I don't know, Abdullah, if you want to quickly, I guess, 01:47.210 --> 01:51.410 first just give like an overall status of what's going on with the project 01:51.410 --> 01:54.550 when we could expect delivery, things like that. 01:54.870 --> 02:00.350 And then we could get Brindle involved and he could talk about the actual software 02:00.350 --> 02:01.930 and updates of where we're at, that. 02:03.190 --> 02:03.770 Sure thing. 02:05.450 --> 02:09.830 So the last update was that... 02:09.830 --> 02:11.710 Brindle, if you could bring up the Noto, too. 02:11.850 --> 02:13.770 If you can show it on your screen. 02:13.910 --> 02:15.970 I think you have a video set up for it if you want to do that. 02:15.970 --> 02:17.310 Yeah, sure. I can do that. 02:19.890 --> 02:22.410 Oh, Jesus, the light. I'm sorry. Hold on. 02:23.590 --> 02:24.250 No worries. 02:24.310 --> 02:26.670 One second. Let me fix the camera angles to the light. 02:27.250 --> 02:30.110 Abdullah will talk as you do that. Go ahead. 02:30.890 --> 02:36.590 So we've given the factory, the guild, go ahead to manufacture. 02:37.930 --> 02:43.110 And part of the delay is, well, they've got a major holiday coming up 02:43.970 --> 02:51.550 October 1st to the 7th is National China Day or China Week. 02:52.130 --> 02:54.690 Essentially, that's where everything is shut down. 02:54.970 --> 02:56.050 That's part of the delay. 02:57.950 --> 03:02.350 In the meantime, yep, this is the production sample with the new display. 03:02.710 --> 03:04.270 There's been a lot of changes. 03:06.110 --> 03:10.110 So perhaps I could skip over like the... 03:10.110 --> 03:12.650 Well, let's give them the overall updates. 03:12.690 --> 03:15.210 All right, we have the issue with the holiday and whatnot, 03:15.210 --> 03:17.330 but what are we... 03:18.030 --> 03:21.170 What can we say in terms of the risk point? 03:22.470 --> 03:26.830 Yeah, October end might be pushed a week back, 03:27.090 --> 03:32.290 but I made it clear and definitely the process has started. 03:32.730 --> 03:39.470 So I know that despite any unforeseen challenges, 03:39.470 --> 03:44.290 we'll still be able to get these at the end of October 03:44.290 --> 03:45.230 at the very least. 03:46.150 --> 03:47.610 Oh boy, end of our... 03:47.610 --> 03:51.550 Are we guaranteeing that they will be at Moneratopia? 03:52.090 --> 03:53.290 Can we guarantee that? 03:53.590 --> 03:54.470 I mean, obviously, I have... 03:54.470 --> 03:55.430 Yeah, that's the goal. 03:56.370 --> 04:01.570 That's what I've been working for pretty much 24-7. 04:01.950 --> 04:05.030 And so we've kind of been trudging along. 04:05.230 --> 04:06.890 There's a lot of things we've added. 04:07.890 --> 04:12.090 Most notably the new enclosure and display stuff, 04:12.470 --> 04:17.790 but I want to get into like the new stuff that we've added 04:17.790 --> 04:20.470 since we last spoke. 04:20.870 --> 04:22.930 So there's the Monerica, 04:23.750 --> 04:28.170 a directory for the circular economy. 04:28.730 --> 04:31.470 And so that has introduced RSS feeds. 04:32.610 --> 04:36.050 And so that'll show the latest additions 04:36.050 --> 04:37.710 to the Monerocircular economy. 04:38.730 --> 04:41.830 And of course, with XMR Bazaar, 04:41.950 --> 04:47.710 hopefully we'll be able to later add the new additions 04:47.710 --> 04:49.010 in the same way. 04:50.290 --> 04:50.870 And... 04:50.870 --> 04:54.470 Yeah, I'm pretty sure we have RSS feeds set up for that. 04:55.490 --> 04:57.050 Yeah, Monerica is new. 04:57.430 --> 05:00.810 That came out after we implemented the new feeds. 05:01.770 --> 05:05.190 And so along with all the other feeds that we have, 05:05.190 --> 05:06.670 Monerica is a new one. 05:07.330 --> 05:09.090 And then we have new keyboards. 05:09.290 --> 05:12.390 This is based off of customer feedback. 05:13.170 --> 05:15.670 So along with the standard QWERTY keyboard, 05:16.010 --> 05:19.770 we now have AZERD and Quartz, 05:19.970 --> 05:21.890 which is used in Germany, I believe. 05:22.810 --> 05:26.770 And also dedicated a numpad row on that keyboard. 05:27.970 --> 05:30.710 Sync percentage, yeah. 05:31.030 --> 05:34.430 And there's a new Wi-Fi selection menu. 05:34.430 --> 05:37.650 Maybe if you go to device and Wi-Fi. 05:39.770 --> 05:40.090 There we go. 05:40.270 --> 05:43.050 Yeah, I'm kind of cautious on showing it 05:43.050 --> 05:44.550 because my home network is on it too, 05:44.650 --> 05:46.390 and I'd rather not show that. 05:46.550 --> 05:48.070 But it does show networks. 05:49.150 --> 05:50.050 Yeah, we'll get to that. 05:50.230 --> 05:51.470 We'll streamline the menu. 05:52.130 --> 05:55.610 Also mining, we've switched that from P2Pool 05:55.610 --> 05:57.350 to solo mining. 05:57.910 --> 06:00.310 We just thought it might give us 06:00.310 --> 06:03.810 overall better odds of success. 06:03.810 --> 06:05.210 In terms of mining. 06:06.290 --> 06:09.150 And the hash rate, which we've tested, 06:09.650 --> 06:14.430 is not much different to P2Pool mining. 06:14.890 --> 06:16.130 P2Pool was slightly higher. 06:16.650 --> 06:20.690 And with solo mining, we're getting around 700 passes per second, 06:20.850 --> 06:21.990 which is... 06:21.990 --> 06:24.110 Yeah, roughly between 600 and 700, yeah. 06:26.090 --> 06:31.830 Also, we've got a new address lock. 06:32.790 --> 06:36.550 So this will give a new pin locks basically 06:36.550 --> 06:38.570 to lock the device as well as 06:38.570 --> 06:41.070 lock the addresses on your device. 06:41.670 --> 06:46.090 And we'll get into this in a later feature as well. 06:47.010 --> 06:49.610 As well as the standard features 06:49.610 --> 06:55.010 that we've had, Brindle's finish testing, LWS, 06:55.910 --> 06:59.330 remote nodes that you can port forward 06:59.330 --> 07:00.930 and use it over ClearNet, 07:02.050 --> 07:06.130 which was part of the original use case. 07:07.270 --> 07:11.210 So using it over your local network 07:11.210 --> 07:13.130 and also port forwarding 07:13.130 --> 07:16.050 and then using it remotely from another network, 07:16.330 --> 07:19.210 still being able to access your node 07:19.210 --> 07:21.330 at pretty much full speed. 07:22.350 --> 07:24.170 Along with Tor and I2P, 07:24.590 --> 07:26.110 which are slower, but yes, 07:26.230 --> 07:28.330 they do get around a lot of problems 07:28.330 --> 07:32.110 that we've had with node security 07:32.110 --> 07:34.770 and just security in general. 07:35.050 --> 07:38.050 Tor doesn't require port forwarding in any way. 07:38.450 --> 07:40.290 And so if you're using Tor, 07:40.410 --> 07:41.950 which is enabled by default, 07:42.150 --> 07:48.170 then you don't need to go into your router 07:48.170 --> 07:49.630 and change any settings, 07:50.310 --> 07:53.810 port forward settings to access your node remotely. 07:54.230 --> 07:55.210 It will be slower. 07:56.250 --> 07:58.350 You'll need to access your node over Tor, 07:58.590 --> 08:02.130 but you'll know that it's at least your node 08:02.130 --> 08:04.890 and that the protocol, 08:05.330 --> 08:09.170 the transactions are still being communicated 08:09.170 --> 08:12.730 to the node over Tor or I2P. 08:13.850 --> 08:17.230 And then some issues that we had in the field. 08:18.730 --> 08:23.570 Things like corruption, things like this, 08:23.570 --> 08:27.250 a lot of random bugs that we've fixed. 08:27.850 --> 08:30.190 And also there's a recovery button, 08:30.830 --> 08:32.190 perhaps you could show that. 08:37.790 --> 08:39.530 It's a little close by, but there you go. 08:40.690 --> 08:42.410 Please focus. Come on. 08:42.850 --> 08:44.150 These are recessed buttons. 08:44.910 --> 08:46.610 One of them says boot on the left 08:46.610 --> 08:48.550 and one of them says RCBY, 08:48.790 --> 08:49.450 which is recovery. 08:50.170 --> 08:51.390 And what recovery will do 08:51.390 --> 08:54.450 is essentially factory reset your device 08:54.450 --> 08:56.350 in case anything breaks 08:56.350 --> 08:57.910 like your screen isn't turning on. 08:58.470 --> 09:01.830 There's some kind of corruption with blockchain, 09:02.610 --> 09:06.510 any file system type of gremlin 09:06.510 --> 09:07.790 that might have... 09:07.790 --> 09:09.230 You have to understand that 09:10.130 --> 09:13.350 we've tried to keep things as light as possible 09:13.350 --> 09:14.850 in overlinux. 09:15.110 --> 09:18.690 It really is an exceptional performance 09:19.410 --> 09:20.730 with the new hardware. 09:21.470 --> 09:23.570 But the complexity sometimes 09:23.570 --> 09:26.550 can cause unexpected gremlins 09:26.550 --> 09:29.130 and that's what we're still in the process of 09:29.890 --> 09:31.350 QC and finding QC. 09:32.330 --> 09:33.550 To make it all work together, 09:33.770 --> 09:36.790 it's a lot, especially with all the extra features 09:36.790 --> 09:39.450 and bells and whistles around the node itself. 09:41.350 --> 09:41.830 Right. 09:42.770 --> 09:44.290 Another cool new feature, 09:45.330 --> 09:47.470 we've had translation 09:47.470 --> 09:49.970 like 110 different languages. 09:51.510 --> 09:54.430 And so we've added this to news as well. 09:54.730 --> 09:56.750 Previously, news was just English. 09:57.190 --> 09:59.710 But now, no matter what feed it is, 10:01.730 --> 10:04.470 using an open source program 10:05.330 --> 10:06.950 called Libre Translate, 10:07.070 --> 10:08.650 which is running locally on the node, 10:09.670 --> 10:13.570 that's going to give you translations 10:13.570 --> 10:16.170 to pretty much all the languages 10:16.170 --> 10:17.550 that we support. 10:17.690 --> 10:18.950 Oh, that's awesome. That's amazing. 10:19.450 --> 10:21.570 That's a great accessibility feature 10:22.010 --> 10:22.970 for anyone. 10:24.130 --> 10:26.050 And last but not least, 10:26.330 --> 10:28.170 I know there's been a lot of 10:29.450 --> 10:33.030 talk about the Monero circular economy 10:33.030 --> 10:36.150 and Doug has been 10:37.010 --> 10:40.230 kind of tirelessly advocating 10:40.230 --> 10:42.110 for Monero adoption, 10:42.290 --> 10:43.650 pushing for versions 10:43.650 --> 10:45.170 to come on board, 10:45.510 --> 10:46.910 not only personally, 10:47.170 --> 10:49.310 with the show, 10:49.850 --> 10:53.250 but with initiatives like XMR Bizarre. 10:54.350 --> 10:56.030 And so growing the circular economy 10:56.030 --> 10:58.410 has been very important to both of us. 10:59.090 --> 10:59.890 And to that end, 11:00.010 --> 11:02.270 we're very excited to announce a new feature 11:02.270 --> 11:04.710 which will be available on release, 11:05.090 --> 11:07.850 which allows users to accept Monero 11:07.850 --> 11:10.090 directly via your node. 11:10.090 --> 11:11.730 And this is done 11:12.410 --> 11:14.590 via an open source project, 11:14.810 --> 11:15.410 Monero Pay, 11:16.450 --> 11:19.170 which is a simple backing 11:19.170 --> 11:20.750 to receive Monero. 11:21.670 --> 11:23.530 Brindale, there seems to be 11:23.530 --> 11:24.950 some focus issue perhaps. 11:25.410 --> 11:26.210 Oh, I'm sorry. 11:29.110 --> 11:31.530 I was trying to get more lines. 11:31.870 --> 11:33.430 Yeah, if you could pull it out a little, 11:33.550 --> 11:34.670 maybe back away a little bit. 11:35.010 --> 11:36.070 One second. 11:37.230 --> 11:37.470 Okay. 11:37.470 --> 11:41.350 And so bringing merchants 11:41.350 --> 11:43.430 into the Monero circular economy 11:43.430 --> 11:45.130 has been a mission, you know, 11:45.150 --> 11:48.310 that we've been working towards. 11:48.810 --> 11:50.430 And we hope to add in this mission 11:50.430 --> 11:51.930 with Monero Pay, 11:52.530 --> 11:53.750 which presents a simple 11:53.750 --> 11:56.810 non-custodial point-of-sale interface 11:56.810 --> 11:58.630 on Nodo, 11:59.050 --> 12:00.390 and that will 12:01.990 --> 12:04.410 use a center primary wallet 12:04.410 --> 12:05.310 and view key 12:06.350 --> 12:08.430 and it will generate 12:08.430 --> 12:09.450 sub-addresses 12:10.010 --> 12:12.050 and keep a track of 12:12.730 --> 12:14.530 transactions on your device. 12:15.590 --> 12:17.450 And the benefit of this 12:17.450 --> 12:19.130 is that your funds could still be 12:19.130 --> 12:20.490 on your primary wallet, 12:20.730 --> 12:23.770 like your cake or whatever you first created your wallet, 12:24.130 --> 12:26.590 whether it's Monero GUI 12:27.750 --> 12:28.390 or... 12:28.390 --> 12:30.090 And so the wallet is your own. 12:30.190 --> 12:32.670 You just enter the, just like with LWS, 12:32.670 --> 12:34.470 the primary address 12:34.470 --> 12:36.170 and the public view key 12:36.170 --> 12:39.330 and it'll use wallet RPC 12:39.330 --> 12:41.750 to generate sub-addresses 12:41.750 --> 12:44.190 each time we want to receive a payment. 12:44.610 --> 12:46.110 It's still quite a lot of blur. 12:47.870 --> 12:50.850 It is amazing that you guys 12:50.850 --> 12:53.050 developed this additional feature in the meantime, 12:53.250 --> 12:53.850 and I know, 12:54.650 --> 12:56.930 I saw a lot of passion involved with it. 12:57.010 --> 12:58.490 You guys were excited about this one. 12:58.730 --> 12:59.390 You guys, when you were working on it. 12:59.390 --> 13:00.010 Yeah, for sure. 13:00.490 --> 13:02.090 It makes total sense, right? 13:02.190 --> 13:03.770 You have a device with a screen on it. 13:04.490 --> 13:06.450 Nine out of ten times you would be using this 13:06.450 --> 13:08.090 in like a store 13:10.210 --> 13:11.090 sale setting. 13:11.730 --> 13:13.310 Why not put a QR code on it 13:13.310 --> 13:14.070 to receive payments? 13:14.530 --> 13:15.550 It's like perfect for it. 13:16.150 --> 13:17.930 Yeah, it becomes a little POS system. 13:18.630 --> 13:21.230 Yeah, you don't have to whip the phone out 13:21.230 --> 13:22.850 every time you want to accept Monero. 13:23.610 --> 13:25.550 The supermarket is a prime example. 13:26.110 --> 13:27.590 It's there on the kiosk 13:27.590 --> 13:29.640 and that's your dedicated Monero. 13:31.190 --> 13:32.870 I was telling Abdullah 13:32.870 --> 13:35.290 the holy grail would be if we could get to the point 13:35.290 --> 13:36.850 where it then can kind of like 13:36.850 --> 13:39.490 integrate with existing POS systems 13:39.490 --> 13:41.390 like using APIs from 13:41.390 --> 13:42.470 you know, like Square 13:42.470 --> 13:44.750 or these other popular systems 13:44.750 --> 13:47.190 where it could actually 13:47.190 --> 13:48.630 use the hardware. 13:49.790 --> 13:50.190 You know what I'm saying? 13:50.470 --> 13:51.650 I think it can already support that. 13:52.450 --> 13:54.330 Like most of those systems have 13:54.330 --> 13:56.410 like integration with Monero 13:56.410 --> 13:57.630 by themselves. 13:57.870 --> 13:59.890 So if they could be pointed to this as a note 13:59.890 --> 14:01.130 it shouldn't theory work. 14:01.890 --> 14:03.250 Question mark, but I'm not 14:03.250 --> 14:05.470 100% sure that I haven't researched it. 14:08.090 --> 14:09.470 What would you guys 14:10.390 --> 14:11.930 describe as the reasoning 14:11.930 --> 14:13.670 as going in this direction versus 14:14.550 --> 14:15.730 or you know 14:16.230 --> 14:18.190 adding BTC pay server to this thing 14:18.190 --> 14:19.490 or like, you know, what's the 14:20.190 --> 14:21.030 what are the differences? 14:23.090 --> 14:23.890 BTC pay 14:23.890 --> 14:24.950 is quite a beast 14:24.950 --> 14:26.910 in its own. Like it's not that server 14:26.910 --> 14:29.110 I'm not like ragging on it here, but it's quite 14:29.110 --> 14:31.210 large. It needs quite a bit of setup. 14:31.970 --> 14:32.450 It's ideally 14:32.450 --> 14:34.730 ran in Docker, which we don't 14:34.730 --> 14:36.870 use on this device so it would be quite a lot of 14:36.870 --> 14:37.690 overhand in itself. 14:38.750 --> 14:40.590 It's primarily designed for Bitcoin 14:40.590 --> 14:42.230 and it has Monero optionally 14:42.890 --> 14:43.710 slept onto it. 14:44.330 --> 14:47.050 Monero pay is made by people in the Monero community 14:47.050 --> 14:47.810 for Monero. 14:47.810 --> 14:49.690 It's very thin 14:49.690 --> 14:51.490 and it sits between a Monero wallet 14:52.270 --> 14:53.310 and whatever 14:53.310 --> 14:55.730 UI you build on top of it, so it's 14:55.730 --> 14:56.450 perfect for 14:57.250 --> 14:58.470 what we were going for. 14:59.410 --> 15:01.630 This allowed us to keep things really 15:01.630 --> 15:03.730 light and focused on Monero. 15:04.290 --> 15:04.730 Yeah. 15:05.550 --> 15:07.650 Who's been contributing to Monero? Like who's 15:07.650 --> 15:09.270 like the main dev behind Monero pay? 15:09.810 --> 15:11.210 It's two people, Siren 15:11.650 --> 15:14.090 and some other guy that I forgot the name of. 15:15.450 --> 15:16.110 They also 15:16.110 --> 15:18.030 made Metronero, which is their own point 15:18.030 --> 15:19.830 of sale built on top of Monero pay. 15:22.170 --> 15:24.090 I think it's MoneroPay.eu 15:24.090 --> 15:25.630 is how you can get to there. 15:25.890 --> 15:27.710 We gotta get them on the show 15:27.710 --> 15:29.710 or maybe participating in the conference even. 15:31.110 --> 15:31.670 That would be cool. 15:32.410 --> 15:33.250 Yeah, maybe we make 15:33.250 --> 15:35.650 Monero pay part of the 15:37.050 --> 15:38.110 hackathon thing we're doing 15:38.110 --> 15:39.670 with BTC pay server. 15:39.870 --> 15:41.910 Maybe developing on that too could be understanding 15:41.910 --> 15:43.110 and just throwing ideas out there. 15:44.950 --> 15:46.070 Very cool, man. 15:46.250 --> 15:46.890 Very cool guys. 15:47.270 --> 15:49.430 This is super exciting that you've added 15:49.430 --> 15:51.990 the pay terminal feature 15:51.990 --> 15:52.970 in the POS system. 15:55.070 --> 15:56.610 Tux, you got any questions 15:56.610 --> 15:57.610 from what you've seen so far? 15:59.390 --> 16:00.310 Looks pretty cool. 16:00.810 --> 16:01.730 It's a really nice device 16:02.470 --> 16:04.010 and I don't know if this was read out yet. 16:04.150 --> 16:05.750 Your brother tipped $1.23. 16:05.910 --> 16:07.250 How will you guys handle firmware updates 16:07.250 --> 16:09.910 or any other updates to the console, etc.? 16:10.950 --> 16:11.990 The device 16:11.990 --> 16:12.770 runs there too. 16:13.650 --> 16:16.170 It runs an auto-updater that runs once a day 16:16.170 --> 16:17.530 that will include updates 16:17.530 --> 16:19.690 for WM itself 16:20.450 --> 16:21.930 along with updates for 16:21.930 --> 16:23.350 all the sources that are used 16:23.350 --> 16:25.710 for Monero D, Monero Block Explorer 16:26.730 --> 16:27.870 and all the other ones. 16:29.250 --> 16:30.330 They're all tailor made 16:30.330 --> 16:31.550 for each source. 16:31.810 --> 16:33.730 Monero only updates when there's a new release. 16:35.130 --> 16:35.650 LWES 16:35.650 --> 16:37.410 updates when there's a new tag, etc. 16:37.410 --> 16:40.170 It runs that daily. 16:40.370 --> 16:41.390 If you keep the device running 16:41.390 --> 16:42.070 it'll update. 16:42.730 --> 16:44.930 I think it's 3 or 4 in the morning 16:45.610 --> 16:47.190 so it has to be as little 16:47.190 --> 16:49.090 of an inconvenience as possible. 16:51.750 --> 16:52.890 Any chance of firmware? 16:54.130 --> 16:55.190 That is included 16:55.190 --> 16:56.750 with the updates for Linux 16:56.750 --> 16:57.590 as far as I know. 16:58.050 --> 16:59.810 It's actually subscribed to 16:59.810 --> 17:02.490 Flopt, the firmware update manager. 17:02.670 --> 17:03.410 As far as I know, yes. 17:03.410 --> 17:04.530 That's cool. 17:04.990 --> 17:07.570 I have my Nodo 17:07.570 --> 17:08.710 sitting here. 17:09.010 --> 17:11.390 It was sitting dormant for a couple of weeks 17:11.390 --> 17:12.570 just because 17:12.570 --> 17:16.170 mine didn't have 17:16.170 --> 17:16.810 that feature yet 17:16.810 --> 17:18.310 so it needed to be manually updated 17:18.310 --> 17:20.710 but we did it last night. 17:21.350 --> 17:23.630 Now it should have 17:23.630 --> 17:25.050 the late enough software 17:25.050 --> 17:26.170 where it can auto-update. 17:26.310 --> 17:27.210 We'll see tomorrow. 17:27.550 --> 17:29.530 This will be a good test if I wake up to 17:29.530 --> 17:29.830 anyway. 17:30.330 --> 17:31.650 A more functional Nodo. 17:32.570 --> 17:33.730 Perfect test environment. 17:34.390 --> 17:37.070 You can turn the camera on 17:37.070 --> 17:37.670 for a second. 17:38.110 --> 17:39.870 I want to emphasize 17:39.870 --> 17:40.430 that 17:41.890 --> 17:42.550 since 17:44.790 --> 17:46.470 I hope I can 17:46.470 --> 17:48.470 go into this a little bit more 17:48.470 --> 17:49.690 because there's a lot 17:49.690 --> 17:52.370 and it's hard 17:52.370 --> 17:53.790 to communicate all this 17:53.790 --> 17:55.690 via text, via channels 17:55.690 --> 17:55.970 or 17:55.970 --> 17:58.130 what have you. 17:59.250 --> 18:00.290 Just 18:00.290 --> 18:03.270 to give context to the whole thing 18:03.270 --> 18:04.470 we started 18:05.270 --> 18:06.430 late 2021 18:07.470 --> 18:08.990 when I restarted 18:08.990 --> 18:11.650 with this idea 18:11.650 --> 18:12.470 about doing 18:13.330 --> 18:14.650 a plug-and-play node. 18:15.190 --> 18:17.490 I had surveyed 18:17.490 --> 18:18.790 the landscape 18:18.790 --> 18:21.530 and the hypothesis 18:21.530 --> 18:22.730 was that 18:22.730 --> 18:24.270 there's this 18:24.270 --> 18:26.430 huge market for hardware 18:26.430 --> 18:28.530 a lot of it is controlled by these mega 18:28.530 --> 18:29.030 corpse 18:29.030 --> 18:31.450 on the very high end 18:31.450 --> 18:33.290 and on the consumer level 18:34.430 --> 18:35.190 there's 18:35.190 --> 18:36.450 overtime 18:36.450 --> 18:38.510 and erosion of 18:38.510 --> 18:40.710 building stuff 18:40.710 --> 18:42.390 like the hacking culture 18:42.390 --> 18:43.150 that maybe 18:43.930 --> 18:47.390 the early value started out 18:48.470 --> 18:49.650 plugging in 18:49.650 --> 18:51.710 different chips and stuff 18:53.030 --> 18:53.930 trying to 18:53.930 --> 18:54.370 make 18:55.310 --> 18:56.630 all kinds of things 18:56.630 --> 18:57.650 and 18:58.830 --> 19:00.350 given how difficult 19:00.350 --> 19:02.370 it is to get the right 19:03.350 --> 19:05.210 tool and to be able to 19:05.210 --> 19:06.230 even know that 19:06.230 --> 19:09.370 you need a particular set 19:09.370 --> 19:11.330 of tools over something else 19:11.330 --> 19:12.870 for example mobile 19:13.450 --> 19:16.010 everything is pretty much locked down 19:16.010 --> 19:16.950 by the manufacturer 19:16.950 --> 19:18.830 from the get go 19:18.830 --> 19:21.250 there are very few exceptions 19:21.250 --> 19:22.790 I think graphing on 19:22.790 --> 19:24.330 XO is one of them 19:24.690 --> 19:26.210 and it works 19:26.890 --> 19:27.250 great 19:29.210 --> 19:30.410 that's one of the 19:30.950 --> 19:32.910 that's probably the 19:32.910 --> 19:34.890 way to go and part of that 19:34.890 --> 19:37.030 goes back to self-custody 19:37.030 --> 19:38.830 of your hardware and so what 19:38.830 --> 19:41.030 we've built is really just scratching 19:41.030 --> 19:42.710 the surface of what's possible 19:42.710 --> 19:44.870 we've had a vision to 19:44.870 --> 19:45.470 develop 19:46.660 --> 19:47.590 node features 19:48.490 --> 19:50.630 and we've slowly added 19:50.630 --> 19:52.710 usability features 19:52.710 --> 19:55.090 after care for consideration 19:55.090 --> 19:56.970 each time and so 19:56.970 --> 19:58.270 since we started 20:00.670 --> 20:02.570 the hardware spec 20:03.710 --> 20:05.430 along with everything else 20:05.430 --> 20:06.270 has changed 20:06.870 --> 20:08.970 drastically and right now what we're 20:08.970 --> 20:11.110 looking at is the 32GB 20:11.110 --> 20:12.270 model with 20:12.270 --> 20:13.810 all the 20:13.810 --> 20:16.090 iterations that were made 20:16.090 --> 20:17.570 to the enclosure and 20:18.750 --> 20:20.210 UI as well 20:20.210 --> 20:22.230 which is a bespoke UI 20:23.150 --> 20:23.870 using 20:23.870 --> 20:26.190 again Qt open source 20:26.190 --> 20:28.150 and so it's highly custom 20:28.150 --> 20:30.130 and we've 20:30.130 --> 20:32.210 ensured that it's running 20:32.210 --> 20:34.170 off of GPU so it's not going 20:34.170 --> 20:36.190 to take resources away 20:36.190 --> 20:37.770 from whatever 20:37.770 --> 20:40.330 the node is doing at the 20:40.330 --> 20:42.630 time and so what we're 20:42.630 --> 20:44.430 allowing essentially is full control 20:44.430 --> 20:45.130 and 20:46.330 --> 20:47.250 over your 20:48.330 --> 20:50.470 hardware you're free to flash 20:50.470 --> 20:51.270 this to 20:52.130 --> 20:54.030 run whatever OS you're 20:54.030 --> 20:56.170 free to and there's 20:56.170 --> 20:56.890 no essential 20:58.090 --> 21:00.230 lock on hardware 21:00.230 --> 21:01.890 to that extent 21:01.890 --> 21:02.610 and 21:02.610 --> 21:05.910 I mean there's a lot more to 21:05.910 --> 21:07.950 explore with just 21:07.950 --> 21:09.550 node or adding more stuff 21:09.550 --> 21:11.010 as we go along 21:11.010 --> 21:13.450 there's a lot of cool stuff that we had to 21:13.450 --> 21:15.610 leave behind or differ 21:17.470 --> 21:18.030 indefinitely 21:18.030 --> 21:19.750 things cool stuff 21:19.750 --> 21:20.870 like the 21:21.790 --> 21:23.890 TX city I believe it's called 21:23.890 --> 21:25.110 or TX street 21:26.910 --> 21:28.030 yeah that's 21:28.030 --> 21:28.510 a cool thing 21:28.510 --> 21:30.430 I want to get that up there man 21:30.430 --> 21:31.870 I want to get that up there 21:32.890 --> 21:34.950 it would look really fantastic 21:34.950 --> 21:36.370 60 frames per second 21:36.870 --> 21:38.210 running off of 21:38.210 --> 21:39.710 the OLED display 21:39.710 --> 21:42.790 so we'll get there 21:42.790 --> 21:44.910 it's important for us to 21:44.910 --> 21:45.410 really 21:47.250 --> 21:49.250 hunker down and focus on 21:49.250 --> 21:50.670 what really matters 21:50.670 --> 21:53.050 like the original focus 21:53.050 --> 21:54.390 which was to be a node 21:54.930 --> 21:56.770 and maybe if I could just 21:56.770 --> 21:59.310 show like the extent of 22:00.830 --> 22:02.870 yeah I'm going to share my screen 22:02.870 --> 22:04.550 just to show you guys some picture 22:04.550 --> 22:06.750 you think we ever get to the point where 22:06.750 --> 22:08.370 it's like people are 22:08.370 --> 22:10.850 building apps that you could 22:10.850 --> 22:12.290 then you know there's 22:12.650 --> 22:14.470 a Monero Nodo store 22:14.470 --> 22:16.630 where you can download apps 22:16.630 --> 22:18.450 that have run on the Nodo 22:19.790 --> 22:21.450 I think we've already gone 22:21.450 --> 22:23.290 in that direction already 22:23.290 --> 22:25.170 just that we've already 22:25.170 --> 22:26.930 selected LWS 22:26.930 --> 22:27.930 Monero Paying 22:27.930 --> 22:32.030 just to re-iterate 22:32.030 --> 22:33.810 I mean when this project first started 22:33.810 --> 22:34.310 right 22:35.030 --> 22:37.530 our mission was to just create 22:37.530 --> 22:39.890 a plug and play Monero node 22:39.890 --> 22:42.090 at the time the attempt 22:42.090 --> 22:43.950 was the Monero box 22:43.950 --> 22:45.530 which thank you 22:45.530 --> 22:47.690 to that gentleman as well 22:47.690 --> 22:49.410 he was helpful with us in the early days 22:51.030 --> 22:51.670 and 22:51.670 --> 22:53.530 you know we're sitting there we're looking at 22:53.530 --> 22:54.710 we're trying to create basically 22:54.710 --> 22:56.250 the mission was 22:56.250 --> 22:58.290 make it something that 22:58.290 --> 23:00.870 somebody like me can just plug in 23:00.870 --> 23:02.330 and it runs a full node 23:02.330 --> 23:04.090 and that you can then easily 23:04.090 --> 23:06.070 connect your cake wallet 23:06.070 --> 23:07.990 or your Monero user wallet to it 23:07.990 --> 23:09.530 so you're running your own node 23:10.150 --> 23:12.190 using LWS that was really 23:12.190 --> 23:13.410 the feature set 23:13.410 --> 23:16.210 that we were going for which we've achieved 23:16.790 --> 23:17.350 and 23:17.350 --> 23:19.950 Brindle actually I want to ask you about that 23:19.950 --> 23:20.810 how 23:22.410 --> 23:23.750 easy are we 23:23.750 --> 23:25.970 is that at this point but let me just finish 23:25.970 --> 23:27.050 my larger point here 23:27.050 --> 23:29.850 but then from there the project really did grow 23:29.850 --> 23:31.870 once we realize all right we're going to have 23:31.870 --> 23:33.970 these devices sitting on people's desks 23:35.470 --> 23:36.310 why not 23:36.310 --> 23:38.030 what happens if we add a 23:38.030 --> 23:39.790 screen to it and start to just take advantage 23:39.790 --> 23:41.730 of the fact that you now have a narrow 23:41.730 --> 23:43.090 piece of hardware sitting 23:43.090 --> 23:46.030 in people's desks in their stores 23:46.030 --> 23:46.890 in their businesses 23:48.050 --> 23:49.790 and once you add a screen 23:49.790 --> 23:51.170 and things like that 23:51.690 --> 23:53.730 the potential is really endless 23:53.730 --> 23:55.750 with what we can do it can be much 23:55.750 --> 23:57.590 more a Monero 23:57.590 --> 23:59.630 plug-and-play node first and foremost 23:59.630 --> 24:01.350 but it really can be 24:01.350 --> 24:03.370 a piece of hardware that becomes quite usable 24:03.370 --> 24:04.350 for Monero users 24:06.270 --> 24:07.210 yeah so 24:08.030 --> 24:09.030 adding a wall 24:09.030 --> 24:09.530 LWS 24:11.470 --> 24:12.590 yes LWS 24:14.050 --> 24:15.390 it's pretty easy to add 24:15.390 --> 24:17.770 with Monero you have to manually 24:17.770 --> 24:19.790 add the address to LWS 24:19.790 --> 24:21.650 on the device in order to 24:21.650 --> 24:23.650 have it work because my Monero doesn't 24:23.650 --> 24:25.590 send like a request 24:25.590 --> 24:27.590 to add the wallet to it 24:27.590 --> 24:28.930 that's just a my Monero thing 24:29.530 --> 24:31.290 with Edge, Edge does send 24:31.290 --> 24:32.630 a request to 24:34.010 --> 24:35.250 the LWS daemon 24:35.250 --> 24:37.610 on the device and you have a little menu where you can 24:37.610 --> 24:39.510 just hit accept or deny 24:40.250 --> 24:41.670 when it's added it'll 24:42.150 --> 24:43.270 look for new transactions 24:43.270 --> 24:45.630 24-7 or at least as long as you have the node 24:45.630 --> 24:47.450 running and whenever you want 24:47.450 --> 24:48.410 you can load up your 24:48.930 --> 24:50.510 my Monero or Edge wallet 24:50.510 --> 24:52.290 and it'll instantly have your 24:52.290 --> 24:54.770 balance and you're ready to send 24:56.150 --> 24:58.230 with other wallets it's pretty easy to add 24:58.230 --> 25:00.070 you just look up on 25:00.070 --> 25:01.750 networks and then 25:02.410 --> 25:04.650 on ClearNet it'll show the local IP 25:04.650 --> 25:05.770 to which you can connect 25:06.410 --> 25:08.830 I've done it on the official Monero wallet 25:08.830 --> 25:09.830 I've done it on Feather wallet 25:09.830 --> 25:11.410 I've done it on Cake wallet 25:11.410 --> 25:13.130 I've done it on Monerio 25:13.130 --> 25:15.690 and it all works out of the box just fine 25:16.430 --> 25:17.630 it's very easy to do 25:18.370 --> 25:19.750 it's about as straightforward as 25:19.750 --> 25:21.570 any other node except that it shows you 25:21.570 --> 25:22.510 what you need to enter 25:24.150 --> 25:24.630 yeah 25:25.310 --> 25:27.830 the address is displayed and you just enter 25:27.830 --> 25:29.130 that into your node 25:29.130 --> 25:31.270 add as node, enter the address 25:31.270 --> 25:33.610 to be clear though 25:33.610 --> 25:35.310 we're not there with Cake yet right 25:35.310 --> 25:37.870 in terms of using LWS on Cake 25:37.870 --> 25:39.130 yeah Cake does not have LWS 25:39.130 --> 25:41.090 and I would love if it was ended 25:41.090 --> 25:42.250 because it's such a nice feature 25:42.250 --> 25:43.710 same with Monerio 25:43.710 --> 25:45.030 I would love if it would support 25:45.030 --> 25:47.710 Tux you've got to make that happen 25:47.710 --> 25:48.990 I thought we had some 25:49.510 --> 25:51.330 what are you doing here Tux? 25:51.330 --> 25:52.630 we had some pull over 25:52.630 --> 25:53.910 Cake what's going on 25:54.750 --> 25:55.630 we have 25:57.310 --> 25:58.850 definitely talked about it 25:58.850 --> 26:01.590 one of the concerns that was brought 26:01.590 --> 26:02.210 up recently 26:03.490 --> 26:06.010 was in terms of the user experience 26:06.010 --> 26:07.490 because we're thinking about if we had 26:07.490 --> 26:08.290 this feature for 26:09.390 --> 26:10.870 we want to make sure that 26:10.870 --> 26:11.750 we provide 26:12.430 --> 26:14.450 guide tutorials for people to set this up 26:14.450 --> 26:15.450 even without a Monerio node 26:15.450 --> 26:17.350 obviously if they have a Monerio node it's more ideal 26:17.930 --> 26:20.230 and I myself haven't looked into 26:20.230 --> 26:22.310 how simple the setup is yet 26:22.310 --> 26:24.210 because it sounds like it's not the easiest thing to setup 26:24.210 --> 26:26.050 and then of course you have to actually 26:27.610 --> 26:28.410 accept the 26:28.410 --> 26:29.070 the wallet 26:30.970 --> 26:31.770 like invitation 26:32.230 --> 26:33.550 on the LWS side 26:33.550 --> 26:35.930 and that was actually one of my projects this week 26:35.930 --> 26:37.930 that I was going to start yesterday 26:37.930 --> 26:38.390 that 26:39.170 --> 26:40.810 got interrupted abruptly 26:41.450 --> 26:43.810 was setting up LWS on my end 26:43.810 --> 26:45.990 and making sure I understand the flow 26:47.170 --> 26:49.010 so that would be easy enough 26:49.010 --> 26:51.330 but I didn't get to that for obvious reasons 26:52.290 --> 26:53.270 but yeah we're 26:53.270 --> 26:54.410 talking about it 26:55.250 --> 26:55.850 and 26:56.730 --> 26:57.770 we have 26:58.830 --> 27:01.270 so much bandwidth and we're really 27:01.270 --> 27:03.070 trying to hone in on 27:03.070 --> 27:05.070 focusing on fixing a bunch of longstanding 27:05.430 --> 27:06.150 Monerio issues 27:06.890 --> 27:08.650 so we want to deal with that first but 27:08.650 --> 27:09.470 we're definitely 27:11.390 --> 27:12.090 trying to 27:13.470 --> 27:14.470 push for that if we can 27:14.470 --> 27:16.130 at least I am, I want it to happen 27:17.610 --> 27:19.450 but there's certain things that get prioritized 27:19.450 --> 27:20.530 and it's I can't just 27:21.010 --> 27:22.810 say let's do this necessarily myself 27:22.810 --> 27:23.810 because I want to right 27:24.570 --> 27:26.510 but don't worry about trying to make it happen 27:28.550 --> 27:29.810 well if you need any help with it 27:29.810 --> 27:30.670 you know where to find me 27:36.400 --> 27:37.600 yeah like I said 27:39.600 --> 27:40.120 Islands 27:41.740 --> 27:42.480 yeah yeah 27:42.480 --> 27:44.700 come collab with Brindle 27:45.440 --> 27:46.200 I know 27:46.880 --> 27:49.640 Seth said too he had his eye on it 27:49.640 --> 27:50.620 as well so I'm sure 27:50.620 --> 27:53.800 I know Vic will definitely get a little 27:53.800 --> 27:55.540 once he sees these things up and running 27:55.540 --> 27:57.320 and you know people are adding 27:58.000 --> 27:59.460 other competing wallets 27:59.460 --> 28:00.580 with all of the US I'm sure 28:00.580 --> 28:02.280 Kake will quickly 28:02.280 --> 28:03.320 it's such a nice experience 28:03.320 --> 28:05.060 especially when you're out and about 28:05.060 --> 28:07.160 and you're in a store and you don't have to wait 10 minutes 28:07.160 --> 28:08.920 to get the recent like five blocks 28:08.920 --> 28:11.580 yeah have you been 28:11.580 --> 28:12.960 so have you been like living out 28:12.960 --> 28:14.560 have you been using it in that regard 28:15.640 --> 28:16.580 yes I have 28:16.580 --> 28:19.420 mostly online though I haven't found anyone IRL 28:19.420 --> 28:20.880 who wanted to accept Monero 28:20.880 --> 28:21.560 I live in the Netherlands 28:21.560 --> 28:23.460 and people here 28:23.460 --> 28:26.420 they don't even use cash anymore everybody just uses 28:28.340 --> 28:29.120 debit cards 28:29.120 --> 28:30.200 everywhere so 28:31.500 --> 28:33.040 to even begin about Monero 28:33.040 --> 28:34.640 why would I do that 28:34.640 --> 28:36.780 taking over over in your country 28:38.320 --> 28:39.280 any chance 28:39.280 --> 28:41.280 we get you over to Mexico City 28:41.280 --> 28:43.240 no not a chance man I'm sorry 28:44.180 --> 28:44.660 BA 28:44.660 --> 28:46.940 and going to no plan Hannibal or plane 28:46.940 --> 28:48.480 I'm not going to do it sorry 28:49.580 --> 28:51.200 I hate planes I hate heights 28:51.200 --> 28:52.900 I live in the lowest 28:52.900 --> 28:54.320 country in Europe so 28:55.680 --> 28:56.160 okay 28:56.980 --> 28:58.540 maybe I'll see it Monero 28:58.540 --> 29:00.220 we'll come over to him at some point 29:00.220 --> 29:00.700 how about that 29:01.500 --> 29:03.740 maybe you can drive over to Monero 29:03.740 --> 29:05.820 he could make that happen 29:05.820 --> 29:08.620 and Abdullah we were really hoping to have him 29:08.620 --> 29:10.080 in Monero Topia but it's going to be 29:10.080 --> 29:11.920 difficult for him for his 29:11.920 --> 29:14.120 travel situation as well with visas 29:14.120 --> 29:14.640 and stuff 29:15.820 --> 29:17.900 so we'll definitely have a remote 29:19.080 --> 29:19.600 talk 29:19.600 --> 29:22.140 maybe it could be a workshop right because we'll have the 29:22.140 --> 29:22.900 notos there 29:22.900 --> 29:24.960 maybe it could be some kind of remote 29:24.960 --> 29:26.660 workshop but yeah 29:26.660 --> 29:28.320 there'll be a noto presence 29:28.900 --> 29:30.680 if there's ever a Monero Topia 29:30.680 --> 29:32.160 in Europe I will definitely attend 29:33.900 --> 29:34.680 oh word 29:34.680 --> 29:36.300 okay I don't know 29:36.900 --> 29:38.660 that's Monero Khan's 29:38.660 --> 29:40.520 the territory 29:40.520 --> 29:42.000 Monero Khan is in Europe 29:43.580 --> 29:44.120 yeah 29:44.120 --> 29:47.180 we all have weird funny 29:47.180 --> 29:47.600 languages 29:49.200 --> 29:49.980 let me just 29:49.980 --> 29:50.580 pull up 29:52.100 --> 29:53.060 go ahead 29:53.060 --> 29:54.200 ask your question 29:54.200 --> 29:58.020 I have a question about the device 29:58.020 --> 29:58.620 because I remember 29:59.260 --> 30:00.900 in the specs I remember a while 30:01.480 --> 30:03.460 maybe a few months ago there was a change 30:03.460 --> 30:06.020 in regards to I think how much RAM it has 30:06.020 --> 30:07.700 and it also changed the price 30:07.700 --> 30:09.520 so if you could just give clarity 30:09.520 --> 30:10.020 on 30:11.320 --> 30:13.140 what people are getting who had 30:13.140 --> 30:15.300 purchased it at the previous price 30:15.300 --> 30:17.440 with the previous specs are they getting exactly that 30:18.260 --> 30:19.280 true thing 30:19.280 --> 30:21.440 yeah happy to go into that 30:21.440 --> 30:22.700 it's 30:23.430 --> 30:25.180 part of the iterations 30:25.180 --> 30:26.520 that we went through 30:28.280 --> 30:29.500 when we started 30:29.500 --> 30:31.220 out we had 30:31.220 --> 30:33.420 a different processor which was a six 30:33.420 --> 30:35.540 core and as we 30:35.540 --> 30:37.580 gradually built up 30:37.580 --> 30:39.660 new technology also came out 30:39.660 --> 30:41.260 and then the need for better 30:41.260 --> 30:43.840 technology as well like with the display 30:43.840 --> 30:45.400 and so we 30:45.400 --> 30:46.840 then migrated to 30:47.400 --> 30:48.960 from 16 to 30:48.960 --> 30:51.160 32 gigabytes of RAM 30:51.160 --> 30:52.320 and 30:53.300 --> 30:55.300 part of the reason for that is 30:55.300 --> 30:56.740 just to 30:58.640 --> 30:59.640 expand 30:59.640 --> 31:01.120 the usability 31:01.120 --> 31:03.540 of Nodo we found 31:03.540 --> 31:03.960 that 31:05.080 --> 31:06.920 given certain situations 31:06.920 --> 31:09.500 like the black marble attack 31:09.500 --> 31:11.600 some certain nodes were 31:11.600 --> 31:12.380 kind of 31:13.400 --> 31:14.800 struggling and it 31:14.800 --> 31:16.680 wouldn't certainly hurt to have 31:16.680 --> 31:18.580 extra bandwidth and it's 31:18.580 --> 31:20.220 serving us really quite well 31:20.220 --> 31:22.060 it really enables 31:23.300 --> 31:24.800 a whole lot of 31:24.800 --> 31:26.400 other stuff that we can do 31:26.400 --> 31:28.360 with the device that we wouldn't have 31:28.360 --> 31:30.060 been able to otherwise 31:31.680 --> 31:32.880 along with 31:32.880 --> 31:34.000 a terabyte 31:34.000 --> 31:36.320 to a two terabyte SSD 31:36.320 --> 31:38.560 of as standard and so 31:38.560 --> 31:40.480 what you see is pretty much 31:40.480 --> 31:42.320 what everyone will be getting 31:42.320 --> 31:43.360 everyone will be getting 31:43.360 --> 31:46.220 the latest and greatest 31:46.220 --> 31:48.780 Nodo with 32 gigabytes of RAM 31:48.780 --> 31:49.560 with the 31:49.560 --> 31:52.140 two terabytes of SSD 31:52.140 --> 31:53.900 and the 31:53.900 --> 31:56.280 eight core processor and the 31:56.280 --> 31:58.340 fantastic OLED display 31:58.340 --> 32:00.580 along with all the work 32:00.580 --> 32:02.180 that we've put into on 32:02.180 --> 32:03.700 the UI itself 32:05.500 --> 32:08.100 and going forward I think 32:08.100 --> 32:10.080 I should point out that 32:13.900 --> 32:15.260 I would say 32:16.960 --> 32:18.160 to underestimate 32:18.160 --> 32:20.100 the time it would take 32:20.100 --> 32:22.340 to accomplish a project like this 32:22.340 --> 32:22.660 with 32:23.780 --> 32:24.500 the 32:25.220 --> 32:27.580 given the size of our team and 32:28.100 --> 32:29.560 I think it's really quite 32:30.100 --> 32:31.940 an amazing feat that 32:31.940 --> 32:33.200 everyone has 32:33.820 --> 32:35.460 been able to pull together 32:35.460 --> 32:36.600 and 32:36.600 --> 32:38.800 I just want to kind of 32:38.800 --> 32:40.920 give a shout out to the 32:41.080 --> 32:42.720 Minero devs 32:42.720 --> 32:44.900 and Dan Sherman as well 32:44.900 --> 32:45.680 who's been 32:45.680 --> 32:48.560 by Nodexmr 32:48.560 --> 32:49.080 and 32:51.060 --> 32:53.480 so starting point for us 32:53.480 --> 32:54.140 obviously 32:55.100 --> 32:57.360 Nodo has now become its own thing 32:57.360 --> 32:59.880 an entirely different device 33:01.620 --> 33:03.400 partly due to 33:03.400 --> 33:04.920 the nature of 33:04.920 --> 33:06.940 the customizations 33:06.940 --> 33:07.840 for the hardware 33:07.840 --> 33:10.480 but in essence 33:11.100 --> 33:13.280 what Dan has been doing and the devs 33:13.280 --> 33:14.500 have been doing tirelessly 33:14.500 --> 33:16.160 shipping away full time 33:16.160 --> 33:17.500 it really is 33:20.100 --> 33:22.100 it really inspires 33:22.100 --> 33:25.120 to want to build 33:25.120 --> 33:27.220 and things may 33:27.220 --> 33:29.060 take time but definitely 33:29.060 --> 33:30.600 we do have the 33:30.600 --> 33:32.540 the capability to 33:32.540 --> 33:33.520 to build 33:34.240 --> 33:36.640 our own infrastructure and I think 33:36.640 --> 33:38.360 self custody of hardware 33:38.360 --> 33:40.660 and Nodo being kind of like 33:40.660 --> 33:41.700 the low energy 33:42.360 --> 33:44.400 portable device and then 33:46.180 --> 33:48.260 after release we can 33:48.260 --> 33:50.860 look into how to scale that up 33:52.420 --> 33:54.740 one of the things with the Nodo design 33:54.740 --> 33:56.440 was just as with Minero 33:56.440 --> 33:58.520 it was very carefully the 33:58.520 --> 34:00.580 stack and the hardware 34:00.580 --> 34:01.140 and 34:02.180 --> 34:03.600 the things that 34:03.600 --> 34:06.340 made tiny little decisions 34:06.340 --> 34:07.680 things like using 34:08.520 --> 34:10.020 Debian not using Docker 34:10.020 --> 34:12.560 and the custom stuff 34:12.560 --> 34:14.420 like having SSDs on board 34:14.420 --> 34:16.100 having an RTC on board 34:16.100 --> 34:17.920 which is basically 34:17.920 --> 34:20.100 a real tank clock 34:20.100 --> 34:21.620 on your device which 34:22.520 --> 34:24.500 most single board computers don't have 34:25.740 --> 34:27.180 and so all 34:27.180 --> 34:28.060 the 34:28.060 --> 34:29.980 aspect of 34:30.480 --> 34:32.560 moving from 16 gigabyte to 34:32.560 --> 34:34.460 32 gigabyte was really 34:34.460 --> 34:35.340 something that 34:36.260 --> 34:38.720 wasn't an easy decision to 34:38.720 --> 34:40.620 make because we knew 16 would be 34:40.620 --> 34:42.260 great for today but 34:43.300 --> 34:44.680 you know there were 34:44.680 --> 34:46.020 some doubts given 34:46.020 --> 34:47.460 the 34:48.440 --> 34:50.780 future changes to the Minero protocol 34:50.780 --> 34:52.200 where we could see 34:52.200 --> 34:53.620 a serious slight 34:54.200 --> 34:56.080 I think the size increases 34:56.080 --> 34:57.980 to the transaction 35:00.140 --> 35:02.380 before and after the Seraphis 35:02.380 --> 35:03.940 and 35:03.940 --> 35:06.120 possibly with starting with 35:06.120 --> 35:07.840 the full chain membership 35:07.840 --> 35:10.020 as well which is likely to have 35:10.020 --> 35:11.800 some impact 35:11.800 --> 35:13.940 and so 35:14.940 --> 35:16.180 yet working 35:16.180 --> 35:18.180 with Artec who was also 35:18.180 --> 35:20.160 really helpful in 35:21.160 --> 35:22.040 giving 35:22.040 --> 35:23.800 direction as to how 35:23.800 --> 35:25.280 we could 35:26.120 --> 35:27.800 measure our scaling 35:27.800 --> 35:30.100 ability on 35:30.100 --> 35:32.420 device and so 35:34.080 --> 35:35.540 I would say that 35:35.540 --> 35:38.200 what we've come up with is really an 35:38.200 --> 35:40.220 optimal configuration and it didn't 35:40.220 --> 35:42.020 really make sense to 35:42.020 --> 35:43.960 ship a 16G 35:43.960 --> 35:46.080 device especially given 35:46.080 --> 35:48.380 the negligible cost 35:48.380 --> 35:50.240 increase and 35:50.240 --> 35:51.940 the potential 35:51.940 --> 35:54.440 performance benefit as a result 35:55.560 --> 35:56.320 yeah 35:56.320 --> 35:58.260 I mean first and foremost just 35:58.260 --> 36:00.320 going to say Abdulla man amazing job 36:00.320 --> 36:02.380 amazing job obviously had a lot of people 36:02.380 --> 36:04.040 helping you out in different ways I know you 36:04.040 --> 36:06.220 weren't the dev 36:06.220 --> 36:08.100 necessarily coding things 36:08.100 --> 36:10.420 but you were the project 36:10.420 --> 36:12.100 manager the leader the 36:12.100 --> 36:13.820 visionary obviously with my 36:14.080 --> 36:16.300 my far-fetched ideas 36:16.300 --> 36:17.200 but you 36:17.200 --> 36:19.420 you brought it all 36:19.420 --> 36:22.360 into reality into fruition 36:22.360 --> 36:24.340 and you drove it home 36:24.340 --> 36:26.560 amazing job man 36:26.560 --> 36:26.920 and 36:28.080 --> 36:30.060 you have an amazing design 36:30.060 --> 36:32.100 ability I mean you see it in 36:32.100 --> 36:34.220 the way that Nodo itself has designed 36:34.220 --> 36:35.000 the branding 36:35.000 --> 36:37.940 I mean this guy is 36:37.940 --> 36:40.020 an artist in addition to being 36:40.020 --> 36:42.480 a tech 36:42.480 --> 36:43.580 designer savant 36:44.440 --> 36:45.540 and he puts 36:45.540 --> 36:47.540 a ton of effort into these things and he 36:47.540 --> 36:49.620 just has amazing creative abilities 36:50.240 --> 36:51.800 and project management 36:51.800 --> 36:53.740 abilities and amazing amount of 36:53.740 --> 36:55.000 patience oh my god 36:55.440 --> 36:57.440 amazing amount of patience really 36:57.440 --> 36:59.580 so mostly in communicating 36:59.580 --> 37:01.540 with me I can be 37:01.540 --> 37:03.540 quite harsh sometimes god damn it 37:03.540 --> 37:05.240 Abdulla but 37:05.240 --> 37:07.860 he's taking it 37:07.860 --> 37:09.600 taking it to this 37:09.600 --> 37:11.700 far and we will get it across the finish line 37:11.700 --> 37:13.700 and I do want to say 37:13.700 --> 37:15.300 what do I want to say oh yeah 37:15.300 --> 37:17.560 only seven left so 37:17.560 --> 37:18.120 if you go to 37:18.820 --> 37:20.160 add cart here 37:20.160 --> 37:22.840 here's a little thing we might want to fix 37:22.840 --> 37:25.040 I mean it's just a website thing you got to select this first 37:25.040 --> 37:25.420 okay 37:26.440 --> 37:28.140 there's only one color though right 37:28.140 --> 37:30.000 they're all mineral orange 37:31.620 --> 37:32.140 everybody's 37:33.220 --> 37:35.180 getting the founders edition 37:35.700 --> 37:36.740 everybody like 37:37.960 --> 37:39.260 like Abdul has said 37:39.260 --> 37:41.120 is getting the latest upgrades 37:42.420 --> 37:43.060 so I guess 37:43.060 --> 37:44.940 I want to touch on that so people who 37:44.940 --> 37:47.120 had paid before because it was like it was 37:47.120 --> 37:49.180 cheaper before they're basically getting 37:49.180 --> 37:50.800 grandfathered into this new version 37:50.800 --> 37:52.360 I'm understanding what you were saying 37:53.140 --> 37:54.900 yes yes I think we 37:54.900 --> 37:56.920 had asked people to give us 37:56.920 --> 37:58.600 some more payment if they didn't 37:58.600 --> 38:00.040 but it doesn't matter where 38:00.800 --> 38:02.600 people haven't those that haven't 38:03.420 --> 38:05.160 they're being included everybody's 38:05.160 --> 38:06.840 getting everybody's getting a note out here 38:06.840 --> 38:08.940 everybody's getting a note 38:08.940 --> 38:10.360 you get a note out here 38:10.360 --> 38:12.820 let me quickly move the level 38:12.820 --> 38:13.500 real quick 38:14.680 --> 38:15.360 besides 38:16.360 --> 38:18.500 dirty of the pre-order 38:18.500 --> 38:20.120 users did in fact 38:20.120 --> 38:22.340 we did offer them a discounted 38:22.340 --> 38:24.660 price to upgrade like not 38:24.660 --> 38:26.620 the full difference in price 38:26.620 --> 38:28.600 but like half of that 38:28.600 --> 38:30.800 and it's like 38:30.800 --> 38:32.280 almost everyone 38:32.600 --> 38:34.520 had so it wasn't really a thing 38:34.520 --> 38:36.500 we knew everyone was 38:36.500 --> 38:36.940 going to get 38:37.760 --> 38:39.380 everybody was on board 38:41.660 --> 38:44.300 also I want to say in terms 38:44.300 --> 38:45.480 of future 38:46.300 --> 38:47.560 release schedules 38:48.200 --> 38:50.260 it really has been difficult to 38:50.260 --> 38:51.820 time things down and especially 38:51.820 --> 38:53.320 the first time around 38:53.320 --> 38:54.920 there's just so much 38:56.900 --> 38:57.620 different 38:59.020 --> 38:59.740 streams 39:00.360 --> 39:01.920 involved not just software 39:01.920 --> 39:04.060 and I want to say I hope 39:04.060 --> 39:06.040 like the stuff we did 39:06.040 --> 39:07.820 kind of goes skin deep it's not 39:07.820 --> 39:09.840 just the beauty of the enclosure which is 39:09.840 --> 39:10.220 really 39:10.220 --> 39:13.620 a lot of detailing went into that no doubt 39:13.620 --> 39:15.780 but the interface as well 39:15.780 --> 39:17.840 and we hope like a lot of the 39:17.840 --> 39:18.720 logic and 39:19.460 --> 39:21.060 the little stuff 39:21.620 --> 39:23.860 that we hope really gets 39:23.860 --> 39:28.140 a good experience out of 39:28.140 --> 39:29.520 using your note 39:31.920 --> 39:33.860 on your value and narrow tip to 39:33.860 --> 39:35.980 dollar great show as always thank you so much 39:35.980 --> 39:37.620 man thank you so much 39:37.620 --> 39:39.920 and another tremendous thank you 39:39.920 --> 39:40.880 to obviously 39:41.780 --> 39:43.640 you know Abdullah and Brindle 39:43.640 --> 39:45.860 and Cheon and everybody 39:45.860 --> 39:47.320 that's been building it 39:47.320 --> 39:49.200 and Arctic Mind that helped out 39:49.200 --> 39:51.160 and everybody but 39:51.160 --> 39:53.800 to everybody that bought one that was an early 39:53.800 --> 39:55.700 adopter took the risk with us 39:56.420 --> 39:57.440 stayed along 39:57.440 --> 40:00.280 for the long ride and waited patiently 40:00.960 --> 40:02.300 just getting updates 40:02.300 --> 40:04.220 in the chat but being 40:04.220 --> 40:06.240 excited about the fact that we were 40:06.240 --> 40:08.320 continuing to develop on it 40:08.320 --> 40:10.080 tremendous thank you to everybody this thing 40:10.080 --> 40:12.100 absolutely would not happen 40:12.100 --> 40:14.040 if people didn't give us trust 40:14.040 --> 40:16.020 in the beginning so 40:16.020 --> 40:18.320 I thank you for trusting me 40:18.320 --> 40:20.280 because I think that was really the role I 40:20.280 --> 40:21.500 played in this is guys 40:22.160 --> 40:24.220 trust me because I have these people 40:24.220 --> 40:25.780 building it and 40:25.780 --> 40:28.080 people came they took 40:28.080 --> 40:29.920 shot they bought these 40:29.920 --> 40:31.880 without knowing if we'd make it to the finish line 40:31.880 --> 40:33.900 so greatly appreciate all 40:33.900 --> 40:36.060 the early adopters all the founders 40:36.820 --> 40:37.980 it's tremendous help 40:38.700 --> 40:40.140 we're putting a lot of money 40:40.140 --> 40:42.000 into this project at the end of the 40:42.000 --> 40:43.660 day and the fact that everybody 40:43.660 --> 40:46.000 pre-ordered took a lot 40:46.000 --> 40:47.840 of weight off our shoulders we only have 40:47.840 --> 40:49.100 I think we're saying only 40:49.820 --> 40:52.160 yeah we're only saying six left in stock 40:52.160 --> 40:53.920 because we'll have a few that 40:53.920 --> 40:55.760 we'll keep on hand that we're going to bring down 40:55.760 --> 40:57.680 to the conference maybe sell 40:57.680 --> 40:59.700 a few in person but other than that there's 40:59.700 --> 41:01.440 only six that are left to order 41:01.440 --> 41:02.820 online of the first 41:03.500 --> 41:05.700 hundred order this is a really 41:05.700 --> 41:07.320 cool device guys I mean yeah 41:07.320 --> 41:09.620 it cost a little bit of money but 41:09.620 --> 41:11.660 it's very very custom right this 41:11.660 --> 41:13.280 isn't some off to the shelf 41:15.060 --> 41:15.580 rebranded 41:15.580 --> 41:17.500 like no or one of those 41:17.500 --> 41:19.460 small pcs you can buy it's got 41:20.180 --> 41:21.780 a bit more of a custom 41:21.780 --> 41:23.560 hardware which 41:23.560 --> 41:25.780 is pretty cool and of course the actual 41:25.780 --> 41:27.580 case is very high quality 41:27.580 --> 41:28.960 and I've seen I've seen one I 41:29.320 --> 41:29.820 saw it 41:31.680 --> 41:32.720 in Benercon 41:32.720 --> 41:35.380 and then I saw it in New York at Doug's place 41:35.380 --> 41:37.280 a very nice device very high quality 41:37.280 --> 41:39.300 the screens looks amazing 41:39.300 --> 41:41.260 because of the OLED and 41:41.260 --> 41:43.040 it's got really good specs as well 41:43.560 --> 41:45.320 so yeah it's a fully 41:45.320 --> 41:47.420 custom SBC fully custom 41:47.420 --> 41:49.500 case and the price 41:49.500 --> 41:51.500 isn't so bad once you consider the 41:51.500 --> 41:53.280 overall package 41:54.200 --> 41:55.380 it really is 41:55.380 --> 41:57.300 quite quite good value 41:57.300 --> 41:59.380 considering what you get for 41:59.380 --> 42:01.380 your money most mobile 42:01.380 --> 42:03.580 phone started a thousand dollars most 42:03.580 --> 42:05.180 flagships at least start there 42:05.180 --> 42:07.480 and they're not I mean they don't have 42:07.480 --> 42:09.180 this kind of flexibility there 42:09.180 --> 42:11.500 you can't plug in I mean you may be able 42:11.500 --> 42:13.520 to plug in displays and stuff which you can do 42:13.520 --> 42:14.840 with noto but 42:15.360 --> 42:17.260 you know this has ethernet this is like 42:17.260 --> 42:18.760 a conventional computer 42:18.760 --> 42:20.580 and it has 42:20.580 --> 42:21.980 like a super charged 42:22.580 --> 42:24.560 everything all integrations 42:24.560 --> 42:26.700 the ports are the latest the fastest 42:27.300 --> 42:27.900 the 42:28.520 --> 42:30.540 Wi-Fi and the Ethernet 42:30.540 --> 42:32.300 as well and so 42:32.300 --> 42:34.360 it really is a no compromise 42:34.360 --> 42:35.380 approach 42:36.160 --> 42:38.140 and if I remember correctly this is still 42:38.560 --> 42:41.040 this rock chip the RK3588 42:41.040 --> 42:42.500 that's still a 42:42.500 --> 42:45.100 decent amount faster than the Raspberry Pi 5 isn't it 42:45.100 --> 42:46.760 yeah it's way faster 42:46.760 --> 42:47.520 faster 42:48.460 --> 42:50.240 with the 32 gigabyte 42:50.760 --> 42:53.240 RAM and with you know all the integrations 42:53.240 --> 42:55.060 on board there's no bottlenecks 42:55.060 --> 42:55.960 and so 42:56.420 --> 42:58.200 the actual performance is 42:58.200 --> 43:00.700 likely to be you know way higher 43:00.700 --> 43:02.320 especially at higher loads 43:03.600 --> 43:04.320 and 43:05.440 --> 43:06.160 for 43:06.680 --> 43:08.580 next batches I would say we're 43:08.580 --> 43:10.420 I mean this this is probably 43:11.400 --> 43:12.600 we're close to 43:12.600 --> 43:13.300 having 43:14.380 --> 43:16.040 post out the first batch 43:16.040 --> 43:17.740 of the orange devices 43:17.740 --> 43:19.080 the next batches will be 43:19.080 --> 43:20.060 silver and black 43:20.060 --> 43:21.140 and 43:22.220 --> 43:24.760 we might just use a quarterly 43:25.260 --> 43:26.720 release schedule that's just 43:27.040 --> 43:28.740 easier for me to 43:28.740 --> 43:29.520 kind of 43:32.440 --> 43:33.080 because 43:33.080 --> 43:34.960 you know monthly or you know timing 43:34.960 --> 43:37.460 even though future batches are 43:37.460 --> 43:38.920 likely to be more predictable 43:38.920 --> 43:40.580 because there's less 43:40.580 --> 43:42.560 there's less variables 43:42.560 --> 43:43.840 but already have 43:45.040 --> 43:45.760 completed 43:46.540 --> 43:48.480 QC of the software 43:48.480 --> 43:49.020 and 43:50.720 --> 43:52.160 you know 43:52.160 --> 43:54.380 the design has 43:54.380 --> 43:56.940 has already gone through like one major batch 43:56.940 --> 43:57.960 and so 44:01.340 --> 44:02.180 it'll be 44:02.180 --> 44:03.080 just a matter of 44:03.080 --> 44:04.760 kind of saying okay give us 44:04.760 --> 44:05.940 100 more and 44:06.380 --> 44:08.280 just waiting for them to 44:08.280 --> 44:10.340 give us that even though you know it's 44:10.340 --> 44:11.660 tricky China's tricky but 44:12.180 --> 44:14.340 there's always compromises with hardware 44:14.340 --> 44:15.980 right and I personally had to 44:15.980 --> 44:18.400 apply out there to kind of personal risk 44:20.480 --> 44:22.460 maybe I'm exaggerating 44:22.460 --> 44:24.220 but you know it's it's it's always 44:24.220 --> 44:25.500 been a thing 44:26.220 --> 44:27.900 rather without going into like 44:27.900 --> 44:29.900 the CCP aspect 44:29.900 --> 44:31.280 of the whole thing 44:32.440 --> 44:34.140 the industries bunch 44:34.140 --> 44:36.120 and they do 44:36.120 --> 44:37.640 have like the 44:37.640 --> 44:39.700 we did guarantee 44:39.700 --> 44:41.860 certain things like being able to 44:41.860 --> 44:43.620 have like the full schematic 44:43.620 --> 44:45.980 of the hardware that the block 44:45.980 --> 44:47.640 diagram and all the 44:47.640 --> 44:48.780 the whole 44:50.040 --> 44:52.000 diagram of the hardware 44:52.000 --> 44:54.580 layout so that you know 44:54.580 --> 44:56.080 that we can have it 44:56.080 --> 44:58.080 verified and we knew what 44:58.080 --> 44:59.160 we were getting 44:59.960 --> 45:00.760 and so 45:00.760 --> 45:00.860 so 45:03.880 --> 45:04.680 yeah I mean 45:04.680 --> 45:05.280 it's just 45:06.360 --> 45:08.520 it's been a great labor of 45:08.520 --> 45:10.600 love I would say to get to 45:10.600 --> 45:12.180 this point it's really 45:13.180 --> 45:13.660 I mean 45:14.880 --> 45:16.300 I do want to ask 45:16.300 --> 45:18.620 John do I ask this earlier in the show 45:18.620 --> 45:20.500 I hope he's since been convinced 45:20.500 --> 45:22.160 then as to as to why 45:22.160 --> 45:24.400 I use one of these instead of running my idea on a computer 45:24.400 --> 45:26.600 well I think it's right there 45:26.600 --> 45:28.360 it's a unique device 45:28.360 --> 45:29.920 designed for a specific purpose 45:30.680 --> 45:32.200 and yeah you could 45:32.200 --> 45:34.280 run Minera D on a normal computer on any 45:34.280 --> 45:36.200 Linux computer this is just a Linux computer 45:36.200 --> 45:38.260 after all but it comes with a nice 45:38.880 --> 45:40.080 kind of built out 45:40.080 --> 45:41.980 interface for the ecosystem 45:41.980 --> 45:43.620 where you can install stuff easily 45:44.320 --> 45:46.140 and if you're someone who just wants something 45:46.140 --> 45:47.540 that's quick and easy 45:47.540 --> 45:50.360 and will be continually supported 45:51.120 --> 45:52.440 this might be for you 45:52.440 --> 45:54.380 and it's such a cool unique device 45:54.380 --> 45:56.200 anyway by itself 45:56.200 --> 45:57.740 yeah and I think 45:57.740 --> 45:59.720 there's something to the fact that 45:59.720 --> 46:01.920 it is built just first and foremost 46:01.920 --> 46:04.220 for the purposes of running a reliable 46:04.220 --> 46:05.880 plug-and-play dedicated 46:05.880 --> 46:07.600 node as described 46:07.600 --> 46:09.980 right in Minera what is the Minera node 46:09.980 --> 46:11.740 unproved optimized dedicated 46:11.740 --> 46:13.980 dedicated being the keyword right so the idea 46:13.980 --> 46:15.580 is that this thing is running 46:15.580 --> 46:18.260 24-7 plugged in somewhere 46:18.260 --> 46:19.900 and that you're relying on it 46:19.900 --> 46:22.200 as your own personal note can you do it on a 46:22.200 --> 46:23.460 computer sure you can 46:23.460 --> 46:25.700 but this allows you hopefully 46:25.700 --> 46:27.360 to do it in a way where you have a machine 46:27.360 --> 46:29.100 just dedicated for that purpose 46:29.100 --> 46:31.340 so if anything happens with your 46:31.340 --> 46:33.120 computer using for other things now you 46:33.120 --> 46:35.340 just want your node running 24-7 46:35.340 --> 46:37.320 so it's always usable you connect to it 46:37.320 --> 46:39.580 with LWS and then obviously all these 46:39.580 --> 46:41.440 other reasons we're talking about 46:41.440 --> 46:43.280 right because then it becomes more than 46:43.280 --> 46:45.140 just a node becomes 46:45.140 --> 46:47.100 a little Minero computing device 46:47.100 --> 46:49.240 for various Minero related apps 46:49.240 --> 46:50.740 and just like Demi is saying 46:51.660 --> 46:53.020 you know if you're 46:53.020 --> 46:54.760 experienced and you want to do on your computer 46:54.760 --> 46:56.880 that's totally fine but if you're a noob 46:56.880 --> 46:58.680 then yeah setting setting that up 46:58.680 --> 46:59.920 all that stuff up and 47:00.900 --> 47:02.340 not just setting it up but then 47:02.340 --> 47:04.280 maintaining it making sure it works if there's 47:04.280 --> 47:06.440 any problems with it that can be a lot for someone 47:06.440 --> 47:08.700 who's not experienced like not everyone 47:08.700 --> 47:10.280 has their computer on 24-7 47:10.280 --> 47:12.680 yep so this is an easy way 47:12.680 --> 47:13.800 that anybody can go 47:14.420 --> 47:16.740 you plug it in and it just 47:16.740 --> 47:18.320 works you don't have to think about it really 47:18.320 --> 47:19.880 you don't have to think about the source it's 47:19.880 --> 47:22.180 necessary for running a node like 47:22.180 --> 47:23.940 oh do I have 200 gigabyte 47:23.940 --> 47:25.700 spare on my my laptop's hard drive 47:26.040 --> 47:27.920 yeah there's no complexity 47:27.920 --> 47:30.000 that goes with running a node 47:30.000 --> 47:31.580 plus all your other stuff 47:31.580 --> 47:33.600 this is really the recommended way 47:34.320 --> 47:35.920 running a Minero node I would say 47:35.920 --> 47:38.100 just node on device nothing 47:38.100 --> 47:39.420 you know as little 47:39.420 --> 47:41.380 as possible 47:42.000 --> 47:44.420 and so we've really kind of 47:45.700 --> 47:46.560 taken that 47:46.560 --> 47:47.720 to the extreme keeping 47:48.440 --> 47:50.380 just monarity and just a bunch of 47:50.380 --> 47:52.220 value value added 47:52.220 --> 47:53.240 sort of stuff 47:54.400 --> 47:55.860 there's one over there 47:55.860 --> 47:58.320 I do have one more question if I could ask before 47:58.320 --> 47:59.340 move on to the news 48:00.800 --> 48:02.540 built for Tumen 48:02.540 --> 48:04.240 to be able to use it's literally 48:04.240 --> 48:06.760 I was literally the monkey that they're testing 48:06.760 --> 48:07.840 it on so 48:07.840 --> 48:10.060 that is what it's built for 48:10.060 --> 48:10.820 it's built for 48:12.080 --> 48:13.280 node has only 48:14.220 --> 48:15.140 a pin unlock 48:15.140 --> 48:17.300 or possible with a long password too 48:17.920 --> 48:19.120 so there's actually 48:19.120 --> 48:21.240 an admin password that set 48:21.240 --> 48:23.140 up at first boot so the first time 48:23.140 --> 48:25.200 you open up node and you turn it on 48:25.200 --> 48:27.260 you'll be met with a screen you'll have 48:27.260 --> 48:28.640 to change your own password 48:29.120 --> 48:31.140 and we've done this because we didn't want 48:31.140 --> 48:32.480 to just set a default 48:33.060 --> 48:34.440 password Minero node and 48:35.620 --> 48:36.700 have you 48:36.700 --> 48:38.740 you've not changed it ever 48:38.740 --> 48:40.680 and that be a risk to 48:40.680 --> 48:43.040 promote SSH 48:43.040 --> 48:43.820 access 48:44.550 --> 48:46.560 and so you'll be 48:46.560 --> 48:48.200 kind of forced 48:48.200 --> 48:50.400 to set a new pass admin password 48:50.400 --> 48:52.120 for your device at first boot 48:52.680 --> 48:54.520 and you'll be asked to 48:54.520 --> 48:56.720 set your two different 48:56.720 --> 48:58.840 pins one of them being the device pin 48:58.840 --> 49:00.700 which basically locks your screen 49:00.700 --> 49:02.560 right so if you just want to lock 49:02.560 --> 49:04.680 your screen and not be able to access 49:04.680 --> 49:06.580 like the settings on the device 49:06.580 --> 49:08.360 that's one pin 49:08.360 --> 49:10.240 and then there's the address pin 49:10.240 --> 49:12.220 and this is a bit more 49:12.220 --> 49:14.340 complex but it's quite clever 49:14.340 --> 49:16.240 actually what this does is locks all 49:16.240 --> 49:18.260 addresses including the 49:18.260 --> 49:20.220 minor deposit and the Minero 49:20.220 --> 49:22.220 pair address and the idea being 49:22.220 --> 49:23.740 that if 49:24.320 --> 49:26.580 I'm an admin running a bunch of stores 49:26.580 --> 49:28.200 five different stores I have five 49:28.200 --> 49:29.720 devices at each store 49:30.180 --> 49:32.180 and I just set my own 49:32.180 --> 49:33.940 wallet my primary 49:33.940 --> 49:36.440 wallet and view key on each device 49:36.440 --> 49:37.400 and 49:37.400 --> 49:39.980 one set that locks 49:39.980 --> 49:41.640 behind an address pin 49:42.190 --> 49:44.080 and you can only change that 49:44.080 --> 49:46.560 with the special address pin 49:46.560 --> 49:47.320 and so 49:48.170 --> 49:50.500 the idea being that you just need to have them 49:50.500 --> 49:52.560 your anyone can pretty much 49:52.560 --> 49:54.480 use access to the device 49:54.480 --> 49:55.780 without being able to 49:56.440 --> 49:58.000 modify or reroute 49:58.000 --> 49:59.800 payments potentially it's just 50:00.190 --> 50:01.600 one of those. Right yeah if this 50:01.600 --> 50:03.680 NoDo is sitting in you know 50:03.680 --> 50:05.240 one of these Minero 50:05.240 --> 50:07.480 marijuana dispensaries here 50:07.480 --> 50:08.900 where they're accepting Minero 50:08.900 --> 50:10.540 cash and Minero payments 50:10.540 --> 50:13.180 the people working at the store 50:13.180 --> 50:14.780 will have access to the NoDo 50:14.780 --> 50:16.800 to manipulate in some ways 50:16.800 --> 50:19.500 but they won't be able to change the addresses inside 50:19.500 --> 50:20.900 right so it becomes 50:20.900 --> 50:22.480 it becomes a POS system 50:22.480 --> 50:24.820 that can't be taken advantage of 50:24.820 --> 50:26.040 by any of the employees 50:26.040 --> 50:28.480 at a place that's running it 50:28.480 --> 50:31.080 I'll do one more question if I can ask 50:31.860 --> 50:32.660 true good 50:33.560 --> 50:35.220 so you mentioned that 50:36.000 --> 50:37.000 it has 50:37.000 --> 50:39.160 it's including Minero pay I haven't used that 50:39.160 --> 50:41.140 myself personally I would 50:41.140 --> 50:43.200 like to try it out I do really like BTC pay 50:43.200 --> 50:43.540 server 50:44.580 --> 50:45.620 and I know 50:46.720 --> 50:48.940 you were looking into having 50:48.940 --> 50:51.040 that as maybe not coming 50:51.040 --> 50:53.060 with it but being something that could be installed and I know 50:53.060 --> 50:54.380 there's an aversion to Docker 50:55.120 --> 50:57.120 on the device which I don't 50:57.120 --> 50:58.280 really personally have a problem with 50:59.540 --> 51:00.340 would it be 51:00.340 --> 51:02.180 would it be something that you're looking into 51:02.180 --> 51:04.140 maybe like okay so somebody wants 51:04.140 --> 51:06.080 to use BTC pay server there's a script 51:06.080 --> 51:08.140 an easy script that'll just install Docker 51:08.140 --> 51:10.020 and all that stuff for the user if they want to 51:10.460 --> 51:12.020 I could work on that yeah sure 51:13.060 --> 51:14.280 because I mean obviously someone 51:14.280 --> 51:16.120 like me I can just install it if I want to 51:16.120 --> 51:17.460 regardless I'm just thinking of 51:18.380 --> 51:20.180 there's probably going to be a lot of people that 51:20.180 --> 51:22.240 will want BTC pay server anyway just because 51:22.240 --> 51:23.460 of how accessible it is 51:23.460 --> 51:25.820 you can tell me what the benefit of BTC 51:25.820 --> 51:27.180 pay server is over Monero 51:27.180 --> 51:29.080 just curious 51:29.820 --> 51:31.720 I couldn't tell you myself because I haven't actually 51:31.720 --> 51:33.820 used Monero pay I'd like to try out Monero pay 51:33.820 --> 51:34.140 myself 51:35.080 --> 51:36.840 I'll look into it soon for sure 51:36.840 --> 51:39.280 no UI on Monero pay itself right so 51:39.280 --> 51:40.480 that's why I went for it 51:42.600 --> 51:43.940 I didn't really 51:43.940 --> 51:45.180 get a chance to really 51:46.660 --> 51:47.480 talk about 51:47.480 --> 51:49.900 really BTC pay and Monero pay 51:49.900 --> 51:51.740 in depth BTC pay 51:51.740 --> 51:53.620 of course we could certainly 51:53.620 --> 51:55.720 run the BTC pay server 51:55.720 --> 51:57.180 Monero focus store 51:57.180 --> 51:58.380 or otherwise 51:58.980 --> 51:59.540 and 52:00.960 --> 52:03.540 the question remains is what it's going to look 52:03.540 --> 52:05.660 like on device like it's not going to have 52:05.660 --> 52:07.180 integration with 52:07.180 --> 52:08.940 no UI and so 52:08.940 --> 52:11.640 we're going to have to build interfaces or at 52:11.640 --> 52:12.380 least display 52:12.380 --> 52:14.040 the BTC 52:15.180 --> 52:15.740 UI 52:16.480 --> 52:18.440 we could have a little web view for it 52:18.440 --> 52:20.940 yeah that could be done but then you know 52:20.940 --> 52:21.840 it's not going to look 52:21.840 --> 52:23.420 and part of 52:23.420 --> 52:26.540 of course there was the issue with Docker 52:26.540 --> 52:27.100 and 52:28.700 --> 52:30.440 it's not really an issue it's more 52:30.440 --> 52:32.060 a design choice really 52:32.740 --> 52:34.760 and is integrated 52:34.760 --> 52:35.500 as possible 52:36.560 --> 52:38.440 it might be a little bit darker but 52:39.060 --> 52:39.620 yeah 52:41.040 --> 52:42.960 yeah it was very easy 52:42.960 --> 52:45.140 at the beginning to kind of just throw everything 52:45.140 --> 52:46.440 in with Docker that was 52:46.440 --> 52:48.240 like the obvious choice but 52:48.240 --> 52:50.280 at the very beginning we were faced 52:50.280 --> 52:51.720 with this and we kind of 52:51.930 --> 52:53.360 chose to go the 52:54.010 --> 52:55.720 native route basically running 52:56.240 --> 52:57.240 on Linux 52:59.380 --> 53:01.660 and one of the other 53:01.910 --> 53:03.620 advantages with Monero pay is that it 53:03.620 --> 53:04.700 allowed us to 53:06.240 --> 53:07.820 it doesn't have 53:07.820 --> 53:09.900 features BTC pay 53:09.900 --> 53:11.660 server has like you know products 53:12.780 --> 53:13.960 with preset 53:13.960 --> 53:15.320 amounts stuff like that 53:15.320 --> 53:17.280 so it's really very simple 53:17.280 --> 53:18.920 interface which allowed us 53:18.920 --> 53:20.980 to also control the 53:20.980 --> 53:22.940 the front end of it 53:22.940 --> 53:24.040 so it really 53:25.300 --> 53:26.580 fits in with 53:27.140 --> 53:29.180 everything else on 53:29.180 --> 53:30.720 the note of UI 53:31.320 --> 53:32.980 yeah really all Monero 53:32.980 --> 53:35.020 does is it automatically 53:35.020 --> 53:37.080 checks for new payments to certain 53:37.080 --> 53:39.200 addresses that it creates and it has a little callback 53:39.200 --> 53:39.520 URL 53:40.260 --> 53:43.100 that it'll send a request to when 53:43.100 --> 53:44.980 the payment is done which is very easy to work 53:45.580 --> 53:46.140 with 53:46.140 --> 53:49.100 so it's something that's a bit more custom it has to 53:49.100 --> 53:50.880 be taken advantage of 53:50.880 --> 53:53.040 yes and you build the UI 53:53.040 --> 53:55.200 or the thing on top of it 53:55.200 --> 53:56.860 yeah we will 53:56.860 --> 53:59.100 you know we'll have this thing as I said 53:59.100 --> 54:00.920 obviously running at Monero Topia 54:00.920 --> 54:02.820 will be the nodes that people can 54:02.820 --> 54:04.680 connect to locally down there 54:04.680 --> 54:07.120 you know hopefully that will improve 54:07.120 --> 54:09.100 the infrastructure people will be able 54:09.100 --> 54:11.060 to more quickly sync their 54:11.060 --> 54:12.920 wallets but in addition 54:12.920 --> 54:14.620 we'll get a vendor 54:14.620 --> 54:16.740 vendor or two to have 54:16.740 --> 54:18.260 a note of sitting out in front 54:18.260 --> 54:20.620 on their stand perhaps 54:20.620 --> 54:22.360 and we could be testing out 54:22.880 --> 54:24.640 Monero Pay POS system 54:24.640 --> 54:25.720 that would be super cool 54:25.720 --> 54:28.160 at the conference 100% 54:29.100 --> 54:30.880 we're going to have BTC pay there 54:30.880 --> 54:32.740 competing as well so it should be 54:32.740 --> 54:33.580 interesting actually 54:35.180 --> 54:37.140 it amounts to 50 cents 54:37.140 --> 54:38.760 even for non-nodes you want your node 54:38.760 --> 54:40.000 to be isolated not have other 54:40.000 --> 54:42.020 process running while excited as you would 54:42.020 --> 54:44.620 on your Windows or Mac 54:44.620 --> 54:44.900 computer 54:45.840 --> 54:46.960 very true 54:48.980 --> 54:50.100 alright guys 54:50.700 --> 54:52.520 I tortured you guys enough 54:53.260 --> 54:54.320 one more thing 54:54.320 --> 54:55.760 very small thing 54:56.520 --> 54:57.680 because I was thinking about it 54:57.680 --> 55:00.500 it has I2P on board it uses I2PD 55:00.500 --> 55:02.080 which is a simpler implementation 55:02.560 --> 55:04.520 C++ instead of the big bloated 55:04.520 --> 55:05.540 I2P Java 55:05.540 --> 55:07.840 I don't hate it but it's not meant 55:07.840 --> 55:08.860 for this device but 55:09.560 --> 55:11.400 this also means that if you have 55:11.400 --> 55:13.120 your node you can just use it 55:13.120 --> 55:15.680 also alongside it as an I2P 55:15.680 --> 55:17.360 router that you can connect to 55:17.360 --> 55:18.640 so you can use your little 55:19.720 --> 55:21.600 I2P dedicated browser and connect 55:21.600 --> 55:23.920 it to the node and browse I2P websites 55:23.920 --> 55:24.640 if you want to 55:25.600 --> 55:27.720 just a simple 55:27.720 --> 55:29.400 small feature but it's nice to have because it's 55:29.400 --> 55:30.960 another dedicated thing that you just 55:31.460 --> 55:33.520 use it for because I2P works better if you keep 55:33.520 --> 55:35.280 it running for long periods of time 55:35.280 --> 55:37.200 which not everybody with a laptop can do 55:38.460 --> 55:39.740 adoption with I2P 55:40.280 --> 55:41.500 that's always been it's 55:41.500 --> 55:43.140 a QECO and 55:43.140 --> 55:44.880 I would love to see more adoption 55:44.880 --> 55:46.640 than I2P because it's such a cool network 55:49.040 --> 55:49.480 compared 55:49.480 --> 55:50.420 to Tor it's way more 55:50.420 --> 55:52.640 will we take for the node to run a Tor 55:53.460 --> 55:55.320 node no that's not in the cards right 55:55.320 --> 55:56.720 it runs a Tor node 55:56.720 --> 55:58.940 oh it's running a Tor node 55:58.940 --> 56:00.280 and an I2P node 56:00.280 --> 56:02.060 yeah holy shit 56:02.060 --> 56:04.280 and you also have the ability to 56:04.280 --> 56:06.120 route all connections through Tor 56:07.000 --> 56:08.460 so how much space 56:08.460 --> 56:09.780 is that taking up on the node 56:09.780 --> 56:11.660 the Tor node 56:11.660 --> 56:13.540 not a whole lot no 56:14.060 --> 56:15.900 a few megabytes 56:17.620 --> 56:20.220 I obviously have no Tor 56:20.220 --> 56:20.820 knowledge 56:22.520 --> 56:23.360 very cool 56:24.600 --> 56:26.400 amazing yeah because one of the 56:26.400 --> 56:28.120 urban hackers is going to be giving a 56:28.120 --> 56:29.840 workshop on Tor 56:29.840 --> 56:32.120 down at Minerotope as well 56:32.120 --> 56:34.140 and trying to convince people to 56:34.140 --> 56:35.980 run their own Tor node 56:36.760 --> 56:38.140 yeah so in addition 56:38.140 --> 56:39.940 to contributing to the Minerot network 56:39.940 --> 56:41.880 by running your own node you're also contributing 56:41.880 --> 56:43.220 to Tor and I2P 56:43.220 --> 56:47.000 you also get the benefits 56:47.000 --> 56:48.440 of those as well 56:48.440 --> 56:50.540 it's already talking about running an actual 56:50.540 --> 56:52.760 like a Tor Relay 56:52.760 --> 56:53.560 server 56:54.340 --> 56:55.600 yeah maybe that's why 56:55.600 --> 56:57.420 are you talking about like running the Tor 56:57.420 --> 56:59.280 Damon locally for you to use Tor 57:00.080 --> 57:01.560 yeah I mean is there benefits 57:01.560 --> 57:03.360 to the network when you're running a Tor 57:03.360 --> 57:04.940 Damon locally or it's only 57:05.640 --> 57:06.580 not that much 57:06.580 --> 57:07.340 okay 57:09.260 --> 57:11.860 that's what I'm meaning it would be running a Tor Relay 57:11.860 --> 57:13.740 right so to run a Tor Relay 57:13.740 --> 57:15.420 what are the constraints of that 57:15.960 --> 57:16.680 just bandwidth 57:17.160 --> 57:18.280 yeah just a bit of bandwidth 57:19.000 --> 57:21.060 and the very tiny possibility 57:21.520 --> 57:23.420 of the Fats knocking on your door because they think 57:23.420 --> 57:24.960 if you're running an exit 57:26.200 --> 57:27.080 well true 57:27.080 --> 57:29.560 what I'm getting at would it ever make sense to run 57:29.560 --> 57:31.520 Tor Relays on could that be an app 57:31.520 --> 57:33.200 on the no-no would that make sense 57:34.060 --> 57:35.500 it could be a simple 57:35.500 --> 57:37.260 setting it doesn't have to be 57:37.260 --> 57:39.340 a whole app on its own it can just be a simple 57:39.340 --> 57:41.500 setting if you want I could have that 57:41.500 --> 57:41.900 if you want 57:42.880 --> 57:45.260 we've also considered VPN as well 57:45.260 --> 57:47.400 you know incorporating a simple 57:47.400 --> 57:49.700 like just entering your IVP 57:49.700 --> 57:50.640 or low-fat 57:51.500 --> 57:52.860 credentials or something 57:52.860 --> 57:54.520 and just connecting 57:54.520 --> 57:56.240 giving you an interface 57:56.240 --> 57:58.600 to set your VPN on 57:58.600 --> 57:58.960 device 57:58.960 --> 58:01.520 you know there's 58:02.640 --> 58:04.040 we'll just say stop 58:04.040 --> 58:06.060 this is we're going to stop 58:06.270 --> 58:08.040 now and then 58:08.570 --> 58:10.460 we're going to worry about adding 58:10.460 --> 58:12.340 all the cool stuff later 58:12.340 --> 58:14.040 and really 58:14.900 --> 58:15.880 you know 58:15.880 --> 58:18.460 focus on what we do 58:18.460 --> 58:19.460 have currently 58:19.460 --> 58:21.200 which is also cool stuff 58:21.200 --> 58:23.260 yeah and there is 58:23.260 --> 58:25.900 we look forward to hearing from everyone 58:25.900 --> 58:27.480 there's been a lot of great feedback 58:27.480 --> 58:30.120 we've incorporated a lot of stuff based off of 58:30.120 --> 58:30.740 just people 58:32.200 --> 58:34.120 talking on one of the channels 58:34.120 --> 58:36.380 or you know just asking hey 58:36.380 --> 58:37.600 can we do this and 58:38.580 --> 58:40.160 saying yeah we could do that 58:40.160 --> 58:40.880 no problem 58:42.040 --> 58:44.520 accessibility stuff like the keyboards came about 58:44.520 --> 58:46.380 that way Doug he requested 58:46.380 --> 58:48.000 news app news 58:48.000 --> 58:49.400 and you know 58:50.340 --> 58:51.600 nicer display 58:51.600 --> 58:53.740 and so it really has become this 58:54.380 --> 58:56.000 like the cool device 58:56.000 --> 58:57.480 that everyone seems to want 58:57.480 --> 59:00.000 that is going to draw attention to 59:00.000 --> 59:02.280 even though it's really 59:02.280 --> 59:03.920 simplifying the whole process 59:03.920 --> 59:06.200 of getting like the basic 59:06.200 --> 59:07.360 stuff done with it 59:08.160 --> 59:10.060 relaying transactions through it 59:10.060 --> 59:10.920 accepting payments 59:10.920 --> 59:14.280 and LWS 59:14.280 --> 59:15.560 stuff you know accessibility 59:16.060 --> 59:16.340 again 59:17.340 --> 59:19.920 yeah I do really love the idea of adding 59:19.920 --> 59:21.160 potentially Tor relay just keep 59:21.160 --> 59:23.200 putting that on the list of 59:23.200 --> 59:25.620 potential things that we might want to add 59:26.280 --> 59:28.420 I should point out that once this is 59:28.420 --> 59:30.020 out there once you know we'll get there 59:30.020 --> 59:32.280 eventually and once this is 59:32.280 --> 59:33.220 really out there 59:33.980 --> 59:35.920 and we begin to 59:35.920 --> 59:38.260 kind of get into the next batches 59:38.260 --> 59:40.200 I really want to 59:40.200 --> 59:41.900 really have time essentially 59:41.900 --> 59:43.920 to focus on 59:44.820 --> 59:46.180 merchant adoption 59:46.180 --> 59:48.080 I think there's been some talk 59:48.080 --> 59:49.880 about you know getting those 59:49.880 --> 59:51.480 fantastic flyers out there 59:51.480 --> 59:53.760 getting merchants 59:53.760 --> 59:55.700 involved so it could be 59:55.700 --> 59:57.320 kind of layered not just 59:57.900 --> 59:59.740 adoption with Monero but 59:59.740 --> 01:00:01.960 making accessible 01:00:01.960 --> 01:00:03.960 the receiving of payments 01:00:03.960 --> 01:00:06.000 and the whole stack 01:00:06.000 --> 01:00:07.380 of 01:00:07.380 --> 01:00:09.560 that may 01:00:09.560 --> 01:00:09.980 I mean we 01:00:11.000 --> 01:00:13.360 get these to the point where I could start going 01:00:13.360 --> 01:00:15.360 to these weed dispensaries here 01:00:15.360 --> 01:00:17.140 in New York and be like hey you might want to add 01:00:17.140 --> 01:00:19.180 one of these to your store so you can accept 01:00:19.180 --> 01:00:21.220 Monero payments and it integrates 01:00:21.220 --> 01:00:22.280 with your POS like 01:00:23.080 --> 01:00:25.140 that's the holy grail we get to that point right 01:00:25.140 --> 01:00:27.800 and now we're 01:00:27.800 --> 01:00:29.440 we're onboarding stores 01:00:29.440 --> 01:00:33.980 and it's making sense to them 01:00:33.980 --> 01:00:35.280 they're not dealing 01:00:35.280 --> 01:00:37.560 with cash which is 01:00:37.560 --> 01:00:38.740 you know dangerous right where they 01:00:38.740 --> 01:00:40.780 people come in and rob them take all their cash 01:00:41.360 --> 01:00:42.560 they're dealing with 01:00:44.340 --> 01:00:45.640 untraceable digital cash 01:00:45.640 --> 01:00:47.100 that they're 01:00:47.100 --> 01:00:49.500 nobody can steal from the store I mean it's like 01:00:49.500 --> 01:00:51.220 there's real utility there 01:00:52.300 --> 01:00:53.880 we just need to continue 01:00:53.880 --> 01:00:55.700 to build out the ecosystem that 01:00:55.700 --> 01:00:56.680 allows them to do that easily 01:00:56.680 --> 01:00:59.080 I see tux gas trying to move us along 01:00:59.080 --> 01:01:01.520 before we go another tight quest 01:01:01.520 --> 01:01:03.800 until it gets time constrained so am I 01:01:03.800 --> 01:01:04.820 but thank you guys 01:01:04.820 --> 01:01:06.860 for coming on and showing 01:01:06.860 --> 01:01:08.860 showing off the note it's 01:01:08.860 --> 01:01:11.240 very cool product and I'm excited for it myself 01:01:11.240 --> 01:01:12.920 I just want to end on one 01:01:12.920 --> 01:01:14.780 the one last thought right is 01:01:14.780 --> 01:01:16.760 you know the reason we're talking 01:01:16.760 --> 01:01:18.200 about I run a dedicated note 01:01:18.600 --> 01:01:20.920 the reason why I'm running for the noobs out there 01:01:20.920 --> 01:01:22.880 right it's important to run 01:01:22.880 --> 01:01:24.520 your own node so that 01:01:24.520 --> 01:01:26.580 it makes your essentially 01:01:26.580 --> 01:01:28.400 makes your use of Monero 01:01:28.400 --> 01:01:31.100 more untraceable and untrackable 01:01:31.100 --> 01:01:32.860 you're not taking the risk 01:01:32.860 --> 01:01:34.140 of going through some 01:01:34.780 --> 01:01:36.540 you know malicious node 01:01:37.480 --> 01:01:38.800 that's scanning your 01:01:38.800 --> 01:01:40.440 usage of Monero that knows 01:01:40.440 --> 01:01:42.800 every time you're trying to send a Monero transaction 01:01:42.800 --> 01:01:44.020 that can see your IP 01:01:44.020 --> 01:01:46.600 so it allows you to use 01:01:46.600 --> 01:01:48.760 Monero the most private and secure 01:01:48.760 --> 01:01:50.800 way possible when you're running your own 01:01:50.800 --> 01:01:52.500 node and just because 01:01:52.500 --> 01:01:54.460 you're not mining it doesn't mean that you're not 01:01:54.460 --> 01:01:55.940 helping the network by running a node