GRAPE — MEDIA FACT SHEET Updated: October 2, 2026 OVERVIEW Grape is a DAG-based network built around VINE, with EVM compatibility, GRP as its core currency, GGT for governance across much of the chain, and Daxly as its AI engine for software creation and ongoing autonomous work. The current product description brings together a graph-based network, programmable applications, currency, governance and AI. Contact Grape for current deployment details, approved quotes and interview requests. THE COMPONENTS VINE: Grape's network architecture. The technical paper describes transaction-containing sites that reference earlier sites in a directed acyclic graph. A parallel commit sequence coordinates ledger state, account balances and smart-contract results. GRP: The core currency that powers the Grape chain. Historical Grape material describes GRP as the main ecosystem coin, connected to access to ecosystem functions and services. GGT: The governance token. Historical Grape material describes proposals and voting on ecosystem direction, including decisions about support for projects launching on Grape. Current participation and execution depend on the active governance framework. Daxly: Grape's AI engine for creating software and supporting ongoing autonomous work. The AI product described in earlier Grape presentations has been renamed Daxly. ARCHITECTURE AND PARTICIPATION The VINE paper distinguishes light clients, which create and sign transactions, from full nodes, which verify transactions, assemble sites and exchange information with peers. Commit processing provides a coordinated ledger reference. These architectural roles are not a current node installation or enrollment specification. EVM compatibility is part of Grape's current product direction. Builders should obtain the current network configuration, supported releases and integration instructions before connecting an application. PERFORMANCE CONTEXT Grape's stated design capacity is up to 2,700 transactions per second per user node. This is a design specification, not a live measurement or an independently verified benchmark. Realized performance depends on implementation, hardware, network conditions and coordination. Do not multiply this figure into a claimed aggregate benchmark without supporting test evidence. SOURCE CONTEXT The VINE technical paper, v.02, is a 27-page architecture reference from an earlier implementation stage. Pages 8–12 describe the transaction graph, commits, contracts and node responsibilities. Pages 17 and 23 record implementation limitations at that stage. The paper is not an audit or proof of current production behavior. The supplied Grape presentation describes AI-assisted creation and application areas. Current GRP, GGT, EVM, Daxly and capacity descriptions above reflect Grape's updated product direction. Historical materials are background references, not confirmation of current sale terms, asset identifiers, launch dates or governance parameters. RESOURCES Grape beta website: https://beta.grap3.com/ Research: https://beta.grap3.com/research VINE technical paper: https://beta.grap3.com/assets/grape-techpaper.pdf Brand artwork: https://beta.grap3.com/brand Historical primary references for GRP and GGT roles: Grape Lightpaper V5, "Distribution: $GRP & $GGT" https://www.grap3.com/wp-content/uploads/2023/07/Grape-Lightpaper_V5.pdf GGT one-pager, "What is GGT?" and "Grape DAO" https://buy.grap3.com/images/GGT_one-pager.pdf These historical source URLs are provided for attribution; their current download availability is not confirmed by this fact sheet. CONTACT General, press, research and technical enquiries: info@grap3.com Please include your publication or organization, topic, questions and deadline when requesting media information.