Aegis Code

Changelog

What changed.

Release notes and compatibility details for the public platform.

Version 2026.09.09.2 ·

Device access and service observations

Added

  • Unified HWID binding for dashboard, Discord and public Get Key licenses, with owner controls for reset, ban and unban.
  • License security activity with key references, timestamps and truncated expected/received device hashes.
  • A public status page backed by recorded API and edge checks, with explicit missing-data periods and dedicated Discord panel observations.
  • This public changelog, using Version, Date, Added, Fixed and Notes for release updates.

Fixed

  • Protected edge delivery now needs a current origin authorization; an old license snapshot cannot grant access after a reset or ban.
  • Concurrent first-device executions cannot replace each other’s binding or exceed the remaining use limit.
  • Device resets and license status changes invalidate previously issued loader sessions.

Notes

  • Existing Discord bindings are preserved. Previously unbound keys receive a seven-day transition; new keys require a device identifier immediately.
  • Binding hashes expire after 90 inactive days and require an explicit reset. Mismatch hashes are removed after 30 days.
  • HWID values supplied by clients can be spoofed. Already delivered code cannot be recalled.
  • Status history begins with actual observations. Discord remains without fresh data until the dedicated test project is configured and its panel is checked.

Version 2026.09.09.1 ·

Public documentation, pricing and Get Key

Added

  • Public documentation and pricing routes with separate page metadata and a shared billing catalog.
  • Off, Free and Linkvertise access modes, with a separate owner opt-in for the public project catalog.
  • Public key security activity and automatic deletion of IP/browser risk hashes after 30 days.

Fixed

  • Repeated and concurrent confirmations no longer issue additional keys from one completion.
  • Unavailable or unverified Linkvertise gates cannot issue a key.

Notes

  • Existing enabled Linkvertise projects and their previous access links are preserved. New projects start with public issuance off.
  • Obfuscation raises the effort needed for analysis; it does not guarantee that client-side code remains secret.