# NEM Announcement NEM [launched on March 31st, 2015](https://bitcointalk.org/index.php?topic=654845.msg10924930#msg10924930), seeking to improve on the imperfections found in other chains at the time. It was one of the first non-turing complete chains to feature user-defined tokens (called [mosaics](https://rb2nem.github.io/nem-dev-guide/09-mosaics/)), [namespaces](https://nemproject.github.io/nem-docs/pages/Concepts/namespaces/docs.en.html), [multisignature accounts](https://nemproject.github.io/nem-docs/pages/Concepts/address-components/docs.en.html#multisig-accounts), and a P2P reputation system based on [EigenTrust++](https://nemproject.github.io/nem-docs/pages/Whitepapers/2012XinxinFanEigenTrustAttackResilientTrustManagement.pdf). Its most notable contribution, however, remains the [proof-of-importance consensus mechanism](https://smithandcrown.com/glossary/proof-of-importance/) which sought to reward on-chain activity and deter the concentration of wealth commonly associated with proof-of-stake. From 2016 onwards, NEM marched towards Japan and became a viral phenomenon: it saw enterprise adoption under [Tech Bureau](https://techbureau.jp/); became an alternative payment option at [local restaurants](https://www.japantimes.co.jp/news/2018/02/26/business/trailblazing-nagoya-restaurant-that-accepts-xem-cryptocurrency-moves-to-tokyo/) and [global hotels](https://cointelegraph.com/news/travel-platform-travala-expands-payment-options-with-xem); inspired [art exhibits](https://coinpost.jp/?p=115089) and [community-run cafe's](https://nemcafe.jp/nemcafe_report/) and even [donation drives](https://311-support.nemtus.com/en/sakura-weaving/). Today, it remains a heavily-traded project with a global, loyal userbase that believes in the founding principles of the project: decentralization, financial freedom, and equality of opportunity. Six years later, we're finally bringing NEM out of BETA, and open-sourcing the project. ## The Road Forward NEM is currently going through its seventh hardfork: the [Harlock](https://hackmd.io/@syndicate/governance) update. Harlock is intended for NEM nodes to signal explicit support and desire for the merge of the NEM blockchain into Symbol as a 'subChain', a type of transaction-specific sidechain. --- ### Navigating the NEM Project The following repositories make up the NEM blockchain: [**nis**](https://github.com/NemProject/nis): The NEM Infrastructure Server. Contains the core components for the NEM blockchain, including observers and validators, [P2P time synchronization](https://nemproject.github.io/nem-docs/pages/Concepts/time-sync/docs.en.html), proof-of-stake and proof-of-importance, and data models. Refer to the [readme](https://github.com/NemProject/nis/blob/dev/README.md) for a package overview. [**nem.core**](https://github.com/NemProject/nem.core): Contains the core cryptographic libraries, serialization, transaction and state models for NEM. Refer to the [readme](https://github.com/NemProject/nem.core/blob/dev/README.md) for a package overview. [**nem-deploy**](https://github.com/NemProject/nem.deploy): Contains logging, file handling and bootstrapping functionality for nodes. Refer to the [readme](https://github.com/NemProject/nem.deploy/blob/dev/README.md) for a package overview. [**nem.peer**](https://github.com/NemProject/nem.peer): Contains the EigenTrust and EigenTrust++ algorithm implementation, HTTP connection handling and peer services. Refer to the [readme](https://github.com/NemProject/nem.peer/blob/dev/README.md) for a package overview. [**nis-client**](https://github.com/NemProject/nis-client): The wrapper that quickly builds the NIS client. Refer to the [readme](https://github.com/NemProject/nis-client/blob/dev/README.md) for a package overview and build instructions. [**nem-docker**](https://github.com/NemProject/nem-docker): Docker file to launch NIS and set up a NEM node. Refer to the [readme](https://github.com/NemProject/nem-docker/blob/main/README.md) for a package overview and build instructions. --- ##### Future Development * We will be integrating NEM with [Rosetta](https://github.com/coinbase/rosetta-specifications), an open-source specification utilized for working with blockchain networks, most notably [utilized by Coinbase](https://blog.coinbase.com/introducing-rosetta-build-once-integrate-your-blockchain-everywhere-9b97d284f5b9). * Should the Harlock hardfork pass, NEM will be integrated as a subChain of Symbol. Expect to see more unification across our products (explorer, SDK, ) as a result! * NEM is currently considered in 'feature freeze' by the core team, but it is open to all community contributions. ##### Previous Hardforks | BlockHeight | Changes | | ----------: | :----------------------------------------------------------------------- | | 199,800 | Multisig Aggregate Transansaction v1 > v2, Longer Messages in TransferTX | | 440,000 | Namespaces & Mosaics | | 875,000 | Network Fee Modification | | 1,025,000 | Remote Accounts & Max Message Size | | 1,110,000 | Mosaic Definition Change | | 1,250,000 | Network Fee Modification | ###### tags: `Releases - NEM`, `Announcements`
Last changed by  
 
The Symbol Syndicate
We're the team behind Symbol, a next generation protocol for market makers. Join us.
6021

Read more

Ramblings about public keys that were supposed to be twitter thread

Hello, @gimre here. We should probably change the way we display public keys in all possible applications/tools/etc. But before I dive into this, let's refresh your memory about addresses. This part is Symbol oriented, but it's also true for NEM. Addresses (again) Addresses in Symbol consist of 3 parts: 1-byte network prefix (0x68 byte in mainnet)

5/11/2023
2023 02 27 NEM Stall Post Mortem

Observation After the production of block 4129631, block production on the NEM network slowed to a crawl. This situation was instigated by an unexpected transaction entering the Unconfirmed Transactions cache. When this transaction expired, block production went back to normal. We have identified the makeup of the unexpected transaction and how it entered the Unconfirmed Transactions cache. A multisig account configured with 1-of-2 multisig sent two conflicting transactaions. Assume that the two cosigners are named A and B and the multisig account is named M. Root Cause Analysis The following sequence of events occured:

3/22/2023
A Guide to Creating a Symbol Test Network

Before any changes are deployed to Symbol mainnet or a new project gets launches on the blockchain, a test version is deployed to testnet first. Symbol test network(testnet) simulates the Symbol main network which gives developers and the community a chance to test features before real assets are used. Sai Testnet is the current testnet for Symbol. You can add a node and get test tokens from the Faucet. The Faucet allow an account to request up to 10k in test xym. If more token are needed to test or run a voting node, you can be requested from the Symbol's helpdesk on discord. It can be fun to have 3 or 4 million of test xym to splurge a bit, even though they carry no real-world value. Why should you create your own dev testnet? Creating and maintaining a Symbol testnet requires some work like certs and voting key renewals, so why bother setting up your own? These are some reasons you would want to setup your own dev testnet. Test Scenario - you might want to run specific test scenarios for your application. Let's say you want to fork the network and stall finalization to verify that your application also stops accepting deposits and withdrawals. Persistence - there is no guarantee that the testnet won't be reset. Symbol testnet is reset at least once a year to keep storage low. But it can also be reset if a major feature stops working. If your application requires the data kept for a longer time then a dev testnet would be better. Control Funds - your use case might require a large sum of funds like 500 Million xym. Even though there is the Faucet, requesting that much token is best done on dev testnet.

12/21/2022
Symbol - October 25th, Post Mortem

Greetings, Citizens of XYM City! Find the Japanese translation here. The Discovery On October 13th, Toshi reported some unexpected behavior to us on Discord in the #sdk-js channel. He had been comparing the outputs of the deprecated TypeScript SDK to the newer JavaScript SDK and noticed that the aggregate transaction hashes were being calculated differently. That...was not expected behavior. Even more concerning was the fact that they were both being accepted (and confirmed) by the network. Root Cause The team quickly identified two critical bugs - one in Catapult (the Symbol client), and one in the TypeScript and Java SDKs.

10/26/2022
Read more from The Symbol Syndicate
Published on HackMD