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
@@ -286,51 +286,6 @@ Notable threats to the system that could impact assets.
286
286
287
287
**Assets Affected**: Decentralization
288
288
289
-
#### T?: Honey Pot Contract
290
-
291
-
**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.
292
-
293
-
**Prerequisites**:
294
-
- Knowledge of building a Cardano smart contract
295
-
- Enough ADA to appeal to enough users
296
-
297
-
**Attack Vector**:
298
-
1. Lock a lot of ADA into a script that allows anyone to take `amount` while the remainder must be kept in the script.
299
-
2. Advertise the honey pot and that `amount` of ADA is available for free.
300
-
3. Race with everyone in claiming the output.
301
-
a. If attacker is successful, only transaction fees were spent and `amount` can go back into the honey pot.
302
-
4. Continue until funds run out.
303
-
304
-
**Cost**: HIGH - Enough ADA to appeal many concurrent users and keep the attack going.
305
-
306
-
**Impact**:
307
-
-**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.
308
-
-**Throughput**: Reduces available throughput by amount of transactions attracted by the honey pot.
309
-
-**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.
310
-
311
-
**Assets Affected**: High Throughput, Operational Sustainability
312
-
313
-
#### T?: Delayed Praos Blocks
314
-
315
-
> [!WARN]
316
-
> Is this a threat or rather part of the Blockchain Safety asset?
317
-
318
-
**Description**: Delaying praos blocks due to long ledger state building (too many txs), impacting liveness and safety.
319
-
320
-
**Impact**:
321
-
-**Chain Quality**: Increased likelihood of chain forks and lower chain quality
322
-
323
-
**Assets Affected**: Blockchain Safety
324
-
325
-
#### T?: Excessive Chain Growth
326
-
327
-
> [!WARN]
328
-
> TODO and how do we describe threats that are not attacks?
329
-
330
-
**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.
336
291
@@ -429,6 +384,51 @@ Notable threats to the system that could impact assets.
429
384
430
385
**Assets Affected**: Operational Sustainability, High Throughput
431
386
387
+
#### T?: Honey Pot Contract
388
+
389
+
**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.
390
+
391
+
**Prerequisites**:
392
+
- Knowledge of building a Cardano smart contract
393
+
- Enough ADA to appeal to enough users
394
+
395
+
**Attack Vector**:
396
+
1. Lock a lot of ADA into a script that allows anyone to take `amount` while the remainder must be kept in the script.
397
+
2. Advertise the honey pot and that `amount` of ADA is available for free.
398
+
3. Race with everyone in claiming the output.
399
+
a. If attacker is successful, only transaction fees were spent and `amount` can go back into the honey pot.
400
+
4. Continue until funds run out.
401
+
402
+
**Cost**: HIGH - Enough ADA to appeal many concurrent users and keep the attack going.
403
+
404
+
**Impact**:
405
+
-**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.
406
+
-**Throughput**: Reduces available throughput by amount of transactions attracted by the honey pot.
407
+
-**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.
408
+
409
+
**Assets Affected**: High Throughput, Operational Sustainability
410
+
411
+
#### T?: Delayed Praos Blocks
412
+
413
+
> [!WARN]
414
+
> Is this a threat or rather part of the Blockchain Safety asset?
415
+
416
+
**Description**: Delaying praos blocks due to long ledger state building (too many txs), impacting liveness and safety.
417
+
418
+
**Impact**:
419
+
-**Chain Quality**: Increased likelihood of chain forks and lower chain quality
420
+
421
+
**Assets Affected**: Blockchain Safety
422
+
423
+
#### T?: Excessive Chain Growth
424
+
425
+
> [!WARN]
426
+
> TODO and how do we describe threats that are not attacks?
427
+
428
+
**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