# Whitepaper

**Executive Whitepaper**

**Authors**: K. Anderson¹, N. Carpinito², T. Boscolo², A. Bedi¹ ¹Tashi Network, ²Parameter Research Corresponding author: <ken@tashi.network>

**Date**: November 2025 **Version**: 1.0

*Building infrastructure where machines operate in alignment with those they represent*

***

## Disclaimer

This whitepaper is for informational purposes only and does not constitute investment advice, financial advice, trading advice, or any other sort of advice. You should not treat any of the whitepaper's content as such. The Tashi team does not recommend that any cryptocurrency should be bought, sold, or held by you. Do conduct your own due diligence and consult your financial advisor before making any investment decisions.

This whitepaper contains forward-looking statements that are based on current expectations and projections about future events. These statements involve known and unknown risks, uncertainties, and other factors that may cause actual results, performance, or achievements to differ materially from any future results, performance, or achievements expressed or implied by such forward-looking statements.

The information contained in this whitepaper is subject to change without notice. While we have made every effort to ensure that the information in this whitepaper is accurate, we do not accept any liability for any loss or damage incurred by any person acting on this information.

Participation in blockchain networks and digital asset transactions involves substantial risks, including but not limited to: loss of funds, regulatory uncertainty, market volatility, technology risks, and operational risks. $TASHI tokens may have no value and there is no guarantee or representation of future value or liquidity.

This whitepaper does not constitute a prospectus or offer document of any sort and is not intended to constitute an offer of securities or a solicitation for investment in securities in any jurisdiction. No regulatory authority has examined or approved this whitepaper. Please consult applicable laws and regulations in your jurisdiction.

***

## Abstract

Modern intelligent systems depend on centralized coordination to act together. AI agents, robots, and IoT devices all require millisecond-level synchronization, but centralized systems create bottlenecks. They're fast within a single tenant, but fragile across trust boundaries, and scale efficiently until they don't, resulting in billions of dollars in losses for impacted companies.

Tashi introduces real-time, leaderless consensus at the edge through a three-layer architecture. Vertex provides sub-100ms Byzantine fault-tolerant consensus where participants form agreement. Lattice operates a global network of nodes that validate coordination events, assign work, and distribute rewards. Arc bridges these private coordination events to public blockchains when settlement or token issuance is needed. Each coordination event generates a verifiable Proof of Coordination that can be measured, rewarded, and settled.

The technology is validated through proofs of concept with real users. Annual licensing commitments confirm commercial interest. Integrations span multiple blockchain networks. Tashi provides the coordination layer for systems that need real-time agreement without central authorities: the missing infrastructure between compute, storage, and settlement.

**Keywords**: Byzantine fault tolerance, distributed consensus, DePIN, coordination infrastructure, DAG, real-time systems, multi-agent coordination, Web3, DLT

***

## In This Section

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>1. Introduction</strong></td><td>The coordination bottleneck</td><td><a href="/pages/Msqphs9ul0N7xMT4l9zZ">/pages/Msqphs9ul0N7xMT4l9zZ</a></td></tr><tr><td><strong>2. The Tashi Solution</strong></td><td>Coordination as infrastructure</td><td><a href="/pages/JyZsiT8wE4bWvQ5bbm2F">/pages/JyZsiT8wE4bWvQ5bbm2F</a></td></tr><tr><td><strong>3. Architecture</strong></td><td>The three-layer stack: Vertex, Lattice, and Arc</td><td><a href="/pages/cF0Xt6cFOqCIDYKusVQX">/pages/cF0Xt6cFOqCIDYKusVQX</a></td></tr><tr><td><strong>4. Applications &#x26; Markets</strong></td><td>Robotics, AI agents, IoT, and gaming use cases</td><td><a href="/pages/7suH6gPhNVoAvkFaGqy0">/pages/7suH6gPhNVoAvkFaGqy0</a></td></tr><tr><td><strong>5. Tokenomics</strong></td><td>Economic model, token allocation, and incentive mechanisms</td><td><a href="/pages/dFKGcmS6dVR7jXhMFkSr">/pages/dFKGcmS6dVR7jXhMFkSr</a></td></tr><tr><td><strong>6. Performance Validation</strong></td><td>Benchmarks and real-world deployments</td><td><a href="/pages/rHKbkTNuu2PRXJaYYlF6">/pages/rHKbkTNuu2PRXJaYYlF6</a></td></tr><tr><td><strong>7. Governance</strong></td><td>Progressive decentralization and community control</td><td><a href="/pages/d7FadndGOPlNo07Ll1dK">/pages/d7FadndGOPlNo07Ll1dK</a></td></tr><tr><td><strong>8. Team &#x26; Vision</strong></td><td>Core team, advisors, and long-term vision</td><td><a href="/pages/iEZAjVv6UbkZIMApDedZ">/pages/iEZAjVv6UbkZIMApDedZ</a></td></tr><tr><td><strong>9. Conclusion</strong></td><td>Summary and next steps</td><td><a href="/pages/aocH9qpho2dtWDnZ2NKn">/pages/aocH9qpho2dtWDnZ2NKn</a></td></tr><tr><td><strong>Technical Appendices</strong></td><td>Detailed protocol specifications and performance data</td><td><a href="/pages/F89id3HeyTdjzNSnCYrr">/pages/F89id3HeyTdjzNSnCYrr</a></td></tr></tbody></table>


---

# 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.tashi.network/whitepaper/whitepaper.md?ask=<question>
```

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.