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.