GM, GM, everybody. Can anyone hear me?
Yeah, I can hear you okay. I can hear you okay.
Wait a few minutes for some people to get in here and then we'll take it away.
I know. Cross chain maxi. I'm unleashing from stealth, guys.
No way you're blessing us with your presence on this Friday morning.
Yes, yes. You should be so lucky.
Yeah, I'm lucky you're lucky, dude.
I got star chains popped up as well. I just want to make sure if you're going to be joining from your account,
or is there another account coming up as well?
No. Hi. Hello, guys. It's Dennis here, so I'll be joining from here.
We'll probably wait like another maybe one to two minutes and then we can kind of get started in the meantime.
Mr. B, it's wonderful for you to bless us, as we said earlier, but yeah, we've been disgraced of your presence recently
until we got lucky enough for you to kind of hop off, talk about outposts. We've been missing it.
We've been missing it, that's for sure.
Hey, what can I say, man? I mean, the last several months, actually, the last year was actually a lot of cross-chain projects.
Some of them are still in the works and, you know, one of them, likely the outposts, has got announced recently
and basically lit up the entire RBC. So I'm excited to kind of finally come on and call out of my jet cave and talk about it, you know.
Jayden, if you want to kind of set the stage and get us going on the different kind of upfront contract of this call
and then we can kind of take it away from there.
I'd be happy to. Yeah, we're lucky enough to have the SOAR chain folks here today to talk all things SOAR and all things Jackal.
We've been talking with the team over at SOAR chain for a bunch of months now, really, really, really great team.
They've got some really exciting developments as of late and really since we started talking to them upwards of six months ago.
So what we wanted to do today is just all get in a room, talk about the things that are keeping us up at night, what we're excited about
and how we're planning on collaborating and potentially taking over the world here.
Right on, right on. And that being said, Dennis, do you want to kind of take it away and introduce yourself and introduce SOAR chain
and then we'll follow up with what we do and who we are.
Yeah, definitely. So I'm Dennis. I'm the CTO and co-founder of SOAR chain.
So about me, I'm actually coming from an electrical and electronics engineering background.
I've been working on autonomous vehicles for about six years now, and I've been in the automotive industry for about 10 years.
I've been in crypto since 2013, of course, only as a trader, let's call it, and also a project follower, so to say.
And we've been working on SOAR chain for about, I guess, a couple of years now, almost two years.
And yeah, that is pretty much about me.
And SOAR chain, actually, I don't want to just keep it too long, came out of the necessity that we saw when working within the automotive industry,
where we have many different parties, all these different technologies and many market forces at play.
The industry is highly fragmented. There is no open protocol to glue all the stakeholders together,
because at the end of the day, you have the car manufacturers, you have their tier one suppliers, and you have the end users as drivers.
And there is a huge disconnect between all these parties, mostly due to the fact that these companies are really large and like hundred-year-old companies.
They've optimized all the mechanical things, manufacturing processes, everything, but they haven't been able to become software-oriented,
and they're trying to turn their vehicles into software-defined vehicles.
But in order to do that, they need an open platform and a proper platform that regulates the interactions between all the parties within the space.
So SOAR chain basically came out of the necessity, and we started building it where Cosmos SDK chain, obviously, where IBC enabled.
And a few things about SOAR chain is that it is built to deal with a lot of data, especially mobility data.
It is a lot different than IoT data or any other data points that we are used to, because it is defined in terabytes, and it is a constant stream of data, sensor data, camera data.
And all of these things are verified on chain, and the proof is mutably written onto the chain.
So it kind of acts as the data availability layer, maybe, it could be called that, but the best part about it is the scaling layer, where we have incentivized nodes that are not validators,
that can be thought of as decentralized sequencers, who constantly receive data from the vehicles, aggregate the proofs, create a single proof out of the aggregated data, and submit this to the layer one.
And layer one then doesn't have to do the computation again, it only verifies the proof. And thus, we enable the verified data, and by verified, we mean verification of its authenticity, originality, integrity, and most importantly, plausibility.
And of course, why is this important? Because when you make this data available on chain, you open up a whole range of possible applications, developers can come develop different taps on source chain, ranging from pay how you drive insurance to road monitoring applications,
or more vehicle to vehicle applications, such as pre-crash warnings, or vulnerable road user detection, platooning applications, and all of these are possible with source chain.
And a final thing is that we have a hardware aspect where you basically get this device and plug it into your vehicle, and it acts as a hardware wallet slash data collector from your vehicle.
And this enables you to start participating in the source chain protocol, specifically participating in this proof of availability, where you are required to prove the availability of your vehicle through some cryptographic means, and thus get network rewards in return.
Yeah, there's a lot more to say, obviously, but I think that's pretty much a very long summary of what source chain is.
No, it's extremely interesting. And I like the ability to have just vehicle connectivity overall. I have like very little experience in the space. But I'm really close before I get team that does kind of like they do dash cams, right? It's just kind of like one of those things and having a way for your to do like fleet management to just like collect data and understand different things about kind of the city and like the value of that data is pretty fascinating, where you can sell it to the city, you can sell it to people that are building things.
You can sell it to all kinds of different sides of that and just trying to find value also for like the vehicle manufacturers to kind of get data so they can kind of get those build, measure and feedback loops. From my standpoint, there's a lot of value in just having the ability to connect your car and have like a reliable stream of data and have something that's a public good that you can kind of interoperate between vehicles as well.
It's exciting for my point of view, to say the least, I'll kind of get into Jacqueline what we do. So my name is Patrick, I'm the co founder of Jacqueline protocol. We have Jayden B also up here. So Jayden is kind of head of BD. B is the the Interchain God at Jacqueline Labs, where he kind of focuses on cross chain integrations and all that good stuff.
What Jacqueline does in a nutshell is we do decentralized storage, where it's really fast, you have on chain permission, super private and interoperable through IDC, and hopefully through some other messaging platforms as soon as well. So this is something where we have scalable hot storage.
It's really the what we believe is like the best technology currently out there where we have a proof of stake blockchain, we have on chain permissions, everything super speedy, retrieval super speedy, and having everything we need to kind of build web scale applications on blockchain technology.
That's kind of us in a nutshell. And I think I would love to like pass it over to be because a really large, really large chunk of what we're looking to do with store chain and with other partners as well is this outpost model, which is pretty fascinating.
And be I know you put a lot of work into it. And I'd love to kind of get your spiel on how outposts works and why it's valuable.
Hey guys, everyone. My name is B. B fan, cross chain developer at Jackal Abster and also core core core core developer.
And essence. Oh yeah, my background is computer engineering. So connecting vehicles to blockchains is just kind of right up my alley there.
So really short and sweet. We made a major breakthrough with our crushing integrations a couple of weeks ago.
It was featured on like the main Adam into chain account and basically everywhere where we ported the entire functionality of our blockchain to a smart contract, a web assembly module specifically.
What this means is that any cosmos SDK chain that has a smart contracting platform like cosm wasm or like any kind of web assembly platform can run that contract and have the complete functionality of the jack of protocol on their chain.
What this means for the user. So imagine someone has our toy tokens or Utah tokens or any any cosmos tokens. Really, they don't have to swap jackal. They don't have to go to an exchange and deal with all that.
They can just use that token natively on the archway chain on the atom chain on the osmo chain to use jackal pop storage self custodial private storage and yeah, that's that's that's the biggest innovation and we we're the first team in the world.
Someone can come at me for this, but we've done our research and we're the first team in the world to send a custom modules, custom modules.
Message across IBC specifically using into chain accounts and for this this this announcement with so chain is kind of the perfect timing because so chains premier smart contracting platform is cosm wasm, which is we have assembly base, which makes us compatible with so chain off the bat at the protocol level.
So never mind API spaghetti or JavaScript API's or SDK's at the chain level compatible with the bat. So just just imagine data being sent from from a vehicle across two blockchains kind of wild.
So yeah, that's the latest development. And as far as like talking about future partners and whatever I'll kind of pass on to Patrick and Jayden because I don't I know we're talking to a lot of people. I don't know.
I know we're talking to a lot of people. I don't know how much I can say and how much I cannot say, but yeah, almost this is sorting space. So yeah, absolutely. Thanks for the context there. It's it's pretty special. And just like from first principles, you just have access to all of jackal's functionality on any cosmos chain that like runs cosm wasm or web assembly.
It's it's pretty fascinating that sense. We're like now you have on chain access directly there. You don't have to go to osmosis for jackal transfer to jackal get an account there. You can just do it all locally with a simple smart contract call.
So I'm curious, Dennis, when it comes to like kind of like storage and things like that, like what do you guys care about? Because I know that these vehicles all the data like just spits off data like crazy from location to like all like the if you hit the brakes really hard, that'll like trigger an event.
If you have a camera on the vehicle, that'll that's like a ton of data. That's kind of depending on like the resolution, of course, but that's a ton of data that just spitting off these cars all the time. And I'd love to hear about where you guys are with like kind of managing that and what what are like kind of like the the base needs of sort chain in general when it comes to kind of managing this data and how you guys go about it.
Yeah, so the first thing to understand about mobility data is that it is really something we've never seen before. It is said that an average modern vehicle is able to generate about like two terabytes of data per day.
And it'll just end per day, I guess, that that takes into account some two, three hours of drive. And as these vehicles become more and more autonomous, it'll just go up to four terabyte as they're claiming.
This is, of course, like LiDAR data, point cloud data, camera data, sensors data, even like AC data, seats data, whatever, like passenger, everything added up, of course, like maybe 880 90% of this data is useful when it is used in real time, meaning that either on the car itself or by the nearby vehicle.
So the vehicle to vehicle aspect is an important one. But the vehicle to network part is actually what we're currently working on to optimize where you have a constant stream of data from all the sensors.
And even though it does get pre processed, it still needs some way of being verified. So the initial goal is to verify the data for its integrity, authenticity and plausibility.
This is first like the first line of defense is the hardware itself, it is a secure hardware, meaning that it has a secure element inside of it, it has secure that and this means like it has a chipset that stores the private keys and all the sensitive credentials, the certificates and everything.
And there are also some other security measures such as having a secure boot, meaning that no other firmware would be able to run on it. And even if it does run on it, we would be able to get the fingerprint of what kind of firmware running on it.
And also that's decided through an on chain process where you know which exact firmware is running on it through a fingerprinting process.
This is like the pre processing stage and then it comes to the scaling layer that we call runners. It is a state machine replicated, highly asynchronous and like this also makes it censorship resistant.
And they're actually the data. This is actually the most important part about the data being distributed because they're right now the data is just being cached for some time.
And once the proofs are generated and sent to the blockchain, they're not stored anymore. And they don't really need to be stored for the time being because these are just the proof of availability rewards where they as the name implies vehicles just prove their availability.
But we have this thing called the data provision request, which is actually a way for the data consumers who could be like that developers companies like data marketplaces anyone who need want to use this data for their business case and to provide some utility to the users.
They submit an on chain data provision request where the eligible vehicles are notified through an off chain indexer and there they basically if they're eligible and of course if they have opted in to provide the data, they start streaming the data to this runner network.
And there we're still not involved with the data storage part and the main function of storage chain is to actually facilitate the secure streaming of this verified data from the generator to the consumer from the data generator to the data consumer and to actually act as a verification layer and protect both parties through the trustless protocol.
There, the goal is to, of course, like in this case we assume that the data consumer who could be, let's say, a predictive maintenance application, they will be storing the data themselves.
But of course, the idea is to provide this as an end to end service, where they would be able to with a click of a button or with direct integration without going out to some centralized storage providers, like, I don't know, S3 buckets, whatever, they would just have everything integrated and they would actually have their data.
The reference to their data on chain and they would have permanent storage through decentralized storage provider, which is jackal. So that's how we're envisioning the exact data pipeline for the time being.
And this is pretty much something we are very excited about.
It's pretty fascinating, right, to have the ability for you to kind of spit off data off your car and also kind of like maintain the ownership and self custody in the event that those users want to sell that data and it's their choice, right?
And it's pretty fascinating by leveraging blockchain technologies, on chain permissions, who has access to what files over time, leveraging your public and private key pairs.
It's, I'm pretty excited about it. Overall, just having the ability to kind of maintain self custody ownership and a ridiculously high security posture around that specific data and kind of have a way for you to monetize it or donate it or keep it for yourself or do things like that or give it the sort.
You have so many different options since it's so modular from that side of things, just directly at the chain level.
B, I'm curious what your thoughts are of how this integration would go and what that would look like. Obviously, it's still early days, but how do you see the architecture for this working? And I'd love to kind of, Dennis, add your input as well, just on how that would look.
Yeah, of course, I imagine every single device that sort of is working on can send data directly to the sort chain itself, the chain itself.
But as far as sending that data from sort chain to our chain and then to our source providers, everything just happens through the outposts.
As of right now, for us, of course, your data is protected by your ledger, which is your private key and only you can unlock your data. And then that's ultimately shipped into an IBC packet on the outposts and then sent across the wire over to the Java protocol.
But at the beginning of the outposts, it's that simple. I really can't say anymore. That's just how it works in a sentence, essentially. So Dennis, I'm going to ship it off to you. But yeah, we have compatibility off the jump.
Yeah, that is actually like one of the most exciting and, I guess, convenient things about working with Jekyll, where we would utilize the direct IBC connection to basically exchange assets as general as it gets, of course, and to still get the data.
And if we give the ownership of the data to our users, like it wouldn't be actually going to some other custodial service, but rather they would actually have full control over it through their key pairs.
So that's actually, I guess, almost revolutionary, I'd say.
It's pretty cool from that side of things. I'm excited to just try to... The way I see blockchain is I just find them fascinating in general, right? The best way to dumb it down is just a simple Excel spreadsheet. It's a fancy Excel spreadsheet, where it's a Excel spreadsheet that's really never wrong.
It's this magic Excel spreadsheet where you can use it for who has what things are with time and using it for who has what proofs of the vehicle mobility data in your use case, for example, and verifying that and making sure that all that data is verified using the technology or using the technology as a data permission system.
And it's just so malleable into different ways. It's pretty fascinating overall. Regarding Sorochain and what you guys... What does your year look like in general? So I know that you guys have two products that seem to be out.
You have the MODIS, the MODIS Mini, and I'm sure you guys are working on a bunch of protocol upgrades. What's it looking like for you guys in the next year?
Yeah, it is also a pretty busy schedule, a busy release schedule, I'd say, where we're currently on the incentivized testnet. We'll be actually freezing the whole thing, hopefully on 8th of March, the blockchain side.
We're working on some new features on the hardware side. Right now, the main focus is on the MODIS Mini devices, which is kind of like an entry-level device, which is designed for general user base.
We have another device called MODIS Pro. It is still under QA tests. It's got a lot more complex systems in it, like system on chips on it, such as the vehicle-to-vehicle capability, like a very high category LTE, higher computational power.
So it is like a flagship product, so to say. But right now, the MODIS Minis are being shipped to the users, and we have done a lot of optimizations in terms of the power consumption.
Soon, the connectivity features are going to be diversified. So right now, it is connected through the hotspot. The Bluetooth functionality will be added to that.
And on top of that, we will, as I mentioned, enable the data provision request, which is a whole new way of the network participants to do more actions.
Basically, the actual purpose of Source Chain will be fulfilled. And there, we have right now around 13 adapts coming into play, ranging from all these things that I mentioned, like ride-hailing applications, safety applications, some AI application that would also utilize the camera of the mobile app.
And many of these are actually in the works. Some by us, and some by completely external teams that are developing on Source Chain.
So the developer traction is also really something that we really value, because in our case, it is all about the dApps that are being developed on Source Chain.
So Source Chain, as the protocol itself, is like we're not interested in implementing everything as a future, everything as a base level future that lies on the blockchain logic, but rather just implement the functionalities and expose them as easy to use API-like interfaces so that the developers can just come and develop their applications.
We've recently released some template smart contracts related to ride-hailing insurance, a very comprehensive set of insurance smart contracts.
That's also one of the strategies that we have. We will be actually releasing sample smart contracts and sample applications where the developers will be able to just deploy them with a single click and just configure the configuration file.
It's almost like a no code, whatever, and it will just streamline their processes. They will be able to focus on the applications and the business logic itself.
So this is pretty much what we have coming in the next six months.
I know the reason why we like you guys a lot, and we're excited to work with you in general, is we have a lot of respect for hardware-based businesses where you have your entire blockchain that's one thing to build.
Then you have a hardware side of things, and hardware is just insane. I have a lot of respect for it overall.
How far you guys are along in your roadmap is pretty exciting, and kudos to you guys. Just absolutely crushing it on that front, and you're already shipping things. It's wonderful, wonderful on that front.
The thing that I find pretty interesting about this is having this level of connectivity gives you the ability to have a different streamlined insurance product.
You were talking about that specifically, and that's something that intrigued me quite a bit.
Where you have the ability for you to run insurance based on the vehicle diagnostics or different data that's coming off your vehicle every day, whether it's camera base, whether it's a brake sensor, speed, stuff like that.
Where you can have a little bit more personalized insurance plans, it seems like, from my understanding. Is that where you guys head that right now for one of your service offerings?
Yeah, that is because it is the easiest and the most straightforward use case to understand by many. The insurance providers are already all over this thing.
We have a couple of companies actually developing their own business with the four chain data pipeline.
One of the things we're also working about this is to protect the user privacy in a way that through privacy preserving systems, of course, where there would be two things.
One is revealing as little user data as we can.
And the second thing is when they are receiving the initial policy, like the premium, there are two things.
The first one is pretty straightforward. We had this old way of doing the premium yearly thing where your mileage would be taken into account and whether you had an accident or not.
And then it went through some changes and it became like a pay as you drive with all these metro miles and stuff. And now it's moving towards more pay how you drive.
But there's one important aspect when you use some pay how you drive insurance directly from an insurance provider.
One, you're putting a device that you don't know what is running and you're providing all your data to a single company without knowing anything about it.
And the second thing is that you're providing your data and in a plain text way where they will be able to use that data not only for calculating your premium, but also for even location based ads or like they can sell it, whatever.
In our case, what we're trying to enable is to balance out the equation and give just the necessary data to the provider and even anonymize it in a way that they wouldn't be able to link it with you.
So that is something in the works where the deployer of these contracts would be actually enforced to use a privacy preserving method.
And the second thing which we're working on, which is really interesting, I think, is to enable a completely privacy preserving premium offer reception.
I don't know like the exact term, but basically you will have multiple insurance providers and you want the one that fits your needs best.
Maybe like you want a really dynamically changing premium. Maybe you're like a high risk driver. I don't know. Maybe you have other needs and you'll have to give your data to five different providers just for them to give you an offer and you would be sharing your data with all of them.
What we're working on right now is the ability to share your data in a completely encrypted way and it gets processed while it is encrypted. Nothing is revealed and the algorithm, the parameters of this algorithm would be selected by the insurance providers
and they would actually give you a policy where they wouldn't even see what they're giving to you and only you would be able to reveal it once they give it to you because it would also be encrypted.
It's based on fully homomorphic encryption and that's also something we're very excited about and we'll be demoing soon with some of the partners.
It would be really interesting and I know that just for example, just in a workflow, for example, I have a motor spinning in my vehicle. I want to get insurance so I plug it in. I collect data for a certain amount of time and then after a certain amount of time, I have the option to go and find insurance providers, for example.
What you're telling me basically is that I can have some compute running over that data where I could, are we submitting ZK proofs to the insurance providers saying these are the specific proofs instead of giving all of the data up.
It's what my understanding is but it also seems like you're doing fully homomorphic stuff.
Am I kind of like in the right?
Yeah, exactly. But it is not even like nothing is revealed so it is like run in a fully homomorphic, completely encrypted data.
But of course, at the end of the day, you would have to reveal your data to the provider that you pick, but it just limits your data to just circulate around all these companies.
You would at least provide your data in a, like it is still encrypted and we are also going to use some ZK proofs to actually preserve the user's privacy when they choose to work with the insurance provider.
But that is like a next steps for us. The initial thing is to protect their privacy while they're receiving premiums from different providers because you don't really need to give your plaintext data anymore.
And that makes complete sense, right? Where you can kind of use proofs to kind of get the quotes from the different providers and then when you finally decide on a provider, then you can release your data to that one provider rather than having multiple cybersecurity attack vectors, you only have now one.
Cool. No, it is pretty fascinating on that front.
I am excited for this integration. I wonder where it can go. And what I am also curious about with like the programmability of the actual data that the user has, I am curious what applications can be built with that as well on SOAR chain, where now you have like a full permission system.
You have all kinds of different stuff where you can kind of change permission for like specific data sets completely on chain in six seconds where you kind of like, it is pretty cool. It is pretty cool, for that sense at least.
Wow. What are you guys thinking? Jayden, you have not been talking in a while. B, what are your thoughts?
Just sitting here soaking it all up.
Of course, of course. I know Marston is really proud of you. He wants to come up. I know you should come up to a specific conference here in Toronto that I am going to be going to. I think Marston, I do not know B, I do not know if you are aware or not, but it is the Homomorphic Encryption Conference in Toronto where it is pretty cool to see the teams there.
It is like some pretty heavy crypto guys for sure. Everyone is really focused on the cryptography side of things. It seems like a pretty cool conference to be. I would love to see you guys there, SOAR chain.
I guess it is the FH org conference, right? I know the guys, they are crazy. They are the founders of, not founders maybe, but the guys that made it practical to use, at least, with human beings lifetime.
That is the thing, right? Everyone has always been like Homomorphic Encryption is right around the corner and like 10 years later we are like still so close, right? It is like the holy grail of cryptography really. I know Marston is pretty excited. I know Guy Zeiskin from Secret Network. He left and he is building something called Phoenix. It is like an EBM, fully Homomorphic chain, which is pretty cool as well.
It is exciting times in the developments that are happening right now in our lifetime. We have AI going on. We have fully Homomorphic Encryption around the corner. We have some pretty crazy consensus algorithms for these blog chains now.
Let alone proof of stake where we can start to get into like Tenderman consensus, Narwhal and Tusk, all these different things. The advancements are just, it feels like the acceleration is pretty fast right now. I am just happy to be a part of it.
Yeah, the market is definitely turning around and super pumped. Everyone is kind of big on protocols that are leveraging both blockchain and AI, which is super exciting. I just want to add on one thing to what I was saying before, guys.
The Outpost itself is open source. The storage Outpost, the contract is open source. You can read about how it works on the blog on our Twitter. I think it is called Breakthrough App chains running as smart contracts and follow its development, guys. We are super pumped.
We are actually meeting with Dennis and some of the blockchain devs next week to hash everything out. I guess maybe Patrick, this is time for Q&A.
Yeah, I think that is perfect. It is probably time to wind down here pretty quickly. I got to catch a flight. I got to go back to Ottawa and go home. If anyone has any specific questions, feel free to request. I would kind of give you guys a few seconds to make some requests here.
If not, Dennis, do you have any last things that you would want to specifically say before we shut this down?
We are on the incentivized testnet. You can participate in many ways. The most straightforward way is to get a modus mini and start participating.
If not, we still have some community challenges and whatnot. Come join the Discord.
Other than that, of course, about this partnership, we are very happy to be doing this. Hopefully, it will be an integral part of 4 Chain. That is what I am envisioning.
Yeah, that is pretty much it.
Right now, we have Earl. Earl, how is it going? Let us know what your question is.
You might be muted right now, if you are chatting.
Hey, GM, GM, everyone. How are you? What is the idea of GM?
Okay, I saw a link from Jaska from your protocol last week. I feed the form. We have to submit our wallet. Is the link from you?
A link from us to submit a wallet address?
Yes, yes, yes. We have to submit a wallet address from Timpy.
If you have any questions, I would like to reach out to the team. If it is associated with the airdrop, that was not done by our team. Feel free to reach out to them.
I am shutting this down. There are no other questions left.
Really, for us, if you want to get involved with the Jaka protocol, hop in the Discord, hop in the Telegram, follow the development.
We are doing some pretty crazy stuff over there with the Outpost contracts and all the cross-chain integration stuff, let alone like RAG frameworks.
That is a whole other can of worms. That is everything from us. Jaden?
Yeah, just a quick note before we let everyone get on with the Friday here. As Dennis said a little bit earlier, and kind of directing this towards the members of the Jaka community that are on this call,
for everybody that wants to get involved, please do go check out SwordChain, pick up a Modus MIDI. I know that we have already had members of the Jaka community pick one up,
which is phenomenal for any sort of partnership where we can leverage our community and get more eyeballs on projects that we are partnering with here.
We are wishing Dennis and the SwordChain team all the best. If members of our community want to help out, we would absolutely love that, as Dennis said.
Yeah, likewise. I guess you already have an end-user product where I can just use it as a storage, personally.
I'd also urge everyone in our community to take a look at it. It's much more resilient and I guess much more cost-effective compared to other providers when you look at it.
100%, especially when we are relating to geo-redundant hot storage. It's pretty expensive, pretty quick, right? I'm sure you're aware of what you guys are doing over at SwordChain.
Yeah, for us, we have a few apps. If anyone wants to try it out, we have API if you're a business and you want geo-redundancy.
You can use the API if you want the self-custodial privacy nature, ownership nature of the protocol. The Jaka dashboard is the best for anything that's privacy-related.
We also have two other applications that are public, like publishing files.
If you want something to be published for 200 years, you can upload it to Radiant.
Or if you want a medium style, you want to do some writing and you want to make sure that you just have a place where there's no information supply chain of tags or anything like that.
I didn't have the ability to have something live on the protocol for 200 years. You can also upload it to Beacon, which is kind of like our medium style, like editor basically.
It's just a markdown editor built into the browser that just stores files in Jaka.
Anyways, really great chatting with you. We have one more request of one person coming up here.
Let's see if he gets connected. Raj, how are you?
Hello, good evening. Can you hear me?
I wanted to know, okay, Modus Mini is available across the world, or is there any specific reason?
Raj, your question was, is the Modus Mini available worldwide?
Yeah, sorry, I didn't understand. Yeah, it is actually. So we're shipping worldwide and it is available in almost all the countries, all the continents and almost all the countries.
Okay, and once I get the Modus Mini, then what kind of airdrop I can expect as an end user?
The first thing is the base airdrop, which is actually given to all the Minis bought before the mainnet,
where it will have a cryptographic certificate in it to prove that it was actually manufactured before the Genesis event of mainnet.
And on top of that, once you receive it, you basically start participating in the network,
participating in the proof of availability and also start generating network rewards through it, which also counts towards the airdrop.
Okay, and that Modus Mini is applicable for all vehicles or any certain vehicle only?
You would have to check the database at cars.sorchain.com for your specific vehicle.
If it is there, then it is supported. It might not be there, but still supported.
In either case, you can come join our Discord and ask it on the vehicle discussion channel or any other channels, basically.
Okay, because I check on the solar chain and I figured it out that there are a few vehicles. Okay, those details are not available.
Yeah, you can come ask in the community and we'll be happy to help.
Okay, okay. And Discord is the only communication channel or do you have any telegram channels?
Yeah, we also do have a telegram. You can also join that one as well.
Okay, and the second question, okay, if those who are not participating in the Modus Mini, so is there any other way around where we can get a airdrop?
There are like some zealie challenges for like community building and all those stuff. You can also participate on those one as well.
Okay, and when you are planning to go into the mainnet?
It is planned at the end of this quarter, probably towards the mid April or so.
Okay, and if you allow me to ask one more question, then I'll ask.
Okay, so do you have any plan for seed round for retail investors as well?
Not at the moment and like I really also don't have the ability to disclose that information.
Okay, but seed round will be there, right?
Like I can't actually give any info about that one.
Okay, got it. Thank you. And last question. Okay, SoarChain is building their own layer 1 blockchain?
Yes, it is a Cosmos SDK based layer 1 blockchain. We have like validators and everything, all the full set.
Alright, got it. Thank you.
Thanks for coming up Raj and make sure to drive safe out there.
Yeah, I'm driving while talking to you. So that is the reason I'm on speaker. Okay, I'm driving my car and I was checking on the store chain whether my car is available or not.
And I'm driving Maruti Suzuki. Okay, but I was not able to figure it out because there are many more brands. Okay, so which one is mine that I'm checking?
No, of course. Just make sure you pull out the car manual when you get home though. Just say get home safe. Okay.
And also like one last thing, I forgot to mention about the things. We recently got added an integration with Tesla. So anyone with a Tesla can also participate in the, wow. Yeah, through the Tesla API actually. So not really, they, what is mini but also the API itself. It's a direct integration.
One more question. How long it will take to deliver? Currently it's around for four weeks.
Okay. And can I configure myself or I need to get it done by someone technician or something? No, no, no. You can just plug it into the vehicle's OBD2 port. It's right underneath the steering wheel.
Okay, got it. Thank you. Thanks all.
All right. Yeah, if anyone has any last questions, we can bring you up or if you, if that's it, really great space. I had a lot of fun. Thanks for, as always, sort of excited to get that integration going, get that OPPOS shipped and then we can just see where, where the art of the possible is. It's going to be exciting times just kind of connecting all the infrastructure of all of our L1 chains.
Hey guys, before we sign off, I just want to say, Dennis, thank you so much for coming on. It's always great to meet other other engineers that are really maxis on building decentralized apps and really, really looking forward to collaborating next week on that, on that dev call.
And for everyone else, you want to get the inside school. I want to do a shameless plug. And if you want to get the inside scoop on the latest question developments and for our Jackal, hit me with a follow. Follow us on GitHub, Twitter.
And yeah, thank you so much for coming. Any questions, please come up. But, yeah.
I think we're going to shut this one down now, but really good chat with everyone as always. See you guys, I guess next week or next thing is a town hall Wednesday.
Thanks for coming to everyone.
Thanks a lot, guys. Thanks for coming, guys.