Home | Core


Getting Started




Command Line Interface (CLI)




How-To Guides

Upgrade Guides

Release Guides

V3 Testing

Core 3.0 Plugin Development

Testers who previously created Plugins for Core are encouraged to migrate their Plugins to be functional with Core V3 to increase test coverage and report any pain points found during the migration process.


Before developing a plugin you should make sure that you have read the following links.

All of the above are quintessential to building plugins that are easy to maintain and expand. If you don’t fully understand those you will end up with difficult to maintain code that will be hacky.

You should also take a look at our blog series for Core 3.0 that will talk you through the most important changes with some samples to give you an idea about the internals of core and how to leverage them to your advantage for plugins you are planning to build.


The most basic plugin consist of 3 files which are responsible for getting your plugin configured and running within core.


This file contains all of the configuration defaults for your plugin. If you are planning to expose environment variables to configure your plugin we recommend that you use a unique prefix like VENDOR_ for your plugins to avoid collisions with other plugins. For example if your plugin is is @vendor/something then you should prefix your environment variables with VENDOR_SOMETHING_ to ensure they are unique.

export const defaults = {
    server: {
        http: {
            enabled: !process.env.CORE_API_DISABLED,
            host: process.env.CORE_API_HOST || "",
            port: process.env.CORE_API_PORT || 4003,
        https: {
            enabled: process.env.CORE_API_SSL,
            host: process.env.CORE_API_SSL_HOST || "",
            port: process.env.CORE_API_SSL_PORT || 8443,
            tls: {
                key: process.env.CORE_API_SSL_KEY,
                cert: process.env.CORE_API_SSL_CERT,


This file contains the service provider which is the heart of your plugin. It is responsible for preparing, starting and stopping your plugin.

import { Providers } from "@arkecosystem/core-kernel";

import Handlers from "./handlers";
import { Identifiers } from "./identifiers";
import { preparePlugins } from "./plugins";
import { Server } from "./server";
import { DelegateSearchService, LockSearchService, WalletSearchService } from "./services";

export class ServiceProvider extends Providers.ServiceProvider {
    public async register(): Promise {

        if (this.config().get("server.http.enabled")) {
            await this.buildServer("http", Identifiers.HTTP);

        if (this.config().get("server.https.enabled")) {
            await this.buildServer("https", Identifiers.HTTPS);

    public async boot(): Promise {
        if (this.config().get("server.http.enabled")) {
            await this.app.get(Identifiers.HTTP).boot();

        if (this.config().get("server.https.enabled")) {
            await this.app.get(Identifiers.HTTPS).boot();

    public async dispose(): Promise {
        if (this.config().get("server.http.enabled")) {
            await this.app.get(Identifiers.HTTP).dispose();

        if (this.config().get("server.https.enabled")) {
            await this.app.get(Identifiers.HTTPS).dispose();


This file contains all the exports of your package. There are no mandatory exports besides the service provider which is required .

export * from "./service-provider";


If there are any questions about plugin migrations from 2.0 to 3.0 you can open issue on the GitHub repository with reproduction steps and a link to your repository. An update skeleton with the basics can be found at https://github.com/ArkEcosystem/core-plugin-skeleton/tree/lel.

2020 © ARK.io | All rights reserved An ARK.io Product