SPACEMESH The next stage of cryptocurrency is easy to understand, safe to use, kind to the planet
On the protocol front, we finalized the design and began implementation work of the Hare certification round—the last major update to the Hare protocol for genesis. We’re also getting very close to finalizing several other important elements.
These include, firstly, the nonce scheme, which differs from the simple, sequential integer nonces that Ethereum uses, and better fits the mesh data structure. Secondly, the account data structures. Since we’re launching without light client support, we’ll be starting with a straightforward key-value database, but we need to factor in design considerations and do some future-proofing for upgrading to a trie structure later. And thirdly, the design for protocol versioning. This is an important tool to prevent cross-chain replay attacks, and to make sure that all relevant tooling (Smapp, explorer, dashboard, etc.) can support multiple chains at genesis.
Additionally, research efforts are underway regarding both SVM and the Accounts/Templates/Transactions model. The former involves discussions of the high-level tradeoffs among: account unification, consensus-execution decoupling (aka “miner-verifier separation”), semantic preprocessing of transactions, smart-contracts level metaprogramming (dynamic account creation, and dynamic template creation). The latter is well advanced, and will stand as a more formalized companion to the corresponding unified documentation chapters that we’ll begin publishing soon.
Regarding Smapp, we’ve entered the final testing phase of the latest Smapp release, which will include a new Modern Dark Skin and an updated meshing status screen that provides additional transparency regarding a smesher’s per-epoch eligibility and rewards. We began work on a Genesis Product Plan that includes upcoming updates and development of SMREPL, hardware wallet (Ledger) and Vault with MultiSig. We also started New API developments for Smeshing Statuses and Reward Estimation. This will expand into further API updates with the latest transaction format.