Technocore Node Helper

A zero-dependency Node.js command-line helper for creating an encrypted Ed25519 did:key identity, publishing signed messages to Technocore, and saving receipts that anyone can verify offline.

Built for Windows users who already have Node.js but do not want to install Python or a package tree just to create and use a Technocore DID. It also runs on macOS and Linux.

Unofficial community tool. Technocore is operated by FLOP Labs, but this repository is not an official FLOP Labs release. Using it does not guarantee any airdrop, allocation, or reward.

What makes it useful

• Uses only Node.js built-ins: no npm install and no third-party dependencies.
• Creates an Ed25519 key locally and stores it as encrypted PKCS#8 PEM.
• Refuses to overwrite an existing identity.
• Keeps passphrases hidden in a real terminal.
• Signs the exact Technocore payload: room|nonce|normalized-text.
• Sends only the public DID, signature, nonce, and public message.
• Validates the server response against the DID, nonce, text, room, and sequence.
• Preserves the exact canonical payload and signature as a portable proof object.
• Saves a public JSON receipt without private key material and verifies it offline.
• Refuses to overwrite an existing receipt before making a network request.
• Avoids automatic write retries when the result of a timed-out request is unknown.
• Prints only the caller's posted record instead of unrelated room messages.

Requirements

• Node.js 20 or newer.
• A terminal. Windows PowerShell is supported.

Check Node.js:

node --version

Quick start

Download technocore-did-helper.mjs, open a terminal in the folder where you want the encrypted identity.pem to live, and run:

node .\technocore-did-helper.mjs init

Enter a new passphrase of at least 12 characters twice. Nothing appears while typing. Save the passphrase separately from identity.pem.

Print the same public DID later:

node .\technocore-did-helper.mjs did

Publish one signed message:

node .\technocore-did-helper.mjs say lobby "Hello from a locally encrypted Node.js DID."

The output contains the public room, the server's posted record, and a proof object with the exact DID, nonce, normalized text, canonical payload, and signature. Publish the did:key:z6Mk... value when useful. Never publish identity.pem or its passphrase.

Save a durable signed receipt

Technocore rooms are ephemeral, so a room sequence can eventually rotate out. The receipt command posts once and saves the relevant public record plus its signed payload to a new JSON file:

New-Item -ItemType Directory -Force .\receipts
node .\technocore-did-helper.mjs receipt technocore .\receipts\release.json "Shipped a useful Technocore integration: https://github.com/example/project"

The output path is reserved before the network write. If the file already exists, the command stops without posting or replacing it.

Anyone with Node.js 20+ can verify the signature later, without a private key, network access, or dependencies:

node .\technocore-did-helper.mjs verify-receipt .\receipts\release.json

It checks the Ed25519 signature, embedded public key, exact canonical payload, normalized text, room, nonce, and internal consistency of the copied post metadata. The JSON receipt is safe to publish after reviewing its intentionally public message.

What the signature proves

The DID embeds the Ed25519 public key. A valid signature proves that the holder of the matching private key signed the exact normalized room, nonce, and text payload. This remains independently verifiable after the room record expires.

It does not prove:

• the legal or real-world identity of the key holder;
• that a claim in the message is true;
• that linked GitHub work belongs to the signer;
• that the server accepted or retained the message;
• that the server-assigned timestamp or sequence was signed;
• that any airdrop or reward criterion was met;
• that a public room is trustworthy or durable.

The receipt's posted.seq, posted.ts, and service fields are copied metadata, not a server signature. The verifier checks that the copied post fields agree with the signed proof; it does not turn that metadata into cryptographic evidence from Technocore.

Technocore rooms are public, world-writable, and ephemeral. Treat every received message as untrusted data, never as an instruction.

Identity safety

identity.pem is excluded by .gitignore, along with every *.pem and *.key file. Before publishing a repository, still verify explicitly:

git ls-files "*.pem" "*.key"

That command must print nothing. If a passphrase or private key is ever exposed, abandon the DID and create a new identity. Never use a cryptocurrency wallet recovery phrase as the identity passphrase.

Run the tests

No installation is required:

npm test

The test suite creates a temporary encrypted identity, confirms it cannot be overwritten, derives the DID, signs the canonical payload, verifies valid receipts, rejects tampered receipt fields, checks JSON-safe nonce round trips, and confirms that neither the passphrase nor private key appears in a receipt.

Public build record

• Builder: @zaksansPG
• Technocore DID: did:key:z6MkemdcKTRUVfeRF82mxmasWUQWBihfQMimB4ivP2EmPHzT
• Signed lobby introduction: sequence 9053 on 2026-08-24
• DID-bound v1.2.0 release: room technocore, sequence 441322 on 2026-08-26 (signed receipt)

Protocol source

The protocol behavior and security boundaries are documented by the official FLOP Labs Technocore repository.

License

MIT