flybrainlabs/node

Authority and service APIs for flybrainlabs.

Durable goal competition, commit/reveal processing, full replay coordination, private artifacts, scientific publication, customer tickets and accounting APIs. The Marketplace catalog and checked financial domain are under development; production payments are not enabled.

• src/target_authority.rs
• src/product.rs
• src/economic_ledger.rs
• src/market/
• config/

Each imported file has one owning repository. component.json maps maintained files into the shared build layout. Dependencies are pinned by commit in the infrastructure release manifest.

Use Rust 1.90 or newer (the source uses edition 2024), Node 22 or newer and Python 3.11 or newer. Optional scientific Python dependencies are in tools/requirements-research.txt in the assembled workspace. SBF builds require the compatible Solana/Agave build tools.

First assemble the exact source revisions:

git clone https://github.com/flybrainlabs/infra.git flybrainlabs/infra
python3 flybrainlabs/infra/tools/workspace.py checkout --repos flybrainlabs
python3 flybrainlabs/infra/tools/workspace.py assemble --repos flybrainlabs --output flybrainlabs-workspace
cd flybrainlabs-workspace
npm ci

Run the applicable checks from the assembled workspace:

cargo test -p flypow --lib --test target_authority --test product_api --test market_catalog
cargo build --locked --release --bin target_authority

This transition keeps the existing cross-component import paths intact. Cloning this repository alone does not supply its external components. The assembler creates a disposable build layout; all maintained edits belong to the owning repositories. Use workspace.py sync for intentional changes made in that layout, then review the component diffs and validate them before publication.

Full-model and browser integration checks require existing, verified local resources and explicit arguments. They do not download a model or reset a browser profile by default. Isolated chain checks require their own local bank; production funds and addresses are never substituted.

• All maintained documentation, commit messages, issues, PRs and release notes are written in English. Product interfaces may remain bilingual.
• Completed, verified updates are committed and pushed automatically to flybrainlabs/node using normal fast forwards.
• Keys, wallets, customer inputs, node databases, private artifacts, browser profiles and model caches stay outside Git and website exports.
• Production payment and reward configuration remains disabled until its actual asset identities, authorities, funds and operating gates are satisfied.

See AGENTS.md, the development guide, architecture and status.

Project code retains the declared MIT OR Apache-2.0 license. Data descriptors and third-party assets retain their own source attribution and licenses; this code license does not relicense MaleCNS data or third-party libraries. The import preserves numerical/identity fixtures and does not reinterpret existing scientific or financial records. See NOTICE.

The finite Solana Devnet wallet-mining extension is described in the execution and acceptance record and canonical Result layout. Use the assembled workspace for cross-component imports and pinned release verification. Public receipts are in the contracts repository under deploy/wallet-mining-v3/; private signers, signed journals and full response archives remain outside source repositories. The two-unit acceptance budget is complete. Future paid work requires a new prospectively frozen finite plan. Actual extension-wallet and physical-device confirmation remain separate gates.

The Social service (tools/social_server.mjs) shares existing wallet sessions and SQLite/WAL while running separately on loopback 8791. config/social-community-v1.sql is an additive checksummed migration. Run npm run test:community, npm run typecheck:community and npm run lint:community in the assembled workspace. The new API/provider/client modules opt into JavaScript type checking; legacy financial modules retain their existing validation suites. No relayer or asset execution is started by the Social service. See docs/social-community-system.md.