Development

GitHub metrics:

Development is ongoing. Commits on public GitHub appears regularly, several times a day.

Developer activity (from Coinlib.io):

The IOTA Foundation announced the full release of the Trinity wallet on all major mobile and desktop platforms.

Trinity started from humble beginnings as a Computer Science summer project at University College London. The project gained traction among the IOTA community, and as it grew and entered alpha testing, the talented team of community developers and designers took full-time positions within the IOTA Foundation. And now, with over $1.8 billion worth of IOTA transacted and over 160,000 downloads across all platforms, Trinity has become a resounding success. With the results of world-leading cybersecurity firms, SixGen’s security audit, the stable, feature-complete wallet has been released in full.

But the people involved in making Trinity what it is today extend far beyond the IOTA Foundation. This is and has always been a community project. IOTA had thousands of community members tirelessly testing across alpha and beta, submitting bug reports and making feature requests. Others diligently translating strings to allow support for over 25 languages. And others contributing to the wallet’s codebase. Ultimately this is a project that has involved thousands of contributions from thousands of people.

Trinity holds two principles at its core: user-friendliness and security. A wallet should be straightforward to use for new and advanced users alike, while securing funds and protecting from external attack. Applying these principles at every stage of the development process has given rise to a wallet that makes generating, storing and backing up seeds and sending and receiving IOTA an extremely simple and secure process.

Our industry-leading wallet, Trinity, delivers on IOTA’s goal to provide secure, accessible and community-driven token storage for the international cryptocurrency marketplace -Dominik Schiener

Trinity is available across iOS, Android, Windows, Mac and Linux. Download it here.

Read the press release here.

Ict, Coordicide, and, of course, Qubic.

The base node currently carries on the Bee name and will be written in Rust. It will include most of the common node components that are needed by all projects, all tied together with a flexible messaging architecture. The actual projects will be built on top of this. This means that some boundaries between projects will disappear and the team can move people around to help out where necessary more easily.

The base node will be based on the experiences they had while building each project and borrows several elements from those projects that they found would result in the best modular architecture. To make good usage of their resources most original Omega team members will be focused on building this new base node. The new design is such that the functionality of several IXIs will be absorbed in the new messaging architecture without sacrificing the flexibility of the architecture. It should allow for easy and flexible insertion and replacement of modules and it should also minimize repetition of efforts by multiple projects.

The new architecture supports the Qubic supervisor component directly and will make integrating the Q-node functionality more easy. And because the basic requirements for any node are now clear they can already start building this base node while the Coordicide team finalizes their specifications. So once these specifications appear they will be able to directly start implementing them on a working base node. Doing it this way removes a bottleneck where otherwise they would have had to wait for the specifications first before they would have been able to start working on the Coordicide node.

This last part is where the importance of being able to meet face to face really stood out. In only a few days the team was able to hammer out a solid proposal for the Bee node with the parties involved and clearly separate base functionality from specific functionality. That would have taken weeks of messaging otherwise.

Now let’s see what all this means for the projects.

Ict

Lukas and Samuel, together with community member /alex/ and a few others will start building the Bee base node. Once this common base node is done they will probably move on to adding the Ict-specific parts to get a working Ict/Bee again.

FPGA

The FPGA team just got bolstered by hiring Jonathan Shaffer (formerly known as Beeef). They are now working on a new idea that should allow them to run Abra-based tritcode directly on FPGA without the intermediate resource-intensive step of generating, compiling and synthesizing Verilog code. This is a breakthrough of huge magnitude. Instead of having to build from tritcode for every type of FPGA out there specifically, they now only need to generate tritcode once and can load and run it on the fly. They’re currently designing and building the first Proof of Concept of this new system.

Qupla

Part 7 in the series of articles that explore the depths of the Qubic Computation Model (QCM) is still nearing completion. With all the reshuffling Eric Hop’s management duties took precedence and there was no time to finish it. But rest assured that he will make it happen soon(tm).

Evaldas (lunfardo) has been working in on the Qubic project and will probably take over some of Erics’ duties in that regard to allow him to help direct the overall development efforts on all projects that will use the Bee platform.

Coordicide

With the integration of all projects in the same platform it seems only natural that they include the Coordicide efforts from now on as well. To be sure, this means that the Qubic status update has become a lot less Qubic-specific over time, and it may be that they will rebrand it to engineering update or something like that. The team is still deciding on that, but until that happens they will happily update you about any Coordicide specific news in this new section.