From 54936ef412f26246330b67815f927abfd8f5818e Mon Sep 17 00:00:00 2001 From: Donny <130464015+defitricks@users.noreply.github.com> Date: Tue, 19 Nov 2024 14:45:05 +0200 Subject: [PATCH 1/5] Typo Update faq.mdx --- docs/exchange-operators/faq.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/exchange-operators/faq.mdx b/docs/exchange-operators/faq.mdx index 689cdb85a..6f4788ace 100644 --- a/docs/exchange-operators/faq.mdx +++ b/docs/exchange-operators/faq.mdx @@ -26,7 +26,7 @@ The latest third-party audit reports are publicly available here: :::note -Any news and updates related to exchange listing shared by the Mina Foundation are on [www.minaprotocol.com](https://minaprotocol.com) or the official [Mina Protocol]](https://x.com/MinaProtocol) X (Twitter). Mina Foundation cannot individually answer any listing questions. +Any news and updates related to exchange listing shared by the Mina Foundation are on [www.minaprotocol.com](https://minaprotocol.com) or the official [Mina Protocol](https://x.com/MinaProtocol) X (Twitter). Mina Foundation cannot individually answer any listing questions. ::: From d7507427216710d1f9c2738015287794b5caf649 Mon Sep 17 00:00:00 2001 From: Donny <130464015+defitricks@users.noreply.github.com> Date: Tue, 19 Nov 2024 14:46:48 +0200 Subject: [PATCH 2/5] Typo Update index.mdx --- docs/exchange-operators/index.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/exchange-operators/index.mdx b/docs/exchange-operators/index.mdx index 4a8f85cc8..a38819801 100644 --- a/docs/exchange-operators/index.mdx +++ b/docs/exchange-operators/index.mdx @@ -29,7 +29,7 @@ Use Rosetta API if you are: - Integrating the Mina blockchain with your exchange - Building blockchain applications, such as explorers and wallets -Using Rosetta for building your application is preferrable, as it's API is more appropriate for applications and far more stable than GraphQL. +Using Rosetta for building your application is preferable, as it's API is more appropriate for applications and far more stable than GraphQL. - [Running with Docker](/exchange-operators/rosetta/run-with-docker) - How to install Rosetta from Docker image @@ -49,4 +49,4 @@ For answers to the most frequently asked questions about listing MINA, see [FAQ ## Questions? -Post any questions in Mina’s Github Discussions: https://github.com/MinaProtocol/mina/discussions \ No newline at end of file +Post any questions in Mina’s Github Discussions: https://github.com/MinaProtocol/mina/discussions From f8dca89944248c47996eb8006a8df69507e898d6 Mon Sep 17 00:00:00 2001 From: Donny <130464015+defitricks@users.noreply.github.com> Date: Tue, 19 Nov 2024 14:48:06 +0200 Subject: [PATCH 3/5] Typo Update block-producers.mdx --- docs/mina-protocol/block-producers.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/mina-protocol/block-producers.mdx b/docs/mina-protocol/block-producers.mdx index 6761cbc82..ffcc8de35 100644 --- a/docs/mina-protocol/block-producers.mdx +++ b/docs/mina-protocol/block-producers.mdx @@ -26,7 +26,7 @@ To successfully produce a block, a block producer must have the current state of The opportunity to produce a block for a slot is determined by a [verifiable random function](/glossary#verifiable-random-function-vrf) (VRF). Think of this function as a lottery. Each block producer independently runs this VRF for each slot and if the output is greater than a threshold proportional to the producer's stake, they have the chance to produce a block at the designated slot. -This process is secret so that only the private key holder can determine the VRF output and only they know when they are to produce a block. This selection process aids security as it is impossible for an adversary to target a known block producer at a certain slot, e.g., by a denial of service or targeted attack. As a result, multiple producers can be selected for the same slot. When multiple producers produce a valid block for the same slot, ta short-range fork is produced where the consensus rules select the longest chain. +This process is secret so that only the private key holder can determine the VRF output and only they know when they are to produce a block. This selection process aids security as it is impossible for an adversary to target a known block producer at a certain slot, e.g., by a denial of service or targeted attack. As a result, multiple producers can be selected for the same slot. When multiple producers produce a valid block for the same slot, a short-range fork is produced where the consensus rules select the longest chain. The stake distribution is determined from the SNARKed ledger at the last block of `current epoch-2`, so there is a delay for any recently acquired or [delegated stake](#stake-delegation). For example, if the current epoch is 10, the staking distribution is determined from the SNARKed ledger of the last block of the 8th epoch. From 31fe8327aee1b39f5f914695e9535649c31bb768 Mon Sep 17 00:00:00 2001 From: Donny <130464015+defitricks@users.noreply.github.com> Date: Tue, 19 Nov 2024 14:49:33 +0200 Subject: [PATCH 4/5] Typo Update index.mdx --- docs/mina-protocol/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/mina-protocol/index.mdx b/docs/mina-protocol/index.mdx index 3518ae1c8..30dd7ee2b 100644 --- a/docs/mina-protocol/index.mdx +++ b/docs/mina-protocol/index.mdx @@ -49,7 +49,7 @@ This section describes how the Mina Protocol works. ## Node Operators -[Node Operators](../node-operators) describes how to run Mina nodes on a Mina network. Mina nodes fulfill different roles within the network. +[Node Operators](../node-operators) describe how to run Mina nodes on a Mina network. Mina nodes fulfill different roles within the network. ## Node Developers From 04fefe15c8d88902689d60455d2d24f6c6ca9fd5 Mon Sep 17 00:00:00 2001 From: Donny <130464015+defitricks@users.noreply.github.com> Date: Tue, 19 Nov 2024 14:51:24 +0200 Subject: [PATCH 5/5] Typo Update lifecycle-of-a-payment.mdx --- docs/mina-protocol/lifecycle-of-a-payment.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/mina-protocol/lifecycle-of-a-payment.mdx b/docs/mina-protocol/lifecycle-of-a-payment.mdx index 536e98c21..140ff165c 100644 --- a/docs/mina-protocol/lifecycle-of-a-payment.mdx +++ b/docs/mina-protocol/lifecycle-of-a-payment.mdx @@ -35,7 +35,7 @@ Any member of the network can create a payment and share it with the Mina networ ### Step 2: To produce a block, Bob's payment gets put in a todo list -A block producer node is chosen on the network for a given time slot. The currently active producer choses in-flight payments based on payment fees and places them in a list to be processed called a transition block. Block producers earn mina for building these blocks. The producer generates a SNARK defining the structure of the transition block as compared to the previous block (but not yet verifying these new payments). The producer transmits this new information for SNARK workers to process. +A block producer node is chosen on the network for a given time slot. The currently active producer chooses in-flight payments based on payment fees and places them in a list to be processed called a transition block. Block producers earn mina for building these blocks. The producer generates a SNARK defining the structure of the transition block as compared to the previous block (but not yet verifying these new payments). The producer transmits this new information for SNARK workers to process. ### Step 3: To prove a SNARK transaction, Bob's payment gets SNARK-signed