Honeycomb Protocol

Honeycomb Protocol provides APIs and SDKs to integrate Solana blockchain functionality into applications without requiring deep blockchain expertise. Key constraints and architectural details include:

• Blockchain Support: Currently designed exclusively for Solana.
• Modularity: Developers can use only the specific modules required for their application.
• Project-Centric Model: All data and functionalities are scoped to a 'Project'. A project represents a separate app; creating a project is typically the first step before using other features.
• Beta Status: The protocol is in beta; features may change or be incomplete.

To maintain security, Honeycomb Protocol distinguishes between project authority and delegate authority:

• Project Authority Keypair: Must NEVER be exposed to the client-side. It is recommended not to store this on the server-side either.
• Delegate Authority: Use the delegate authority system to grant fine-grained permissions to a specific keypair. This delegate keypair can be stored on the server-side to perform programmatic actions.
• Client-Side Restriction: Never expose any keypair (Project or Delegate) that can modify project settings to the client-side.

The following administrative and configuration tasks must be performed server-side for security:

• Projects: Creating/managing projects, changing project drivers, managing delegate authorities, and assigning badges.
• Users & Profiles: Adding XP, achievements, or custom platform data to profiles.
• Characters (NFTs): Creating assembler configs (and managing traits), creating character models and Merkle trees, minting characters, and updating traits.
• Resources: Creating resources, Merkle trees, recipes, and minting or importing/exporting resources.
• Missions: Creating mission pools and individual missions.
• Staking Rewards: Creating/updating staking pools, adding multipliers, and managing reward pools and Merkle trees for SPL tokens.

The following user-facing actions can be integrated client-side:

• Projects: Claiming badges.
• Users & Profiles: Creating user accounts, creating project-specific profiles (one per user per project), and updating profile data.
• Characters (NFTs): Wrapping and unwrapping characters.
• Resources: Transferring, burning, wrapping/unwrapping resources, and crafting/cooking items using recipes.
• Missions: Sending characters on missions and recalling them (which automatically claims pending rewards).
• Staking Rewards: Staking/unstaking characters or tokens, and claiming rewards (tokens remain staked during a claim).

Honeycomb Protocol provides multiple integration paths depending on the target platform:

• JavaScript/TypeScript: The @honeycomb-protocol/edge-client SDK is the primary library for web applications to construct, sign, and submit transactions.
• Unity (C#): A dedicated Unity SDK providing C# APIs and pre-built prefabs for Web3 functions.
• Godot (GDScript): A Godot-friendly interface and SDK for game integration.
• C++ (Unreal Engine): SDK support is available for Unreal Engine.
• MCP Server: An implementation of the Model Context Protocol (@honeycomb-protocol/mcp) that exposes on-chain infrastructure (projects, profiles, resources, etc.) via an STDIO interface for AI agents.