Extensions

Developers could opt to create extensions to add more features into NEM. However, to become an accepted extension, it should be proposed as a NEM Improvement Proposal.

The reason behind the NEM Improvement Proposal is to ensure that the new library is reviewed, tested and shared among NEM developers.

  • Accepted specification
  • At least one implementation that successfully passes the code review.
  • Compatible with third-party projects that implement/uses the same NIP Library.

Supported extensions

Name Description
catapult service bootstrap Starter project to get developers up and running with a running Catapult Service.
nem2-camel A component to turn the asynchronous transaction announcement into synchronous.

Community extensions

Name Description
Apostille library Transferable, updatable, branded, and conjointly owned blockchain notarizations.
Non-fungible asset library Work with unique and updatable assets.

Do you need to create a NIP to create an extension? No, you don’t. In fact, we suggest not submitting a NIP until you build a extension that improves the NEM blockchain and the different projects that use it. Since the extension can be changed multiple times, developers should spend more time experimenting and learning, creating a specification later on.

Add a new extension to this page by clicking the “Edit on Github” button at the top-right part of the screen.