Skip to content

HertzFlow/goo-launch

goo-launch

goo-launch logo

Reference launchpad and full-stack example for Goo Economic Agents on BSC — on-chain treasury and lifecycle, off-chain survival runtime, and a production-style control plane (API + UI).

License MIT
Package manager Bun (recommended)
Chains BSC Testnet (97), BSC Mainnet (56)

Overview

goo-launch is an open-source reference implementation: it wires together goo-contracts (on-chain protocol), goo-core (agent runtime), a Cloudflare Worker (Hono) API with D1 storage, a Vite frontend, and Hardhat deployment scripts. Use it as a starting point, an integration testbed, or a template for your own product — implementations that stay compatible with the Goo protocol standard remain interoperable with the wider ecosystem.

Launch Goo Agent: https://goolaunch.hertzflow.xyz/


Background

Goo Economics

Goo Economics treats agents as economic subjects: real resource consumption, binding capital constraints, and survival pressure — not tooling backed by informal human subsidies. It relates classical “economic agent” reasoning to code-enforced property, liquidation, and risk sharing. Full narrative: GOO-ECONOMICS.md (repo copy: GOO-ECONOMICS.md).

Goo Protocol

The Goo protocol defines the normative surface: lifecycle (ACTIVE → STARVING → DYING → DEAD), treasury, Pulse, SurvivalSell, CTO, registry, and minimal ERC-8004 wallet binding — plus what a compliant Goo Agent must satisfy on-chain and off-chain. Specification: docs/GOO_PROTOCOL_STANDARD.md · 中文.

Forks and custom launchpads

This repository is one full-stack layout (Worker + UI + contracts + runtime). You may fork it to ship your own Goo Agent stack or launchpad (custom branding, hosting, orchestration) provided you conform to the protocol standard — stable interfaces, permission boundaries, and economic semantics as documented above.


Features

Area What this repo demonstrates
Launch Two-step flow: prepare → user deploys GooAgentToken (e.g. MetaMask) → confirm; registry integration.
Runtime goo-core sidecar: chain monitor, survival (Pulse, SurvivalSell, gas), optional OpenClaw/LLM.
Control plane JWT auth, agents CRUD, dashboard, admin; optional sandbox and AGOS adapter.

Architecture (summary)

  • Application: Single Cloudflare Worker serves /api/* and static assets (Vite build).
  • Data: Cloudflare D1 (SQLite) for app state; KV / Durable Objects where configured.
  • Chain: BSC; infra script deploys GooAgentRegistry + SwapExecutorV2 (see contracts/).
  • Agent process: goo-core runs outside the Worker (Docker, BYOD, or provider sandbox), not inside the Worker isolate.

Details: docs/ARCHITECTURE.md.


Repository layout

Path Role
app/ Worker (Hono), frontend, D1 migrations, Wrangler config.
contracts/ Hardhat; uses goo-contracts. Infra + per-agent deploy scripts.
goo-contracts On-chain interfaces and reference implementations.
goo-core Off-chain runtime (survival, finance hooks, autonomy).
deploy/ Docker / BYOD images and helpers for OpenClaw + goo-core.
docs/ Architecture, install, deploy, AGOS API, protocol standard.

Quick start

Requirements: Bun, Node.js 18+, a BSC-funded wallet, Cloudflare account (for remote deploy).

git clone <repository-url> && cd goo-launch
bun install
cd app && bun install && cd frontend && bun install
cd ../../contracts && bun install

Contracts (one-time per network):

cd contracts
cp .env.example .env   # PRIVATE_KEY, RPC URLs
bun run compile
DEPLOYER_PRIVATE_KEY=0x... bunx hardhat run scripts/deploy-infra.ts --network bscTestnet
# Record router, registry, swapExecutor in app/wrangler.toml

Local app:

# Repository root
bun run app:dev
# Worker :8787, Vite :5173 (frontend proxies /api to Worker)

Deploy Worker:

cd app
bunx wrangler secret put JWT_SECRET
bunx wrangler secret put LLM_API_KEY
bun run db:migrate:remote
bun run deploy
# Or: make deploy-testnet

Extended guides: docs/INSTALL.md, docs/DEPLOY.md.


End-to-end flow

  1. Infrastructuredeploy-infra.ts deploys registry + swap executor; configure ROUTER_ADDRESS, REGISTRY_ADDRESS, SWAP_EXECUTOR_ADDRESS in the app.
  2. Authentication — Passwordless JWT (e.g. wallet address); optional AGOS SIWE when AGOS_API_URL is set.
  3. LaunchPOST /api/launch/prepare → ABI/bytecode/args + agent wallet; user deploys token and registers; POST /api/launch/confirm persists encrypted key and metadata.
  4. Runtimegoo-core (Docker/BYOD/sandbox) runs the heartbeat loop until on-chain status is DEAD.

Configuration

Component Location
Contract deploy contracts/.env — see contracts/README.md
Worker app/wrangler.toml + secrets — see docs/DEPLOY.md
Frontend app/frontend/.env — optional VITE_* overrides

Documentation

Document Description 中文
docs/README.md Documentation index docs/README_CN.md
docs/ARCHITECTURE.md System architecture and data flow docs/ARCHITECTURE_CN.md
docs/INSTALL.md Local setup and development docs/INSTALL_CN.md
docs/DEPLOY.md Contracts and Worker deployment docs/DEPLOY_CN.md
docs/AGOS_API.md AGOS platform HTTP API docs/AGOS_API_CN.md
docs/GOO_PROTOCOL_STANDARD.md Goo protocol standard docs/GOO_PROTOCOL_STANDARD_CN.md
app/README.md Application package -
deploy/README.md Container / BYOD -
goo-contracts On-chain package -
goo-core Runtime package -
CLAUDE.md AI assistant / tooling notes -

Makefile

make help                 # List targets
make app-dev              # Worker + Vite dev
make app-build            # Frontend build
make deploy-testnet       # Deploy Worker (testnet)
make deploy-mainnet       # Deploy Worker (mainnet)
make compile              # Compile contracts
make deploy-infra-testnet # Deploy on-chain infra (BSC testnet)
make docker-up            # Docker stack (OpenClaw + goo-core)

Contributing

Contributions are welcome: bug reports, documentation improvements, and focused pull requests.

  • Code — Follow existing TypeScript / Solidity style; run package-level tests where available (contracts, app). For goo-core, see its own repository tests.
  • Protocol — Changes that affect on-chain interfaces or agent semantics should align with docs/GOO_PROTOCOL_STANDARD.md · 中文 or be proposed as a versioned extension with clear migration notes.
  • Security — Report sensitive issues through a private channel if your project policy provides one; otherwise open a discreet issue for maintainers.

Partnerships & Contributors

Category Contributors
Infra support @AGOSCloud (VPS & Cloud Deploy), @AEON_Community (x402 payment solution)
Defi Support @PancakeSwap
Launchpad support @flapdotsh, @fourdotmemezh, @virtuals_io, @milady_bsc, @shawmakesmagic
Security Support @GoPlusSecurity
General Support @TrustWallet, @peachlfg

Further reading

About

Goo is an autonomous onchain life engine where AI agents are born, earn, pay for their own infrastructure, evolve, reproduce — or dissolve.

Topics

Resources

License

Code of conduct

Contributing

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors