You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/threat-model.md
+45-45Lines changed: 45 additions & 45 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -284,51 +284,6 @@ Notable threats to the system that could impact assets.
284
284
285
285
**Assets Affected**: Decentralization
286
286
287
-
#### T?: Honey Pot Contract
288
-
289
-
**Description**: An attacker deliberately makes ADA available on-chain so anyone races to claim it with the goal of producing many conflicting transactions. This is very similar to T1, but uses cryptocurrency instead of network resources.
290
-
291
-
**Prerequisites**:
292
-
- Knowledge of building a Cardano smart contract
293
-
- Enough ADA to appeal to enough users
294
-
295
-
**Attack Vector**:
296
-
1. Lock a lot of ADA into a script that allows anyone to take `amount` while the remainder must be kept in the script.
297
-
2. Advertise the honey pot and that `amount` of ADA is available for free.
298
-
3. Race with everyone in claiming the output.
299
-
a. If attacker is successful, only transaction fees were spent and `amount` can go back into the honey pot.
300
-
4. Continue until funds run out.
301
-
302
-
**Cost**: HIGH - Enough ADA to appeal many concurrent users and keep the attack going.
303
-
304
-
**Impact**:
305
-
-**Resource Waste**: Network processes all conflicting transactions trying to spend the honey pot output, but only one pays fees at a time. Highest costs are from perpetual storage when conflicting transactions are submitted concurrently.
306
-
-**Throughput**: Reduces available throughput by amount of transactions attracted by the honey pot.
307
-
-**Artifical traffic / low tps**: While this artifical traffic will account into the systems throughput, typically measured in transactions per second (tps), the attacker could require these transactions to be big and computationally costly, resulting in a relatively low tps addition.
308
-
309
-
**Assets Affected**: High Throughput, Operational Sustainability
310
-
311
-
#### T?: Delayed Praos Blocks
312
-
313
-
> [!WARN]
314
-
> Is this a threat or rather part of the Blockchain Safety asset?
315
-
316
-
**Description**: Delaying praos blocks due to long ledger state building (too many txs), impacting liveness and safety.
317
-
318
-
**Impact**:
319
-
-**Chain Quality**: Increased likelihood of chain forks and lower chain quality
320
-
321
-
**Assets Affected**: Blockchain Safety
322
-
323
-
#### T?: Excessive Chain Growth
324
-
325
-
> [!WARN]
326
-
> TODO and how do we describe threats that are not attacks?
327
-
328
-
**Description**: Chain growing too much due to honest demand and too high capacity parameterization (as a threat, not an attack). When SPOs cannot add as much storage as is needed, they cannot validate the chain and decentralization is impacted.
**Description**: Attacker creates EBs referencing non-existing transactions to waste network resources and disrupt certification.
334
289
@@ -427,6 +382,51 @@ Notable threats to the system that could impact assets.
427
382
428
383
**Assets Affected**: Operational Sustainability, High Throughput
429
384
385
+
#### T?: Honey Pot Contract
386
+
387
+
**Description**: An attacker deliberately makes ADA available on-chain so anyone races to claim it with the goal of producing many conflicting transactions. This is very similar to T1, but uses cryptocurrency instead of network resources.
388
+
389
+
**Prerequisites**:
390
+
- Knowledge of building a Cardano smart contract
391
+
- Enough ADA to appeal to enough users
392
+
393
+
**Attack Vector**:
394
+
1. Lock a lot of ADA into a script that allows anyone to take `amount` while the remainder must be kept in the script.
395
+
2. Advertise the honey pot and that `amount` of ADA is available for free.
396
+
3. Race with everyone in claiming the output.
397
+
a. If attacker is successful, only transaction fees were spent and `amount` can go back into the honey pot.
398
+
4. Continue until funds run out.
399
+
400
+
**Cost**: HIGH - Enough ADA to appeal many concurrent users and keep the attack going.
401
+
402
+
**Impact**:
403
+
-**Resource Waste**: Network processes all conflicting transactions trying to spend the honey pot output, but only one pays fees at a time. Highest costs are from perpetual storage when conflicting transactions are submitted concurrently.
404
+
-**Throughput**: Reduces available throughput by amount of transactions attracted by the honey pot.
405
+
-**Artifical traffic / low tps**: While this artifical traffic will account into the systems throughput, typically measured in transactions per second (tps), the attacker could require these transactions to be big and computationally costly, resulting in a relatively low tps addition.
406
+
407
+
**Assets Affected**: High Throughput, Operational Sustainability
408
+
409
+
#### T?: Delayed Praos Blocks
410
+
411
+
> [!WARN]
412
+
> Is this a threat or rather part of the Blockchain Safety asset?
413
+
414
+
**Description**: Delaying praos blocks due to long ledger state building (too many txs), impacting liveness and safety.
415
+
416
+
**Impact**:
417
+
-**Chain Quality**: Increased likelihood of chain forks and lower chain quality
418
+
419
+
**Assets Affected**: Blockchain Safety
420
+
421
+
#### T?: Excessive Chain Growth
422
+
423
+
> [!WARN]
424
+
> TODO and how do we describe threats that are not attacks?
425
+
426
+
**Description**: Chain growing too much due to honest demand and too high capacity parameterization (as a threat, not an attack). When SPOs cannot add as much storage as is needed, they cannot validate the chain and decentralization is impacted.
0 commit comments