Skip to content

Commit a08799e

Browse files
authored
Add reference to plasma
1 parent 260eb99 commit a08799e

File tree

1 file changed

+1
-1
lines changed
  • public/content/developers/docs/data-availability/blockchain-data-storage-strategies

1 file changed

+1
-1
lines changed

public/content/developers/docs/data-availability/blockchain-data-storage-strategies/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ Depending on your security tradeoffs, it might be acceptable to put the informat
7777

7878
2. Have a mechanism that ensures availability. For example, in [Redstone](https://redstone.xyz/docs/what-is-redstone) any node can submit an availability challenge. If the sequencer does not respond onchain by the deadline, the input commitment is discarded, so the information is considered never to have been posted.
7979

80-
This is acceptable for an optimistic rollup because we are already relying on having at least one honest verifier for the state root. Such an honest verifier will also make sure it has the data to process blocks, and issue an availability challenge if the information is not available offchain.
80+
This is acceptable for an optimistic rollup because we are already relying on having at least one honest verifier for the state root. Such an honest verifier will also make sure it has the data to process blocks, and issue an availability challenge if the information is not available offchain. This type of optimistic rollup is called [plasma](/developers/docs/scaling/plasma/).
8181

8282

8383
## Contract code {#contract-code}

0 commit comments

Comments
 (0)