Skip to main content
ROCSI
ROEN
Menu

Current Work / 02 / Active

Active
Domain
Open-source integration / Digital infrastructure
Started
2024 (public repository)
Development
Active open-source development
Environment
WordPress plugin / NMKR API

Connector for NMKR

An open-source connector that turns remote NFT project data into locally manageable, observable WordPress state.

NMKR Connect synchronizes Cardano and Solana project and token data through the NMKR API, stores operational state inside WordPress, and exposes synchronized data through responsive site components. ROCSI develops it as an integration project where reliability, recovery, observability, and public development are treated as first-class engineering concerns.

View source on GitHub ↗All Current Work →

01 / Why

External data is useful only when synchronization remains understandable and recoverable.

The integration problem

A WordPress site that depends directly on remote project and token data needs more than an API request. It needs a predictable way to import, reconcile, store, update, and present that data without turning every page view into an upstream dependency.

Long-running synchronization also creates operational questions: who owns the active run, what progress means before completion, how interrupted state is recognized, how duplicates are handled, and how failures remain visible instead of being mistaken for success.

Why ROCSI developed the connector

NMKR Connect gives ROCSI a concrete open-source environment for working on API-to-local-state integration, operational observability, recovery behavior, and public technical documentation inside a widely deployed content-management system.

The objective is not to abstract away WordPress or NMKR. It is to make the boundary between the remote service, the synchronization engine, local site data, and the presentation layer explicit enough to operate and inspect responsibly.

02 / Synchronization system

Remote source, explicit run state, local presentation.

The connector sits between WordPress and the NMKR API. Synchronization is treated as a run with observable progress and terminal state; project, token, detail, history, and metric data are persisted locally so front-end presentation is not coupled to a live upstream request on every render.

  1. 01

    WordPress site

    Administrators configure synchronization and site authors render synchronized project or token data through the plugin's registered shortcodes.

  2. 02

    NMKR Connect

    The connector coordinates API traversal, run ownership, progress, deduplication, reconciliation, terminal finalization, and recovery from stale or interrupted state.

  3. 03

    NMKR API / Studio

    Remote Cardano and Solana project and token information remains the upstream source; the connector does not present its local cache as an independent source of truth.

  4. 04

    Local data and metrics

    WordPress tables retain synchronized entities plus run history and operational metrics so current and historical behavior can be inspected without exposing credentials.

03 / What exists today

Synchronization, presentation, and observability are operational capabilities—not one opaque task.

The public repository contains the implementation and detailed procedures. This ROCSI page concentrates on the engineering responsibilities the project is exercising rather than reproducing the plugin manual.

Operational

  • Cardano and Solana project and token synchronization through the NMKR API with local WordPress persistence.
  • Run-scoped synchronization controls with progress, final result, history, metrics, and stale/interrupted-state recovery behavior.
  • Sequential token traversal with per-run UID deduplication, explicit reconciliation, and canonical completed finalization.
  • Responsive grid, list, carousel, single-token, and single-project shortcodes backed by synchronized local data.

In development

  • Continuing release, adoption, packaging, documentation, and maintenance work around the public plugin.
  • Extending regression coverage and operational checks around synchronization edge cases, compatibility, and recovery behavior.
  • Refining administrator-facing observability so progress, errors, historical runs, and relevant metrics remain useful without leaking secrets.

Exploring

  • Reusable patterns for moving external API data into inspectable local CMS state without hiding synchronization boundaries.
  • Additional presentation or integration surfaces only where they justify their operational and maintenance cost.
  • Ways to improve cross-environment diagnostics while keeping public logs, examples, and evidence safely sanitized.

04 / Engineering principles

A synchronization system should fail visibly before it succeeds falsely.

01

Remote and local state stay distinct

The local database is a managed synchronized representation, not a reason to obscure the upstream source or synchronization boundary.

02

Runs have explicit ownership

Long-running work needs a coherent active-run identity, terminal state, and recovery path rather than loosely related progress flags.

03

100% means finalized

Discovery progress remains provisional; completion is reserved for canonical terminal finalization after reconciliation succeeds.

04

Observability is operational control

Progress, errors, timing, history, and metrics help administrators distinguish slow work, interrupted work, and completed work.

05

Open development remains sanitized

Public code, tests, logs, screenshots, and examples must remain useful without exposing API keys, credentials, or private environment details.

05 / Research relationships

Integration work becomes infrastructure research when failure modes are treated as part of the system.

NMKR Connect connects ROCSI's durable research interests to operating open-source software, especially where external services, local state, and maintainable public infrastructure meet.

Open Digital Infrastructure

Exercises maintainable open-source infrastructure patterns around synchronization state, recoverability, observability, documentation, and public validation.

Emerging Technologies

Provides a practical integration layer for Cardano and Solana project/token ecosystems without making the website itself dependent on blockchain-specific presentation logic.

Explore ROCSI research →

06 / Project state

Active

Active

NMKR Connect remains under active open-source development. Delivered functionality is usable while release, adoption, maintenance, documentation, and reliability work continue in the public repository.

Current focus

  • Keep synchronization progress and terminal state trustworthy across normal, interrupted, and stale-run scenarios.
  • Maintain public validation and documentation that are useful without depending on private deployment evidence.
  • Move the project toward easier distribution and adoption without weakening operational or security boundaries.

07 / Direction

Strengthen the connector as maintainable open infrastructure.

Direction is driven by real synchronization behavior, public testing, release readiness, and the maintenance cost of each additional integration surface.

  1. 01Continue hardening synchronization, recovery, compatibility, and administrator-facing observability.
  2. 02Improve packaging, distribution, adoption, and contributor-facing documentation around the public repository.
  3. 03Carry reusable lessons from API synchronization and local-state management into ROCSI's wider open digital infrastructure work.

08 / Source / collaborate

The repository is the implementation record.

ROCSI uses this page to explain the project and its engineering concerns. Source, detailed procedures, validation material, and contribution history remain in the public GitHub repository.

View source on GitHub ↗View all Current Work →Open the Workbench →Discuss collaboration →

09 / Public project surfaces

Source and implementation stay inspectable.

The GitHub repository is the implementation record. The public project site provides the live-facing context without replacing source-level documentation.

Source repository

Open GitHub repository ↗

Public project site

Open public project site ↗