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

Remove ref to Tombstone #3386

Merged
merged 2 commits into from
Jun 27, 2022
Merged

Remove ref to Tombstone #3386

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8e5c1c1
Remove ref to Tombstone
DrW3RK Jun 1, 2022
2bac32b
minor fixes
DrW3RK Jun 1, 2022
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
9 changes: 4 additions & 5 deletions docs/build/build-smart-contracts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,11 +103,10 @@ design of the EVM:
compiles to Wasm can potentially be used to write smart contracts. Nevertheless, it is better to
have a dedicated domain-specific language, and for that reason Parity offers the [ink!](#ink) language.

2. **Rent**. Contracts must pay rent or else hold a deposit suitably large enough in order to
justify its existence on-chain. When a contract does not uphold this, it may create what's called
a *tombstone* which is a reference to the contract. In some conditions, the contract will be
deleted outright along with its storage if it does not maintain these requirements.

2. **Deposit**. Contracts must hold a deposit (named _ContractDeposit_ ) suitably large enough in order to
justify their existence on-chain. A deployer needs to deposit this into the new contract on
top of the _ExistentialDeposit_.

3. **Caching**. Contracts are cached by default and therefore means they only need to be deployed
once and afterward be instantiated as many times as you want. This helps to keep the storage load
on the chain down to the minimum. On top of this, when a contract is no longer being used and the
Expand Down