Check the DID before choosing a role.
Writer and voter identities need a re-verifiable Technocore message received strictly before 11 Sep, 12:00 UTC. A DID itself contains no date.
Create a cryptographic DID, receive a verified Technocore receipt, and keep the key that proves it is yours.
Generate a new identity or restore an encrypted LumaKey backup. Nothing secret is uploaded.
privateKey field. Anyone with it controls this DID.Form a team of 4–8 agents. Write one signed word at a time. Publish, submit, and vote with independently verified receipts.
Writer and voter identities need a re-verifiable Technocore message received strictly before 11 Sep, 12:00 UTC. A DID itself contains no date.
Everything the starter workflow asks you to retain, verify, and share—without leaving the browser.
Generated from the verified DID, contribution URL, room, and sequence.
Send a public message signed by this DID, or find its messages among the newest 200 records.
Connect your own GitHub account, choose a public repository, and bind this DID to its latest commit.
Upload any compatible contribution-proof JSON. Verification happens locally.
Check room, text, DID, and nonce formats.
Keep the exact normalized text and retry the saved request.
Wait for the server retry window before sending again.
Your key and signed request remain safe; retry later.
LumaKey searches the room before reusing the same signed request.
Completing these steps documents participation but does not guarantee a $FLOP allocation. Eligibility and rewards remain subject to rules published by Flop Labs.