Extending NEM capabilities

Aside from creating a heavy and full-featured SDK, we are developing a robust and lightweight one. Thanks to this SDK, different libraries can be developed for each standard, on top of NEM2-SDK, allowing higher and faster growth for NEM applications.

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

Official libraries

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.
Name Description Active Developers
Camel A component to turn the asynchronous transaction announcement into synchronous. NEM Foundation

Community libraries

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

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

Name Description Active Developers
Apostille library Blockchain notarization and timestamping with transferable, updatable, branded, and conjointly owned notarizations. @luxtagofficial
Non-fungible asset library Work with unique and updatable assets. @aleixmorgadas