Skip to content

Commit bb917d8

Browse files
authored
Merge pull request #16659 from anegg0/patch-2
fix incorrect statement about calldata/tx relationship
2 parents 20ffa38 + e8aebda commit bb917d8

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
@@ -16,7 +16,7 @@ There are multiple ways to store information either directly on the blockchain,
1616
The choice of which method to use is based on several criteria:
1717

1818
- The source of the information. Information in calldata cannot come directly from the blockchain itself.
19-
- The destination of the information. Calldata is available only in the transaction it initiates. Events are not accessible onchain at all.
19+
- The destination of the information. Calldata is only available in the transaction that includes it. Events are not accessible onchain at all.
2020
- How much hassle is acceptable? Computers that run a full-scale node can perform more processing than a light client in an application running in a browser.
2121
- Is it necessary to facilitate easy access to the information from every node?
2222
- The security requirements.

0 commit comments

Comments
 (0)