The current top-level Karak domain redirects to OpenGDP and now frames the network as a base layer for programmable GDP, sovereign payment rails, institution-grade stablecoin settlement, and tokenized markets.
That new homepage branding does not erase the still-public restaking architecture. The V2 contracts README explicitly defines Karak Restaking around stakers, operators, vaults, slashing, and Distributed Secure Services (DSS).
The current contract README says operators allocate vault stake to DSSs, DSSs can slash delegated vaults, and protocol timing protections include a 9-day withdrawal / stake-update delay plus a 2-day slashing cooldown per operator.
The GitHub organization still exposes clearly restaking-native repos such as v2-contracts, wormhole-dss-contracts, karak-onchain-sdk, and DSS-Templates, alongside newer infrastructure repos like roll-op and kuda-operator.
The Wormhole DSS repo shows at least one concrete downstream use case: enabling Wormhole Native Token Transfer validation through a Karak-backed DSS on EVM chains where Karak is deployed.
The DSS templates repo confirms Karak expects third parties to build DSS implementations on top of the protocol rather than only consume a fixed first-party service set.
The public staking app still presents itself as “Karak | Staking,” which reinforces that the restaking surface remains live even as the homepage narrative has broadened.
Whitepaper / litepaper status
No canonical standalone Karak whitepaper or litepaper surfaced during this pass.
The clearest current first-party sources were the redirected homepage, staking app title, GitHub organization surface, and public contract / DSS READMEs.
The split between OpenGDP branding and still-live restaking / DSS infrastructure is itself a key cataloging detail worth preserving.