tashi-primary-sources-2026-05-15

Tashi primary sources

Reviewed: 2026-05-15 UTC

Executive whitepaper / top-level framing

• https://docs.tashi.network/whitepaper/whitepaper.md
  • Best concise primary framing for this pass.
  • Used to confirm the basic three-layer architecture — Vertex, Lattice, and Arc — and Tashi’s positioning as coordination infrastructure for AI agents, robots, IoT, and gaming rather than a conventional public chain.
  • Also useful for confirming that the current whitepaper is an executive-style document with appendices and for anchoring the project’s own terminology around Proof of Coordination.

Vertex consensus layer

• https://docs.tashi.network/whitepaper/whitepaper/architecture/vertex.md
  • Best source for the local-consensus mechanism.
  • Used to confirm the leaderless DAG design, gossip-about-gossip, virtual voting, fairness claims, fast-finality framing, meshnet abstraction, and the role of Vertex in producing signed coordination outcomes.
  • Especially important because it makes clear that Vertex is not just a generic throughput claim or ordinary leader-based block production system.

Lattice node market / control plane

• https://docs.tashi.network/whitepaper/whitepaper/architecture/lattice.md
  • Best source for the practical control plane.
  • Used to confirm the Orchestrator-versus-Resource-Node split, discovery/routing/validation/failover functions, peer-attestation-based triangulated validation, reputation scoring, slashing thresholds, and the role of stake, location, and historical performance in job assignment.
  • This is the key source for identifying where control and rent concentrate in the current design.

Proof object and validation boundary

• https://docs.tashi.network/protocol/protocol/proofs-of-coordination.md
  • Best source for the portable output object.
  • Used to confirm that a Proof of Coordination minimally contains a supermajority signature set plus a hash of agreed data, that proofs are compact and independently verifiable, and that Orchestrators validate them before rewards are issued.
  • Also important for showing that the exact proof payload beyond the core signature-plus-hash guarantee is still being finalized.

Arc settlement layer

• https://docs.tashi.network/whitepaper/whitepaper/architecture/arc.md
  • Best source for the public-settlement boundary.
  • Used to confirm that Arc is activated only when private coordination outcomes need blockchain settlement, token issuance, asset transfer, or public signaling.
  • Helpful for making the architecture’s offchain-first design explicit: most coordination stays private and Arc is only the high-energy bridge to public chains.

Tokenomics / payment interfaces / reward mechanics

• https://docs.tashi.network/whitepaper/whitepaper/tokenomics.md
  • Best source for the economic control plane.
  • Used to confirm the USD- and USDC-based payment interfaces, Reward Points backed at 100 points per $1,the60/30/10revenuesplitacrossResourceNodes/Foundation/Orchestrators,the10,000$TASHI staking requirement per Resource Node, pooled staking, and the bonus structure for loyalty, staking, and peak-demand work.
  • Especially important because it shows apps do not need $TASHI to use the system; token demand is pushed toward operators and staking rather than end-user access.

Governance and maturity caveats

• https://docs.tashi.network/whitepaper/whitepaper/governance.md
  • Best source for current-centralization caveats.
  • Used to confirm the Foundation-led progressive-decentralization path, the future rather than present handoff of economic and network-parameter control to token holders, and the planned later open-sourcing of Vertex.
  • Important because it makes the present governance reality much more centralized than a generic decentralized coordination network label would suggest.

Main takeaways from this pass

• Tashi is best understood as a three-layer coordination stack: Vertex for local leaderless consensus, Lattice for global infrastructure validation and routing, and Arc for public settlement when needed.
• The most important control surface is not the DAG consensus claim alone. It is the Orchestrator layer that chooses jobs, validates proofs, manages reputation, injects failover, and co-signs rewards.
• Proof of Coordination is the distinctive portable object in the stack: compact, session-scoped, signature-backed, and usable for both reward validation and blockchain settlement.
• The current materials also expose real centralization boundaries: Foundation-led governance in the early phase, a still-proprietary Vertex core, and a payment interface that can run through a centralized gateway even though a direct-USDC path also exists.