PLAYBOOK.md
Vertex Swarm Integration The Aether Bridge utilizes Vertex 2.0 as its primary coordination layer. By stripping out central orchestrators, our agents use the Vertex P2P mesh to discover peers and verify transaction state in milliseconds, ensuring zero cloud dependency and maximum resilience
This repository contains the leaderless settlement layer for AetherUX, utilizing the Vertex/Tashi consensus engine for resilient P2P coordination.
- x402 Intercepts: Dynamic fee and settlement redirection at the agent level.
- Stateful Handshake: Real-time state replication via Tashi FoxMQ.
- Blackout Mode: P2P IOU persistence when primary RPCs are unavailable.
/agents/aether_agent.py: Core logic for the Stateful Handshake and x402 intercepts./tashi/docs: Technical architecture and protocol specifications./contracts: (If applicable) Soroban/Stellar settlement hooks.
- Install dependencies:
pip install tashi-sdk(simulated) - Launch Agent A:
python agents/aether_agent.py --id Alpha - Launch Agent B:
python agents/aether_agent.py --id Beta🛠️ Local Setup Configure Environment: cp .env.example .env Add Keys: Open .env and enter your TASHI_CELL_ID and TASHI_API_KEY from the Tashi Console.
Launch Node: npm install npm start
- "The 60-Second Blackout Stress Test" (Reproducibility) The judges emphasized that "Localhost is a graveyard." You need a clear section that tells them exactly how to see the resilience for themselves.
How to Run the Resilience Demo:
Install dependencies: pip install ecdsa
Execute the simulation: python3 blackout_sim.py
What to look for: Observe the script simulate a Cloud API failure, trigger a local hardware-anchored signature (NIST P-256), and successfully dispatch the swarm via the local P2P mesh.
- "Vertex BFT Integration & FoxMQ Coordination" The judges are specifically looking for how you handle failures using their preferred stack. Add a "Coordination Layer" section:
Vertex BFT: Explain that the "Edge Medic" consensus isn't just local—it uses Vertex BFT to ensure that if a drone node is "killed" (like the FLUIDSWARM project they praised), the remaining nodes agree on the state of the medical supplies.
FoxMQ: State that communication between the wearables and drone relays is handled via a FoxMQ message bus to ensure zero-loss packet delivery during intermittent connectivity.
-
"The Sovereign Merchant Flow" (B2B / ROI) Since this is an institutional trust rail, add a brief table showing the "Old Reality" vs. the "AetherBridge Reality." Feature,Legacy Cloud-Dependent,AetherBridge (Edge Medics) Trust Anchor,Centralized Auth (AWS/Google),Hardware-Anchored (NIST P-256) Connectivity,100% Uptime Required,Blackout-Resilient (Local First) Gas Efficiency,Standard EVM ($$$),90% Reduction (Arbitrum Stylus) Vocal Intent,Transcription only,TruthLayer Vocal Signatures
The core logic for the Vertex Swarm Challenge is located in /agents/aether_agent.py.
- Stateful Handshake: Lines 13-28
- Blackout Mode / P2P Resilience: Lines 33-36
- x402 Settlement Logic: Integrated within the agent state management.
To address the "Shipping Gap," we have provided a one-touch simulation that proves our Coordination and Resilience works at the edge.
This script launches two nodes, establishes a Vertex/FoxMQ handshake, and then kills the primary node to demonstrate local state recovery.
python scripts/blackout_sim.py
2. Technical Proof Points
Coordination: Watch the logs to see Beta detect the loss of Alpha without crashing.
Vertex Integration: Our aether_agent.py uses the FoxMQ layer to broadcast heartbeat signals locally.
Real-World Value: This stack ensures that field medics can continue logging patient data and IOUs even when the central clinic goes dark.
One-Pager: https://docs.google.com/document/d/1WCPXCqH52RNEn1XyFY6DkxbVQF5P1qQZKvtuUcsdN1U/edit?usp=sharing
Demo Video: https://youtu.be/FOBf4af3o4U