Seastead Convoy Mode

The convoy idea is very plausible: each seastead remains an independent vessel, but the group shares position, sensor, traffic, weather, and intent data so that the entire convoy can move as a coordinated fleet. The key is to treat the convoy system as a layered safety system rather than as one communications link or one autopilot.

Short recommendation: Use a three-layer communications system:

Marine safety layer: AIS, VHF voice/DSC, radar, navigation lights, sound signals.
Low-rate robust mesh: 900 MHz / 868 MHz / 915 MHz LoRa or FHSS telemetry for heartbeats, alarms, slot assignments, and breakaway commands.
High-rate local mesh: 5 GHz WiFi 5/6 directional or sector radios for RTK corrections, tracks, video snippets, software updates, and high-rate coordination.

Starlink is useful for internet, weather, remote monitoring, and cloud services, but should not be the only communications system used for local convoy safety.

1. Communications Mesh Hardware

1.1 Expected Range Over Water

Over open water, the main limitation for 5 GHz links is usually line-of-sight, antenna height, Fresnel-zone clearance, multipath reflections from the sea surface, rain, and antenna pointing.

Approximate radio horizon for two antennas of equal height:

Two antennas at 10 ft above water: about 9 statute miles / 8 nautical miles.
Two antennas at 20 ft above water: about 12 to 13 statute miles / 11 nautical miles.
Two antennas at 30 ft above water: about 15 to 16 statute miles / 13 to 14 nautical miles.

For convoy use, if grid spacing is hundreds of meters to a few nautical miles, 5 GHz is easily adequate if the radios are mounted high and have clear view.

1.2 Recommended Radio Architecture Per Seastead

Layer	Purpose	Suggested Hardware	Typical Cost Per Seastead	Expected Performance
5 GHz high-rate mesh	Main local data network: RTK corrections, telemetry, sensor tracks, compressed video, convoy database replication.	Four 5 GHz sector radios or wider-beam directional radios mounted around the roof/mast. Examples: Ubiquiti airMAX/UISP, MikroTik, Cambium ePMP, TP-Link Omada outdoor gear.	DIY/COTS: roughly $800 to $2,500 for four radios/antennas. Add $300 to $1,000 for PoE switch, router, cables, surge protection, mounts.	At 0.5 to 2 nautical miles: often 100 to 400 Mbps aggregate possible. At 3 to 8 nautical miles: often 20 to 150 Mbps depending on antenna gain, channel width, sea state, and interference.
900 MHz / 868 MHz / 915 MHz low-rate mesh	Fallback safety telemetry: heartbeats, emergency breakaway, watch confirmation, reduced-state convoy mode.	LoRa, LoRaWAN, or FHSS telemetry radios. Examples: RFD900x, Meshtastic-compatible LoRa modules, industrial 900 MHz serial radios.	$100 to $600 per seastead depending on ruggedness and redundancy.	Data rate from hundreds of bits/s to tens of kbps. Range can be several nautical miles to 20+ nautical miles line-of-sight with good antennas.
Marine VHF + DSC	Legal/safety voice communications, distress, bridge-to-bridge contact, coordination with non-convoy vessels.	Fixed marine VHF with mast antenna, DSC connected to GNSS.	$300 to $1,000 per seastead.	Usually 5 to 25 nautical miles depending on antenna height and conditions.
AIS	Broadcast identity, position, course, speed; receive commercial traffic; convoy situational awareness.	Class B SOTDMA AIS transponder is preferable to cheaper CSTDMA Class B.	$800 to $1,500 per seastead.	Typically 5 to 30 nautical miles depending on antenna height and traffic density.
Starlink	Internet, weather, cloud sync, remote support, software updates, backup coordination.	Starlink maritime/mobile terminal, router integration.	Hardware and service plan vary significantly.	High bandwidth, but not deterministic enough to be the primary local safety/control link.

1.3 Four Directional Antennas vs. Four Sector Antennas

Using four antennas around each seastead makes sense, but for a moving convoy I would favor wide sector antennas over narrow point-to-point dishes.

Narrow high-gain dishes can give excellent range and bandwidth, but they assume the neighbor is in a very specific direction. If the seastead yaws, rotates, or if the assigned grid changes, narrow beams may lose alignment. Four 90-degree sector antennas, or four moderately directional antennas with broad beamwidth, are more forgiving.

A good practical configuration:

One rugged router/firewall inside the seastead.
One managed PoE switch.
Four 5 GHz outdoor radios, each covering approximately one quadrant.
One small omnidirectional WiFi antenna for discovery and close-range service access.
One independent low-rate 900 MHz / LoRa / FHSS radio.
Independent VHF and AIS antennas mounted as high as practical.

Regulatory note: 5 GHz, 6 GHz, 900 MHz, 868 MHz, and 915 MHz rules vary by country and by flag state. Some channels require DFS radar avoidance. Some regions do not permit the same power levels or frequencies. Design the radios so their country code, channels, bandwidth, and transmit power can be configured legally.

1.4 Expected Data Needs

Data Type	Approximate Bandwidth	Notes
Convoy position/velocity/health telemetry	< 100 kbps per seastead	Even at 10 Hz updates, this is small.
RTK GNSS corrections	1 to 20 kbps	Small, but should be low-latency and reliable.
Shared traffic tracks	< 100 kbps normally	Transmit fused tracks, not raw video, for routine operation.
Compressed camera stream	2 to 8 Mbps per 1080p stream	Use on demand. Do not stream every camera continuously unless bandwidth is abundant.
Radar tracks	Small if processed locally	Radar video/raw data can be much larger; processed targets are preferred.
Software updates / files	High but non-urgent	Deprioritize below safety traffic.

2. Recommended Mesh Software

2.1 Network Routing

For the high-rate 5 GHz mesh, there are several viable options:

Approach	Pros	Cons	Recommendation
Babel or OLSR Layer-3 mesh routing	Robust, proven, works well with IP networks, avoids some Layer-2 broadcast issues.	Requires more network engineering.	Good choice for a serious convoy mesh.
B.A.T.M.A.N. advanced	Simple Layer-2 mesh behavior; convenient for prototypes.	Can become inefficient with lots of broadcast/multicast traffic.	Good for early testing; be careful with scaling.
802.11s mesh	Standards-based WiFi mesh.	Hardware/driver support varies; performance may be unpredictable.	Usable but test thoroughly.
Vendor proprietary PtMP, e.g. airMAX, Cambium ePMP	Excellent long-distance wireless performance; good TDMA behavior.	Less flexible as a true ad-hoc mesh; may prefer hub/spoke or planned topology.	Good for fixed neighbor links or sector-based planned convoy topology.

For a low-cost but serious system, I would use Layer-3 routing with Babel or OLSR on the seastead routers, and keep the radio links as simple Ethernet/IP links. Use static addressing, DNS or mDNS carefully, and avoid flooding the mesh with unnecessary multicast traffic.

2.2 Data Middleware

A good software stack could include:

Signal K / NMEA 2000 / NMEA 0183: marine instrument data, AIS, GPS, wind, depth, heading.
OpenCPN: navigation display, charts, AIS visualization.
ROS 2 / DDS: robotics-style sensor fusion, autonomy, control, and distributed state sharing.
MOOS-IvP: marine autonomy framework, especially useful for autonomous surface vessel behaviors.
MQTT or NATS: convoy-wide event bus, watchkeeping events, alerts, status dashboards.
Protocol Buffers or FlatBuffers: efficient binary message formats for tracks and state.
WireGuard VPN: encrypted convoy network overlay, especially over Starlink and for remote access.

A practical architecture is:

Use NMEA/Signal K for local marine data ingestion.
Use ROS 2 or MOOS-IvP for autonomy and control logic.
Use NATS or MQTT for convoy-wide status, alerts, watchkeeping, and database replication.
Use Protobuf messages for seastead state, object tracks, sensor reports, and command intents.

2.3 Time Synchronization

Precise time matters for parallax, camera bearings, radar fusion, and RTK.

Each seastead should have a GNSS receiver providing PPS time.
Use Chrony or PTP internally to synchronize computers and cameras.
Every sensor report should include timestamp, sensor position, sensor orientation, and uncertainty.

3. Convoy Mode Behavior

3.1 Basic Concept

The convoy should have a shared virtual coordinate frame. For example:

A virtual convoy origin.
A convoy heading and speed.
A grid spacing.
Assigned slots, such as row/column positions relative to the convoy origin.

Each seastead tracks its assigned slot using GNSS/RTK, IMU, thrusters, and stabilizers. The seasteads exchange their state so neighbors know not only where each unit is, but where it intends to be.

3.2 Joining Procedure

A robust joining procedure might look like this:

Discovery: New seastead announces itself over AIS, VHF if needed, and the local mesh if in range.
Authentication: Convoy software verifies the seastead's cryptographic identity and software compatibility.
Slot assignment: Convoy controller recommends a grid position, preferably on the outer edge of the convoy.
Approach corridor: The newcomer is given an approach path from outside the convoy, avoiding crossing between existing seasteads.
Speed limit: During capture, the newcomer operates at reduced relative speed.
Pre-capture checks: Thrusters, GNSS, IMU, communications, and emergency stop/breakaway functions are tested.
Capture radius: When within a defined distance, e.g. half a grid spacing, convoy mode activates.
Station keeping: The seastead transitions from manual/approach control to automatic slot tracking.

3.3 Leaving Procedure

Leaving should be as formal as joining:

Seastead requests departure.
Convoy assigns an exit corridor.
Neighbors are notified.
Seastead moves outward from the grid before changing course significantly.
Slot becomes vacant and may be reassigned.

3.4 Loss-of-Communication Behavior

Every seastead needs deterministic fallback behavior. For example:

Failure	Suggested Response
Loss of high-rate 5 GHz mesh, low-rate link still active	Continue convoy mode using reduced telemetry. Stop video. Increase safety margins.
Loss of all local mesh, AIS/VHF still working	Hold slot briefly, then transition to preplanned breakaway course if not restored.
GNSS degraded	Use IMU/dead reckoning briefly, reduce speed, increase spacing, alert watch.
Thruster or stabilizer failure	Announce degraded maneuverability, increase spacing, possibly exit convoy.
Computer/autopilot fault	Revert to independent safe mode. Human watch takes over if possible.

A critical design point: do not allow an uncontrolled unit to remain inside a tight grid indefinitely. It should either regain control quickly or execute a safe, predictable breakaway maneuver.

3.5 Suggested Grid Spacing

The safe grid spacing depends on sea state, speed, station-keeping accuracy, thruster authority, latency, and human comfort. In calm prototype conditions you might test small spacing, but offshore convoy spacing should probably be much larger than the seastead length.

Reasonable development stages:

Dockside/sheltered-water test: 50 to 100 ft spacing.
Calm-water prototype convoy: 150 to 300 ft spacing.
Offshore operational convoy: hundreds of meters may be more realistic, especially at night or in poor visibility.
Heavy weather: expand spacing or dissolve convoy formation.

Safety note: A grid of independent vessels is not exempt from COLREGS. Each seastead remains responsible for collision avoidance, lights, sound signals, lookout, and appropriate action. The software should assist compliance, not replace it.

4. Shared Sensing and “Night Watch”

4.1 Sensors Per Seastead

A good sensor package would include:

AIS transponder and AIS receiver.
Marine radar, preferably solid-state broadband or Doppler-capable radar.
Visible-light cameras covering 360 degrees.
Thermal cameras for night detection of vessels, people, and unlit objects.
GNSS/RTK receivers, ideally dual-antenna for heading.
IMU, compass, wind sensor, barometer.
Optional acoustic sensors or hydrophones, though these are more experimental for navigation.

Cameras alone are not enough. Radar is very valuable because it can detect objects in darkness, haze, and partial rain, and it gives direct range measurements.

4.2 Object Track Database

The convoy should maintain a shared object-track database. Each object track should include:

Unique track ID.
Estimated position, course, speed, and uncertainty.
Classification: AIS vessel, radar target, camera target, bird, buoy, debris, unknown, etc.
Which seasteads and sensors have observed it.
Time of last observation.
Collision-risk score.
Recommended action.

For parallax-based camera rangefinding, accurate calibration is essential. Each camera report should include:

Camera position in the convoy coordinate frame.
Camera orientation.
Lens calibration.
Timestamp.
Bearing/elevation estimate and uncertainty.

The larger the baseline between observing seasteads, the better the range estimate. For distant objects, angular error dominates. For example, a 0.1 degree bearing error is about 1.7 milliradians. At long ranges, even small angular errors can create hundreds of meters of range uncertainty, so radar and AIS association remain important.

4.3 Watchkeeping System

Convoy mode should include a human watchkeeping protocol:

Each watchstander logs into the convoy watch system.
The system shows who is on watch, from which seasteads, and for how long.
Watchstanders must periodically confirm alertness, e.g. every 5 to 15 minutes.
Failure to confirm escalates: local alarm, convoy alarm, VHF call, then designated backup watch.
Detected traffic, weather changes, equipment faults, and near misses are logged.
There should be an explicit “reduced watch” or “heavy weather watch” mode with stricter requirements.

A useful model is to treat the convoy like a distributed bridge team. The computers continuously scan, but humans remain responsible for judgment and legal watchkeeping.

5. Control and Autopilot Requirements

5.1 Local Control

Each seastead should be able to hold position and heading independently before attempting convoy mode. Required local capabilities:

Thruster control with health monitoring for all six RIM drives.
Active stabilizer control with fault detection.
GNSS/RTK positioning.
IMU-based motion estimation.
Independent emergency stop and manual override.
Battery state-of-charge monitoring per leg.
Graceful degradation if one leg/inverter/battery subsystem fails.

5.2 Formation Control

There are two main formation-control approaches:

Approach	Description	Pros	Cons
Leader/follower	One convoy leader defines course/speed; all others track assigned offsets.	Simple and easy to understand.	Leader failure must be handled. Can create single point of authority.
Virtual leader / shared plan	All seasteads follow a shared virtual convoy frame.	More robust; no physical unit has to be “the leader.”	Requires better time sync, consensus, and software discipline.

I recommend a virtual leader. The convoy has a planned track, speed, and heading. Each seastead tracks its slot relative to that virtual reference. If communication degrades, each unit can continue briefly using the last valid virtual-leader state.

5.3 Collision Avoidance Overrides

Formation keeping must be lower priority than collision avoidance. The hierarchy should be:

Prevent collision with people, vessels, and fixed hazards.
Comply with COLREGS and legal navigation obligations.
Protect the seastead from capsize/flooding/structural overload.
Maintain safe separation from convoy neighbors.
Maintain assigned grid slot.
Optimize energy use and comfort.

6. Cybersecurity and Authentication

Convoy mode creates a safety-critical network. It should not rely on “open WiFi plus trust.”

Each seastead should have a cryptographic identity/certificate.
Convoy control messages should be signed or sent over mutually authenticated encrypted channels.
Use WireGuard or mutual TLS for IP-layer security.
Separate networks: control, sensors, guest WiFi, entertainment, and maintenance.
Log all remote commands.
Require local human authorization for dangerous actions.
Detect GNSS spoofing by comparing AIS, radar, inertial estimates, and relative positions.
Do not trust AIS blindly; AIS is useful but not authenticated.

7. Wave-Energy Interaction of a Convoy

7.1 Can Many Seasteads Reduce Average Wave Height?

Some local wave reduction is possible, but it should not be assumed for the basic design.

Each seastead will scatter, reflect, radiate, and dissipate some wave energy. With many seasteads, the scattered waves can interfere with incoming waves. In certain places and at certain frequencies, this can reduce wave height. In other places it can increase wave height. For a regular sinusoidal wave train, carefully spaced objects can create interference patterns. But real ocean waves are broadband, directional, and random.

The important points are:

Energy is not destroyed unless dissipated by drag, turbulence, breaking, or active energy extraction.
Wave cancellation in one area often means increased wave energy somewhere else.
Long-period ocean swell has wavelengths far larger than a 44 ft seastead.
Small structures are much more effective against short chop than against long swell.
A loose convoy with hundreds of meters of spacing will probably have little useful wave-sheltering effect.
A dense array could reduce short wind waves inside the array, but might also create uncomfortable reflected and confused seas.

7.2 Scale Comparison

Wave Type	Typical Wavelength	Likely Interaction With 44 ft Seastead
Small wind chop	3 to 30 ft	Noticeable scattering/damping possible, especially with many units close together.
Moderate wind waves	30 to 150 ft	Some interaction, but convoy spacing and seastead geometry matter greatly.
Ocean swell	150 to 1000+ ft	Individual seasteads are small relative to wavelength; little attenuation expected.

7.3 Formation Effects

If the goal is wave reduction while parked, a formation could be arranged like a porous floating breakwater:

Place more seasteads on the up-wave side.
Use staggered rows rather than a simple square grid.
Keep gaps small enough to affect the target wavelengths.
Accept that this works better for short-period waves than long swell.

While underway, the formation should be chosen primarily for navigation safety, communications, and collision avoidance, not wave cancellation. A convoy optimized for wave interference may be fragile because the “right” spacing changes with wave period and direction.

Recommendation on waves: Do not count on convoy wave attenuation as a primary comfort or safety feature. Treat it as a possible bonus. Measure it with wave buoys, motion sensors, and controlled sea trials. If wave reduction becomes an important goal, model it with potential-flow or CFD tools and validate with scale testing.

8. Practical Development Roadmap

Phase 1: Single-Seastead Instrumentation

Install GNSS/RTK, IMU, AIS, VHF, radar, cameras, and local data logging.
Prove that one seastead can hold heading and position safely.
Log power consumption, thruster response, stabilizer response, and motion in waves.

Phase 2: Two-Seastead Relative Control

Test the local 5 GHz mesh and 900 MHz fallback link.
Share position, heading, velocity, and health.
Test virtual-leader tracking at large separation.
Test emergency breakaway.
Test the inter-seastead walkway mode only after basic relative control is very reliable.

Phase 3: Small Convoy

Operate three to five seasteads in a simple line or triangle formation.
Test slot assignment, joining, leaving, and degraded communications.
Validate shared object tracking using AIS, radar, and cameras.
Run night-watch drills.

Phase 4: Larger Grid

Expand to a grid or staggered formation.
Measure communications performance as the mesh grows.
Measure wave field changes inside and around the convoy.
Test heavy-weather expansion and convoy dissolution procedures.

9. Approximate Per-Seastead Cost for Convoy Electronics

Subsystem	Low-Cost Prototype	More Robust Version
5 GHz mesh radios, antennas, mounts	$1,000 to $2,500	$3,000 to $10,000+
Router, PoE switch, cabling, surge protection	$500 to $1,500	$2,000 to $5,000
900 MHz / LoRa fallback telemetry	$100 to $600	$1,000 to $3,000
AIS Class B SOTDMA	$800 to $1,500	$1,500 to $3,000
Marine VHF/DSC	$300 to $1,000	$1,000 to $3,000
GNSS/RTK, antennas, heading receiver	$500 to $2,000	$3,000 to $15,000
Radar	$1,500 to $4,000	$5,000 to $25,000+
Cameras and thermal cameras	$500 to $5,000	$10,000 to $50,000+
Compute hardware	$500 to $2,000	$3,000 to $15,000

For a cost-conscious prototype, the dedicated convoy communications hardware excluding radar/cameras could plausibly be in the $2,000 to $6,000 per seastead range. A more rugged marine-grade system with redundancy can easily move into the $10,000 to $30,000+ range per seastead before counting high-end sensors.

10. Overall Recommendation

The convoy mode is technically feasible, but should be designed as a safety-critical distributed marine system. The best near-term design is:

Four-quadrant 5 GHz sector mesh for high-rate local data.
Independent 900 MHz / LoRa / FHSS low-rate backup.
VHF, DSC, AIS, and radar as non-negotiable marine safety systems.
GNSS/RTK with local IMU and robust timestamping.
Virtual-leader formation control with explicit join, leave, and breakaway procedures.
Shared object-track database, but local collision avoidance authority on every seastead.
Human watchkeeping integrated into the software with confirmation and escalation.
Cybersecurity from the beginning: authenticated seasteads, encrypted links, signed control messages.
Wave-reduction treated as experimental, not assumed.

If you design the mounting points, cable runs, mast space, PoE power budget, and electronics cabinet now, the convoy features can be added without major structural changes later. The most valuable design provision is probably a high, clear, serviceable communications mast location with room for multiple antennas, lightning/surge protection, and redundant cable paths into the electronics bay.