Developers could opt to create extensions to add more features into Catapult. 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 Catapult 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 a private test network.
nem2-camel A component to turn the asynchronous transaction announcement into synchronous.

Ongoing work

Name Description
Apostille library Transferable, updatable, branded, and conjointly owned blockchain notarizations.
nem2-faucet Faucet application for Catapult.
nem2-hd-wallets Experimental library to handle hyper deterministic wallets for Catapult.
nem2-nonfungible-asset Experimental library to handle non-fungible assets for Catapult.
nem2-secret-sharing Implementing Shamir’s secret sharing on Catapult.
nem2-qr-library Experimental library to generate QR specification for Catapult.
nem2-uri-scheme Experimental library to handle uri scheme for Catapult.
nem2-wallet-browserextension Experimental browser wallet for Catapult.

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 Catapult 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.