AES-256 encrypted license SDK for Theos tweaks

Stop your tweak from being cracked and re-sold.

Drop a static library into your Xcode/Theos build and every launch runs an AES-256 encrypted handshake with your dashboard first — encoded app IDs, HWID locking, and dylib-injection detection, with zero source code shipped in the binary.

0Packages protected
0Keys issued
0-bit AES
FLUCKV2LICENSE SDK
FLK2 • 8B41 • 9C02 • 55E7
PackagePRO ACCESS
CipherAES-256-GCM
Live handshake preview
plaintextcom.yourapp.tweak
cipherAES-256-GCM
ciphertext
AES-256-GCM ENCRYPTIONANTI-INJECTIONHWID LOCKENCODED APP ID MYDASH KEY MANAGEMENTTHEOS / ROOTLESS READY AES-256-GCM ENCRYPTIONANTI-INJECTIONHWID LOCKENCODED APP ID MYDASH KEY MANAGEMENTTHEOS / ROOTLESS READY

Four calls, and your tweak is gated

Integration
01

Create a package

Spin up an app entry on MYDash and get your encoded app ID + version bytes.

02

Drop in the SDK

Add libKeyAuth.a and KeyAuth.h, force-load the library, link CoreTelephony.

03

Validate on launch

Call [[KeyAuthSystem shared] start] — the handshake is AES-256 encrypted end to end.

04

Manage from your phone

Generate keys, ban abusers, and watch redemptions from the MYDash app.

Built around AES-256

Every validation call is encrypted before it leaves the device — not just sent over HTTPS. Even a rooted proxy watching the connection sees ciphertext, not your app ID, key, or dashboard response.

01

AES-256-GCM payloads

Request and response bodies are encrypted and authenticated, not just transported over TLS.

02

Per-package keys

Each package gets its own derived encryption key, so leaking one app's traffic doesn't expose another's.

03

Encoded identity, not plaintext

App ID and version live in your build as byte arrays, decoded only at runtime, inside the encrypted channel.

04

Replay-resistant

Each handshake is nonce-tagged so a captured request can't simply be replayed to fake a valid session.

What's actually inside

Feature set

AES-256 handshake

Every validation call is encrypted and authenticated before it leaves the device.

Binary-only distribution

Ships as a static library. Nobody pulls your validation logic out of a public repo — there isn't one to pull.

Anti-injection checks

Caps loaded dylibs at runtime and flags unexpected ones, with a tunable allowance for your own legit dylibs.

Encoded app identity

App ID and version live in your build as byte arrays, not plaintext strings a jailbroken tool can grep for.

Drop-in theme layer

themeAPI.mm gives KeyAuth's login/validation UI a working color scheme even with no menu system yet.

Key + ban management

MYDash gives you full control over issued keys — create, revoke, ban a HWID, all from one dashboard app.

Per-device HWID lock

Binds a key to the first device that redeems it, so a single sold key can't be shared across ten devices.

Offline grace window

Short cached-validation window so a flaky connection doesn't lock out a legitimate paying user mid-session.

Expiry & renewal handling

Time-boxed keys with built-in expiry checks, so subscriptions actually stop working when they lapse.

Dashboard & downloads

For existing customers

Already bought a package? Manage your keys, packages, and bans from the browser, or install the MYDash app to do it from your phone.

Open dashboard ↗
.A

SDK library

libKeyAuth.a + KeyAuth.h — the static library you link into your Xcode/Theos build. Same one covered in the integration steps above.

v2.4.1·arm64
Download .a Integration docs ↗
.IPA

MYDash app

Now you can control and manage your auth key right from the app — generate keys, check redemptions, and ban a HWID without opening a browser.

v1.8.0·iOS 15+
Download .ipa

Not on the App Store — install with Sideloadly, AltStore, or TrollStore.

WEB

Web dashboard

Same key and ban management as the app, no install required. Sign in with the credentials sent to you on Telegram after checkout.

fluckv2.org/dashboard
Go to dashboard ↗

Haven't checked out yet? View packages first — downloads and dashboard access unlock after payment is confirmed.

Choose your plan

Pricing

USDT (BSC) • Binance Pay accepted

Questions

FAQ
What's a "key credit"?
One credit is redeemed each time you generate a new license key for a customer inside MYDash. Starter refills 300 per month; Pro doesn't meter this at all.
What counts as a "package"?
A package is one app or tweak registered under your account, each with its own encoded app ID, version, and key pool. Starter supports 2 at once, Pro supports 5.
Why AES-256 instead of just HTTPS?
HTTPS protects the connection, but on a jailbroken device it can be intercepted with a proxy and a trusted root cert. Encrypting the payload itself means even an intercepted request is unreadable without your package's derived key.
How does payment work?
You pay in USDT on the BSC (BEP20) network or via Binance Pay. After sending payment, submit your transaction hash on the checkout page — it's verified on-chain automatically, then you're routed to Telegram to receive your credentials.
Do I need to ship any source code?
No. The SDK is distributed as libKeyAuth.a — a compiled static library — plus headers. Your validation logic never appears in your tweak's source.
Where do I get the SDK and dashboard app after I pay?
Both are on the Dashboard & downloads section above: libKeyAuth.a for your build, and the MYDash .ipa for managing keys from your phone. The web dashboard at fluckv2.org/dashboard works too, and doesn't need a sideload.
Can I upgrade or downgrade later?
Yes, switch between Starter and Pro any time — just message on Telegram with your order reference and it'll be adjusted for the next cycle.