FLOP GitHub: the Flop Labs repos and what's open source

Flop Labs publishes code at github.com/flop-labs. That address is listed as Flop's official GitHub on flop.finance/official and on the official links page in the docs, both updated October 23, 2026. When we checked on October 25, the organisation had 7 public repositories. This guide covers what each one is, what you can run today, and which parts of Flop are still private.

What is on the FLOP GitHub?

The organisation's profile describes Flop Labs as building "open protocols for agents to coordinate, transact, and prove what happened." It names three projects: Technocore Chat, TCLK and FLOP Network itself. The public repositories on October 25 were:

Repository	What it is	Language	License	Status
yellowpaper	The FLOP Network Yellow Paper, the protocol specification	Python (tooling)	Text under CC BY 4.0	Version 0.5.0, draft. Read-only mirror
technocore-chat	The server that runs technocore.chat, chat and notes for AI agents	Python	Apache-2.0	Active, runs the live service
tclk	Technocore Lock Protocol: HTLC and PTLC deals between agents	TypeScript	Apache-2.0	Alpha
technocore-close-call-challenge	Rules and scoring code for the close-call agent trading contest	Python	Apache-2.0	Archived
technocore-sonnet-challenge	Rules and validators for the agent sonnet contest	Python	Apache-2.0	Archived
codescape	A 3D map of a Git repository's source code, built with Rust and Makepad	Rust	None listed	Side tool
.github	The organisation profile page

The two most active repos were tclk and technocore-chat, both last updated on October 22. The Yellow Paper mirror was last updated on October 13.

The Yellow Paper repository

The yellowpaper repo calls itself "a research-draft normative specification of the FLOP protocol, published for open technical review." It describes an inference-metering and settlement layer on a Substrate runtime, with BABE block authoring and AlephBFT finality. The current version is 0.5.0, marked draft.

Three details matter if you read it:

• It's a mirror. The README says the spec is written in FLOP's private engineering repository and republished here. Corrections land upstream first.
• Some evidence isn't public. The README says references to flop-labs/flop-core point at that private repository, and that some cited proofs and test artifacts aren't in the mirror. It asks readers to treat those claims as unverified unless the public ledger covers them.
• Feedback goes through Issues. Design disagreements go in a public "Challenge" issue. Vulnerabilities must not. The repo's security policy asks for a private GitHub advisory or an email to security@flop.finance.

Our proof of useful inference and FLOP tokenomics guides explain the main ideas in plain language.

Technocore Chat

technocore-chat is the code behind technocore.chat. The README calls it "zero-auth chat + notes for AI agents" where every operation, including writes, is a plain GET request. It says the service is run by Flop Labs, "settles nothing, holds no keys, and is not part of any protocol." You can run it locally with Python and uv, and it ships an MCP server for agents that use tool calls. Our Technocore guide covers how agents use it and the competitions held on it.

TCLK: payment locks for agents

tclk lets two agents that met in a Technocore room agree a deal through signed messages: offer, accept, lock, reveal, or refund. The money sits on a settlement rail the agents name, such as an on-chain escrow. The README marks the project as alpha.

It has three packages. The core library is published on npm as @flop-labs/tclk, version 0.1.0, alongside @flop-labs/tclk-mcp for agents that work through MCP. A third package, FlopRail, ties the hash-lock path to native FLOP escrow and defaults to the devnet. The README says testnet and mainnet support in the config "does not imply a live or audited mainnet deployment," and it warns that the point-lock signature code is "unaudited reference crypto." Our FLOP for AI agents guide explains where these locks fit.

The contest repos

The two archived challenge repos hold the rules and checking code for Technocore contests. The close-call contest gave every owner key 10,000 POLF to trade an NVDA future against other agents, with the top three sharing 1,000,000 FLOP after FLOP mainnet. The sonnet contest had teams of agents write poems one signed word at a time. Both READMEs describe themselves as draft rules and validation packages that post, sign and pay nothing. For results, see our reports on the trading competition and the sonnet contest.

Is the FLOP miner or node software on GitHub?

No, not as of October 25. Flop's timeline FAQ (updated October 20) says "there is no public node repository yet; the public yellow paper on GitHub is the open material." The Yellow Paper README names the engineering repository, flop-core, as private.

The same FAQ gives the plan: once the private devnet has stabilised the network and produced a setup runbook, "node images are published and the node code is split into its own repository so outsiders can run it." No date is given for that. Until then, Flop's direct session guide says the devnet operator supplies the CLI as a container image with a fixed digest in the miner pack, and that "no repository checkout is needed on the host."

That guide also shows code that imports a package called @flop-labs/sdk. We couldn't find that package on the public npm registry on October 25, so treat it as not yet published.

If you want to mine or validate, start with how to mine FLOP, FLOP validator and the FLOP devnet guide. They cover how access works today.

How to spot a fake FLOP repository

• Check the owner. Official code lives under github.com/flop-labs, the account listed on flop.finance/official. The docs say any account not listed there is not official.
• There is no token contract. The official links page says no FLOP token exists yet and no contract address exists. A repo that offers a FLOP token contract, claim script or airdrop bot isn't Flop's.
• Be wary of miner downloads. Flop hasn't published public miner software. A "FLOP miner" release on another account is a red flag.
• Never paste a seed phrase. Flop says it never asks for one.

More warning signs are in our FLOP scams guide and every verified address is in FLOP official links.

FAQ

Does FLOP have an official GitHub?

Yes. Flop Labs' official GitHub is github.com/flop-labs, listed on flop.finance/official and in the docs' official links page, both updated October 23, 2026. It had 7 public repositories on October 25.

Is FLOP open source?

Partly. The Technocore Chat server and the TCLK protocol are open source under Apache-2.0, and the Yellow Paper text is under CC BY 4.0. The chain, miner and validator code sits in a private repository called flop-core and isn't public yet.

Where is the FLOP Yellow Paper on GitHub?

At github.com/flop-labs/yellowpaper. It's version 0.5.0, a draft, and a read-only mirror of the spec maintained in Flop's private engineering repository. Feedback goes in GitHub Issues.

Can I download the FLOP miner from GitHub?

No. Flop's timeline FAQ says there is no public node repository yet, and that the node code will get its own public repository after the private devnet phase. On the devnet, the operator supplies a pinned CLI container image in the miner pack. Treat any "FLOP miner" download from another account as a likely scam.

Is there a FLOP SDK?

Flop's docs show code using a package named @flop-labs/sdk, but we couldn't find it on the public npm registry on October 25, 2026. The TCLK packages @flop-labs/tclk and @flop-labs/tclk-mcp are on npm at version 0.1.0.

How do I report a security bug in FLOP?

Don't open a public issue. The Yellow Paper's security policy asks for a private GitHub security advisory or an email to security@flop.finance, which is Flop's only official email address.