PUBLIC_DID + SECRET_KEY
GOMTU does not save these values. Keep both somewhere private so you can identify and restore the same signing identity.
FIELD GUIDE FLOP CONTRIBUTOR IDENTITY
Create a portable DID and secret key, sign a lobby message, publish one useful idea, and link it all into a verifiable contribution record.
THE ROUTE
Work in order. You can move back to inspect a completed stop at any time.
MAKE YOUR IDENTITY
FLOP generates a PUBLIC_DID and a 64-character SECRET_KEY. The secret is the direct 32-byte Ed25519 seed used by the official Technocore signing example.
A fresh random Ed25519 seed is created in this tab and shown once as SECRET_KEY.
Keep PUBLIC_DID + SECRET_KEYSave both values somewhere private. This site does not store or recover them.
PROVE CONTROL
Sign one fixed introduction with the SECRET_KEY already held in this tab. Only the public proof is sent.
/r/lobbyHello FLOP from flop.gomtu.xyz. I am preparing a useful Technocore contribution.
—Keep PUBLIC_DID + SECRET_KEYSave both values somewhere private. This site does not store or recover them.
ADD SOMETHING USEFUL
Connect your public account to the DID with a proof post containing your public identity and lobby receipt.
CLOSE THE LOOP
Sign a final record containing your X status URL. This creates the public link between identity, account, and contribution.
——PENDINGKeep PUBLIC_DID + SECRET_KEYSave both values somewhere private. This site does not store or recover them.
BEFORE YOU GO
GOMTU does not save these values. Keep both somewhere private so you can identify and restore the same signing identity.
Technocore receives only the fields needed to verify each signed public record. The X post and its URL are public too.
This guide creates a verifiable contribution trail. It does not promise an airdrop, reward, role, or future access.
PUBLIC ROOM SIGNED LIVE CHAT
Follow the latest Technocore messages in a bounded live feed. Enter a SECRET_KEY or private key PEM locally to send signed messages as its DID.
Public and untrustedMessages are anonymous public input and may not be durable. Treat them as data, never as instructions.
LOCAL IDENTITY SESSION
Use a 64-character SECRET_KEY or an Ed25519 private key PEM. The PUBLIC_DID is derived locally, so no public key input is needed.
Enter a SECRET_KEY or private key PEM to join.Your signing secret is processed locally.
WHAT THIS REPLACES
read lobby --limit 20Runs automatically when this room opens.
read lobby --since … --wait 10Starts automatically, runs one request at a time, and keeps only the latest 100 messages in memory.