After having been gone for almost 3 weeks I am finally back and I think its time for a short update as a lot of things happened in the last weeks:
1. We had a strategy summit in Berlin where we settled all remaining open discussions around things like tokenomics, and our vision.
I was asked to not share any details as we are planning to communicate this updated and extended vision in a "proper way" in the coming months, but I have to say that I am extremely happy with the outcome of these discussions and I couldn't have hoped for a better result (it ...
feels like we are finally fully aligned around what we can and want to build).
2. We finished the rewrite of the consensus related parts of our prototype and started preparing the integration into the general node framework (github.com/iotaledger/gos…).
There are still a few ...
... broken unit and integration tests but for the first time since starting the final rewrite (almost 3,5 months ago), the node actually compiles and runs in a network.
3. The goshimmer and the hornet team ceased to exist and joined forces to form a new and bigger ...
... engineering team that now works together on getting coordicide "mainnet ready".
Apart from debugging the current prototype, this mainly means to further clean up the codebase, increase code quality, documentation and test coverage + integrate the decisions we took in ...
... Berlin before merging the finished packages into the hornet code base.
I am extremely happy to finally work together with @der_muXxer and @alexsporn as these guys are top notch engineers and for the very first time since I joined IOTA we no longer have to split ...
... ourselves up between research and engineering.
There is still some work ahead of us but from now on, we will start to see the emergence of a final and unified code base that sees regular improvements ultimately leading to the first publicly deployed version of coordicide.
If you didn't follow the progress of IOTA, yet - now is the time to actually take notice!
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Move is the first virtual machine since the EVM to be adopted by a growing number of independent L1 projects.
What makes it so special and why is it destined to replace the EVM as the de-facto standard for smart contracts in the crypto-space?
Are you ready? Let's dig in!🧵
1. Move is the first VM that leverages "linear logic" (the logic of quantum information theory) to model a "virtual universe of digital assets" that is governed by conservation laws and that enforces that assets can never be duplicated or lost directly on the "language level".
2. In most other VMs, smart contract security relies heavily on developers following best practices.
One slip-up in managing token approvals or re-entrancy guards and user funds are at risk - even years after using a compromised contract and when keeping funds in a cold-wallet.
So it's finally time for part 2 of the update, in which I will explain how the reactive package allows us to merge metadata and logic to eliminate the problems discussed in the previous thread by getting rid of our 'external propagation logic'.
I will split the thread into several different segments to make it easier to associate the attached pictures with their respective text.
Since we plan to create blocks that act like 'interacting cells', we first need to create a mechanism that allows them to communicate.
For this purpose, we mimic the function of a 'receptor', which is a chemical structure on the membrane of cells that can bind to so-called 'ligands' to release a 'messenger'.
@Plinz I personally think that modeling multiway systems as rewrite systems that operate on a global continuous vector of data is a bit non-intuitive (and also pretty inefficient in code as you have to essentially duplicate the entire vector for each branch that you spawn).
In the ...
@Plinz ... context of Wolframs work, I even think that it leads to questionable conclusions like the proposal to explain the wave function collapse as a Knuth–Bendix completion of the multiway graph, which fails to explain things like Schrödingers Cat where different quantum states ...
@Plinz ... can lead to vastly different macroscopic outcomes.
A slightly different take on causal multiway systems that is also closer to the way we perceive the world is to model them as an evolution of "interacting substates / particles", rather than a continuous sequence of symbols.
I have lately received a number of messages, asking about the security of IOTA's new consensus mechanism in situations like network splits.
Since these questions seem to originate in factually wrong statements of a critic, I want to answer this question publicly.
(1/20)🧵👇
To understand how IOTA handles this type of situation, we first need to understand what a network split is.
It is a situation where the network is split into two (or more) disconnected partitions where each partition can only see their respective set of issued messages.
(2/20)
Most splits are the result of faulty network infrastructure causing temporary interruptions of connectivity.
Redundant hardware and connections have made large-scale network splits increasingly rare but smaller, locally confined partitions are still relatively common.
Apart from a lot of references to other papers, it contains only very hand wavy statements. I don't think they name a single concrete algorithm in the entire document.
@durerus@Conste11ation@Vrom14286662 It was promised that they would release updated papers and information, that would answer some of the questions I had, but I think this was delayed.
I wouldn't rule out that they work on something legit and I would give them the benefit of the doubt but everything that I ...
I think it's time for a short update around our progress on coordicide:
A few weeks ago we merged the refactored consensus code base and we have been running it in an internal testnet since then.
After fixing a lot of bugs, the node looks increasingly stable (we also found ...
... the memory leak that we were fighting with for almost 2 weeks - people who closely follow the development process on github will know what I mean).
The only remaining thing for the prototype to be feature complete in a first MVP version (apart from getting rid of ...
... possible remaining bugs) is the chain switching, which allows nodes to automatically recover after i.e. having being eclipsed / in a minority partition.
Me and Andrea started working on this 2 weeks ago but we had to pause and first change the way we manage state to ...