Latest / Monero Talk / Monero Nodo with Abudllah Khan (Monerotopia23)
Transcript
- 1 00:00:01,720 --> 00:00:24,039 [Applause] 2 00:00:07,840 --> 00:00:27,160 [Music] 3 00:00:24,039 --> 00:00:29,439 and so um uh we've come up with a 4 00:00:27,160 --> 00:00:31,640 configuration that took a lot of work to 5 00:00:29,439 --> 00:00:35,120 come to Hardware stack that we were 6 00:00:31,640 --> 00:00:38,640 happy with and so we're going with a 7 00:00:35,120 --> 00:00:41,840 custom chipset that has been developed 8 00:00:38,640 --> 00:00:46,039 with a lot of uh um considerations in 9 00:00:41,840 --> 00:00:49,719 mind being it portable and also uh being 10 00:00:46,039 --> 00:00:52,559 able to scale with the Monero blockchain 11 00:00:49,719 --> 00:00:55,359 uh for the foreseeable future and so 12 00:00:52,559 --> 00:00:58,239 we're starting with um an opticore 13 00:00:55,359 --> 00:01:01,000 processor and 16 GB of RAM and we'll be 14 00:00:58,239 --> 00:01:03,120 able to have uh terabyt or a couple of 15 00:01:01,000 --> 00:01:06,720 terabytes we're going with one terabyte 16 00:01:03,120 --> 00:01:08,159 of solid state storage and that is um a 17 00:01:06,720 --> 00:01:13,280 fullsize 18 00:01:08,159 --> 00:01:15,439 SSD um that is on board and uh I'll um 19 00:01:13,280 --> 00:01:19,080 that's important because um a lot of 20 00:01:15,439 --> 00:01:21,920 these chipsets have uh external adapters 21 00:01:19,080 --> 00:01:23,759 that plug into the primary chipset and 22 00:01:21,920 --> 00:01:26,880 then you'd be able to plug in a fulls 23 00:01:23,759 --> 00:01:29,960 size SSD or and and so this causes 24 00:01:26,880 --> 00:01:34,280 slowdowns and so we've Incorporated the 25 00:01:29,960 --> 00:01:38,000 M2 slot onto the chipset itself um with 26 00:01:34,280 --> 00:01:40,159 its own heat sink and the GPU will uh 27 00:01:38,000 --> 00:01:42,600 it's a quad core um it's not going to be 28 00:01:40,159 --> 00:01:46,439 used much because the CPU is going to be 29 00:01:42,600 --> 00:01:49,600 doing uh all of the processing of 30 00:01:46,439 --> 00:01:54,360 transactions uh running the rera demon 31 00:01:49,600 --> 00:01:56,200 and uh Power we have USB in and uh 32 00:01:54,360 --> 00:01:58,039 that's useful because if you're out in 33 00:01:56,200 --> 00:02:00,920 the field and we considered this 34 00:01:58,039 --> 00:02:03,039 possibility as well of um it being 35 00:02:00,920 --> 00:02:07,920 deployed out in the field it being in a 36 00:02:03,039 --> 00:02:10,800 backpack or somewhere um and you know um 37 00:02:07,920 --> 00:02:12,879 things of this nature so um it is low 38 00:02:10,800 --> 00:02:17,879 powered and it will support multiple 39 00:02:12,879 --> 00:02:22,080 USBC power sources um and uh uh the 40 00:02:17,879 --> 00:02:25,200 minimum uh wattage will U be revealed um 41 00:02:22,080 --> 00:02:27,560 um in sometime and connectivity was also 42 00:02:25,200 --> 00:02:30,599 important most chipsets do support uh 43 00:02:27,560 --> 00:02:34,239 ethernet and Wi-Fi but we 44 00:02:30,599 --> 00:02:36,560 uh wanted to um get the maximum 45 00:02:34,239 --> 00:02:39,440 bandwidth possible uh to support the 46 00:02:36,560 --> 00:02:42,840 node uh incoming and outgoing um 47 00:02:39,440 --> 00:02:45,959 connections and so we've got a 2.5 gab 48 00:02:42,840 --> 00:02:47,519 gigabit Ethernet and the latest um Wi-Fi 49 00:02:45,959 --> 00:02:50,360 6E with 50 00:02:47,519 --> 00:02:53,519 Bluetooth and uh as well as multiple 51 00:02:50,360 --> 00:02:55,920 other uh USB C's in which you could POS 52 00:02:53,519 --> 00:02:57,800 possibly plug in external storage with 53 00:02:55,920 --> 00:03:00,519 its own blockchain even though you don't 54 00:02:57,800 --> 00:03:03,440 need it you have internal storage 55 00:03:00,519 --> 00:03:06,280 um but other accessories U could 56 00:03:03,440 --> 00:03:10,200 potentially be used uh plugged into to 57 00:03:06,280 --> 00:03:14,080 these additional ports and we also have 58 00:03:10,200 --> 00:03:18,239 a a screen that will allow you to 59 00:03:14,080 --> 00:03:21,760 control uh your node and so the the 60 00:03:18,239 --> 00:03:24,720 highlights of of our implementation is 61 00:03:21,760 --> 00:03:28,280 that we have an unpruned node and it's 62 00:03:24,720 --> 00:03:32,840 not running any other program um like 63 00:03:28,280 --> 00:03:34,760 some um nodes kind of want to tend to do 64 00:03:32,840 --> 00:03:37,159 they they want to try to support 65 00:03:34,760 --> 00:03:40,280 blockchain and ethereum and all this the 66 00:03:37,159 --> 00:03:44,000 focus for uh for me and and for Doug as 67 00:03:40,280 --> 00:03:45,959 well was uh create something that um and 68 00:03:44,000 --> 00:03:48,680 that has security implications as well 69 00:03:45,959 --> 00:03:52,560 being uh and um since we're running 70 00:03:48,680 --> 00:03:55,200 manur natively on Linux um we're able to 71 00:03:52,560 --> 00:03:58,680 get a much more secure and faster 72 00:03:55,200 --> 00:04:01,159 package and we have um Tor and i2p 73 00:03:58,680 --> 00:04:05,480 support as well and and a fully fledged 74 00:04:01,159 --> 00:04:07,480 lws admin this is useful for merchants 75 00:04:05,480 --> 00:04:11,159 or you know users with many wallets 76 00:04:07,480 --> 00:04:15,000 where you can keep track of um incoming 77 00:04:11,159 --> 00:04:17,600 um transactions using um instant like 78 00:04:15,000 --> 00:04:19,880 wordss and so yeah the touchcreen you 79 00:04:17,600 --> 00:04:22,120 can control your node on your device um 80 00:04:19,880 --> 00:04:24,919 or from the web and that includes a 81 00:04:22,120 --> 00:04:27,120 desktop or mobile 82 00:04:24,919 --> 00:04:31,680 platforms and 83 00:04:27,120 --> 00:04:34,919 uh um we we Incorporated uh a dedicated 84 00:04:31,680 --> 00:04:37,320 recovery button uh things go wrong and 85 00:04:34,919 --> 00:04:42,440 we wanted to make this experience of the 86 00:04:37,320 --> 00:04:45,880 node as seamless as possible and uh and 87 00:04:42,440 --> 00:04:49,320 and you know uh so we've developed a a 88 00:04:45,880 --> 00:04:51,880 system where um your configuration is 89 00:04:49,320 --> 00:04:54,440 backed up and so we had to develop the 90 00:04:51,880 --> 00:04:58,120 database for that U you know all putting 91 00:04:54,440 --> 00:05:01,199 all variables uh into one Json file and 92 00:04:58,120 --> 00:05:02,320 and then uh back backing that up and and 93 00:05:01,199 --> 00:05:08,280 and so 94 00:05:02,320 --> 00:05:11,840 on and so um yep we're running uh in A2 95 00:05:08,280 --> 00:05:15,639 LTS um and we started with pyote XMR 96 00:05:11,840 --> 00:05:18,319 because um it does support all types of 97 00:05:15,639 --> 00:05:21,840 single board computers but with that as 98 00:05:18,319 --> 00:05:25,520 a starting point we started to trim and 99 00:05:21,840 --> 00:05:28,080 um tweak uh according to uh our 100 00:05:25,520 --> 00:05:30,039 particular Hardware uh Integrations like 101 00:05:28,080 --> 00:05:32,880 the onboard SSD and 102 00:05:30,039 --> 00:05:35,759 we have on board emmc storage as well 103 00:05:32,880 --> 00:05:38,360 that's um that is used for backups and 104 00:05:35,759 --> 00:05:40,720 things of this nature so that the SSD 105 00:05:38,360 --> 00:05:42,680 and and the CPU can focus primarily on 106 00:05:40,720 --> 00:05:46,520 running the node and it's it's not 107 00:05:42,680 --> 00:05:49,520 bogged down in any case um we did 108 00:05:46,520 --> 00:05:52,199 consider lower possibilities for um 109 00:05:49,520 --> 00:05:55,080 storage capacities with the blockchain 110 00:05:52,199 --> 00:05:57,759 currently sitting at um current less 111 00:05:55,080 --> 00:06:01,919 than 200 gigabytes and and growing at 112 00:05:57,759 --> 00:06:04,919 roughly 60 to 80 gigabytes a year and 113 00:06:01,919 --> 00:06:07,919 and as we Implement surfice that that 114 00:06:04,919 --> 00:06:11,919 could change as well and so there's a 115 00:06:07,919 --> 00:06:16,080 need for a lot of flexibility in the um 116 00:06:11,919 --> 00:06:18,680 in the storage and other um um Hardware 117 00:06:16,080 --> 00:06:21,160 capacities and so we decided to go with 118 00:06:18,680 --> 00:06:22,880 a minimum of a terabyte of storage and 119 00:06:21,160 --> 00:06:27,000 this will support five years of 120 00:06:22,880 --> 00:06:29,039 blockchain growth uh possibly even more 121 00:06:27,000 --> 00:06:32,960 and so we've gone over the recovery 122 00:06:29,039 --> 00:06:36,759 process where you can um it will um you 123 00:06:32,960 --> 00:06:39,599 can uh build Monero from Source um and 124 00:06:36,759 --> 00:06:43,720 the code is all up online uh this the 125 00:06:39,599 --> 00:06:45,919 code will be open source and 126 00:06:43,720 --> 00:06:48,599 um um and so 127 00:06:45,919 --> 00:06:50,919 you you'll be able to kind of see what 128 00:06:48,599 --> 00:06:55,240 it's doing behind the scenes of uh the 129 00:06:50,919 --> 00:06:58,039 recovery process where it can uh you can 130 00:06:55,240 --> 00:07:00,280 erase the blockchain and uh start 131 00:06:58,039 --> 00:07:04,000 syncing from scratch if if you so wish 132 00:07:00,280 --> 00:07:06,319 or in case things go wrong and so um 133 00:07:04,000 --> 00:07:09,160 there are other small things that like 134 00:07:06,319 --> 00:07:11,120 the real-time clock which um not all 135 00:07:09,160 --> 00:07:13,160 single board computers have but is 136 00:07:11,120 --> 00:07:15,960 definitely recommended for security 137 00:07:13,160 --> 00:07:18,560 purposes and so we've uh made efforts to 138 00:07:15,960 --> 00:07:20,520 include an onboard uh module of that 139 00:07:18,560 --> 00:07:25,599 onto the shipset 140 00:07:20,520 --> 00:07:27,639 and um just something that U is uh 141 00:07:25,599 --> 00:07:31,360 Monera specific 142 00:07:27,639 --> 00:07:34,919 uh and also we've developed um well I 143 00:07:31,360 --> 00:07:39,599 have developed a custom case for this 144 00:07:34,919 --> 00:07:41,720 um chipset and it's uh bespoke and 145 00:07:39,599 --> 00:07:45,159 designed from the ground up and we've 146 00:07:41,720 --> 00:07:47,800 considered the terminal uh abilities and 147 00:07:45,159 --> 00:07:51,120 um the overall life cycle we want to be 148 00:07:47,800 --> 00:07:54,639 able to support this for five plus years 149 00:07:51,120 --> 00:07:56,680 um and um the reliability of these ships 150 00:07:54,639 --> 00:07:59,400 are are already well established and 151 00:07:56,680 --> 00:08:01,440 well known and so uh given the right 152 00:07:59,400 --> 00:08:05,080 circumstances in heat management they 153 00:08:01,440 --> 00:08:05,080 will indeed go that 154 00:08:09,599 --> 00:08:14,960 far do you love coffee and Monera as 155 00:08:12,319 --> 00:08:17,560 much as we do consider making gratuitous 156 00:08:14,960 --> 00:08:19,680 org your daily cup pay with Monera for 157 00:08:17,560 --> 00:08:22,000 premium fresh beans and if you like what 158 00:08:19,680 --> 00:08:24,840 you taste send a digital cash tip 159 00:08:22,000 --> 00:08:27,240 directly to the farmers that made it 160 00:08:24,840 --> 00:08:30,540 possible proceeds help us grow this 161 00:08:27,240 --> 00:08:33,679 channel gratuitous and man 162 00:08:30,540 --> 00:08:33,679 [Music] 163 00:08:36,959 --> 00:08:44,600 Arrow it's um it's a CNC um machined 164 00:08:41,519 --> 00:08:48,160 aluminum case and uh it's designed 165 00:08:44,600 --> 00:08:51,120 internally so that it kind of um acts as 166 00:08:48,160 --> 00:08:53,120 a passive heat sink and uh then there 167 00:08:51,120 --> 00:08:57,600 are of course dedicated heat sinks for 168 00:08:53,120 --> 00:09:00,560 the CPU and SSC and uh the top is 169 00:08:57,600 --> 00:09:02,760 removable and just for ease of access 170 00:09:00,560 --> 00:09:05,839 and of course it has all these buttons 171 00:09:02,760 --> 00:09:10,240 the power uh the reset recovery and the 172 00:09:05,839 --> 00:09:14,120 boot buttons um just in case we want to 173 00:09:10,240 --> 00:09:16,600 uh be able to boot from micro SD or or 174 00:09:14,120 --> 00:09:21,120 um the onboard 175 00:09:16,600 --> 00:09:25,040 eimc and this comes around to um once we 176 00:09:21,120 --> 00:09:29,640 have Monero D working on on our chipsets 177 00:09:25,040 --> 00:09:31,600 and uh uh including the um Native block 178 00:09:29,640 --> 00:09:35,839 Explorer and the Manera 179 00:09:31,600 --> 00:09:39,519 WS um we have uh the GPU kind of sitting 180 00:09:35,839 --> 00:09:42,519 idle and this um this issue kind of goes 181 00:09:39,519 --> 00:09:44,760 beyond just our particular chipset um 182 00:09:42,519 --> 00:09:48,279 because even though I would like to try 183 00:09:44,760 --> 00:09:51,079 to implement uh in parallel GPU 184 00:09:48,279 --> 00:09:54,920 processing of those transactions and so 185 00:09:51,079 --> 00:09:56,760 we could expect u a bump in the speed 186 00:09:54,920 --> 00:10:01,279 and 187 00:09:56,760 --> 00:10:04,160 uh to a factor of uh the number of uh 188 00:10:01,279 --> 00:10:09,160 GPU cores that we have and so we have 189 00:10:04,160 --> 00:10:13,959 four cor sitting idle and um using open 190 00:10:09,160 --> 00:10:16,680 CL protocol it is possible to encode uh 191 00:10:13,959 --> 00:10:19,120 transaction um processing when 192 00:10:16,680 --> 00:10:21,320 transaction processing uh and the 193 00:10:19,120 --> 00:10:23,600 challenge to that is the code has to be 194 00:10:21,320 --> 00:10:28,440 written for all the past versions of 195 00:10:23,600 --> 00:10:32,680 mural but I think we could start with um 196 00:10:28,440 --> 00:10:36,040 um when the first versions of bring CD 197 00:10:32,680 --> 00:10:40,360 were implemented and work back for from 198 00:10:36,040 --> 00:10:42,279 that and so I am kind of um still uh 199 00:10:40,360 --> 00:10:45,560 this is one of the items that remains 200 00:10:42,279 --> 00:10:47,600 pending and the implications of of this 201 00:10:45,560 --> 00:10:50,880 particular implementation would go 202 00:10:47,600 --> 00:10:53,760 beyond our uh chipset because anyone 203 00:10:50,880 --> 00:10:57,200 with idle GPU processing power could 204 00:10:53,760 --> 00:11:03,200 potentially be able to 205 00:10:57,200 --> 00:11:07,560 um get much more performance um you 206 00:11:03,200 --> 00:11:11,160 know where otherwise you would have uh 207 00:11:07,560 --> 00:11:15,839 sign your GPU sitting 208 00:11:11,160 --> 00:11:18,160 Idol and uh yep that brings us to uh the 209 00:11:15,839 --> 00:11:21,160 many people uh this has been a global 210 00:11:18,160 --> 00:11:24,399 project uh with many different time 211 00:11:21,160 --> 00:11:27,760 zones and so all the way from Taiwan to 212 00:11:24,399 --> 00:11:30,600 the United States and um our 213 00:11:27,760 --> 00:11:34,200 manufacturers um and many different 214 00:11:30,600 --> 00:11:36,279 developers and along the way um a key 215 00:11:34,200 --> 00:11:40,760 member of 216 00:11:36,279 --> 00:11:44,480 the Arctic mine and Mr Cabanas who 217 00:11:40,760 --> 00:11:49,279 helped a lot with the scaling aspects of 218 00:11:44,480 --> 00:11:53,079 uh um the vision of seeing be able to uh 219 00:11:49,279 --> 00:11:56,000 factor in the many variables uh for 220 00:11:53,079 --> 00:11:59,279 future projection and Dan Sherman of 221 00:11:56,000 --> 00:12:04,519 course who created pyod XMR um uh 222 00:11:59,279 --> 00:12:07,680 without his project um uh it would uh um 223 00:12:04,519 --> 00:12:10,480 um um it's it's been a huge Boon to all 224 00:12:07,680 --> 00:12:13,160 kinds of uh people with idle raspberry 225 00:12:10,480 --> 00:12:16,880 pies lying around and and so it was 226 00:12:13,160 --> 00:12:20,279 indeed the the start for us um and 227 00:12:16,880 --> 00:12:24,279 definitely Dan has been uh great and uh 228 00:12:20,279 --> 00:12:27,680 the other developer Brenda who has um 229 00:12:24,279 --> 00:12:31,600 kind of customized and tweaked and been 230 00:12:27,680 --> 00:12:34,600 our main developer behind 231 00:12:31,600 --> 00:12:37,199 um behind this noo 232 00:12:34,600 --> 00:12:40,120 architecture and our manufacturers as 233 00:12:37,199 --> 00:12:41,880 well and um I wanted to show you some 234 00:12:40,120 --> 00:12:45,440 images of the 235 00:12:41,880 --> 00:12:48,760 prototypes um U bear in mind that uh 236 00:12:45,440 --> 00:12:52,519 this is subject to change our final 237 00:12:48,760 --> 00:12:56,279 prototype um we do have um old 238 00:12:52,519 --> 00:12:59,399 prototypes um around which uh um which 239 00:12:56,279 --> 00:13:02,160 are already Obsolete and so the 16 GB 240 00:12:59,399 --> 00:13:05,120 configuration uh is is undergoing 241 00:13:02,160 --> 00:13:07,560 production the chipsets right now and so 242 00:13:05,120 --> 00:13:11,360 I hope to be able to show you the actual 243 00:13:07,560 --> 00:13:14,320 demonstration at moneron if any of you 244 00:13:11,360 --> 00:13:19,079 um plan to be there or watch the stream 245 00:13:14,320 --> 00:13:24,920 I I it is on the schedule uh to 246 00:13:19,079 --> 00:13:27,920 uh have um actual Uh custom cases for 247 00:13:24,920 --> 00:13:30,240 custom chipsets um and be able to talk 248 00:13:27,920 --> 00:13:30,920 about the the system and show you guys 249 00:13:30,240 --> 00:13:35,160 the 250 00:13:30,920 --> 00:13:37,920 interface and so um I expect a final 251 00:13:35,160 --> 00:13:40,680 shipments a consumer shipments to go out 252 00:13:37,920 --> 00:13:45,240 in uh sometime in 253 00:13:40,680 --> 00:13:50,639 September and um it uh again 254 00:13:45,240 --> 00:13:54,079 U um we do hope that uh this node uh for 255 00:13:50,639 --> 00:13:58,839 a host of reasons uh uh running your own 256 00:13:54,079 --> 00:14:01,279 node is is and why it's beneficial um um 257 00:13:58,839 --> 00:14:04,040 essentially adding much more privacy to 258 00:14:01,279 --> 00:14:06,560 your own transactions and also 259 00:14:04,040 --> 00:14:10,920 contributing to the network and we 260 00:14:06,560 --> 00:14:15,079 imagine uh um a huge number of these um 261 00:14:10,920 --> 00:14:18,320 nodes um causing an impact in um and 262 00:14:15,079 --> 00:14:21,040 mitigating a lot of uh security 263 00:14:18,320 --> 00:14:23,800 vulnerabilities like remote node U 264 00:14:21,040 --> 00:14:26,639 issues um there are complexities to this 265 00:14:23,800 --> 00:14:29,399 issue um because if you are running a 266 00:14:26,639 --> 00:14:31,839 public mod which you can do on this in 267 00:14:29,399 --> 00:14:33,959 which it's accepting incoming uh 268 00:14:31,839 --> 00:14:37,399 transactions and passing them along and 269 00:14:33,959 --> 00:14:41,240 sometimes uh it when it accepts your 270 00:14:37,399 --> 00:14:43,880 transaction sometimes it it does um send 271 00:14:41,240 --> 00:14:46,759 it along uh and 272 00:14:43,880 --> 00:14:50,360 so malicious nodes do remain a threat 273 00:14:46,759 --> 00:14:53,040 but in private mode uh I um it is 274 00:14:50,360 --> 00:14:54,480 definitely better to have your run a 275 00:14:53,040 --> 00:15:01,600 node running 276 00:14:54,480 --> 00:15:04,320 247 as um if you were to open up um your 277 00:15:01,600 --> 00:15:06,360 app or whatever it is and start syncing 278 00:15:04,320 --> 00:15:09,720 with the blockchain and you finish your 279 00:15:06,360 --> 00:15:11,680 transaction and um it downloads a bunch 280 00:15:09,720 --> 00:15:15,040 of blocks and you finish your 281 00:15:11,680 --> 00:15:18,120 transaction and say you just put the app 282 00:15:15,040 --> 00:15:20,480 you're done and when you open that up to 283 00:15:18,120 --> 00:15:22,160 do the next transaction and you know it 284 00:15:20,480 --> 00:15:24,519 starts syncing blocks again from the 285 00:15:22,160 --> 00:15:27,920 that REM note that could also 286 00:15:24,519 --> 00:15:29,120 potentially be used as as a as a marker 287 00:15:27,920 --> 00:15:32,480 and so 288 00:15:29,120 --> 00:15:35,959 um um it's one of the reasons why uh 289 00:15:32,480 --> 00:15:39,600 running your own personal node um uh is 290 00:15:35,959 --> 00:15:42,160 beneficial and uh by not worrying about 291 00:15:39,600 --> 00:15:45,480 other applications running and having a 292 00:15:42,160 --> 00:15:47,040 dedicated and optimized uh system doing 293 00:15:45,480 --> 00:15:51,040 that for you 294 00:15:47,040 --> 00:15:54,680 247 um is um definitely one of the 295 00:15:51,040 --> 00:15:59,959 better or most secure ways of 296 00:15:54,680 --> 00:16:02,600 transacting um Monero and so uh 297 00:15:59,959 --> 00:16:08,279 uh thank you very much for your time and 298 00:16:02,600 --> 00:16:12,600 attention and uh I do look forward to um 299 00:16:08,279 --> 00:16:15,759 um um speaking to uh all of you again 300 00:16:12,600 --> 00:16:18,440 soon as uh this has been my first 301 00:16:15,759 --> 00:16:22,560 introduction to the maner community I've 302 00:16:18,440 --> 00:16:24,839 been a follower of U the whole 303 00:16:22,560 --> 00:16:27,480 philosophical aspect of Monera for quite 304 00:16:24,839 --> 00:16:30,560 some time and and of course I am a 305 00:16:27,480 --> 00:16:33,800 dedicated Monera um I don't care much 306 00:16:30,560 --> 00:16:36,759 about uh the other cryptocurrencies and 307 00:16:33,800 --> 00:16:39,079 so the the focus definitely is Monero 308 00:16:36,759 --> 00:16:42,079 and we hope to be able to deliver on a 309 00:16:39,079 --> 00:16:45,920 seamless U Monero node 310 00:16:42,079 --> 00:16:45,920 experience um thank you very 311 00:16:50,270 --> 00:16:54,450 [Music] 312 00:16:57,480 --> 00:17:00,480 much 313 00:17:03,840 --> 00:17:10,520 [Music]