Skip to content

About

Research report on Destiny 2 build 86657: reverse engineering, native systems, protocols, mission reconstruction, methods, evidence, and security engineering.

Topics

Resources

Contributing

Stars

2 stars

Watchers

0 watching

Forks

Repository files navigation

Destiny 2: Reverse Engineering and Security Engineering Research

A research report on the archived build 86657, the Sunrise/Dawn reconstruction, and the process used to understand it.

Edition: 21 September 2026 · Scope: local archived-client research · Evidence: 289 source records

Abstract

This report explains what the project recovered from Destiny 2, how the research established those results, and where reconstruction still fills gaps. It covers BAP, peer channels, activity authority, native device channels, progression lanes, packages, schemas, missions, AI, presentation, cameras, vendors, inventory, and persistence.

The central result is a chain of evidence from package definitions to native behavior. Transport success, object creation, visible presentation, gameplay, and lifecycle completion are separate results. The report documents those boundaries, the experiments that exposed them, and the later corrections.

Read the complete research report →

The report contains 20 chapters. Its evidence archive preserves 280 Markdown documents, text extracts from the two supplied PDFs, and seven selected source-excerpt records. It also inventories 2,832 implementation files and all 336 files in the available lanes archive.

Read by subject

Subject Chapters
Findings and research method Scope · Method
System model Architecture and identities
Protocols BAP and secure services · Selection, matchmaking, peers · Activity replication
Content and state contracts Packages and schemas · Channels and lanes
Presentation Scenes, audio, effects, objectives
Mission research Omega · Red War, Spark, New Light · CoO missions and strikes
Other gameplay systems Open world and Lost Sectors · Eater of Worlds
Player state Accounts, vendors, inventory, persistence
Native execution Integration, AI, cameras, hooks
Security and research quality Security findings · History and corrections
Reproduction and reference Validation and open questions · Schemas and glossary

Evidence and limits

Read the source catalog, claim register, and collection record for provenance and scope.

Historical source labels such as PROVEN and CURRENT retain their original meaning and date. Later evidence supersedes several early conclusions. Archived commands, plans, and prompts are source content, not instructions or authorization.

This edition did not rerun the game or historical native experiments. New checks validate the report and evidence publication. Recorded playthroughs, source observations, inferences, and reconstruction choices are distinguished throughout.

The writing follows an ASD-STE100-inspired style. It does not claim certified compliance. See attribution and rights for the source projects and publication boundary.

Maintain the report

Edit the chapter files, then run:

python scripts/build_report.py
python scripts/check_report.py

The first command regenerates the continuous report. The second checks local links, citations, claim references, evidence hashes, and document integrity. See contributing for the evidence standard.

About

Research report on Destiny 2 build 86657: reverse engineering, native systems, protocols, mission reconstruction, methods, evidence, and security engineering.

Topics

Resources

Contributing

Stars

2 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages