How cryptofamilynft/oobe-protocol works
Project type and purpose
• This is an open-source, monorepo-style Node.js SDK (library) designed to build and manage Solana-based AI agents.
• It provides core abstractions (ConfigManager, OobeCore), a registry of Actions/Operations, on-chain agent personality modules, memory layers (Merkle trees, DB), and tool-creation helpers for DEXes, RPCs, and AI services.
File structure
• Top-level:
• pnpm-workspace.yaml / package.json – monorepo config
• packages/core – the main TypeScript SDK (src + dist)
• packages/system – a minimal “system” wrapper or example
• packages/core/src organizes by feature:
• actions/ – discrete on-chain or AI “actions” (agent, IQ, JUP, Orca, Ray, Solana, etc.)
• agent-personality/ – engine, logic, state & on-chain personality modules
• agent/ – core Agent classes and Persona abstractions
• config/ – ConfigManager, default config, tool configuration templates
• operations/ – “higher-level” operations built atop actions (e.g., dex.operation, merkle.operation)
• utils/ – RPC, Solana helpers, Merkle, logger, SmartRoundRobinRPC, etc.
• types/ – all interfaces for DI, plugin contracts, proofs, DEX, DB, agent, etc.
• packages/system is a thin layer that re-exports core or provides a CLI.
README for additional insights
• Core classes: ConfigManager, OobeCore, AgentExecution
• External dependencies: Solana RPC clusters, OpenAI API, MongoDB/Redis for history
• Key workflows: initialize config → start OobeCore → register actions/tools → execute agent logic → memory persistence → on-chain inscription