Discord AMA with Jeff - 29 June, 2021

Discord AMA w/Jeff Stalhlnecker

June 29, 2021


Jeff: Another Tuesday… It’s already been another week if you can believe it. Right, so this is the weekly AMA. This is the chance for you to ask me anything. That’s what AMA means. Before you do ask me random stuff; my name is Jeff. I’m from Tech at MXC. Head of Development is that actual title but who cares about titles these days. Basically, I can answer your questions about most stuff, not all, but most stuff. I’ll give you as much insight as I can. Some things obviously cannot be quite answered yet just because some things are still just so far in development that we are not quite sure how it’ll be done. In the meantime, I hope some of you have brought some questions. If not, I’m more than happy to geek out with everybody here about Star Wars stuff. I’m a huge Star Wars fan… there’s always that. So whoever is first, whoever wants to, jump in and ask a question.


Q1: Jeff, I do have one question about shipping delays. Do you have any updates on this question?

Jeff: I can give you what I know. Which region are you in?

Reply: Europe

Jeff: There was a massive amount of miners that came in from the factory for Europe. It depends on when you ordered. So people that ordered a while ago will probably be seeing stuff come through in a week or so. There are probably some people from the sales team that are probably saying, “Don’t say that Jeff.” There was a big shipment that came in from the factory. They should be going out soon. If you’re not inEurope you’ll have to wait for the next shipment which I’m not sure when that comes in.

Q2: Are you trying to do something about shipping? I know you mentioned that during the last AMA.

Jeff: So we are working on a tool to help people see progress a bit better. There are some ideas going around the company on how best to do that so that it is an accurate tool for you to view. So there are items on that. I’ve personally not worked on it that much because I’ve been working mostly on interviewing people to be quite honest. Tons of interviews, it’s been quite exciting. Bringing in new people to help us build up this stuff out a little faster. Then of course the documentation which is in Github. Also, the DataDash app is now public in Github as well, so anyone who wants to can see progress in the app and what’s coming up with the app. All of that is fully available for anyone that wants to look at it.

Q3: My final question is what are the next big steps from the tech side. What are you working on?

Jeff: For me right now, as I’ve reiterated a few times, I want to take a look at the foundation of what we are doing and see what can be improved on it. Right now there will be a phase of refactoring going through. We’ve done a lot of cool stuff and built and built and built. Now it’s time to go and make sure it’s the most efficient possible. For that, we will probably start working on the next big thing - devices. That’s actually hot on the press. I know I keep saying that, but it actually is hot on the press. It’s been going through testing the last few days on our final set server. It’s the final stage of testing. It’s really exciting. So device provisioning is coming soon. Following that there’s massive refactoring, and then following that we will start working more on the device payment structure.

Q4: Quick question about BTC mining - will that be given out per account or per miner.

Jeff: It will be per miner. Right now you are seeing per account because not every miner someone has is being used because we just need to limit the test, but it will be per miner.

Q5: Ever since the export revenue feature came out, not one day did I ever make $14. Everyone says they haven’t made $14. Usually it’s around $10-$11 a day. That’s pretty much for everyone I think.

Jeff: The ranges are user reported. There are different factors that determine what the range is. Just keep asking around, as someone at sometime must have reported $14 as what is being earned.

Reply: I don’t think anyone has hit that $14 mark yet.

Community reply: There have been a few, yeah.

Jeff: I could, in theory, dig around and find out but that would be sharing people’s information which I can’t do.

Q6: So, the algorithm that determines the $10-$14 or any of those calculations that help determine earnings with features - will those ever be made available so that the community can understand these features a bit better?

Jeff: Well it’s all going to begin with miner health. What determines the base rate is proof of participation,it’s set. From there the miner health determines which range the base rate is received. It’s all migrating to that. In the future it will be strictly miner health that determines the amount of base rate that is received by the user and that is a migration period going through right now.

Q7: Could you talk to us a little more about Polkadot potentially being mined and what the timetable is on that?

Jeff: The timetable is going to be not very soon. I’ll say that. Simply because I’ve not dug into it much myself. There are people looking into it right now but I haven’t yet put it into the ok we are building this right now. I want to improve on the miner health a bit and make sure that it is working as intended. It is working as intended, but I want to make sure it is meeting the goals we’ve set for it. Then we have some database restructuring we need to do, which will improve the speed of the application overall as well as the speed of development and adding new features. Then, after the restructuring we will work on the device specific options. For the DOT/Polkadot integration I am bringing on more blockchain developers on team. I have multiple interviews coming up for that right now. They’ll start working with that structure when they come on board.

Q8: Could you share more info on the 1-sided liquidity pool that is coming up on UniSwap?

Jeff: I personally know very little about that. There are other team members that are monitoring, managing, and building that out. So, I would not be able to provide any useful information on that personally.

Q9: One of my friends shared his picture with me and he has a miner on a rough and it looks like the connectors have some paint or something running down his miner. His miner is half orange. Are we supposed to waterproof or are they not safe to be outside?

Jeff: If there is something like that going then he needs to contact support. There might be a manufacturing defect that might not have been waterproof done properly. If that is the case, contact support and there will be parts sent to fix it or if there is damage to the device we will replace it.

Q10: Has there been any more talk about fuel tanks in regards to implementing a fuel cap or is the decision finalized? Jeff: I think at this point the decision is finalized that there is not going to be that added in. Maybe things will be revisited in the future, but from what I’m hearing it’s focusing on moving forward. It’s unfortunate the way things were communicated. I think a change of the communication would not have made everyone happy but would have made people less fearful. In its essence, the fuel tank is a modification for halving. Instead of just halving everyone across the board, the goal was to provide a methodology to allow users to determine when they would “be halved”. It was the goal to put that into the users hands, which is why the marketing ran with that phrase, which so many of you said you hate, so apologies for that. It was the overall goal, so where it was community driven on what happens. It’s unfortunate the way it was communicated but I do not foresee any major changes happening to miner health in the near future in that regard.

Q11: One more quick question on NFTs - Do you have any information on NFTs? Do we receive payment per NFT or can you talk just any more about that?

Jeff: All I can basically say is what is in the article. So if you all have read the article I’ll just be reiterating that. It’s very much a governance based NFT. It allows participants or owners of said NFTs to help make company decisions on what’s being done. Going into the direction, more or less, similar to a DAO. Not exactly like a DAO because MXC is technically not a DAO, but it allows more community governance over the actions done by the Foundation.

Reply: So, it will be used more as a vote token as opposed to anything that is monetized?

Jeff: Yeah, at this stage that is what I see this being used as.

Community reply: It does come with a dividend that was mentioned in the article, if that is what you were referring to.

Jeff: Okay, there is the dividend but the goal of the NFT is governance.

Q12: Would you be able to provide any insight on any of the eligibility requirements or the calculations for the NFTs, as they are pretty technical?

Jeff: I don’t. That’s all outlined in the article. I wouldn’t be able to elaborate further, and I probably should be studying the article more in-depth myself to be honest because that is the outline of where we are going and how it will be built. So that is all in the article, and everything in the article is in very big detail/highly outlined. Maybe, maybe, maybe we will make, like, a simplified version of the article, like a fact sheet, to make that easier to understand.

Q13: So I need to go back through and read the article (DAO Governance / NFT Update Article), but we are not getting dividends?

Jeff: As Tavern said, there are dividends mentioned in the article.

Q14: Adding a little more to that, I saw with the recent app update when you click the “add token” there is now an NFT section. You can’t actually check the box, it just says, “Coming soon.” So I’m assuming you all have that slotted for upcoming sprints but that should be on the horizon soon?

Jeff: It should be on the horizon. I mean, coming soon in the app it’s also looking at interest on it. If you look at how “MVPs”(minimal viable product) are done for different sections. If people tap on something that is grayed out, that tap is still technically able to be counted. So people are able to judge interest which helps build prioritization. So as more people look at it or touch that part of it, and are like, “Oh what is this thing?” I know it says coming soon and it is all grayed out which discourages people to tap on it but there is still some feedback that comes in from that that allows us to prioritize features in the future. That is how I want to work in the future, like that. We will put some, maybe add some features in the app that are not fully fledged, like minimal viable product status, and you click on it and it comes up with a screen like, “Thanks, you are interested in this feature, we are working on it.” Which helps us prioritize future development.

Q15: Jeff, could you go over the beta test? What’s the expectation on being able to provide feedback, or just how can we help improve for you all before you go live with the public release?

Jeff: Basically, what I am looking to do and it is still a process to do that. Once you are in the system you just get early access to the latest release. You get a chance to give me all the fun insights you have and everything that is not working or that is working but you expected and didn’t happen. I have, as I mentioned, let me pull it up real quick… I’ve made the app public on Github. I’m writing a guide on how to put a bug report directly on Github so it’s directly with our developers and then can be prioritized. Then the users that submitted can see ok they are working on this bug, or it was pushed off for this reason, or more details are needed about the bug. You’ll have a chance to work directly with the development team on that. I’m going to go ahead and post that to the general (Discord) channel here: MXC Data Dash GitHub Repo. That’s where the app is. We didn;’t have a name for it when we first started developing it. That’s why it’s called the supernode app on the repo. You’ll be able to take a look at the whole app. You’ll be able to see all the pull requests. Some of them are old, some are kind of new. The older ones probably won’t be merged. That, in general, provides insight. If you all were to go through the read me and figure out how to run the branches, you would technically have an opportunity to see anything coming in the Data Dash app before we may or may not announce it. So you can get as involved as you want to. I’m open, if you know Dart or Flutter and you see an issue and you want to fix it yourself, great. We are going to post all the issues we know about so that any participants or community members that want to dig in and get things fixed faster, you don’t have to, but it’s an option. Most of all, for the beta testers, you will have an early version of the app for a weekend or a week depending on the priority of the release. Like if it is a pretty big bug I’m going to try and send it out a bit faster. After that period of time we will role the app out to the public if there are not any major issues. The thing is, a beta that is released to public members takes about 2-3 days to approve. So during the beta time there will be maybe 1 additional fix done and tested if there is time for that. Otherwise we will get the feedback, incorporate it if we can, and submit the new version for final release. It just depends if there is time. My goal in the future, actually, is to have a 4-week development cycle. So we have a 2 week development sprint that is developing the new feature, and then a 2 week spring that is QA’ing the new features with the beta users. So we have the QA working with it and then we have the beta test out so the users can work with it and then at the end of that 2 weeks we roll out the feature. That also means the features have a minimal 4 week development time, which is a little longer than we currently do.

Q16: Will you have hotfixes as well in between release cycles?

Jeff: Hotfixes, potentially, yes but not always. If it is a super high priority issue like if you tap top up and it doesn’t work or tap withdraw and it doesn’t work then yeah, hotfix immediately. If it is something that is not as critical then it can wait until the release. There is always a process that has to be done, there’s always final testing that has to be done, and I have to do a final round that has to be done to make sure everything is good. As you can see, the automated tests are out of date and need to be updated. So everything is manually tested at the moment and takes time. So when the automated tests are better integrated we may be able to do hotfixes more easily, but until that’s done we have to manually test for release and it will stick within the development cycle.

Q17: Thought about extending the grace period from 3 months to 10 months as a grandfather period?

Jeff: At this stage honestly I don’t see anything going back and reworking the system at that point. The foundations and how it is built or how it is designed and what it functions on might be reworked. The initial terms of that I don’t see changing in the near future.

Q18: Can you please explain the grace period again? Is that when you receive a new miner?

Jeff: When you receive a new miner you have 90 days before miner health applies. During that time your fuel tank still increases in size, it just doesn’t dock your mining health (I think he means it doesn’t affect your base rate earnings, it does affect the actual miner health). 3 months are guaranteed at the base rate no matter what. So you could pull everything out, have it in your basement or have it upside down, and you would still mine at the full amount for the 3 months. At the end of the 3 months though the miner health applies and it will be docked from the base rate based on the health of the miner.

Reply: Does the mean at the end of the 2-3 months if I withdraw all my MXC, if the miner fuel is at 0%, I won’t make the maximum base rate?

Jeff: Correct, you still have to put the MXC back. Personally, I don’t want to give you investment advice as that just isn’t what I do. It’s a plug in and leave it alone to do it’s thing and then in a little bit of time take out what you want.

Q19: User-acceptance testing?

Jeff: Yes and no. I want improvements, suggestions, everything you think can be improved on with the app on the beta. Obviously, we may not get to the improvements immediately but I want the feedback, because without the feedback we won’t know what we need to improve. Just the same, bugs can be submitted in Github, suggestions can be submitted in Github. I’ll be writing an article on how to do that so everyone is aware of how to participate and submit issues.

Q20: Is there a timeframe when we will stop getting paid MXC tokens and switch over fully to IoT downlink fees only?

Jeff: No, in the current plan I don’t see an end to Proof of Participation. There is always going to be some level of base pay. Not everyone is in an area that has a lot of IoT devices. Yet, IoT devices don’t show up before there is an active network. It’s a chicken before the egg or the egg before the chicken conundrum. You’ve got people that want to use devices but they don’t have a network so they go with the telecom or sim card device tech because there is already wireless technology provided. Whereas they would have gone with LoRa or LPWAN or the technology we use if there was a network available. So, there will always be some base reward for the users in rural areas or urban areas. If there are no devices around there will still be a base reward. So that they can have the base rewards and have something for providing the network. That will attract devices to it in the long run.

Reply: Fantastic thanks. I have about 10 miners here, but I don’t have a lot of traffic and I get 0 frames most days so that eases my mind a little bit.

Jeff: Hey, if you are in a small town and you spread those miners out you could have full coverage of an entire town.

Q21: How is altitude going to be calculated. Is that going to hurt you if you are below sea level?

Jeff: No. So, the way that is calculated is that there is a pressure sensor in the miner and a GPS signal so we can base the GPS signal and we can see in a database provided by google service or other services what the altitude of the ground level is in that area. So that is the first step. Then we also look at other miners, if there are any, in the area and from that we build a scale on what’s the best possible and the worst possible and we build a scale and that is how altitude would be calculated. Now, for altitude there was another good point brought up by another user. If there was an antenna attached we wouldn’t know that based on altitude. So, for me, altitude still needs a lot of consideration before it rolls out.

Q22: Is it safe to assume when you all plan to roll out altitude you will give us basic guidelines on suggested height. Not too high or not too low and such?

Jeff: Definitely. I’ll make sure it is all documented on this cool epic documentation I’ve been working on. It’s still only in Github because it will eventually be replacing the MXC wiki eventually. Let me post that here: MXC Github repo You’ll see some of the docs that are coming up. It will all be outlined there. How it’s built, what determines a good or a bad altitude is. That will all be there before release. Then of course there is the beta testing of the app which would give users the opportunity to interact with the altitude before it’s done. Before the release of altitude we would have to give out test accounts because it works on different servers. We’re not going to roll out altitude to everyone and say test it. For a release like altitude I would select X number of beta testers and have provided good feedback in the past and give them access to our test system so they can test it without using their own miners.

Q23: I had a question regarding DKP. So, we are about two weeks into the Das Kaiser project. Are there any insights you can provide on how that is going?

Jeff: So far, there haven’t been any surprises. That’s about the best insight I can provide. It’s running well. It’s running quite well.

Reply: Does it seem like some of the issues from the first test like the valuation of the BTC and MXC have been fixed, or?

Jeff: Yeah, it looks like that but we will have to wait for the test to conclude to make any final conclusions. Like I said though, there haven’t been any surprises at this stage.

Q24: Regarding altitude, I was just thinking that there could be cases where you are 100 meters off the ground but still surrounded by buildings. Why couldn’t it just be that you reach a certain amount of miners and you are fine, instead of how high you are? What if you live on the first floor of an apartment?

Jeff: There are a number of variables that determine the health, right? There are different steps that different people will take to achieve the best possible health. Some people will attach it to a really tall pole, others may attach it to a tower I don’t know. With the altitude we are taking the relative altitude of nearby miners. If you are at 100 meters and there are a lot of buildings around you but everyone else is at ground level you are still doing better than everyone else. The only way for us to accurately measure the signal strength provided by a miner would be for people to have an additional device that people would carry around with them. This would certify the signal strength of their miner. Maybe this is something we could look at in the future. The other option I’ve been looking at and looking at how to build is that if there are enough miners nearby you can check the signal strength of each miner and determine the range of each miner on a large scale using all the devices nearby and all the miners and how they are receiving the information from those devices. That would allow us to semi-automatically determine the individual signal strength of each miner. That would take some time to build out though. That’s my ideal scenario, is that in the future health will be optimized by being able to use the data already inside of a network because all the miners are connected with the same system - the MXProtocol. We would then be able to use the signal strength from the same device to determine the range of each miner. Then that would be the determining factor of health, potentially.

Q25: Will other tokens be considered as fuel in the future or only MXC tokens?

Jeff: At this time, I would only see MXC as fuel. I don’t see any of the other tokens on the multi-token mining platform to be considered required for fuel.

Q26: Just going back to earning BTC in general; in the future will that be something that we just earn passively once all the data trading goes live, or will we need to pair MXC or use fuel to earn Bitcoin?

Jeff: I need to look more into that in more detail. Right now it is just testing to see if the overall system works and how well it works, and if it is equitable. Like, if the resources that we put into the BTC system will actually bring enough to the people mining BTC. So that is the current state. After we finish the testing we do right now, and if that goes really well, we go into the next stage. How do we make this where we can roll it out to everyone but keep it a fair network. You’re going to quote on this in the future, but this is my thing. I don’t see the multi-token mining, well it will be somewhat influenced by miner health because we want the miner to be healthy, but I don’t think it will be docked quite as much as MXC. It is a participation mining so it is possible the multi-token mining will not be may not be influenced by health. It’s possible. That is participation mining in its purest form. There’s a lot of “we will see” on that. We’re still testing stuff within it, and as it moves forward we will build the out-process, and as I mentioned that will be published in the documentation before it goes live.

Q27: What is the orientation?

Jeff: That is whether or not the miner is vertically, horizontally, or upside down. A horizontal miner will provide a great network out to space but won’t help devices nearby.

Q28: Once proof of coverage is implemented will there be an ideal space between devices for folks with multiple miners?

Jeff: Right now there is already Proximity. If you are talking about miners, there is Proximity that is planned and not yet deployed, and maybe not deployed soon. The current plan though is 50 meters. That is to be aware of. Though, it isn’t deployed now and it may be modified before it is eventually deployed based on feedback, I would still say if you have the opportunity to spread out miners 50 meters apart then do that. I know in my apartment it isn’t possible since it is 65 meters. That may be possible for people in the states.

Q29: With the Das Kaiser project running and being successful and serving as a good proof of concept for mining BTC, is it a rational thought/assumption that you can apply the same technology towards other coins in the future? Jeff: Yes, it is possible. It would require some onboarding. That is the direction we want to go with incorporating more and more tokens. One of the things that may be an option is that you may be able to select which tokens you want to mine on the miners, so that the resources of the miner may go to specific tokens, and not try to do it at the same time as that wouldn’t be as equitable. It is intended though to bring in more and more tokens into the multi-token mining ecosystem.

Reply: Great,it may be complex but a cool feature maybe us being able to pick a select set of tokens we may be bullish on and maybe the system would see which one is the most profitable by the day and it could focus more on that one rather than the other ones if there is a hardware limitation.

Jeff: Yeah, it’s definitely something we’ve considered.

Q30: Is the algorithm for the $10-$14 earnings based on closing price or is it the adjusted live MXC price.

Jeff: Yes, it is live. Wait, no no no. That one isn’t live. That one is based on one point throughout the day. I’ll let you figure out when that one point is.

Q31: Is there anything we can do right now to improve base earnings?

Jeff: Not at this moment. Maybe at some point there will be a way to improve it. That would probably come into place when the devices come into play. When the devices come into the network there will be additional income.

Q32: Any news on BTC mining for people that didn’t make the cut for BTC mining from the last announcement?

Jeff: They’ll just have to wait. That’s the only thing I can say about that, sorry. It’s a closed test. There might be another closed test or it might be rolled out in the future. It’ll depend on the results of this test. I’m cautious with this type of rollout so there’ll likely be another test in the future before a major rollout. It’ll just be a larger test.

Q33: Are we able to use two devices? One for the released app and one for the beta app? Jeff: For IOS definitely, since you can use test flight and you can determine which apps you want to install on test flight. For Android it might be more difficult since it’s tied to your account and updates are automatically tied to your account. In theory though, you can add a different Android account for your testing on a different device if you want to and it wouldn’t be able to roll updates out to your main account.

Q34: I know several users that have recently received their miners and their Uptime starts at 0%. Is that by design or a bug?

Jeff: That isn’t a bug, it's more just the way it was designed. So it is an unintentional feature. Basically because it has never been online it has no Uptime and therefore has 0%.

Reply: I think the only concern, and it may not be a major concern, is that if the eligibility for NFTs take into account the grace period then it could ding you. If it happens with everyone though everyone would have that ding and 7 days probably wouldn’t make that big of a difference.

Jeff: It won’t make that big of a difference. I do think the NFT eligibility also has to do with the age of the miner in the sense of how long participation has been happening in the network. That being said, I’m not as familiar with the NFT plan at the moment as I should be. I do think it has a role. If it was a brand new miner that wouldn’t be as likely to get an NFT. We want to get those that have been with us the longest and know us best and are building with us into that governance model because you all are awesome and we love you all. Even you Brokk, on your bike.

Q35: How long does it take you to refuel your fuel if you decide to withdraw it into your stake feature?

Jeff: That really depends on the size of your fuel tank. It’s not fast. I can’t give you exact numbers, because I don’t know that. It depends on the size of your fuel tank. If someone wants to crunch the numbers they are more than welcome to do that. The percentage increases but your fuel doesn’t increase outside of the fuel from your daily mining. The example which I’ve used over and over again is if you have 0/99 in your fuel tank you have 0%. If you earn 1 MXC the next day you have 1/100 or 1%. So the percentage increase is based on this mathematical flow. It does take a long time, it isn’t fast, but it does increase. In theory, if someone wanted to, if they met their RoI they always wanted and they are like, “Now I’m happy, I can cash out.” it’s an incentive not to just turn things off. IF you leave it on it will eventually increase and will continue mining that token.

Q35: How are frames transmitted/received determined?

Jeff: If there are devices nearby (and devices on LoRa send to literally anything that will listen to them), then that message is then sent to the LoRa server. If that device was registered on that LoRa the message could be decrypted. If it wasn’t, it just won’t be saved. So that is how that basically would work. Anything nearby that transmits on a LoRa signal will transmit to your miner.

Q36: Two weeks ago we talked about locking DHX without earning a penalty, was there any progress?

Jeff: We did look into it and did not make progress. It looks like things will be staying the way they are. That said, there is still mining happening, and that’s still a good thing. I’m really looking forward to some of the stuff we are bringing out to the community and the network as a whole.

Q37: Those that have more than 1 miner, are you able to mine other coins/tokens per miner?

Jeff: It’s each miner, not per account. It’s a multi-token miner not a multi-token account. Well, it is a multi-token account but each miner has the multi-token potential.

Q38: Is it possible to test the tax report function?

Jeff: The tax reporting function is released. Go to settings > toggle > Export option. Check it out. Everything from the M2 Pro is on that list. If you are seeing some discrepancies do let me know.

Q39: When do we need to worry about the Proximity of our miners?

Jeff: When I tell you, I guess.

Q40: If I put my miner on my roof is it ever in danger of ever overheating? When should you start getting concerned it is getting too hot? Like with the miner being on the roof and the sun radiating heat from the bottom?

Jeff: I would have to check with the hardware team.

Community reply: The manual says as low as -40C and up to 85C.

Jeff: There we go. So up to 80-85C. Most miners won’t reach that temperature.

Reply: But the roof might.

Jeff: That was what I was just about to say. Outdoor temperature doesn’t necessarily mean the temperature of the miner itself. Maybe if you want to be super careful with it you can put a thermometer in a box so you can tell the temperature of the miner itself. I don’t know if there is a temperature sensor in the monitor. If there is, maybe we should bring that through to the users. That would be helpful, wouldn’t it?

Reply: Well, I’m not worried now but when altitude goes live if I put it up high on my roof I don’t want it to overheat. Jeff: It shouldn’t but I will look into that and I’ll write to the person that knows.

Q41: Any word on defi for MXC?

Jeff: Nothing new but watch the announcements.

Q42: Can you make a demo of the tax reporting function?

Jeff: I can but I can also just say how it works. It takes every transaction of token distributed to the miner and uses the time and date of the token distribution and references that to a system like CoinGecko for the time and date value of the token. Basically, the second that it is mined you have the value of that token in the export. That is how it is currently done. It’s at the price point at the time it was mined.

Q43: Will the withdrawal fees for the DataDash app drop in cost anytime soon?

Jeff: I don’t know. Maybe? I’ll have to look into that and look at the network fees and ask those people that actually know that stuff.

Q44: Some days back I asked if I could hook up a GPS LoRa tracker to the M2 Pro. Someone replied to me that right now it isn’t possible and that you are working on firmware so that it works with the MXProtocol. Are you getting close to that being possible? Jeff: The device system has been a bit buggy which is why it hasn;’t worked. Technically, you can connect any LoRa enabled device to the system at the moment, but there are some bugs that block that if you use the web GUI. Coming in the near future, those bugs will be fixed as that is our current sprint priority. So, in the next few days we will be seeing a release for device provisioning. Which is our own fancy and really cool “Most secure device provisioning system in LoRa ever built” is how I would call it. With that will come the fixes for the devices so they can be used more easily on the network.

Reply: Will we need to pay for the device’s data traffic?

Jeff: Not for your own miner, no.

Reply: For the device?

Jeff: If your device is on your account, the same device as the account with your miner, you won’t pay anything.

Reply: What about when it goes to the neighbors?

Jeff: You can configure whether or not it prioritizes your miner.

Reply: Then does it depend on how much they put the downlink price, right?

Jeff: At the moment the downlink price is set as a whole supernode thing. We still need to build in the smart machine building. Once we have the smart machine bidding done, the downlink price will be configured per miner.

Community reply: I think you can subscribe to your own service right? Jeff: Right.

Q45: If the MXC is used as staking or locks, shouldn't we be able to without penalty?

Jeff: That is also something that has been discussed. I don't foresee a change in the current fuel model in future. That's just the facts for that.

Q46: When will we be able to mine DOT?

Jeff: Already been asked, but it’s being worked on. I’m hiring some new people and once they are on-boarded and they are ready to produce the features then we can have that.

Q47: Since we are providing fuel for liquidity how is that liquidity being used since the data market or DFi isn’t live. Is it just pooling up to use in the future or is it being utilized?

Jeff: Basically it is just holding up now to be used in the future. We kind of jumped the gun on that, potentially. So it’s just being prepared.

Q48: So, in the early documentation on medium they talked about the vault, and the vault being staking. They talked about 40% rewards, however the rewards now are 12% for 2 years. Is this something that can be changed over time or is this something that is static going forward.

Jeff: Probably static, but if I remember correctly the article talks about a 40% boost, which is a boost of the standard rate, whatever that is at this time.

Reply: Right, like right now it says a 12% boost to the standard rate compared with the 40% boost in the article.

Jeff: Well it depends on the standard rate. If the standard rate is whatever, then the 40% boost to the standard would bring it to the 12%, right. I’m not going to try and crunch numbers at the end of the day, but it’s basically a boost.

Jeff: This is a response from the hardware team on the overheating of the miners, “They should not absorb sunlight as they have white plastic. This is why we use white plastic and not something heavy or dark. The gateway should not be placed directly in hot sun though if avoidable. The operating temperatures are graded to operate in 85C+, however; extended temperature stress will degrade the gateways lifetime. Gateway is internal talk for a miner, because it is technically a LoRa gateway. That was the message directly from the hardware team.

Q49: If the miners are waterproof can I spray them with a water hose to cool them down?

Jeff: Don’t submerge it. They are water resistant, not waterproof. It can get wet and work fine in the rain, but don’t submerge it.

Q50: Is the gateway able to be powered with PoE?

Jeff: It’s passive PoE. It’s very specific. So technically PoE but it’s not a PoE switch. So don't just hook it up to a random PoE switch as that could hurt it.

Q51: Watercooled M2 Pro?

Jeff: I’m sure someone could design a water cooled M2 Pro and we could support that and Tweet it out, but if you do build water cooling just don’t submerge it.

Q52: Is MXC the primary dev group working on DHX?

Jeff: Yeah, we are working on it. It’s an idea we helped develop and our devs are primarily working on it. However, we are not stopping anyone from participating and working on it. Once the governance releases it will ensure that it functions as a DAO. It is a DAO, it is intended to be a DAO. Anyone that participates in development at this time is more than welcome to do so. You are helping to build the future of the DHX blockchain, so keep that in mind. It’s pretty epic and cool. Here’s the MD file. Warning, this is a draft: DHX Github Shortpaper. Document is in draft status. This provides a bit more information on DHX and initially was intended to be super easy. The short-paper should clarify things. However, the more and more I wrote it the more complicated it got, so I’m sorry for that. It is an open repo. Anyone can add a summary and add a pull request and we can merge that in. The more people that participate the more DAO-y it becomes, and it is supposed to be a DAO. Outro:

Jeff: Alright , I do have to go. I’ve got to order some stuff for team members and then go pedal in what looks like a very big storm. Thank you all! I’ll chat with you later.

69 views0 comments