WEBVTT 00:00:00.010 --> 00:00:03.229 Hello, everybody. Welcome to the stream. I'm 00:00:03.229 --> 00:00:05.809 here with Joe, and today we are going to be talking 00:00:05.809 --> 00:00:09.470 to the PiFi founders. If you guys have not heard 00:00:09.470 --> 00:00:11.509 about PiFi, you're going to hear about them today. 00:00:11.890 --> 00:00:14.910 And all relevant links should be in the link 00:00:14.910 --> 00:00:16.850 in the description below, so you guys can check 00:00:16.850 --> 00:00:20.570 those out. But if Aftermath is ready, we'll bring 00:00:20.570 --> 00:00:23.329 him in. Can you give us a thumbs up? All right. 00:00:24.910 --> 00:00:29.329 How's it going, guys? Welcome. Hello. Hey. I've 00:00:29.329 --> 00:00:33.590 been watching your streams, so I'm finally on 00:00:33.590 --> 00:00:37.049 the stream, finally. It's nice to speak with 00:00:37.049 --> 00:00:40.909 you. Yeah, actually, we've been chatting back 00:00:40.909 --> 00:00:43.969 and forth quite a bit. Joe, nice to meet you 00:00:43.969 --> 00:00:47.770 face -to -face as well. I think Kelvin's going 00:00:47.770 --> 00:00:50.250 to be here today. Yeah, bring him in. Awesome. 00:00:52.270 --> 00:00:57.140 Hello, Kelvin. Hey, guys. Hey. Welcome. yeah 00:00:57.140 --> 00:01:00.000 well just let me mute him on on discord here 00:01:00.000 --> 00:01:04.340 he's he's on discord there we go okay sorry about 00:01:04.340 --> 00:01:09.439 that all right well let's get into it yeah how 00:01:09.439 --> 00:01:12.159 are you guys how are you guys doing today pretty 00:01:12.159 --> 00:01:15.299 good uh good nice weather out get to see the 00:01:15.299 --> 00:01:18.359 ocean glad the weather's nice for you because 00:01:18.359 --> 00:01:21.560 it's not for me it is not for me either i'm up 00:01:21.560 --> 00:01:25.079 in canada the cold the cold canada weather up 00:01:25.079 --> 00:01:27.859 here man we got ice and snow still on the ground 00:01:27.859 --> 00:01:31.040 so that sucks the grass is getting green here 00:01:31.040 --> 00:01:36.219 oh that's nice jealous so do you want to get 00:01:36.219 --> 00:01:38.739 into i guess we could start off with speaking 00:01:38.739 --> 00:01:44.959 of weather ah yeah good transition yeah um what 00:01:44.959 --> 00:01:48.329 got you into crypto I guess that's that's like 00:01:48.329 --> 00:01:50.549 the question everyone asks in an interview is 00:01:50.549 --> 00:01:52.790 like the first thing. How did you find this space? 00:01:53.730 --> 00:01:58.010 Sure. We have a long history and I'm sure Kelvin 00:01:58.010 --> 00:02:02.989 can speak to a bit of it, too. But I got back, 00:02:02.989 --> 00:02:09.889 let's say, 2019, 18. I was dabbling in the crypto 00:02:09.889 --> 00:02:13.430 space. I had a brother who was. a fanatic for 00:02:13.430 --> 00:02:17.250 a period of time who was into bitcoin and then 00:02:17.250 --> 00:02:20.909 into ethereum at a later date but uh ultimately 00:02:20.909 --> 00:02:23.930 he kind of turned me into a bit of a crypto junkie 00:02:23.930 --> 00:02:28.729 myself for a period of time um uh most of my 00:02:28.729 --> 00:02:32.629 experience was uh dabbling in the altcoin space 00:02:32.629 --> 00:02:36.889 to begin with and to be honest you know the altcoin 00:02:36.889 --> 00:02:39.729 space has had its ups and downs as everybody 00:02:39.729 --> 00:02:45.379 knows and It was difficult to gauge who was going 00:02:45.379 --> 00:02:47.840 to be a good project to get into. There was a 00:02:47.840 --> 00:02:51.560 lot of due diligence that I had to get into in 00:02:51.560 --> 00:02:54.280 order to define kind of what my niche was going 00:02:54.280 --> 00:02:59.219 to be in the space. But yeah, I started off, 00:02:59.240 --> 00:03:05.159 to be honest, I started off with a banger. It 00:03:05.159 --> 00:03:09.409 was Block Create. I jumped into their Discord. 00:03:09.710 --> 00:03:13.169 I have one of theirs. Yeah, you do? Yeah. I mean, 00:03:13.210 --> 00:03:15.030 it's nice to have a little bit of light in your 00:03:15.030 --> 00:03:21.030 life, right? But those guys, obviously, something 00:03:21.030 --> 00:03:23.610 happened with them. I don't even know what they're 00:03:23.610 --> 00:03:27.110 doing necessarily at this point. But I started 00:03:27.110 --> 00:03:31.050 off there, and that's where I met a small group 00:03:31.050 --> 00:03:37.259 of the team that exists today for Pi5. Connected 00:03:37.259 --> 00:03:44.240 on fairly odd things, but we found that each 00:03:44.240 --> 00:03:47.680 one of us had some different skill sets. So I've 00:03:47.680 --> 00:03:52.120 been in the IT industry for, well, almost my 00:03:52.120 --> 00:03:56.979 entire career. I'm probably coming in on 15 to 00:03:56.979 --> 00:03:59.840 17 years -ish, I would think, in the professional 00:03:59.840 --> 00:04:04.539 industry on the enterprise side. And we all have 00:04:04.539 --> 00:04:08.610 day jobs. you know we are very open about that 00:04:08.610 --> 00:04:14.569 um and some some of the guys uh came after the 00:04:14.569 --> 00:04:16.870 fact but most of us found each other in block 00:04:16.870 --> 00:04:20.430 create and during that time we noticed that there 00:04:20.430 --> 00:04:23.290 was no utility for that token we figured out 00:04:23.290 --> 00:04:26.829 obviously that it was a dying project ultimately 00:04:27.420 --> 00:04:29.680 at the end of the day and we wanted to bring 00:04:29.680 --> 00:04:32.420 a little life into the project and that's kind 00:04:32.420 --> 00:04:36.839 of where our mutual paths cross because uh juice 00:04:36.839 --> 00:04:40.319 who's not here at the moment but uh you guys 00:04:40.319 --> 00:04:43.579 have discussed a lot for a long time yeah uh 00:04:43.579 --> 00:04:47.199 all in probably most of the conversations you 00:04:47.199 --> 00:04:50.660 guys had was in the blockchain bay or as it was 00:04:50.660 --> 00:04:55.819 before crypto labs um and juice got together 00:04:55.819 --> 00:05:02.060 with kelvin Kelvin started developing what we 00:05:02.060 --> 00:05:04.740 thought was going to be utility for the block 00:05:04.740 --> 00:05:07.319 create token. We were actually thinking, you 00:05:07.319 --> 00:05:09.459 know, a piece of hardware that has some utility 00:05:09.459 --> 00:05:15.819 that could actually function as a node or potentially 00:05:15.819 --> 00:05:20.620 as a miner. We just thought that those ideas 00:05:20.620 --> 00:05:23.879 were kind of at the forefront of what was happening 00:05:23.879 --> 00:05:26.629 in the space at the time. And we just... figured 00:05:26.629 --> 00:05:28.550 hey maybe we can bring some life back into this 00:05:28.550 --> 00:05:32.250 project ultimately we found out pretty quickly 00:05:32.250 --> 00:05:35.149 that if we were going to tie ourselves to a project 00:05:35.149 --> 00:05:38.990 like that and they didn't care about their token 00:05:38.990 --> 00:05:42.949 or their utility or their tokenomics model that 00:05:42.949 --> 00:05:44.750 it just wasn't going to align really well for 00:05:44.750 --> 00:05:48.350 us long term so if we were going to do something 00:05:48.350 --> 00:05:51.680 what were we going to do and that's kind of What 00:05:51.680 --> 00:05:54.319 really got me deep into crypto at that point, 00:05:54.339 --> 00:05:56.500 and I started looking at a lot of the different 00:05:56.500 --> 00:05:59.500 projects out there. Planet Watch was one of them 00:05:59.500 --> 00:06:05.720 as a result, WeatherXM. And then moving on from 00:06:05.720 --> 00:06:09.139 that, even into today's day, every day I'm looking 00:06:09.139 --> 00:06:12.180 at what's going on in the different spaces. A 00:06:12.180 --> 00:06:13.959 lot of these multi -miners that are coming out 00:06:13.959 --> 00:06:18.240 are pretty fascinating. So, yeah, I have a fascination 00:06:18.240 --> 00:06:21.279 for crypto simply based on the concept of what 00:06:21.279 --> 00:06:23.899 it is. And I do believe that there is a true 00:06:23.899 --> 00:06:28.680 utility for cryptocurrency as a it may not be 00:06:28.680 --> 00:06:33.160 a global currency, but it has utility in the 00:06:33.160 --> 00:06:36.360 sense that it decentralizes and it takes that 00:06:36.360 --> 00:06:39.819 responsibility and onus off of. um a one sing 00:06:39.819 --> 00:06:42.480 single individual and and i appreciate that i 00:06:42.480 --> 00:06:44.860 like the idea of that um and i think that'll 00:06:44.860 --> 00:06:47.839 be better for this this world this economy and 00:06:47.839 --> 00:06:53.180 wherever it's headed right now you know so that's 00:06:53.180 --> 00:06:55.800 my story i'll let kelvin maybe chime in too but 00:06:55.800 --> 00:07:03.500 yeah so my story is pretty similar to his we 00:07:03.500 --> 00:07:07.189 kind of all met up and block create uh And originally, 00:07:07.310 --> 00:07:11.569 our idea was pretty similar to the other projects 00:07:11.569 --> 00:07:14.170 that were out there, like PlanetWatch and WeatherXM. 00:07:14.370 --> 00:07:19.629 Let's just make, I guess, an environmental data 00:07:19.629 --> 00:07:24.110 collection miner that could possibly add that 00:07:24.110 --> 00:07:27.269 utility to blocks. But, you know, over time, 00:07:27.449 --> 00:07:32.360 that idea kind of morphed into... giving users 00:07:32.360 --> 00:07:36.699 the ability to add as many sensors as they want 00:07:36.699 --> 00:07:39.600 from any brand or, you know, whatever, and kind 00:07:39.600 --> 00:07:43.339 of visualize it. We kind of noticed that projects 00:07:43.339 --> 00:07:47.800 that were out there were kind of taking hardware 00:07:47.800 --> 00:07:51.740 and in a way scalping or upping the price on 00:07:51.740 --> 00:07:54.540 it, you know, and, you know, really overcharging. 00:07:54.579 --> 00:07:57.480 And we wanted to make a project that was, you 00:07:57.480 --> 00:08:02.620 know, easy barrier to entry. So that's kind of 00:08:02.620 --> 00:08:05.319 how the project kind of came about in terms of 00:08:05.319 --> 00:08:09.579 me and getting involved in crypto. One of my 00:08:09.579 --> 00:08:14.639 first purchases was Dogecoin, surprisingly. And, 00:08:14.639 --> 00:08:16.740 you know, from there, I just kind of started 00:08:16.740 --> 00:08:21.139 digging a bit deeper into the space. And, you 00:08:21.139 --> 00:08:24.600 know, I kind of came across Algorand. I thought 00:08:24.600 --> 00:08:27.540 the developer experience was a lot smoother than 00:08:27.540 --> 00:08:30.660 a lot of the other coins out there. And it just 00:08:30.660 --> 00:08:33.799 kind of took off from there for me. I'm glad 00:08:33.799 --> 00:08:36.259 you brought up Algorand because it had me a question 00:08:36.259 --> 00:08:39.360 that maybe I'll ask a little later. I guess I 00:08:39.360 --> 00:08:44.460 could ask it now. Were you guys exposed to the 00:08:44.460 --> 00:08:48.720 MyAlgo wallet leak or the wallet hack that happened? 00:08:48.779 --> 00:08:54.120 Did that affect you guys at all? No. Well, at 00:08:54.120 --> 00:08:57.320 least not for me personally in any way, or the 00:08:57.320 --> 00:09:02.320 project. At this point in time, we're sitting 00:09:02.320 --> 00:09:05.240 on testnet. So ultimately, the tokens aren't 00:09:05.240 --> 00:09:10.799 necessarily worth anything. But we'll get into 00:09:10.799 --> 00:09:13.700 that, how that's going to transition forward. 00:09:13.860 --> 00:09:18.259 But not me personally and not the project. I 00:09:18.259 --> 00:09:20.480 don't know, Kelvin, if you were exposed to that. 00:09:20.779 --> 00:09:25.120 You never mentioned it, so I assume not. No, 00:09:25.220 --> 00:09:28.919 I wasn't exposed to it. Yeah, but I know what 00:09:28.919 --> 00:09:31.799 was happening there. I mean, that's horrible. 00:09:32.019 --> 00:09:35.980 And what a horrible way for people to experience 00:09:35.980 --> 00:09:40.039 a great, in my opinion, what's going to be a 00:09:40.039 --> 00:09:44.559 great blockchain down the road. I really think 00:09:44.559 --> 00:09:46.220 it's disappointing to see that kind of stuff 00:09:46.220 --> 00:09:48.519 happen to all these smaller projects. But, you 00:09:48.519 --> 00:09:50.340 know, everybody's got to protect themselves, 00:09:50.580 --> 00:09:53.779 protect their wallets. You know, if it's not 00:09:53.779 --> 00:09:58.460 if it's not if you don't own the keys, then you 00:09:58.460 --> 00:10:02.980 don't own the money. So exactly. Yeah. Yeah, 00:10:03.039 --> 00:10:05.460 I think Algorand is a very unique network. It 00:10:05.460 --> 00:10:07.919 was like the first one that I had to interact 00:10:07.919 --> 00:10:10.559 with my phone on and scan a QR code. And there 00:10:10.559 --> 00:10:12.340 was like that separation, which I thought was 00:10:12.340 --> 00:10:16.139 pretty cool to confirm transactions. I noticed 00:10:16.139 --> 00:10:18.899 your website. I was just checking it out before 00:10:18.899 --> 00:10:21.059 the stream. It's changed a lot. You guys have 00:10:21.059 --> 00:10:23.259 improved on it a lot. Do you guys want to touch 00:10:23.259 --> 00:10:25.360 on what's been going on the past? I guess the 00:10:25.360 --> 00:10:27.000 past week you guys have had some interesting 00:10:27.000 --> 00:10:31.720 stuff. For sure. Kelvin. Can probably talk to 00:10:31.720 --> 00:10:35.720 the website changes. Yeah, so there's been a 00:10:35.720 --> 00:10:39.259 few different changes. We're actually kind of 00:10:39.259 --> 00:10:43.379 we've for the past around five or six months, 00:10:43.460 --> 00:10:46.480 we've been working on revamping our software 00:10:46.480 --> 00:10:48.899 and providing, you know, a better experience 00:10:48.899 --> 00:10:51.960 overall. I feel like our first iteration wasn't. 00:10:52.250 --> 00:10:54.809 you know, fully our best. And, you know, we've 00:10:54.809 --> 00:10:56.970 really been working hard to kind of put together 00:10:56.970 --> 00:11:02.389 that new version. We've also included an affiliate 00:11:02.389 --> 00:11:05.750 program that can, you know, anyone can sign up 00:11:05.750 --> 00:11:07.970 for. And with that affiliate program, you'll 00:11:07.970 --> 00:11:11.070 be able to kind of get those referral links and, 00:11:11.110 --> 00:11:13.009 you know, help spread the word about the project 00:11:13.009 --> 00:11:19.480 as well. With the new software. We've got a lot 00:11:19.480 --> 00:11:21.919 of our users were asking for Docker compatibility. 00:11:22.200 --> 00:11:26.200 So we've kind of allowed users to kind of containerize 00:11:26.200 --> 00:11:32.820 the application. access it that way. And what 00:11:32.820 --> 00:11:37.320 also comes with the application is an open API, 00:11:37.460 --> 00:11:40.460 if you will, that would allow you to access the 00:11:40.460 --> 00:11:43.200 raw data of all of your sensors, depending on 00:11:43.200 --> 00:11:45.139 what sensor that you have connected and you put 00:11:45.139 --> 00:11:48.159 in. So there's a lot of great changes with our 00:11:48.159 --> 00:11:50.500 software. So that's kind of what we've been working 00:11:50.500 --> 00:11:53.440 on for the past five or six months. We've had 00:11:53.440 --> 00:11:57.860 a lot of... backlash from our community for taking 00:11:57.860 --> 00:12:01.080 so long but you know we've really been you know 00:12:01.080 --> 00:12:04.559 focusing and putting on the work and give us 00:12:04.559 --> 00:12:08.480 a real quick rundown on what the pie five project 00:12:08.480 --> 00:12:11.539 is about like the entirety of the idea about 00:12:11.539 --> 00:12:15.179 it the challenges that you're trying to provide 00:12:15.179 --> 00:12:19.299 solutions to just the essence of the of the project 00:12:19.299 --> 00:12:24.720 overall Yeah, I can probably answer that to some 00:12:24.720 --> 00:12:27.940 degree here for you guys. You know, PiFi Network 00:12:27.940 --> 00:12:33.279 was created with the intent of allowing people 00:12:33.279 --> 00:12:36.700 to centralize off -the -shelf type products. 00:12:37.570 --> 00:12:41.389 into one visible pane so that you have accessibility 00:12:41.389 --> 00:12:45.850 to that data and to that information in one central 00:12:45.850 --> 00:12:48.289 location. One of the problems that a lot of people 00:12:48.289 --> 00:12:51.029 run into today and part of what we'll probably 00:12:51.029 --> 00:12:56.519 talk about also is we are moving into smart home 00:12:56.519 --> 00:13:00.039 integrations. And so part of the process in doing 00:13:00.039 --> 00:13:03.580 that is finding ways essentially to take these 00:13:03.580 --> 00:13:05.460 off -the -shelf products that people are integrating 00:13:05.460 --> 00:13:07.159 into their homes today with these standalone 00:13:07.159 --> 00:13:12.059 visible UIs. And they're having to access multiple 00:13:12.059 --> 00:13:15.059 applications in order to access the data or visualize 00:13:15.059 --> 00:13:18.519 that data or even control and manage those sensors 00:13:18.519 --> 00:13:21.899 in their homes. So a big part of what we're trying 00:13:21.899 --> 00:13:24.669 to accomplish here is... Bringing all of those 00:13:24.669 --> 00:13:26.909 pieces together so that you have accessibility 00:13:26.909 --> 00:13:30.370 to all that data in one central location. I think 00:13:30.370 --> 00:13:33.710 the power of that also allows us to be able to 00:13:33.710 --> 00:13:38.289 manage and allow for more control of what's happening 00:13:38.289 --> 00:13:41.070 with that data set that you have. You get to 00:13:41.070 --> 00:13:43.129 control that data. You own that data. We're not 00:13:43.129 --> 00:13:45.490 taking the data and telling you that you have 00:13:45.490 --> 00:13:48.149 to go and access it elsewhere or you're not necessarily 00:13:48.149 --> 00:13:50.549 paying for that data either to visualize it. 00:13:50.889 --> 00:13:54.429 in the application itself. So that's one of the 00:13:54.429 --> 00:13:59.629 things that we're addressing. Second to that, 00:13:59.730 --> 00:14:03.250 obviously, people are trying more and more now 00:14:03.250 --> 00:14:07.750 to have more information about what's going on 00:14:07.750 --> 00:14:09.490 in their home when they're not there. So a lot 00:14:09.490 --> 00:14:15.029 of people who are working on... setting up Airbnbs 00:14:15.029 --> 00:14:18.269 or they have remote locations or vacation homes 00:14:18.269 --> 00:14:19.850 that they're trying to monitor while they're 00:14:19.850 --> 00:14:22.950 outside of the house or on vacation somewhere 00:14:22.950 --> 00:14:26.129 else. We're trying to give them the ability to 00:14:26.129 --> 00:14:30.190 control those devices remotely. So on the docket 00:14:30.190 --> 00:14:33.789 for us is a mobile app as well. That's going 00:14:33.789 --> 00:14:37.350 to give you visibility into your sensors and 00:14:37.350 --> 00:14:40.590 what's happening in those locations. You know, 00:14:40.610 --> 00:14:46.100 remote access is something that is always something 00:14:46.100 --> 00:14:48.200 desired when you're talking about smart home 00:14:48.200 --> 00:14:51.460 integration. So remote access to those devices 00:14:51.460 --> 00:14:55.000 is going to be huge. And we do expect, based 00:14:55.000 --> 00:14:59.179 on the multi -platform approach that we're taking, 00:14:59.460 --> 00:15:03.340 that there will be a larger adoption to the mobile 00:15:03.340 --> 00:15:06.759 application. But at the end of the day, you know, 00:15:06.779 --> 00:15:09.559 we're focused currently on that web UI that we 00:15:09.559 --> 00:15:14.690 have locally on the machine. And obviously, you 00:15:14.690 --> 00:15:16.850 guys know that we've been working on it for so 00:15:16.850 --> 00:15:19.610 long at this point. There's so many pieces that 00:15:19.610 --> 00:15:22.690 we want to integrate. And eventually, some of 00:15:22.690 --> 00:15:25.690 the things that, and to give you a sneak peek 00:15:25.690 --> 00:15:27.490 or whatever, I'm sure Kelvin can show you what 00:15:27.490 --> 00:15:29.830 the new UI in the Windows environment looks like. 00:15:30.029 --> 00:15:32.309 It's exactly the same as what you'll see on a 00:15:32.309 --> 00:15:36.590 pie. But you'll see that we have some sneak peek. 00:15:37.600 --> 00:15:41.820 menu systems that will give you a heads up as 00:15:41.820 --> 00:15:43.620 to some of the things that we're working on so 00:15:43.620 --> 00:15:46.720 in order for you to kind of know what's going 00:15:46.720 --> 00:15:49.039 on you'll have to check out the app but basically 00:15:49.039 --> 00:15:54.860 our our ideal goal down the road here is to allow 00:15:54.860 --> 00:15:58.820 for automation to happen within your your home 00:15:58.820 --> 00:16:03.179 within your devices and allow that type of automation 00:16:03.179 --> 00:16:05.950 and control and potentially And I don't want 00:16:05.950 --> 00:16:08.809 to say AI at this moment because we'll address 00:16:08.809 --> 00:16:12.309 that when we come to it. But we've got a lot 00:16:12.309 --> 00:16:16.049 of interest in that kind of realm of things in 00:16:16.049 --> 00:16:18.970 the conversations we're having on the dev chat. 00:16:20.470 --> 00:16:25.389 Excellent. So what kind of data are you looking 00:16:25.389 --> 00:16:30.330 to collect? Well, I think that it all depends. 00:16:31.129 --> 00:16:33.970 Well, we're open to collecting all types of data. 00:16:34.049 --> 00:16:40.629 We're not just focused on just, I know that we 00:16:40.629 --> 00:16:43.309 get put into a box, right? We get put into a 00:16:43.309 --> 00:16:44.850 box depending on the sensors that we integrate 00:16:44.850 --> 00:16:48.889 first. And I don't want to be rude in saying 00:16:48.889 --> 00:16:51.049 that we're not interested in that because that's 00:16:51.049 --> 00:16:55.769 certainly, like all the error element data that's 00:16:55.769 --> 00:17:00.679 coming out. And atmospherical data, it's great. 00:17:01.019 --> 00:17:04.440 And we love that type of data. But we're also 00:17:04.440 --> 00:17:07.359 talking about moving into soil moisture sensors. 00:17:08.299 --> 00:17:11.000 We're also talking about weather data right now, 00:17:11.220 --> 00:17:17.299 outside and inside. And we're talking about power. 00:17:18.380 --> 00:17:21.420 power consumption data, water consumption data. 00:17:22.160 --> 00:17:25.119 And these are things, honestly, you know, the 00:17:25.119 --> 00:17:31.339 broader conversation is if we target those categories 00:17:31.339 --> 00:17:36.900 more broadly, there's opportunity for the individuals 00:17:36.900 --> 00:17:39.059 that are collecting that data or using that data 00:17:39.059 --> 00:17:43.250 for themselves. to circumvent certain types of 00:17:43.250 --> 00:17:47.549 expectations from insurance companies, being 00:17:47.549 --> 00:17:50.990 able to prove out that your house has not had 00:17:50.990 --> 00:17:53.750 any level of humidity over a period of time, 00:17:53.930 --> 00:17:58.150 saving you money ultimately at the end, and also 00:17:58.150 --> 00:18:00.690 for homeownership, you know, inspections that 00:18:00.690 --> 00:18:02.309 are happening in your homes. Think about it. 00:18:02.589 --> 00:18:04.849 You know, from that perspective, if we can get 00:18:04.849 --> 00:18:07.210 into those different categories more broadly, 00:18:07.369 --> 00:18:10.349 I'm certain that all types of data is going to 00:18:10.349 --> 00:18:14.529 be on the table for us. And honestly, anything 00:18:14.529 --> 00:18:18.829 that integrates to a smart home integration in 00:18:18.829 --> 00:18:22.650 whatever your eyes that is, we're likely going 00:18:22.650 --> 00:18:24.809 to be open to the idea of adopting it. We've 00:18:24.809 --> 00:18:27.990 had community members post things that we found 00:18:27.990 --> 00:18:31.130 interesting and decided, why not? Why not integrate 00:18:31.130 --> 00:18:35.029 it? um so if that's of interest to any of the 00:18:35.029 --> 00:18:37.009 community members that might be in the chat or 00:18:37.009 --> 00:18:41.730 or uh come across us through this video uh drop 00:18:41.730 --> 00:18:43.950 us a line in the discord we're very active in 00:18:43.950 --> 00:18:46.470 our discord anytime we see things we're always 00:18:46.470 --> 00:18:49.549 responding and uh and we love that interaction 00:18:49.549 --> 00:18:52.869 without the community we got nothing so i apologize 00:18:52.869 --> 00:18:55.309 if it seems like i'm asking very basic questions 00:18:55.309 --> 00:18:58.589 but i think the most the audience here is very 00:18:58.589 --> 00:19:02.180 new to this project itself so trying to lay the 00:19:02.180 --> 00:19:05.059 foundational groundwork to that so let's say 00:19:05.059 --> 00:19:08.019 someone wants to be involved in pi fi and earning 00:19:08.019 --> 00:19:10.240 on the network or just involved with the project 00:19:10.240 --> 00:19:12.220 overall what were the first steps for them to 00:19:12.220 --> 00:19:18.319 be kelvin let's get him involved oh sure uh one 00:19:18.319 --> 00:19:21.140 of the first steps would be to purchase a license 00:19:21.140 --> 00:19:26.339 from our web page um Once you purchase a license, 00:19:26.680 --> 00:19:30.720 right now we're working on that support for Linux 00:19:30.720 --> 00:19:37.619 and Windows. So for Windows, it just depends 00:19:37.619 --> 00:19:39.779 on what kind of sensors you have. Ultimately, 00:19:39.900 --> 00:19:43.700 we support the Aware Element, the SenseEdge Mini, 00:19:44.059 --> 00:19:47.099 the AtmoTube, which is kind of in beta right 00:19:47.099 --> 00:19:53.359 now. And then we have the Kasa Energy Smart Plug. 00:19:54.109 --> 00:20:01.150 Um, we have the HT 20, um, and the PM 2 .5. Um, 00:20:01.250 --> 00:20:06.009 so, uh, a lot of those are indoor, but ultimately 00:20:06.009 --> 00:20:08.730 we do plan on like a aftermath looted to going 00:20:08.730 --> 00:20:10.990 into outdoor, but, uh, essentially you would 00:20:10.990 --> 00:20:14.990 need one of those sensors. Um, and then, uh, 00:20:15.130 --> 00:20:17.829 if you decide to send data to the network, you 00:20:17.829 --> 00:20:20.769 would just need a GPS module, uh, because the 00:20:20.769 --> 00:20:31.440 VK, uh, uh, And then that's it, really. I have 00:20:31.440 --> 00:20:34.220 links for most of the sensors in the description 00:20:34.220 --> 00:20:37.799 below, as well as the GPS modules. If you're 00:20:37.799 --> 00:20:39.880 on the web page and you're looking for the supported 00:20:39.880 --> 00:20:42.940 list of sensors, just check out the light paper. 00:20:43.440 --> 00:20:46.059 And at the very bottom two pages, I believe that 00:20:46.059 --> 00:20:48.140 we list everything that's currently supported. 00:20:49.349 --> 00:20:52.609 Is the website currently still undergoing changes 00:20:52.609 --> 00:20:55.509 as you guys posted in your announcements in the 00:20:55.509 --> 00:20:57.869 Discord server? I know you were having. It's 00:20:57.869 --> 00:21:01.390 all live now? It's live. It's live today. Oh, 00:21:01.549 --> 00:21:05.069 cool. We're pretty happy about it. We're happy 00:21:05.069 --> 00:21:07.690 about the new changes to it, obviously, with 00:21:07.690 --> 00:21:11.170 the affiliate program being introduced. I think 00:21:11.170 --> 00:21:14.130 that'll be a good success for the community and 00:21:14.130 --> 00:21:18.640 give back, essentially. the efforts of the community 00:21:18.640 --> 00:21:21.819 in trying to spread the word on the project like 00:21:21.819 --> 00:21:24.920 we're not here uh and i think it's important 00:21:24.920 --> 00:21:29.200 for us to to prefix this conversation by saying 00:21:29.200 --> 00:21:33.339 we're not here for cash grab and we don't want 00:21:33.339 --> 00:21:35.500 our community members necessarily to be in that 00:21:35.500 --> 00:21:39.960 mindset there's a lot um of good things to come 00:21:39.960 --> 00:21:42.700 in the project that aren't going to be instantaneous 00:21:42.700 --> 00:21:47.980 so um we will we will see a number of things 00:21:47.980 --> 00:21:49.779 coming out over the coming months that are going 00:21:49.779 --> 00:21:53.359 to obviously attract more people to the project. 00:21:53.480 --> 00:21:55.319 But I think once you start to see the smart home 00:21:55.319 --> 00:21:58.759 integration portion starting to roll out into 00:21:58.759 --> 00:22:00.619 the app, I think that's when you're going to 00:22:00.619 --> 00:22:04.819 start to see some real world utility on the basis 00:22:04.819 --> 00:22:08.460 of the application itself. So yeah, be patient 00:22:08.460 --> 00:22:10.680 with us. We're working on it. Definitely looking 00:22:10.680 --> 00:22:13.460 forward to that. So I think one of the things 00:22:13.460 --> 00:22:16.220 that attracted a lot of attention and a lot of 00:22:16.220 --> 00:22:20.519 people's interest was the integration with PlanetWatch 00:22:20.519 --> 00:22:24.039 sensors. I forget which type it was that really 00:22:24.039 --> 00:22:31.619 were no longer applicable to PlanetWatch, but 00:22:31.619 --> 00:22:34.940 could be used with PiFi. Would you like to elaborate 00:22:34.940 --> 00:22:38.460 on how that came about and the idea behind it? 00:22:39.319 --> 00:22:42.230 Yeah, I think. Well, that was the first sensor 00:22:42.230 --> 00:22:44.809 that we attempted to integrate. And I think it 00:22:44.809 --> 00:22:47.730 was on the basis of us seeing what was going 00:22:47.730 --> 00:22:50.490 on in that community at the time. In fact, one 00:22:50.490 --> 00:22:55.990 of our members was heavily invested in that project. 00:22:56.029 --> 00:22:58.529 I think he had upwards of 70 to 100 different 00:22:58.529 --> 00:23:01.619 aware elements. that he was trying to deploy 00:23:01.619 --> 00:23:05.279 from almost like his own business at the time. 00:23:05.380 --> 00:23:08.980 And so we were very familiar with them at the 00:23:08.980 --> 00:23:11.460 time, and we knew that this project was struggling. 00:23:12.339 --> 00:23:16.220 What happened in that scenario, and Kelvin could 00:23:16.220 --> 00:23:18.539 probably talk a little bit to this as well, but 00:23:18.539 --> 00:23:22.099 what we identified as the problem was that they 00:23:22.099 --> 00:23:25.339 were heavily dependent on... third -party integration 00:23:25.339 --> 00:23:29.440 of their cloud services api so because they were 00:23:29.440 --> 00:23:32.980 so heavily dependent on aware themselves they 00:23:32.980 --> 00:23:37.299 they basically messed it up for themselves really 00:23:37.299 --> 00:23:39.660 they just they found themselves in a position 00:23:39.660 --> 00:23:41.940 where they weren't in control of the product 00:23:41.940 --> 00:23:44.720 anymore and the product owners are basically 00:23:44.720 --> 00:23:47.339 saying i'm sorry that's you know we're not going 00:23:47.339 --> 00:23:50.670 to be playing nice with you guys and We're going 00:23:50.670 --> 00:23:52.970 to turn off those devices. So you're not going 00:23:52.970 --> 00:23:55.650 to be able to send to your data or send your 00:23:55.650 --> 00:24:00.930 data any longer. And so they just basically pivoted 00:24:00.930 --> 00:24:05.289 off of that product just overnight. It was fast 00:24:05.289 --> 00:24:07.329 and it was dirty. And I think it was intentional 00:24:07.329 --> 00:24:10.230 that way so that they didn't have to necessarily 00:24:10.230 --> 00:24:15.230 drag it on or try to make amends. It was clear 00:24:15.230 --> 00:24:16.869 to them that it wasn't going to be happening. 00:24:18.430 --> 00:24:20.849 Why wouldn't we want to take a look at it at 00:24:20.849 --> 00:24:23.470 that point if we were able to circumvent that 00:24:23.470 --> 00:24:27.869 situation and create our own integration using 00:24:27.869 --> 00:24:32.390 their local API? It was a pretty easy task for 00:24:32.390 --> 00:24:34.990 us and it was an easy win just in the start to 00:24:34.990 --> 00:24:38.369 get some exposure for the project, but also to 00:24:38.369 --> 00:24:42.960 what we thought was. doing the right thing for 00:24:42.960 --> 00:24:45.160 their community members and trying to provide 00:24:45.160 --> 00:24:47.279 them with an alternative because people were 00:24:47.279 --> 00:24:53.039 just sitting on $200 paperweights in some cases 00:24:53.039 --> 00:24:54.519 because they thought that it wasn't going to 00:24:54.519 --> 00:24:58.980 have any purpose or utility ever again. And that 00:24:58.980 --> 00:25:00.819 was great. I really admire that you were able 00:25:00.819 --> 00:25:03.500 to do that. They should have done it themselves, 00:25:03.759 --> 00:25:05.960 if I'm being honest. And I'm not a trash talker. 00:25:06.000 --> 00:25:08.420 I'm not going to do that. But if they were doing 00:25:08.420 --> 00:25:10.200 what was right for their community at the time, 00:25:10.220 --> 00:25:11.930 they should have done that. And they should have 00:25:11.930 --> 00:25:14.410 figured out a way to do it. But here we are. 00:25:14.470 --> 00:25:17.630 We did it. And we're more than happy that we've 00:25:17.630 --> 00:25:20.329 done that. And we appreciate all those members 00:25:20.329 --> 00:25:23.430 in the community that have brought their awares 00:25:23.430 --> 00:25:26.569 over. It's great. It's helped with the growth. 00:25:27.609 --> 00:25:30.650 I got to say, the setup, if you guys haven't 00:25:30.650 --> 00:25:33.609 seen, I did make a video converting a SenseCap 00:25:33.609 --> 00:25:37.289 M1 into a PiFi device. So there's a couple things 00:25:37.289 --> 00:25:39.690 I'd like to address that. Firstly, the fact that 00:25:39.690 --> 00:25:43.299 you can reuse. different projects devices if 00:25:43.299 --> 00:25:48.359 they have a raspberry pi you can reuse that and 00:25:48.359 --> 00:25:51.859 convert it into a pi fi device and it was very 00:25:51.859 --> 00:25:55.880 easy it took me maybe 15 minutes to get it all 00:25:55.880 --> 00:25:58.980 all said and done and then the setup on the computer 00:25:58.980 --> 00:26:03.759 was very very straightforward so that was great 00:26:03.759 --> 00:26:07.500 yeah i think i know what your follow -up question 00:26:07.500 --> 00:26:10.579 will be Can you guess what it is? Because I just 00:26:10.579 --> 00:26:12.279 lost my train of thought. Yeah, no, I think I 00:26:12.279 --> 00:26:14.539 can because I know you've been asking in the 00:26:14.539 --> 00:26:17.660 Discord a number of times about it. But you were 00:26:17.660 --> 00:26:20.799 asking about the multi -mining capabilities, 00:26:21.440 --> 00:26:27.799 right? So, yes, we are working on pushing out 00:26:27.799 --> 00:26:30.480 an image for those individuals that are looking 00:26:30.480 --> 00:26:33.940 to both mine their helium and then also contribute 00:26:33.940 --> 00:26:38.180 to the PiFi project as well. We're really excited 00:26:38.180 --> 00:26:40.059 about that because I think that there's a number 00:26:40.059 --> 00:26:43.160 of people hurting right now in the helium community, 00:26:43.359 --> 00:26:45.960 not really happy with some of the returns they're 00:26:45.960 --> 00:26:47.619 getting off those devices, and they're looking 00:26:47.619 --> 00:26:52.140 for an alternative way of using those devices. 00:26:52.359 --> 00:26:55.140 So it's really exciting for us. But, you know, 00:26:55.140 --> 00:26:57.880 there's been a couple of things that have changed 00:26:57.880 --> 00:27:02.380 along the way, including the Solana change that 00:27:02.380 --> 00:27:06.630 has kind of changed a little bit. uh of our approach 00:27:06.630 --> 00:27:09.730 so we have had to take a couple steps back just 00:27:09.730 --> 00:27:12.130 to make sure that we're doing it the right way 00:27:12.130 --> 00:27:14.250 and and that we're releasing stable versions 00:27:14.250 --> 00:27:18.890 so yeah helium has definitely had issues like 00:27:18.890 --> 00:27:22.890 yeah and speaking of like stability and and the 00:27:22.890 --> 00:27:25.490 our approach from that perspective i would i 00:27:25.490 --> 00:27:28.150 think it would be good for us to hear from calvin 00:27:28.150 --> 00:27:31.920 just on our approach on how we manage our releases, 00:27:32.019 --> 00:27:34.720 how we're managing things from the back end, 00:27:34.759 --> 00:27:36.380 because I don't think that the community really 00:27:36.380 --> 00:27:40.380 gets a chance to see that on a day -to -day basis. 00:27:40.559 --> 00:27:44.259 So I think it's important that people that are 00:27:44.259 --> 00:27:45.880 getting into the project or interested in the 00:27:45.880 --> 00:27:49.200 project understand our approach holistically 00:27:49.200 --> 00:27:53.059 from the top down. And Kelvin can probably speak 00:27:53.059 --> 00:27:58.690 to that. Yeah, so... Our number one priority 00:27:58.690 --> 00:28:05.069 is stability. So a few changes to the software 00:28:05.069 --> 00:28:08.829 where that stability wasn't necessarily there 00:28:08.829 --> 00:28:12.690 in the previous version was mainly GPS. Getting 00:28:12.690 --> 00:28:17.609 that GPS lock can be a bit difficult considering 00:28:17.609 --> 00:28:22.609 that any small change in positioning can kind 00:28:22.609 --> 00:28:27.380 of release that lock. So what we've done is on 00:28:27.380 --> 00:28:31.039 the back end, we've kind of created a, I guess, 00:28:31.059 --> 00:28:34.480 a caching mechanism, if you will, so that once 00:28:34.480 --> 00:28:39.200 you have that lock, it'll kind of be pulled back 00:28:39.200 --> 00:28:43.880 and set up for when you're sending data to the 00:28:43.880 --> 00:28:51.079 network. And also another issue that was in our... 00:28:51.640 --> 00:28:55.839 Previous release was after some time, you would 00:28:55.839 --> 00:28:59.680 stop sending data. We've kind of really addressed 00:28:59.680 --> 00:29:03.180 that and tried to make sure that on the software 00:29:03.180 --> 00:29:07.440 side. You know, the uptime is reliable. We've 00:29:07.440 --> 00:29:11.180 also really tried to focus on sending out email 00:29:11.180 --> 00:29:13.700 notifications for anything that kind of happens 00:29:13.700 --> 00:29:16.720 on your system. One of the updates that are coming 00:29:16.720 --> 00:29:19.880 out in the future will be a bit, I guess, an 00:29:19.880 --> 00:29:22.299 agent, if you will, that will help out with that 00:29:22.299 --> 00:29:24.720 reporting. So anytime your system goes down, 00:29:24.819 --> 00:29:29.140 you'll be notified instantly. So, I mean. In 00:29:29.140 --> 00:29:32.240 terms of priority and handling issues that arise, 00:29:32.660 --> 00:29:37.359 stability is number one for us. That's great. 00:29:37.599 --> 00:29:42.059 Yeah, I have been mining the testnet tokens since 00:29:42.059 --> 00:29:44.119 it's almost going on three months and a couple 00:29:44.119 --> 00:29:47.400 of days here. And I haven't had a day where I 00:29:47.400 --> 00:29:50.680 haven't gotten at least 20 notifications that 00:29:50.680 --> 00:29:57.339 3 .1415 PiFi is deposited. I like that you guys 00:29:57.339 --> 00:30:00.519 chose that. that amount too i thought those those 00:30:00.519 --> 00:30:05.200 nice little uh math yeah yeah it was definitely 00:30:05.200 --> 00:30:10.400 something we had to do um and and honestly uh 00:30:10.400 --> 00:30:15.039 we're moving over to mainnet is go it's going 00:30:15.039 --> 00:30:17.779 to be a challenge i think to continue to be able 00:30:17.779 --> 00:30:22.940 to use the same distribution We've found that 00:30:22.940 --> 00:30:24.640 there's definitely going to be a little bit of 00:30:24.640 --> 00:30:26.400 a challenge there, although we will continue 00:30:26.400 --> 00:30:30.119 to try and integrate that wherever we can, everywhere 00:30:30.119 --> 00:30:33.940 we can. Speaking of testnet or speaking of the 00:30:33.940 --> 00:30:36.599 mainnet, I'm curious to know when, if you guys 00:30:36.599 --> 00:30:39.859 have a plan on when you're going to make that 00:30:39.859 --> 00:30:42.380 transition, if it's going to be this year and 00:30:42.380 --> 00:30:47.420 if so, like when? Yeah, we are definitely moving 00:30:47.420 --> 00:30:51.950 towards it. One of the things that I was hoping 00:30:51.950 --> 00:30:56.230 Kelvin would touch on is that we won't do anything 00:30:56.230 --> 00:31:01.410 or push out anything or force anything for the 00:31:01.410 --> 00:31:04.789 project if it's not going to be good for the 00:31:04.789 --> 00:31:07.150 project in that moment in time. If we're not 00:31:07.150 --> 00:31:11.009 confident that what we're about to release is 00:31:11.009 --> 00:31:15.480 100%. there and and acceptable to us and we've 00:31:15.480 --> 00:31:17.740 gone through a vetting process of the of the 00:31:17.740 --> 00:31:21.019 software and along with that the tokenomics model 00:31:21.019 --> 00:31:24.960 is so important um so we've been working on that 00:31:24.960 --> 00:31:27.539 non -stop i'll be honest in the background you 00:31:27.539 --> 00:31:29.200 guys don't even know what's been going on but 00:31:29.200 --> 00:31:33.480 we just saw uh an example of something that we're 00:31:33.480 --> 00:31:36.220 going to be utilizing at our main net release 00:31:36.220 --> 00:31:43.220 that is going to ensure a very confident release 00:31:43.220 --> 00:31:47.680 on the tokenomics model for us to sustain the 00:31:47.680 --> 00:31:50.359 project. And I think the sustainability model, 00:31:50.400 --> 00:31:53.700 it needs to be in place first before we can tell 00:31:53.700 --> 00:31:56.859 you that maintenance is coming. But what I can 00:31:56.859 --> 00:31:58.960 tell you is that we have put it on our roadmap 00:31:58.960 --> 00:32:03.619 for this year. And we haven't not met a goal 00:32:03.619 --> 00:32:07.039 yet that we've set in front of us. So that's 00:32:07.039 --> 00:32:10.859 the plan. Yeah, I noticed with PyFi in particular, 00:32:10.940 --> 00:32:13.299 comparing it to other projects, you guys are 00:32:13.299 --> 00:32:17.240 very articulate. Is this the right word? You're 00:32:17.240 --> 00:32:19.779 making sure everything is working and then you're 00:32:19.779 --> 00:32:22.559 releasing it and you're not stepping too far 00:32:22.559 --> 00:32:24.940 out ahead of you. You guys know where to set 00:32:24.940 --> 00:32:28.359 the marker and where to where to stop. And I 00:32:28.359 --> 00:32:29.880 really appreciate that. And I'm sure a lot of 00:32:29.880 --> 00:32:32.539 people in the crypto space will people watching 00:32:32.539 --> 00:32:35.000 this now and in the future that you guys aren't 00:32:35.000 --> 00:32:37.990 just trying to. push something out because the 00:32:37.990 --> 00:32:40.589 community wanted it by friday you're making sure 00:32:40.589 --> 00:32:42.990 if it's actually ready by friday it's going to 00:32:42.990 --> 00:32:45.930 go out on friday yeah we're not in a rush to 00:32:45.930 --> 00:32:50.470 mainnet we just witnessed something pretty pretty 00:32:50.470 --> 00:32:55.369 horrible with some other aware element users 00:32:55.369 --> 00:33:00.430 um just recently and we watched it start we watched 00:33:00.430 --> 00:33:05.059 it to where it's at now. And we're so confident 00:33:05.059 --> 00:33:09.200 that we're like, we just cannot, we cannot let 00:33:09.200 --> 00:33:11.900 our community down like that. So we're so confident 00:33:11.900 --> 00:33:14.500 that our approach is working. It's working right. 00:33:14.599 --> 00:33:17.640 And we appreciate the patience from the community. 00:33:17.960 --> 00:33:21.619 I think it's really important to be engaged with 00:33:21.619 --> 00:33:23.859 them and, and, and have all that feedback, but 00:33:23.859 --> 00:33:27.440 we'll never put the project at risk for the sake 00:33:27.440 --> 00:33:30.240 of. pushing timelines forward that's just not 00:33:30.240 --> 00:33:33.359 how we function and all decisions that are made 00:33:33.359 --> 00:33:36.359 are made from a roundtable perspective all the 00:33:36.359 --> 00:33:40.539 members um and and founding members we feed off 00:33:40.539 --> 00:33:43.339 each other's uh responses but we also make those 00:33:43.339 --> 00:33:46.359 decisions as a collective there's no one individual 00:33:46.359 --> 00:33:49.519 that vetoes everybody else in this project and 00:33:49.519 --> 00:33:52.259 i think that that's been a huge part of what's 00:33:52.259 --> 00:33:55.259 had a lot of success on the back end and why 00:33:55.259 --> 00:33:57.259 this project's still going to this day is that 00:33:57.259 --> 00:34:00.160 we're not only working together, but we're also 00:34:00.160 --> 00:34:04.059 all friends and we just hang out and get to know 00:34:04.059 --> 00:34:07.700 each other really well. There's always room for 00:34:07.700 --> 00:34:10.539 arguments, but for the most part, we do a good 00:34:10.539 --> 00:34:14.199 job of separating that and our decision -making 00:34:14.199 --> 00:34:16.280 process. We're pretty proud of that, that we 00:34:16.280 --> 00:34:19.260 can do that without a whole bunch of rifts between 00:34:19.260 --> 00:34:23.090 members. Really, really good. Yeah, it's more 00:34:23.090 --> 00:34:25.929 of a build it and they will come kind of project, 00:34:26.070 --> 00:34:30.829 which is nice. That sounds like juice. That sounds 00:34:30.829 --> 00:34:33.550 exactly like it. Flux talks about that a lot 00:34:33.550 --> 00:34:36.630 too. It's just like work on building a solid 00:34:36.630 --> 00:34:39.050 foundation and the rest will take care of itself. 00:34:39.670 --> 00:34:43.690 I would agree. I'm curious to know what your 00:34:43.690 --> 00:34:46.789 guys' roles are in PyFi. Because I know you said 00:34:46.789 --> 00:34:50.030 you work in IT for pretty much your whole career. 00:34:50.570 --> 00:34:53.469 What is your role in PyFi and Kelvin's and the 00:34:53.469 --> 00:34:55.650 other people that were unable to make it here 00:34:55.650 --> 00:34:57.250 tonight? Like, how do you guys all coordinate 00:34:57.250 --> 00:35:01.670 everything? I personally deal with security, 00:35:01.969 --> 00:35:05.670 the networking and system infrastructure for 00:35:05.670 --> 00:35:09.769 the most part. But I do wear a lot of different 00:35:09.769 --> 00:35:14.010 hats. I will get into the nitty gritty with troubleshooting 00:35:14.010 --> 00:35:17.170 and support. And I think we all wear a lot of 00:35:17.170 --> 00:35:20.929 different hats. My primary role when I was brought 00:35:20.929 --> 00:35:25.590 on was bringing in that infrastructure. So all 00:35:25.590 --> 00:35:28.489 of our private cloud infrastructure. How many 00:35:28.489 --> 00:35:31.429 people are there in the PiFi team right now? 00:35:32.610 --> 00:35:37.670 There are five founders and there are... Kelvin, 00:35:37.730 --> 00:35:44.250 help me out, man. Let's see. There's about eight 00:35:44.250 --> 00:35:48.650 of us. I mean, especially... Over the new year, 00:35:48.730 --> 00:35:51.170 we've kind of grown a little bit in terms of 00:35:51.170 --> 00:35:54.789 adding new members and new resources to the team 00:35:54.789 --> 00:35:58.710 to kind of help facilitate things. I take care 00:35:58.710 --> 00:36:02.769 of the development aspect. And like Aftermath 00:36:02.769 --> 00:36:07.170 has said, I wear different hats. I'm on the business 00:36:07.170 --> 00:36:10.210 end speaking the tokenomics aspect while working 00:36:10.210 --> 00:36:15.369 on the development documentation. But, you know, 00:36:15.389 --> 00:36:17.110 my primary responsibilities are development. 00:36:18.690 --> 00:36:22.309 Awesome. Yeah, I know Rob is a part of the project 00:36:22.309 --> 00:36:25.170 as well. Rob's been a great addition, man. We 00:36:25.170 --> 00:36:29.489 all love Rob. I see him everywhere. Yeah, that's 00:36:29.489 --> 00:36:33.349 the thing about him. He's everywhere. And that's, 00:36:33.349 --> 00:36:36.590 you know, we brought him on and he just out of 00:36:36.590 --> 00:36:39.429 the gate just was making all the difference in 00:36:39.429 --> 00:36:42.429 terms of the exposure to the project. He's been 00:36:42.429 --> 00:36:46.449 a catalyst for us in talking with any of the 00:36:46.449 --> 00:36:48.530 content creators that we're discussing with. 00:36:49.269 --> 00:36:53.090 He's got great ideas for the project. He's been 00:36:53.090 --> 00:36:57.610 a great asset for us. And yeah, I can't say enough 00:36:57.610 --> 00:37:00.300 good things about him. So he's more the social 00:37:00.300 --> 00:37:03.340 side and kind of marketing is what it seems. 00:37:03.599 --> 00:37:06.119 Yeah, he would be essentially your marketing 00:37:06.119 --> 00:37:10.239 sales director, essentially, for the organization. 00:37:10.500 --> 00:37:14.460 He has been doing a lot of work related to the 00:37:14.460 --> 00:37:18.119 affiliate side of things on that rollout. And 00:37:18.119 --> 00:37:20.500 then, in addition, a lot of the documentation 00:37:20.500 --> 00:37:25.840 you guys see, including even the light paper, 00:37:26.000 --> 00:37:28.630 he had a big part in that as well. uh putting 00:37:28.630 --> 00:37:30.909 that together he's he's just been a really good 00:37:30.909 --> 00:37:36.250 contributor to the project yeah um grumble grumble 00:37:36.250 --> 00:37:41.849 yeah he's grumble has been uh an important part 00:37:41.849 --> 00:37:45.230 well he's been around uh almost as long as as 00:37:45.230 --> 00:37:49.630 all of us uh founders uh he was one of the last 00:37:49.630 --> 00:37:54.019 ones to come on though um but his His role is 00:37:54.019 --> 00:37:58.599 more on the business side of it. And more specifically, 00:37:58.639 --> 00:38:00.900 when we were looking at the legal ramifications 00:38:00.900 --> 00:38:04.659 for things, he was out there getting us in front 00:38:04.659 --> 00:38:07.360 of lawyers and getting us talking with the right 00:38:07.360 --> 00:38:10.380 people and the right resources. As an entrepreneur 00:38:10.380 --> 00:38:15.800 himself, he's definitely been very helpful in 00:38:15.800 --> 00:38:20.070 some of the directive. portions for the business 00:38:20.070 --> 00:38:22.630 you know where we should be taking it and where 00:38:22.630 --> 00:38:24.889 we should be careful and tread lightly here or 00:38:24.889 --> 00:38:27.750 there it's been uh it's been a good relationship 00:38:27.750 --> 00:38:31.909 awesome um and then juice doesn't really do anything 00:38:31.909 --> 00:38:36.389 nice he just kind of hangs around and just stirs 00:38:36.389 --> 00:38:40.110 up stuff in the discord right no juice has been 00:38:40.110 --> 00:38:45.250 an integral part of of the whole entire organization 00:38:45.250 --> 00:38:48.719 and just for me he's the guy that ended up putting 00:38:48.719 --> 00:38:51.260 everybody together ultimately it was his idea 00:38:51.260 --> 00:38:54.820 and you know he's a very smart very intelligent 00:38:54.820 --> 00:38:59.440 person he's uh without a doubt one of the most 00:38:59.440 --> 00:39:02.659 articulate people on our on our staff and we 00:39:02.659 --> 00:39:05.340 appreciate him and his input on everything as 00:39:05.340 --> 00:39:09.920 well and he's just been so uh integral to to 00:39:09.920 --> 00:39:12.579 where we're at now and and a big component of 00:39:12.579 --> 00:39:16.880 it and and honestly he's the one that that has 00:39:16.880 --> 00:39:19.780 kind of put together the structure of how we 00:39:19.780 --> 00:39:24.159 do business, um, internally and externally. And 00:39:24.159 --> 00:39:27.760 I think he's, he's been so good to us in that, 00:39:27.780 --> 00:39:29.960 in that regard. It's been, it's been great working 00:39:29.960 --> 00:39:32.500 with him all these, all these months, years, 00:39:32.599 --> 00:39:37.239 well, year, year, three months. Yeah, exactly. 00:39:38.420 --> 00:39:42.539 I saw some other questions too, like, uh, alluding 00:39:42.539 --> 00:39:47.099 to, uh, some, Some other members that are no 00:39:47.099 --> 00:39:51.579 longer with the project, we definitely have come 00:39:51.579 --> 00:39:55.900 out way stronger since those times. And to be 00:39:55.900 --> 00:39:58.760 honest, the development couldn't have gone any 00:39:58.760 --> 00:40:01.420 better over this past six months. And kudos to 00:40:01.420 --> 00:40:05.139 Kelvin. He's been so good to us. It seems like 00:40:05.139 --> 00:40:07.039 you guys really hit the gas the past couple of 00:40:07.039 --> 00:40:10.559 months here. We did. Well, we basically tore 00:40:10.559 --> 00:40:14.440 it down. We tore it down. Basically, the version 00:40:14.440 --> 00:40:16.480 that everybody's running right now is going to 00:40:16.480 --> 00:40:19.400 be a legacy version. Eventually, we're probably 00:40:19.400 --> 00:40:23.199 going to move away from that version for a few 00:40:23.199 --> 00:40:25.639 reasons. And actually, Kelvin, you should probably 00:40:25.639 --> 00:40:28.420 speak to that new feature that we've just introduced 00:40:28.420 --> 00:40:31.300 into the new version and why we're moving away 00:40:31.300 --> 00:40:39.489 from the old version. Yeah, so there's a few 00:40:39.489 --> 00:40:42.050 different changes with the new version. The old 00:40:42.050 --> 00:40:46.210 version kind of relied on you, I guess, in a 00:40:46.210 --> 00:40:48.489 way running a separate application, Grafana, 00:40:48.610 --> 00:40:53.170 to kind of visualize the data. With this new 00:40:53.170 --> 00:40:55.710 version, we actually have, I guess, the native 00:40:55.710 --> 00:40:59.230 embedded graphs. So there's no extra logging 00:40:59.230 --> 00:41:03.969 in that you need to do. There's a bunch of different 00:41:03.969 --> 00:41:14.610 changes. The old version, I mean, the old version 00:41:14.610 --> 00:41:19.349 isn't really as stable. We've fixed some things 00:41:19.349 --> 00:41:24.190 with the auto updater that, I guess, allows for 00:41:24.190 --> 00:41:27.769 more consistent and clean updates. Like I said 00:41:27.769 --> 00:41:30.469 earlier, you can kind of dockerize and containerize 00:41:30.469 --> 00:41:33.369 this, so you can pretty much run it anywhere, 00:41:33.530 --> 00:41:40.449 essentially. So with this new version that you 00:41:40.449 --> 00:41:43.429 guys are planning on to release or has it already 00:41:43.429 --> 00:41:46.710 been? It's released now. So that's what we've 00:41:46.710 --> 00:41:51.289 been ramping up for this past week was this release. 00:41:51.510 --> 00:41:54.889 And to be honest, we didn't make a whole bunch 00:41:54.889 --> 00:41:57.969 of hype about it. I think because we wanted to 00:41:57.969 --> 00:41:59.949 make sure that if there were any bugs that were 00:41:59.949 --> 00:42:02.469 found early on here, that we had an opportunity 00:42:02.469 --> 00:42:06.920 to address those. As far as I understand, Calvin, 00:42:07.059 --> 00:42:11.300 there's not been too many bugs or hiccups. It's 00:42:11.300 --> 00:42:14.179 just been a couple of questions here and there 00:42:14.179 --> 00:42:16.599 that we've been seeing from the community. But 00:42:16.599 --> 00:42:19.880 yeah, it's released and we're pretty excited 00:42:19.880 --> 00:42:24.880 about it. I'm still getting the PiFi received, 00:42:25.179 --> 00:42:28.519 so I guess it's working. That's good. I have 00:42:28.519 --> 00:42:34.469 just notifications. Galore. It's nice. I miss 00:42:34.469 --> 00:42:37.489 that. I used to get notifications for other projects, 00:42:37.550 --> 00:42:40.809 and it's a good feeling to know that no matter 00:42:40.809 --> 00:42:44.329 what, there's some constant in my life. Yeah, 00:42:44.409 --> 00:42:48.590 no doubt. Guaranteed some Pi -Fi. Yeah. I also 00:42:48.590 --> 00:42:51.269 saw another question in the chat there that I 00:42:51.269 --> 00:42:54.730 was going to answer. There was a question about 00:42:54.730 --> 00:42:59.170 what differentiates us from other data collection 00:42:59.170 --> 00:43:04.780 projects. I think it's, I mean, if you look hard 00:43:04.780 --> 00:43:08.179 enough, it's pretty self -explanatory. But what 00:43:08.179 --> 00:43:11.719 our goal is, is to gather more than just one 00:43:11.719 --> 00:43:13.679 type of data. A lot of these data collection 00:43:13.679 --> 00:43:17.099 companies are choosing one sensor. or one type 00:43:17.099 --> 00:43:18.940 of data, and they're putting themselves in that 00:43:18.940 --> 00:43:21.239 box. Let's throw PlanetWatch out there as an 00:43:21.239 --> 00:43:23.900 example. They're getting air quality data, indoor 00:43:23.900 --> 00:43:28.019 air quality data, and they're not expanding their 00:43:28.019 --> 00:43:29.920 reach in terms of the data sets that they're 00:43:29.920 --> 00:43:33.559 getting. What also sets us apart is we're very, 00:43:33.659 --> 00:43:36.739 very serious about the integrity of the data. 00:43:36.900 --> 00:43:41.019 So the reason that we put the GPS on there is 00:43:41.019 --> 00:43:44.599 so that we can avoid some type of spoofing that's 00:43:44.599 --> 00:43:47.900 going to happen if you If you wanted to go to 00:43:47.900 --> 00:43:50.780 AWS today and stand up a server and connect your 00:43:50.780 --> 00:43:52.579 aware element, you can do that, but you can't 00:43:52.579 --> 00:43:54.579 send it to our network unless you got a GPS dongle 00:43:54.579 --> 00:43:58.559 attached to your device. So if you want to play 00:43:58.559 --> 00:44:02.400 the system and that, we've taken a lot of steps 00:44:02.400 --> 00:44:04.900 on the backend to ensure that the integrity of 00:44:04.900 --> 00:44:08.920 the data is very real and that geolocation of 00:44:08.920 --> 00:44:11.699 that data is reported on the H3Hex system that 00:44:11.699 --> 00:44:16.059 we have on our Explorer. And all of that, to 00:44:16.059 --> 00:44:20.480 say, I don't think that other companies that 00:44:20.480 --> 00:44:25.059 focus in one specific category are at any disadvantage. 00:44:25.480 --> 00:44:27.679 In fact, in some cases that can be an advantage. 00:44:27.880 --> 00:44:31.820 We've made it harder on ourselves to spread our 00:44:31.820 --> 00:44:39.179 selection of sensors to integrate onto our system. 00:44:39.559 --> 00:44:42.519 And it's made it harder for us, but we believe 00:44:42.519 --> 00:44:44.920 that that's the right thing to do because I think... 00:44:44.969 --> 00:44:46.510 If we're going to do the smart home integration 00:44:46.510 --> 00:44:50.369 eventually, and that's another piece to it, I 00:44:50.369 --> 00:44:52.309 don't see them doing anything to that degree 00:44:52.309 --> 00:44:56.690 or any type of automation with the sensors that 00:44:56.690 --> 00:44:59.130 are being integrated onto the platform. Those 00:44:59.130 --> 00:45:02.050 are the things that set us apart today and I 00:45:02.050 --> 00:45:05.349 think will continue to reward us in the long 00:45:05.349 --> 00:45:10.940 term. That's awesome. Looking forward. So we're 00:45:10.940 --> 00:45:13.719 in March, 2023. Do you guys have, I know the 00:45:13.719 --> 00:45:16.380 windows release is live today. Am I correct? 00:45:16.559 --> 00:45:19.480 Okay. It is. I'm excited to check that out. I'm 00:45:19.480 --> 00:45:21.000 definitely gonna be making a video on Calvin 00:45:21.000 --> 00:45:25.360 can probably show a little example if you guys 00:45:25.360 --> 00:45:32.400 want. Sure. Yeah. Oh, okay. He's not prepared. 00:45:34.460 --> 00:45:41.420 No, I'm not prepared today. Go ahead. I'm sorry. 00:45:41.880 --> 00:45:43.840 I was just going to say what we could end up 00:45:43.840 --> 00:45:45.920 doing is anybody that is interested, you guys 00:45:45.920 --> 00:45:47.900 can join their Discord server and you guys could 00:45:47.900 --> 00:45:49.920 maybe show a preview there or something like 00:45:49.920 --> 00:45:52.920 that. And as well, I will be making a video on 00:45:52.920 --> 00:45:54.659 the Windows version. So you guys will be able 00:45:54.659 --> 00:45:58.019 to check that out. Awesome. Yeah, that'll be 00:45:58.019 --> 00:46:01.380 great. Your videos are awesome. They're always 00:46:01.380 --> 00:46:04.230 very detailed, high quality. Really appreciate 00:46:04.230 --> 00:46:06.710 those. Those are great. Thank you. It's nice 00:46:06.710 --> 00:46:10.389 to hear that. Yeah. Nobody needs to hear it. 00:46:10.449 --> 00:46:13.690 Looking forward for the rest of 2023, and I guess 00:46:13.690 --> 00:46:16.289 beyond, but in the near future, let's just go 00:46:16.289 --> 00:46:21.150 with 2023. What are some other major things that 00:46:21.150 --> 00:46:24.869 you guys could share that you might bring on 00:46:24.869 --> 00:46:27.389 to the project or that you're looking to bring 00:46:27.389 --> 00:46:31.429 on or that is like a guaranteed, but you still 00:46:31.429 --> 00:46:34.989 got to work on it? I think you're probably going 00:46:34.989 --> 00:46:38.289 to see a lot more effort put in. Once we know 00:46:38.289 --> 00:46:40.730 that this release is stable, you'll probably 00:46:40.730 --> 00:46:44.010 see a lot more effort put into the mobile side 00:46:44.010 --> 00:46:48.949 of the application. And I don't want to reveal 00:46:48.949 --> 00:46:51.909 too much related to what's going to be on that 00:46:51.909 --> 00:46:56.530 mobile application. But Calvin's already shown 00:46:56.530 --> 00:46:59.170 me a few little things and I'm super excited 00:46:59.170 --> 00:47:03.030 about it. Yeah, keep an eye out for some updates 00:47:03.030 --> 00:47:06.750 on that, for sure. Awesome. Yeah, it would be 00:47:06.750 --> 00:47:10.210 nice to have a PiFi logo on my home screen. Yeah, 00:47:10.309 --> 00:47:14.250 yeah. Well, I can get you one right away. So 00:47:14.250 --> 00:47:17.250 as far as the application, I know you guys don't 00:47:17.250 --> 00:47:19.130 really want to get into it too much, but are 00:47:19.130 --> 00:47:21.809 you planning on launching on iOS versus Android 00:47:21.809 --> 00:47:23.429 first, or are you going to launch them at the 00:47:23.429 --> 00:47:26.750 same time? Because I know it can be tricky. Kelvin? 00:47:29.320 --> 00:47:33.619 It can be tricky. We plan to try to release both 00:47:33.619 --> 00:47:36.559 of them at the same time. We're still a bit early 00:47:36.559 --> 00:47:42.320 into our mobile app development. But the plan 00:47:42.320 --> 00:47:44.039 is to try to release both of them at the same 00:47:44.039 --> 00:47:50.559 time. Awesome. Yeah, that'll be the plan. It's 00:47:50.559 --> 00:47:52.900 weird in the crypto space because most of the 00:47:52.900 --> 00:47:55.559 people that are doing this kind of DIY mining 00:47:55.559 --> 00:47:58.659 are on Android. But traditionally, everyone is 00:47:58.659 --> 00:48:02.559 more of an iOS thing. So that's why I wanted 00:48:02.559 --> 00:48:05.460 to ask that because I've been on both of them 00:48:05.460 --> 00:48:08.079 for a long time. And pretty much the only reason 00:48:08.079 --> 00:48:11.119 why I go to iOS over Android is it's just easier 00:48:11.119 --> 00:48:13.980 for me, for the people that want to talk to me. 00:48:14.099 --> 00:48:16.760 That's funny. I was just talking about this today. 00:48:16.820 --> 00:48:19.630 The ecosystem, once you're in it. you're stuck 00:48:19.630 --> 00:48:22.289 in it, you know? Yeah. Once you choose a phone 00:48:22.289 --> 00:48:26.690 anyways. Yeah. I mean, air tags and my power 00:48:26.690 --> 00:48:29.070 beats, like it just all works so well together. 00:48:29.369 --> 00:48:33.550 Yeah. And FaceTime is nice. That's nice too. 00:48:33.650 --> 00:48:37.769 Yeah. So I guess if you guys have anything else 00:48:37.769 --> 00:48:43.110 you want to say, no, I think we just really appreciate 00:48:43.110 --> 00:48:46.619 you guys even having us on. From an Ask Me Anything 00:48:46.619 --> 00:48:49.239 perspective, I would love to know if there's 00:48:49.239 --> 00:48:54.980 burning questions out there as well. We're always 00:48:54.980 --> 00:48:59.719 engaged in Discord, so don't hesitate to chime 00:48:59.719 --> 00:49:03.940 in or tag us out there. But we are super excited 00:49:03.940 --> 00:49:06.340 for this upcoming year. We know that the community 00:49:06.340 --> 00:49:09.800 has been fantastic to us. And we would love to 00:49:09.800 --> 00:49:13.119 just do even more Hangouts like this with you 00:49:13.119 --> 00:49:15.960 guys. just even talk about other subjects. I 00:49:15.960 --> 00:49:18.679 mean, it's nice to talk about yourself, but you 00:49:18.679 --> 00:49:20.539 know, sometimes it's fun to talk about other 00:49:20.539 --> 00:49:23.619 projects that are out there too. Yeah. And you 00:49:23.619 --> 00:49:27.820 do frequent, I guess, live events in the discord 00:49:27.820 --> 00:49:31.500 pretty often. I've seen. Yeah. We try to keep 00:49:31.500 --> 00:49:35.300 it active, right. We'll run events and a nice 00:49:35.300 --> 00:49:37.239 thing with discord right now is that they'd have 00:49:37.239 --> 00:49:42.309 that new event management. uh little integration 00:49:42.309 --> 00:49:45.530 now yeah so you can actually run events or schedule 00:49:45.530 --> 00:49:48.070 events and people can see what's upcoming as 00:49:48.070 --> 00:49:50.309 well we don't have anything scheduled i don't 00:49:50.309 --> 00:49:53.449 think right now but uh we without a doubt are 00:49:53.449 --> 00:49:55.250 looking forward to this upcoming year because 00:49:55.250 --> 00:49:58.409 we like running competitions we like running 00:49:58.409 --> 00:50:02.110 uh giveaways we do a lot of those so keep an 00:50:02.110 --> 00:50:05.710 eye out for those too but uh we're without a 00:50:05.710 --> 00:50:07.630 doubt uh looking forward to this upcoming year 00:50:07.630 --> 00:50:10.829 it's gonna be so good What would these giveaways 00:50:10.829 --> 00:50:14.690 entail? Would they be licenses, sensors? We've 00:50:14.690 --> 00:50:19.349 given away full packages with a license, a Pi, 00:50:19.769 --> 00:50:23.070 a sensor, all the cabling to go along with it. 00:50:23.789 --> 00:50:29.030 We've done another one where we gave away a sensor, 00:50:29.369 --> 00:50:35.590 an aware element. We've also done another one 00:50:35.590 --> 00:50:39.059 for an activation contest because we knew, that 00:50:39.059 --> 00:50:40.920 people were holding onto their licenses for a 00:50:40.920 --> 00:50:42.300 while. I don't know why people were doing it, 00:50:42.360 --> 00:50:44.139 but people were holding onto their licenses. 00:50:44.219 --> 00:50:45.639 Maybe they thought they were going to be able 00:50:45.639 --> 00:50:47.719 to turn around and sell them real quick or something. 00:50:47.800 --> 00:50:51.420 Who knows? But they were just not activating. 00:50:51.659 --> 00:50:53.920 So we were like, well, we'd love to see all these 00:50:53.920 --> 00:50:56.099 people on the network. So we ran an activation 00:50:56.099 --> 00:50:59.420 competition where we gave away, again, another 00:50:59.420 --> 00:51:03.159 full Pi setup. And so with the new Windows version 00:51:03.159 --> 00:51:05.440 coming out, I'm sure you'll see something pretty 00:51:05.440 --> 00:51:08.059 soon that'll be more geared towards the Windows 00:51:08.059 --> 00:51:11.940 setup. I think you'll see stuff like that. Oh, 00:51:12.019 --> 00:51:14.480 and I forgot to mention, we also have a part 00:51:14.480 --> 00:51:19.360 of our team. His name's Ryan and he's, he does 00:51:19.360 --> 00:51:21.760 all our graphic, sorry, not all our graphics. 00:51:22.199 --> 00:51:26.820 He does all of our 3d printing designs. So for 00:51:26.820 --> 00:51:28.559 those of you that are interested in trying to 00:51:28.559 --> 00:51:32.059 get a hold of something for those BME 680 sensors 00:51:32.059 --> 00:51:39.010 or for the CP 2221 adapter, just. ping t porter 00:51:39.010 --> 00:51:42.949 in our uh in our discord and uh he he should 00:51:42.949 --> 00:51:45.050 be able to uh coordinate something for you because 00:51:45.050 --> 00:51:48.090 he's got these really cool little uh cases for 00:51:48.090 --> 00:51:50.969 those devices now so i'm glad you brought that 00:51:50.969 --> 00:51:54.130 up because um that was actually going to be one 00:51:54.130 --> 00:51:56.389 of my next questions was for 3d printing do you 00:51:56.389 --> 00:51:59.710 guys have um like you just mentioned these sensor 00:51:59.710 --> 00:52:03.769 cases are they going to be on the website or 00:52:03.769 --> 00:52:05.309 is that just going to be a different thing as 00:52:05.309 --> 00:52:08.190 well as do you plan on making some raspberry 00:52:08.190 --> 00:52:10.750 pi cases i know there's tons of them out there 00:52:10.750 --> 00:52:14.070 but do you guys have any like custom ideas we 00:52:14.070 --> 00:52:19.230 had some early on um ideas of pi cases i think 00:52:19.230 --> 00:52:22.449 that's a great idea uh i think we'll definitely 00:52:22.449 --> 00:52:24.789 want to post some of these on the website it 00:52:24.789 --> 00:52:27.610 was originally i think the issue that we were 00:52:27.610 --> 00:52:30.510 going to have was logistics on how many are we 00:52:30.510 --> 00:52:32.130 going to get ordered and are we going to be able 00:52:32.130 --> 00:52:35.980 to you know get them out in time and or is it 00:52:35.980 --> 00:52:38.280 going to be just something that we can't do with 00:52:38.280 --> 00:52:40.139 excellence and that's always something we consider 00:52:40.139 --> 00:52:44.539 but uh as soon as as soon as we have well here's 00:52:44.539 --> 00:52:47.579 the thing he he just uh managed to get another 00:52:47.579 --> 00:52:50.059 printer but this one's like a nice resin printer 00:52:50.059 --> 00:52:54.400 so it's a lot faster for him to churn things 00:52:54.400 --> 00:52:57.199 out so i think that you'll start to see us put 00:52:57.199 --> 00:53:01.420 some more products on the web page itself and 00:53:01.420 --> 00:53:05.199 links to those pieces of hardware. And yeah, 00:53:05.260 --> 00:53:09.519 that's a great idea, the Pi case. We had a few 00:53:09.519 --> 00:53:13.039 concept designs for the Pi case that we actually 00:53:13.039 --> 00:53:15.619 released and just gave, I think we just gave 00:53:15.619 --> 00:53:19.980 away the design for people that had 3D printers. 00:53:20.179 --> 00:53:24.500 So if you want those, he might even still have 00:53:24.500 --> 00:53:28.329 them. Go ahead. I have a 3D printer. Maybe I'll 00:53:28.329 --> 00:53:35.849 try printing them. Yeah. It would be good. I'm 00:53:35.849 --> 00:53:37.849 trying to see if there's any other questions. 00:53:37.989 --> 00:53:41.489 Some of these we have already answered, but Trillion 00:53:41.489 --> 00:53:44.670 Capital asks about a possible refresher on tokenomics. 00:53:44.809 --> 00:53:47.170 Correct me if I'm wrong, but you guys plan on 00:53:47.170 --> 00:53:49.510 changing the tokenomics for the mainnet. So right 00:53:49.510 --> 00:53:53.469 now it's kind of just... We are going to do that. 00:53:55.210 --> 00:53:57.510 The way the tokenomics are planning to be rolled 00:53:57.510 --> 00:54:01.090 out and the specific numbers, I can't tell you 00:54:01.090 --> 00:54:03.869 right now, but I can tell you guys from a high 00:54:03.869 --> 00:54:06.829 level view of what we've discussed internally 00:54:06.829 --> 00:54:09.449 and what our plan is. This could change before 00:54:09.449 --> 00:54:12.230 mainnet, but I just want to be clear about that. 00:54:13.130 --> 00:54:16.849 So the ideal situation for us in the tokenomics 00:54:16.849 --> 00:54:20.469 model, and that's a great question, is that the 00:54:20.469 --> 00:54:23.449 categories that we're putting out there for you 00:54:23.449 --> 00:54:28.519 to be able to. have different sensors in. For 00:54:28.519 --> 00:54:32.820 example, you know, we have indoor, outdoor, energy, 00:54:33.059 --> 00:54:38.480 water sensors. Each one of those will be formulated 00:54:38.480 --> 00:54:42.559 into a category essentially. And I don't want 00:54:42.559 --> 00:54:45.199 to get too, I don't want to lose anybody, but 00:54:45.199 --> 00:54:47.639 each category is going to be worth, let's say 00:54:47.639 --> 00:54:50.940 one point. Okay. So you'll have three points. 00:54:51.500 --> 00:54:54.239 Three different categories is our plan initially 00:54:54.239 --> 00:54:57.960 on mainnet. Each of those categories will have 00:54:57.960 --> 00:55:01.920 a list of sensors under those categories. In 00:55:01.920 --> 00:55:04.960 order for us to incentivize people to diversify 00:55:04.960 --> 00:55:07.219 the datasets that they're going to be contributing 00:55:07.219 --> 00:55:09.980 to the network, what we're doing is we're breaking 00:55:09.980 --> 00:55:13.179 it out as a percentage of that one total for 00:55:13.179 --> 00:55:17.920 each of the sensors in those categories. build 00:55:17.920 --> 00:55:21.179 out more sensors and add more sensors, those 00:55:21.179 --> 00:55:24.119 percentages are going to scale and change a little 00:55:24.119 --> 00:55:27.559 bit as time progresses. So the incentive is there 00:55:27.559 --> 00:55:30.500 for you to earn the max amount of rewards in 00:55:30.500 --> 00:55:34.019 those categories to equate to the one or the 00:55:34.019 --> 00:55:38.900 total of one. And each of those will total three 00:55:38.900 --> 00:55:44.059 as a perfect score. We'll see if we can make 00:55:44.059 --> 00:55:47.960 it happen. That will be tough. That's a lot of 00:55:47.960 --> 00:55:51.179 fractions. That is a lot of fractions. We want 00:55:51.179 --> 00:55:52.840 to try and make it easy enough for people to 00:55:52.840 --> 00:55:56.360 understand it, but also try to find a way to 00:55:56.360 --> 00:55:58.900 incentivize people to continue to add different 00:55:58.900 --> 00:56:02.519 types of sensors to their PiFi network device. 00:56:03.079 --> 00:56:05.739 Absolutely. I think it'll be helpful. Yeah, I 00:56:05.739 --> 00:56:09.019 mean, I have a BME and an aware element, but 00:56:09.019 --> 00:56:11.840 as soon as you guys add something for water, 00:56:12.039 --> 00:56:14.860 I mean, I'm in. Yeah, I think it'll be great. 00:56:14.920 --> 00:56:16.400 And when we get that smart home integration, 00:56:16.840 --> 00:56:18.960 that's the piece that's going to tie it all together 00:56:18.960 --> 00:56:21.900 for everybody. And so, yeah, we're really excited 00:56:21.900 --> 00:56:24.619 about what the future has in that regard. And 00:56:24.619 --> 00:56:28.380 the tokenomics model is built to incentivize 00:56:28.380 --> 00:56:31.880 people's contributions. So then that's what it's 00:56:31.880 --> 00:56:33.699 all about. We're all trying to contribute to 00:56:33.699 --> 00:56:36.860 this project. Awesome. Awesome. Joe, do you have 00:56:36.860 --> 00:56:40.099 anything else you, any other questions or a question? 00:56:40.320 --> 00:56:44.239 I do not. I appreciate you being here. Yeah. 00:56:44.300 --> 00:56:46.800 Thank you guys a lot for coming out. And if you 00:56:46.800 --> 00:56:48.159 guys, like I said, if you guys are interested 00:56:48.159 --> 00:56:50.099 in any of their information, it should be in 00:56:50.099 --> 00:56:53.099 the description below. And that's just the tip 00:56:53.099 --> 00:56:54.920 of the iceberg because then once you go onto 00:56:54.920 --> 00:56:56.920 their websites or the discord server, there's 00:56:56.920 --> 00:57:01.070 a lot more information. I did make a video. converting 00:57:01.070 --> 00:57:03.550 a sense cap like i said earlier into a pi fi 00:57:03.550 --> 00:57:06.429 as well as um just like an overview of the pi 00:57:06.429 --> 00:57:08.250 fi and there's definitely gonna be more videos 00:57:08.250 --> 00:57:11.329 on my channel in the future about pi fi so stick 00:57:11.329 --> 00:57:14.469 around for those but do you guys have anything 00:57:14.469 --> 00:57:18.190 else you want to say about pi fi like no thank 00:57:18.190 --> 00:57:21.469 you for putting this together chris and we're 00:57:21.469 --> 00:57:23.730 just so happy to be here and and be able to tell 00:57:23.730 --> 00:57:27.050 our story and our direction and and the goal 00:57:27.050 --> 00:57:30.159 of the project you know Yeah. I'm looking forward 00:57:30.159 --> 00:57:33.980 to seeing what's happening in the future. It's 00:57:33.980 --> 00:57:36.039 kind of the bear market right now. So there's 00:57:36.039 --> 00:57:39.059 not a lot going on activity wise, but projects 00:57:39.059 --> 00:57:40.920 that are building themselves right now are setting 00:57:40.920 --> 00:57:44.380 up a really good foundation for when bull market 00:57:44.380 --> 00:57:47.039 comes back. Yeah. We've been talking about that. 00:57:47.059 --> 00:57:49.159 You know, the timing might, might be really good 00:57:49.159 --> 00:57:53.920 for us in this year. So yeah, that's awesome. 00:57:54.780 --> 00:57:58.449 Well, thank you guys so much for watching. Feel 00:57:58.449 --> 00:58:00.230 free to like comment, subscribe and subscribe 00:58:00.230 --> 00:58:01.849 to Joe's channel as well. You guys already know 00:58:01.849 --> 00:58:03.750 who he is if you're watching this, but I'll keep 00:58:03.750 --> 00:58:06.070 it in the description below as well as all their 00:58:06.070 --> 00:58:09.070 socials. Thank you guys. And we'll catch you 00:58:09.070 --> 00:58:10.849 in the next one. Thanks.