🧮 Manage data public info #1496
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,20 @@ | ||||||||||||||||||
| --- | ||||||||||||||||||
| sidebar_position: 10 | ||||||||||||||||||
| title: Native Data | ||||||||||||||||||
| description: Associate information with a classic account. | ||||||||||||||||||
| --- | ||||||||||||||||||
|
|
||||||||||||||||||
| You can manage data associated with [accounts](../../stellar-data-structures/accounts.mdx) using the [`ManageData` operation](../../transactions/list-of-operations.mdx#manage-data), no smart contract needed! The data entry uses up one account subentry, increasing base reserves. In exchange for this slight cost, you can retrieve an account with [user-defined](../../../../data/apis/horizon/api-reference/resources/operations/object/manage-data.mdx) key-value pairs. | ||||||||||||||||||
|
Comment on lines
+4
to
+7
There was a problem hiding this comment. This documentation file is placed in the "contract-development/storage" directory, but it describes the ManageData operation for classic Stellar accounts, not smart contract storage. This creates a conceptual mismatch - the file explicitly states "no smart contract needed!" while being located within contract development documentation. While the file title "Native Data" attempts to clarify this distinction, placing it in the storage directory alongside persisting-data.mdx and state-archival.mdx (which are about smart contract storage) may confuse readers. Consider placing this documentation in a more appropriate location such as under stellar-data-structures or transactions, or creating a separate section for classic account operations.
Suggested change
Contributor
Author
There was a problem hiding this comment. Lemme sleep on this. I suppose you're right. And I've made a lot of progress documenting ledger entries, which are a different class of protocol data. This was written closer to my section 2.2 concerns, which seem to be all good |
||||||||||||||||||
|
|
||||||||||||||||||
| Existing community projects use this field for [IPFS/IPNS pointers](https://docs.ipfs.tech/concepts/content-addressing/), verification attestations, and much more. The information shows up towards the end of a Horizon response for a base account URL: | ||||||||||||||||||
|
|
||||||||||||||||||
| ```json | ||||||||||||||||||
| "signers": [ | ||||||||||||||||||
| { ... } | ||||||||||||||||||
| ], | ||||||||||||||||||
| "data": { | ||||||||||||||||||
| "ipns": "azUxcXppNXVxdTVka2l0MjdnYzc4a2RmcWpneGxxaW9mdnBtOXFiY2NrZGtzbzVodHUxcWVjYnl5azQwY3o=", | ||||||||||||||||||
| "your": "value" | ||||||||||||||||||
| }, | ||||||||||||||||||
| "num_sponsoring": ... | ||||||||||||||||||
| ``` | ||||||||||||||||||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The sidebar_position value is set to 10, which conflicts with persisting-data.mdx in the same directory that also has sidebar_position: 10. This will cause unpredictable ordering in the documentation sidebar. Since state-archival.mdx uses 20, this file should use a different value such as 15 to maintain proper ordering.