Another week coming to an end!
Over the last few weeks, we’ve included taskers on what is being built on a pretty detailed level. What we failed to include, though, is what each of those tasks is ultimately building. For example, when we mention Lox Core, and then go on to describe which .js files are being tasked out are assigned and which tasks are completed, you’re probably sitting and wondering, “what’s Lox Core?”
Lox Core, as the name implies, is the heart and soul of the entire ecosystem. We’ve broken Lox Core down into three facets: Network, Chain, and Runtime.
The network portion of Lox Core implements a peer-to-peer network that powers communications between blockchain nodes. Whether that be initiating connections with other nodes, maintaining a view of the entire network, routing messages to the right nodes, the network is a somewhat standalone module that uses information from other parts of the ecosystem.
So when we discuss API integrations under Lox Core, like we did last week, it’s referring to the a task that specifically builds the foundation of the Lox Network ecosystem.
The second facet is what we call Chain. Similar to Network, Chain is aptly named and most people can probably understand that it is referring to blockchain technology.
Chain is responsible for building and maintaining the blockchain data structure. This includes block and chunk production and processing, consensus, and validator selection. However, the Chain is not responsible for actually applying transactions and receipts. It is simply the actual ledger that other parts of the ecosystem can access to generate their own data.
And, finally, there’s Runtime. Runtime is the execution engine that actually applies transactions and receipts and performs state transitions. This also includes compilation of contracts (wasm binaries) and execution of contract calls.
Runtime runs on Network to access data from Chain. The three facets combined make the Lox Core of our public-facing, hybrid blockchain.
At the start of next week’s update, we’ll go into what the portions are referring to, like LOX CLI, LOX EVM, and other components to give meaning to what otherwise may just look like file name extensions.
The MetaLox airdrop is scheduled for Thursday, August 4. Then, a second MetaLox airdrop is scheduled again when the platform launches. That date will be announced later. This means that participants should expect the 1:1 airdrop completed twice.
It also means that the clock is ticking to set your trustline in time if you choose to participate.
The following paragraph will include the direct link to XRPL Services (please note, I intentionally did not link the trustline to that hyperlink; it’s just a link to XRPL Services homepage for your verification). For those unfamiliar, XRPL Services is basically just an interface to the XRPL that simplifies processes, like setting trustlines, and provides seemless integration with XUMM wallet.
If you use manual options, such as XRP Toolkit, please reference the information in the bulleted list above.
And, of course, if you choose not to participate, then there is no need to set a trustline.
Thanks as always for the support, #LoxFamily! – Team Lox