# TLDR; Gameplan is a scalable fan engagement platform built on a rollup architecture that leverages **Bitcoin’s proof-of-work** security, ensures privacy through **Zero-Knowledge Proofs (ZKPs)**, and supports **EVM-compatible** smart contracts for advanced functionality. #### **Core Architecture** * **Gameplan ID** serves as the decentralized identity system, anchoring user credentials and assets on-chain while enabling privacy-preserving interactions. * The platform uses a **rollup architecture** to scale transactions by processing them off-chain and settling them on-chain for efficient, fast interactions. * **ZKEVM** forms the core execution layer, supporting private and secure execution of Ethereum-compatible smart contracts. #### **Social Graph Management** * **On-Chain Social Graph**: Critical data like user identities and relationships (followers, connections) are stored on-chain, providing transparency and security. * **Off-Chain Social Data**: Larger datasets, such as interactions and messages, are stored off-chain in decentralized storage systems, while **cryptographic proofs** ensure data consistency and on-chain verification. #### **Governance Framework** * Gameplan operates under a **decentralized governance model**, allowing users to actively participate in decision-making. Fans and stakeholders vote on key decisions using token-based governance, ensuring community involvement in platform updates, feature development, and operational rules. #### **Security and Scalability** * **zk-Aggregation**: zk-Aggregation is used to batch and validate multiple transactions in a single proof, reducing costs and ensuring high throughput. * **Bitcoin Finality**: Transaction batches are anchored on the Bitcoin blockchain, leveraging Bitcoin’s proof-of-work security for irreversible transaction finality. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.gameplan.io/tech-specs/tldr.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.