mirror of
https://github.com/monero-project/monero-site.git
synced 2024-11-17 16:28:19 +00:00
4c1e8dd858
+ correction on Italian Account + Removed leftover miners.md (replaced by mining.md) + Removed Dust and update Copyright + Code improvement to avoid reading the config file and to use the builtin jekyll config variable passed in the content + Ammount.md:25/26 glitch "\@transaction-privacy" corrected. PL to be checked twice. + Italian ammount.md moneropedia links corrected (terms added to destination entries, unnecessary markdown links removed) + Polish corrections + extend ruby \word-boundary in regex to match `-based` `-like` `-form` + Updated readme according to the new way to add or translate a moneropedia entry + fix mining with CryptoNight variant + rebased to include AR + chery picked #820 to avoid conflicts
16 lines
990 B
Markdown
16 lines
990 B
Markdown
---
|
|
entry: "Block"
|
|
terms: ["block", "blocks"]
|
|
summary: "a container of transactions, a sequence of which forms a blockchain"
|
|
---
|
|
|
|
{% include untranslated.html %}
|
|
### The Basics
|
|
|
|
A block is a container of @transactions, with a new block being added to the @blockchain once every 2 minutes (see constant `DIFFICULTY_TARGET_V2` defined as 120 seconds), on average.
|
|
|
|
Blocks also contain a special type of transaction, the @coinbase-transaction, which add newly created Monero to the network.
|
|
|
|
Blocks are created through the process of @mining, and the @node that successfully mines the block then broadcasts it to each of the @nodes connected to it, who subsequently re-broadcast the block until the entire Monero network has received it.
|
|
|
|
Fake or bad blocks generally cannot be created, as @nodes that receive blocks always verify the @transactions they contain against a set of consensus rules that all nodes adhere to, including validating the cryptographic @signatures on each transaction.
|