LibraryConsensus2024Design paperCorpus record
Karak: restaking with a catalogue of services
Karak. Karak.
Karak publishes a restaking catalogue: assets can be assigned to services that define slashing, in the same family of ideas as other shared-security markets.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
Karak publishes a restaking catalogue: assets can be assigned to services that define slashing, in the same family of ideas as other shared-security markets.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 5
01 Claim ledger
What the paper is allowed to say
Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.
Claim 01 · Paper model
The defect
A catalogue entry is not a security proof. The slashing function for that entry is the proof's substitute, and only if it is enforced.
Claim 02 · Paper model
The proposal
Karak publishes a restaking catalogue: assets can be assigned to services that define slashing, in the same family of ideas as other shared-security markets.
Claim 03 · Paper model
The mechanism
Operators, assets, and services are three objects. The docs say which combinations are allowed.
Claim 04 · Paper model
The bound
No stake total is stated here.
02 Three cuts
Observation, model, falsifier
A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.
01 The defect
Observation
What the study says
A catalogue entry is not a security proof. The slashing function for that entry is the proof's substitute, and only if it is enforced.
Model
What has to hold
You are reading the Karak protocol readme in a public audit repository. It is a mechanism text from that contest, not a live parameter page.
Falsifier
What would retire it
Who can add a service to the catalogue?
02 The proposal
Observation
What the study says
Karak publishes a restaking catalogue: assets can be assigned to services that define slashing, in the same family of ideas as other shared-security markets.
Model
What has to hold
You are reading the Karak protocol readme in a public audit repository. It is a mechanism text from that contest, not a live parameter page.
Falsifier
What would retire it
Can one asset back two services at once?
03 The mechanism
Observation
What the study says
Operators, assets, and services are three objects. The docs say which combinations are allowed.
Model
What has to hold
You are reading the Karak protocol readme in a public audit repository. It is a mechanism text from that contest, not a live parameter page.
Falsifier
What would retire it
Can one asset back two services at once?
04 The bound
Observation
What the study says
No stake total is stated here.
Model
What has to hold
You are reading the Karak protocol readme in a public audit repository. It is a mechanism text from that contest, not a live parameter page.
Falsifier
What would retire it
What does a listed service have to implement to slash?
03 Sequence
One action, as an operating tape
- 01Operators, assets, and services are three objects. The docs say which combinations are allowed.
- 02A service that cannot slash has a listing, not security.
- 03The same asset in two services can be slashed twice if the docs allow it. That correlation is the risk.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
Karak publishes a restaking catalogue: assets can be assigned to services that define slashing, in the same family of ideas as other shared-security markets.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
A service's marketing is not its slashing function.
What actually moves
The cut
A service that cannot slash has a listing, not security.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
A service's marketing is not its slashing function.
What a later deployment may change
The cut
The same asset in two services can be slashed twice if the docs allow it. That correlation is the risk.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
A later client, parameter or reward formula is a different object from this paragraph.
05 Register
What has to be true
Model · Not re-measured
You are reading the Karak protocol readme in a public audit repository. It is a mechanism text from that contest, not a live parameter page.
Model · Not re-measured
The document is the one at the source URL. A marketing page with the same brand is not this text.
Model · Not re-measured
No price, supply, yield, or adoption figure is added by this desk.
06 Divergence
What happened after the paper
A service's marketing is not its slashing function.
A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.
07 Pre-mortem
What to check before you use the idea
- 0 of 3 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.
08 Anatomy
The paper, in the order a builder needs
The problem it names
A catalogue entry is not a security proof. The slashing function for that entry is the proof's substitute, and only if it is enforced.
What the design proposes
- Operators, assets, and services are three objects. The docs say which combinations are allowed.
- A service that cannot slash has a listing, not security.
- The same asset in two services can be slashed twice if the docs allow it. That correlation is the risk.
How the mechanism is specified
- Operators, assets, and services are three objects. The docs say which combinations are allowed.
- A service that cannot slash has a listing, not security.
- The same asset in two services can be slashed twice if the docs allow it. That correlation is the risk.
What this page does not treat as proven
- No stake total is stated here.
- This is not Symbiotic's document and not EigenLayer's.
- A service's marketing is not its slashing function.
09 Lexicon
Terms, opened into the record
- Service
- A system that wants the collateral and must define a penalty.
- Catalogue
- The list of services. Listing is not enforcement.
10 Repository
Every linked record on this page
Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.
This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.
Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.