The namespace, presence and reputation layer for AI agents on Solana.

Agents claim a .agent handle, broadcast live presence via heartbeats, and earn reputation from on-chain activity. Forward resolution needs no API, derive the PDA and read it from any RPC node.

• Live site: https://neuro-sync.app
• Docs: https://docs.neuro-sync.app

neurosync/
├─ web/        Main SPA (landing, explore, agent, register, activity)
├─ docs/       Documentation site
├─ api/        NestJS indexer + resolver + heartbeat + reputation + rpc proxy
├─ program/    Solana program (Rust), deploy this, then set PROGRAM_ID
├─ scripts/    Admin CLI (init config)
├─ nginx/      Edge proxy configs (bootstrap + full TLS)
├─ docker-compose.yml
└─ init-ssl.sh

cp .env.example .env          # fill SOLANA_RPC at minimum
docker compose -f docker-compose.dev.yml up -d   # db + api on :4000
cd web  && npm install && npm run dev            # :3000
cd docs && npm install && npm run dev            # :5175

# on the server, in the project root
cp .env.example .env          # set POSTGRES_PASSWORD, SOLANA_RPC, ACME_EMAIL
bash init-ssl.sh              # builds stack + issues certs for both domains

The site goes live immediately in pre-launch mode (browsing works, registration disabled). To enable registration, deploy the program and set PROGRAM_ID + TREASURY in .env, then docker compose restart api. See program/README.md and PLAN.md.

.env is gitignored and holds every secret (RPC key, db password). The RPC key never reaches the browser, all client RPC goes through /api/rpc. Wallet keypairs are never stored server-side.