VerSkyLicense inquiry
For Researchers

Cite. Evaluate. Extend.

VerSky is intended to be a citable, evaluable protocol — the primary sources are public, the simulation will be open, and collaboration is welcome.

§1 · Cite

Citation block, ready to drop in.

Three primary sources: the whitepaper, and the two pending U.S. patent applications. BibTeX below — paraphrase as your venue requires.

@techreport{prukpatarakul2026versky,
  author      = {Prukpatarakul, Jittapol},
  title       = {{VerSky Protocol Whitepaper}: An air traffic protocol
                  for the low-altitude century},
  institution = {VerSky},
  type        = {Whitepaper},
  number      = {v1.0},
  year        = {2026},
  month       = {May},
  url         = {https://versky.org/whitepaper/versky-whitepaper-v1.0.pdf}
}

@misc{prukpatarakul2026altitude,
  author       = {Prukpatarakul, Jittapol},
  title        = {Altitude-Direction Encoding Protocol for Air Traffic
                   Management with Hexagonal Grid and Intersection
                   Separation},
  howpublished = {U.S. Patent Application No. 19/551,620},
  year         = {2026},
  month        = {February}
}

@misc{prukpatarakul2026aacp,
  author       = {Prukpatarakul, Jittapol},
  title        = {{AI} Aerial Communication Protocol with Peer-to-Peer
                   Negotiation and Deterministic Fallback Resolution},
  howpublished = {U.S. Patent Application No. 19/551,624},
  year         = {2026},
  month        = {February}
}
§2 · Open Questions

Where the work is unfinished.

Honest list. These are questions the protocol design surfaces but does not close. Each is a credible PhD chapter or post-doc thread.

Mixed-fleet capacity bounds

What is the analytical upper bound on hex-cell throughput as the speed-band distribution shifts? Closed-form solutions welcome — current internal work is empirical.

Adversarial AACP

Game-theoretic analysis of Sybil attacks against trust-scored negotiation. Where does the trust mechanism fail gracefully and where does it fail badly?

Reservation-conflict topology

Characterise the topology of conflicts in 4D space-time reservations under stochastic arrival models. Useful for capacity planning, autoscaling, and pricing.

Mode-transition safety

Formal verification of the four operating modes (Full / Degraded / Peer-Only / Standalone) — what invariants hold across the graceful-degradation chain and which can be broken?

Inter-protocol interop

How does a VerSky-compliant fleet interoperate with traditional ADS-B / Mode-S / Remote ID equipped vehicles in shared low-altitude airspace?

Scale-out simulation

10⁴ vehicle scenarios in real time on commodity hardware — what are the architectural sweet spots? Public benchmarks needed.

§3 · Reproducibility

Scenario dataset v1.0.

Three illustrative scenarios in machine-readable JSON. Each defines vehicles and environment parameters that exercise specific filed paragraphs of the protocol. These are starting-point inputs for third-party experimentation, not validated conformance baselines — a public schema and conformance harness ship in a later phase.

P2 ¶[0020], §5.8

Two-Vehicle Head-On (DFR)

Canonical AACP test: opposing-heading vehicles fail negotiation within 500 ms bound; both compute identical DFR yield. Reference scenario for determinism reproducibility.

two-vehicle-headon-v1.json · 1.6 KBDownload ↓
P1 ¶[0030], §3-§5

Asymmetric Traffic Surge

24 NE-bound vs 4 SW-bound vehicles through a 4-cell corridor. Characterises directional throughput under hex-cell capacity bounds. Connects to open question #1.

asymmetric-surge-v1.json · 1.5 KBDownload ↓
P2 ¶[0037]-[0038]

Communication Blackout — Mode Chain

Progressive link loss triggers Full → Degraded → Peer-Only → Standalone mode chain. Illustrates the 5-second standalone-activation threshold and the safety invariants the protocol is designed to preserve.

comm-blackout-v1.json · 2.1 KBDownload ↓

Released under CC-BY-4.0. Cite the scenario_id + version in publications. Have a scenario worth adding? Open a thread — we're building v1.1 from community contributions.

§4 · Collaborate

Joint papers welcome.

If you're working on any of the open questions above — or an adjacent angle we haven't listed — we'd like to hear from you. Reproducibility artefacts, simulation data, and pre-prints are happy to be shared under standard academic terms.