Concept: A distributed mesh network enabling multiple seasteads to maintain precise grid formations while sharing sensor data, computational resources, and watch-standing duties. Leverages moving-base RTK-GPS for centimeter-level relative positioning and WiFi 6 directional arrays for high-bandwidth local mesh networking.
For a grid spacing of 200-500 feet (60-150m) between vessels, 5GHz WiFi 6 provides the optimal balance of bandwidth, range, and cost. Each seastead mounts 4 directional sector antennas arranged in a compass rose pattern (0°, 90°, 180°, 270°) to ensure omnidirectional coverage with high gain.
| Component | Specification | Unit Cost (USD) | Qty per Vessel |
|---|---|---|---|
| Radio Units | Ubiquiti UniFi Building-to-Building Bridge (5GHz) or MikroTik Wireless Wire nRAY 60GHz* backup | $499 - $599 | 4 |
| Sector Antennas | Ubiquiti AM-V5G-Ti (5GHz, 21dBi, 60° beamwidth) or similar | $89 - $120 | 4 |
| Ethernet Switch | Industrial 8-port PoE+ switch, IP67 rated (SparkLAN, Advantech) | $250 - $400 | 1 |
| Cabling | Cat6A shielded, UV/ Salt-spray rated, 50ft runs | $2/ft | 200ft |
| Enclosures | IP68 NEMA boxes with desiccant vents, 316 stainless hardware | $150 | 4 |
| Mast Assembly | 3m aluminum mast with vibration dampening (marine grade) | $300 | 1 |
| Total Hardware Cost per Vessel | ~$3,800 - $4,500 | ||
*Note: 60GHz (WiGig) provides 1Gbps+ throughput for close formation (<100m) but degrades in heavy rain. 5GHz is the primary; 60GHz optional for high-bandwidth sensor fusion in clear weather.
Standard 802.11s has limitations with high-mobility maritime environments. We recommend BATMAN-adv V (Layer 2 mesh) running on OpenWRT or custom Linux embedded systems.
The "Convoy State" is maintained as a Conflict-free Replicated Data Type (CRDT) database shared across all nodes. Each seastead runs a lightweight node of the following:
ConvoyState {
grid_positions: HashMap<VesselID, GridCoord>, // Relative to convoy centroid
rtk_base_offset: Vector3, // Moving base correction
tracked_objects: CRDTMap<ObjectID, Track>, // Parallax-tracked vessels
watch_manifest: PoA_Consensus, // Proof-of-Attention roster
sensor_fusion: DistributedKalmanFilter, // Shared navigation picture
intent_vectors: HashMap<VesselID, Vector2> // Planned course changes
}
To ensure 24/7 coverage without relying on Starlink latency, the convoy uses a Byzantine Fault Tolerant consensus for watch-standing:
Given your 80ft × 40ft triangle platforms, we recommend a Hexagonal Close Packed (HCP) formation rather than square:
However, if using 4 directional antennas, a Square Grid is mechanically simpler. Recommendation: Hybrid approach - 4 primary antennas for cardinal directions, plus 1 central omni-directional (low gain) backup for diagonal neighbors in hex formations.
New vessel announces intent via Starlink/AIS. Convoy assigns grid coordinate (x,y) relative to centroid. Recommended approach vector: upwind/up-current at 45° to grid line to minimize collision risk.
At 500m: New vessel begins directional antenna sweep. Convoy assigns a "guardian" vessel (nearest neighbor) to maintain dedicated comm link. RTK base station data streamed via mesh.
At ½ grid spacing (75m): Convoy Mode activates. Thrusters switch to "station keeping" relative to assigned grid point. Velocity matching algorithm engaged.
Each vessel carries 4-6 cameras (360° coverage). When an unidentified contact appears:
tracked_objects CRDTAccuracy: With 200m baselines between vessels, bearing accuracy of 0.1° yields range accuracy of ±35m at 10km distance. Sufficient for early warning and collision avoidance.
| Role | Responsibility | Rotation |
|---|---|---|
| Centroid Leader | Sets convoy course/speed; maintains RTK base reference | Every 6 hours (reduces single point of failure) |
| Perimeter Watch | Outer ring vessels focus sensors outward | Continuous (overlapping sectors) |
| Relay Node | Maintains Starlink uplink for whole convoy (optional bandwidth sharing) | As needed for weather conditions |
| Recovery Vessel | Designated to assist if vessel has mechanical failure | Rotating daily |
| Phase | Duration | Milestones |
|---|---|---|
| 1: Hardware Integration | Month 1-2 | Install antennas, weatherproofing, power systems. Point-to-point testing at dock. |
| 2: Mesh Formation | Month 2-3 | 2-vessel testing, BATMAN-adv optimization, thruster integration with position keeping. |
| 3: Sensor Fusion | Month 3-4 | Camera calibration, parallax ranging validation, AI training on maritime targets. |
| 4: Fleet Operations | Month 4-6 | 4+ vessel convoy, night operations, emergency drills, watch-standing protocol validation. |
Recommendation: Start with a 3-vessel minimum viable convoy using Ubiquiti WiFi 6 equipment ($4k per vessel). The 5GHz band provides sufficient bandwidth for 4K video streams from all vessels simultaneously, enabling the parallax ranging system. Ensure all hardware is rated for marine environments or housed in IP68 enclosures with active heating to prevent condensation in the 7-foot truss structure.
```