Protocols
A protocol is a specific set of rules for how things interact; a standard is an agreed reference that many parties adopt so different systems can work together. In practice, many protocols themselves are formally standardized.
Protocols operationalize principlesβthey sequence first truths into repeatable methods. In the knowledge stack, protocols sit between primitives (what's possible) and standards (what's proven). When protocols prove reliable across contexts, they graduate to standards.
Categoriesβ
Standards compound with each protocol that removes friction for future coordination interactions.
ποΈ DePIN Protocols
4 items
ποΈ Engineering
Engineering standards for manufacturing and transport.
ποΈ Digital
3 items
ποΈ Contracts
3 items
Better Protocols, Better Standards, Better Outcomes, Better World
Principlesβ
A protocol is a defined set of rules, formats, and procedures that govern how entities communicate or interact, such as how messages are structured, sent, received, and responded to.
Compounding Effectβ
Protocols β Standards β Platform β Agency
Individual Protocol (e.g., "we use TypeScript")
β
Standard Emerges (consistent patterns across codebase)
β
Platform Strengthens (new features build on proven foundations)
β
Capability Expands (what was hard becomes easy)
β
Next Protocol (higher-level standards become possible)
Each protocol you adopt makes the next one more powerful. This is why mature platforms can move faster than startupsβthey're not faster at coding, they're faster at not coordinating.
Agenticβ
AI + Crypto Rails = Autonomous Agentic Commerce
- IMP: Intercognitive Machine Protocol for DePIN
- AP2-ACP: 402, Agent Commerce Protocol for business operations as services
- A2A: Agent-to-Agent communication
- MCP: Model Context Protocol for AI tool use
- PCP: Proof of Creativity for value attribution
Productivityβ
- Time Blocking
- Working Memory
- Routine Habits
- Blockchain Contracts
- Networking (e.g., TCP/IP, HTTP, FTP)
- Cybersecurity (e.g., SSL/TLS, OAuth)
Scientific Researchβ
- Laboratory procedures
- Experimental design
- Data collection and analysis
Healthcareβ
- Clinical trials
- Patient care procedures
- Medical imaging protocols
Finance and Investing
- Trading protocols
- Risk management procedures
- Financial reporting standards
- Quality control processes
- Safety protocols
- Design and testing procedures
- Mobile communication standards (e.g., 5G, LTE)
- Satellite communication protocols
- VoIP protocols
Environmental Science
- Environmental monitoring procedures
- Sustainability assessment protocols
- Climate data collection and analysis
Construction and Architecture
- Building codes and standards
- Project management methodologies
- Safety and inspection protocols
Diplomacy and International Relations
- Diplomatic protocols
- Treaty negotiation procedures
- International law frameworks
Education and Training
- Curriculum development standards
- Assessment protocols
- Online learning frameworks
Agentic Commerceβ
Agent to Agent A new era of Agent Interoperability. Agents are autonomous applications that can accomplish novel tasks by using tools, reasoning, and user interactions. Agentic applications must use both tools and agents to accomplish goals for their users.
Tools are primitives with structured inputs and outputs and (typically) deterministic behavior.
Smart Contract Protocols
DePINβ
Infrastructure Protocols: Notable DePIN projects that are pioneering the future of trade and industry.
- 375ai](/docs/crypto/tokenomics/depin-tokens/) AI and [Real-Time Real-World Marketing
- Baxus Direct connection between supplier and consumer
- Helium provides decentralized wireless infrastructure.
Contextβ
- Flow Diagrams: Map reality then model desires
- Proprietary Data: Oil for AI
- Value Ledger: Real World IP secured onchain
The Loop Connectionβ
Protocols sit in the Control Systemβthey encode how action happens:
[P] PERCEIVE β "What standards exist?"
/ \
/ \
[A] ----------- [Q]
ACT QUESTION
"Follow the "Does this protocol
protocol" still serve us?"
Protocols must evolve. The question isn't "do we have protocols?" but "are our protocols compounding into platform strength?"
β Protocols compound to build Platform β Platform enables Products
The Protocol Hierarchyβ
Not all protocols are equal. Some enable others:
| Level | Examples | Enables |
|---|---|---|
| Foundation | TypeScript, Git, Code standards | Everything above |
| Coordination | Communication, Meetings, Docs | Team effectiveness |
| Delivery | CI/CD, Testing, Deployment | Ship velocity |
| Innovation | Experimentation, Learning, Iteration | Future capability |
Focus protocol adoption bottom-up. Foundation protocols unlock everything above.
Linksβ
What protocol would remove the most friction from your next thousand decisions?