Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: Remove reference to storage rent #489

Merged
merged 1 commit into from
Jul 30, 2023
Merged

fix: Remove reference to storage rent #489

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion specs/DataStructures/Account.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

## Account ID

[account_id]: #account_id

Check failure on line 5 in specs/DataStructures/Account.md

View workflow job for this annotation

GitHub Actions / markdown-lint

Link and image reference definitions should be needed [Unused link or image reference definition: "account_id"] [Context: "[account_id]: #account_id"] 

specs/DataStructures/Account.md:5:1 MD053/link-image-reference-definitions Link and image reference definitions should be needed [Unused link or image reference definition: "account_id"] [Context: "[account_id]: #account_id"]

NEAR Protocol has an account names system. Account ID is similar to a username. Account IDs have to follow the rules.

Expand All @@ -25,8 +25,8 @@

```regex
^(([a-z\d]+[\-_])*[a-z\d]+\.)*([a-z\d]+[\-_])*[a-z\d]+$
```

Check failure on line 28 in specs/DataStructures/Account.md

View workflow job for this annotation

GitHub Actions / markdown-lint

Fenced code blocks should be surrounded by blank lines [Context: "```"] 

specs/DataStructures/Account.md:28 MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "```"]
### Top Level Accounts

Check failure on line 29 in specs/DataStructures/Account.md

View workflow job for this annotation

GitHub Actions / markdown-lint

Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Above] [Context: "### Top Level Accounts"] 

specs/DataStructures/Account.md:29 MD022/blanks-around-headings/blanks-around-headers Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Above] [Context: "### Top Level Accounts"]

| Name | Value |
| - | - |
Expand All @@ -52,7 +52,7 @@

Valid accounts:

```

Check failure on line 55 in specs/DataStructures/Account.md

View workflow job for this annotation

GitHub Actions / markdown-lint

Fenced code blocks should have a language specified [Context: "```"] 

specs/DataStructures/Account.md:55 MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
ok
bowen
ek-2
Expand All @@ -73,7 +73,7 @@

Invalid accounts:

```

Check failure on line 76 in specs/DataStructures/Account.md

View workflow job for this annotation

GitHub Actions / markdown-lint

Fenced code blocks should have a language specified [Context: "```"] 

specs/DataStructures/Account.md:76 MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
not ok // Whitespace characters are not allowed
a // Too short
100- // Suffix separator
Expand All @@ -90,7 +90,7 @@
abcdefghijklmnopqrstuvwxyz.abcdefghijklmnopqrstuvwxyz.abcdefghijklmnopqrstuvwxyz
```

## System account

Check failure on line 93 in specs/DataStructures/Account.md

View workflow job for this annotation

GitHub Actions / markdown-lint

Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "## System account"] 

specs/DataStructures/Account.md:93 MD022/blanks-around-headings/blanks-around-headers Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "## System account"]
`system` is a special account that is only used to identify refund receipts. For refund receipts, we set the predecessor_id to be `system` to indicate that it is a refund receipt. Users cannot create or access the `system` account. In fact, this account does not exist as part of the state.

## Implicit account IDs
Expand All @@ -107,7 +107,7 @@
### Implicit account creation

An account with implicit account ID can only be created by sending a transaction/receipt with a single `Transfer` action to the implicit account ID receiver:
- The account will be created with the account ID.

Check failure on line 110 in specs/DataStructures/Account.md

View workflow job for this annotation

GitHub Actions / markdown-lint

Lists should be surrounded by blank lines [Context: "- The account will be created ..."] 

specs/DataStructures/Account.md:110 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- The account will be created ..."]
- The account will have a new full access key with the ED25519-curve public key of `decode_hex(account_id)` and nonce `0`.
- The account balance will have a transfer balance deposited to it.

Expand All @@ -117,7 +117,7 @@

## Account

[account]: #account

Check failure on line 120 in specs/DataStructures/Account.md

View workflow job for this annotation

GitHub Actions / markdown-lint

Link and image reference definitions should be needed [Unused link or image reference definition: "account"] [Context: "[account]: #account"] 

specs/DataStructures/Account.md:120:1 MD053/link-image-reference-definitions Link and image reference definitions should be needed [Unused link or image reference definition: "account"] [Context: "[account]: #account"]

Data for an single account is collocated in one shard. The account data consists of the following:

Expand Down Expand Up @@ -151,7 +151,9 @@
The storage can only be modified by the contract on the account.
Current implementation on Runtime only allows your account's contract to read from the storage, but this might change in the future and other accounts's contracts will be able to read from your storage.

NOTE: Accounts are charged recurrent rent for the total storage. This includes storage of the account itself, contract code, contract storage and all access keys.
NOTE: To pay for blockchain storage, the protocol locks a token amount per account proportional to its state size.
This includes storage of the account itself, contract code, contract storage and all access keys.
See [Storage Staking](https://docs.near.org/concepts/storage/storage-staking) in the docs.

#### Access Keys

Expand Down
Loading