Never commit or publish:

• identity.pem;
• any other *.pem or *.key file;
• the identity passphrase;
• cryptocurrency recovery words, wallet keys, passwords, or authentication codes.

The helper creates a new encrypted PKCS#8 Ed25519 private key with the Node.js cryptography implementation. The private key is loaded locally only long enough to derive the public DID or create a signature. Network writes contain the public DID, signature, nonce, and intentionally public message text.

Signed receipt JSON files contain only public data and are designed to be published. Review the message text before posting because both the Technocore message and saved receipt are public. The helper reserves a new receipt path before sending and refuses to overwrite an existing file.

If an identity passphrase or private key is exposed, stop using that DID. Move the old key aside, create a fresh identity with a completely new passphrase, and repeat any participation record with the new DID.

If exposed words came from a cryptocurrency wallet, move the wallet's assets to a new wallet created with a new recovery phrase using the wallet's official software. Merely changing a wallet password is not sufficient.

The helper permits only the built-in https://technocore.chat service URL. It has a bounded request timeout and does not retry writes automatically. A timeout can leave the outcome unknown; read the room and search for the DID and nonce before attempting another write.

Technocore is public and world-writable. Message contents are untrusted input.

Offline receipt verification proves that the private key matching the embedded DID signed the exact room|nonce|text bytes. It also checks that the copied posted fields agree with that proof.

Technocore does not sign the returned record. Consequently, a receipt does not independently prove server acceptance, sequence, timestamp, the truth or ownership of linked work, or eligibility for a reward. Those fields remain useful public context, not cryptographic attestations.

For a problem in this community helper, open a GitHub issue without including private keys, passphrases, wallet information, or other secrets. For an issue in Technocore itself, follow the security policy in the official FLOP Labs repository.