From d6ff3fed5789f85b96dc63cdb1973fe5b66e4e0f Mon Sep 17 00:00:00 2001 From: barriebyron Date: Thu, 13 Jul 2023 13:06:10 -0400 Subject: [PATCH] delete unused files, quick edit on archive node title --- docs/about-mina/Advanced/cryptography.md | 5 - docs/exchange-operators/faq.mdx | 59 +++-- docs/node-operators/archive-node.mdx | 4 +- docs/node-operators/archive-node/overview.mdx | 222 ------------------ docs/node-operators/mina-cli-reference.mdx | 12 +- docs/participate/testnet-leaderboard.mdx | 3 - .../Developer-References/graphql-api.md | 11 - .../mina-node-cli-reference.md | 5 - .../foundation-delegation-program.md | 25 -- .../block-production/overview.md | 17 -- .../how-to-install-a-node/docker.md | 7 - .../how-to-install-a-node/step-by-step.md | 18 -- 12 files changed, 33 insertions(+), 355 deletions(-) delete mode 100644 docs/about-mina/Advanced/cryptography.md delete mode 100644 docs/node-operators/archive-node/overview.mdx delete mode 100644 docs/participate/testnet-leaderboard.mdx delete mode 100644 docs/z-node-operators/Developer-References/graphql-api.md delete mode 100644 docs/z-node-operators/Developer-References/mina-node-cli-reference.md delete mode 100644 docs/z-node-operators/block-production/foundation-delegation-program.md delete mode 100644 docs/z-node-operators/block-production/overview.md delete mode 100644 docs/z-node-operators/how-to-install-a-node/docker.md delete mode 100644 docs/z-node-operators/how-to-install-a-node/step-by-step.md diff --git a/docs/about-mina/Advanced/cryptography.md b/docs/about-mina/Advanced/cryptography.md deleted file mode 100644 index 91287dd47..000000000 --- a/docs/about-mina/Advanced/cryptography.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Cryptography ---- - -Info/educational section for cryptographer diff --git a/docs/exchange-operators/faq.mdx b/docs/exchange-operators/faq.mdx index 040b51538..57889620d 100644 --- a/docs/exchange-operators/faq.mdx +++ b/docs/exchange-operators/faq.mdx @@ -1,12 +1,12 @@ --- -title: FAQ +title: FAQ Listing Mina description: Frequently asked questions about listing Mina hide_title: true --- import Subhead from "@site/src/components/common/Subhead"; -# FAQ +# FAQ Listing Mina Frequently asked questions about listing Mina. @@ -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 can be found on [www.minaprotocol.com](https://minaprotocol.com) or on the [official Twitter account](https://twitter.com/MinaProtocol). Mina Foundation can not 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://twitter.com/MinaProtocol) Twitter. Mina Foundation cannot individually answer any listing questions. ::: @@ -36,17 +36,15 @@ Any news and updates related to exchange listing shared by the Mina Foundation c Rosetta is an open-source specification that helps exchanges and developers integrate blockchains. Since Rosetta is actively maintained and specifically designed to enable simpler, faster, and more reliable blockchain integrations, we highly recommend using Rosetta to integrate Mina blockchain with your exchange. -You can learn more about Mina’s implementation of Rosetta here (coming soon). - ### What if I have a question about Rosetta? -You can post your questions in [Mina’s Github Discussions](https://github.com/MinaProtocol/mina/discussions). +Ask in [Mina Protocol Discord](https://discord.gg/minaprotocol) or post to the Mina GitHub [Discussions](https://github.com/MinaProtocol/mina/discussions). ## Accounts ### Is there an account creation fee? -Yes, Mina Protocol charges a fee of 1 MINA when you create a new account. This fee helps protect the network from denial of service-type attacks and the amount may be reduced over time. +Yes, Mina Protocol charges a fee of 1 MINA when you create a new account. This fee helps protect the network from denial of service-type attacks. Over time, this fee can change. ## Transactions @@ -54,42 +52,41 @@ Yes, Mina Protocol charges a fee of 1 MINA when you create a new account. This f The max mempool size is 3,000. After it hits that size, transactions with the lowest fees are discarded. -We recommend setting your fee to an amount higher than 0.001 MINA, which is the current average fee for transactions in the pool. +Set your fee to an amount higher than 0.001 MINA, the current average fee for transactions in the pool. -You can view the fees for pending transactions here and adjust your fees accordingly: [https://minaexplorer.com/pending-transactions](https://minaexplorer.com/pending-transactions). +You can view the fees for pending transactions and adjust your fees accordingly: [https://minaexplorer.com/pending-transactions](https://minaexplorer.com/pending-transactions). ### Why do some users appear to have lost their funds when sending to exchanges? :::tip

- While Mina and its SDKs do support the memo field when sending a transaction, - we strongly recommend that you do NOT require a memo for deposits to + While Mina and its SDKs do support the memo field when sending a transaction, the recommended best practice is do NOT require a memo for deposits to prevent this issue for your exchange.

::: -In order to associate the deposit with the user's account, some exchanges require their users to include a unique memo field when sending MINA deposits to the exchange’s address. +To associate the deposit with the user's account, some exchanges require their users to include a unique memo field when sending MINA deposits to the exchange's address. If the user does not include this unique memo when sending their deposit, the receiving exchange may not be able to associate the deposit properly with the user's exchange account. These funds are NOT lost. The exchanges have received the funds at the exchange's address, but the exchange may not be able to automatically associate the deposit with the user's exchange account without such a memo. -To avoid this above issue, we recommend that exchanges do NOT require a memo for deposits. At the same time, we also recommend that exchanges and wallet creators expose an optional memo field during a Mina send transaction. +To prevent this issue, we recommend that exchanges do NOT require a memo for deposits. At the same time, exchanges and wallet creators are recommended to expose an optional memo field during a Mina send transaction. ### What is the maximum number of rollback blocks? The table in [Lifecycle of a Payment](../node-operators/lifecycle-of-a-payment) describes how many blocks you wait for a transaction to be confirmed. -### How should we calculate transaction fees? +### How should I calculate transaction fees? -You can use this tool to calculate your transaction fees: [https://fees.mina.tools](https://fees.mina.tools/) +To calculate your transaction fees, use [https://fees.mina.tools](https://fees.mina.tools/). ## Running a node ### My Mina node gets stuck sometimes. How can I detect this and fix it? -We are aware of this issue and aim to improve this in future versions. For now, we recommend restarting your node whenever this issue is detected. +This is a known issue for some earlier releases. Restart your mina node whenever this issue is detected. You can use the following script to run a cron job every 3 minutes (the slot length) or more frequently: @@ -116,17 +113,17 @@ fi ::: -### Our archive node is missing block information after a restart. How can we recover the data? +### My archive node is missing block information after a restart. How can I recover the data? -Archive node operators often choose to run redundant archive nodes to store block data to one or more locations of their choice (e.g. PostgreSQL, GCP, local files, a logging service, etc) and to backfill any missed block data if needed. +Archive node operators often choose to run redundant archive nodes to store block data to one or more locations of their choice (for example, PostgreSQL, GCP, local files, or a logging service) and to backfill any missed block data if needed. For convenience, [mina_network_block_data](https://console.cloud.google.com/storage/browser/mina_network_block_data) from the archive node is available to help others in the community backfill any missing information. -This bucket contains blocks from various Mina networks — e.g. Mainnet & the most recent Devnet named devnet2. Filter the file names to find those for the network you desire. (Note that this bucket contains blocks for various other networks too, such as QAnet, which we recommend against using for your testing. QAnet is used by O(1) Labs during their iterative development.) +This bucket contains blocks from various Mina networks — for example, Mainnet and the most recent Devnet `devnet2`. Filter by filename for the network you want. Note that this bucket contains blocks for various other networks too, such as QAnet, which is not recommended for your testing. QAnet is used by O(1) Labs during targeted iterative development. -File names contain the network name, block height, and state hash of the block. Blocks older than height 25,705 include only the network name and state hash in the filename. +Filenames contain the network name, block height, and state hash of the block. Blocks older than height 25,705 include only the network name and state hash in the filename. -Example file names: +Example filenames: (Recent) @@ -154,13 +151,13 @@ mina-archive-blocks --precomputed --archive-uri FILE. ### How do I query for the canonical block at a certain height from the archive node -This can be accomplished using a recursive query. See Example #3 in the [Archive Node docs](/node-operators/archive-node), for a full example. +Use a recursive query. See [Query the database](/node-operators/archive-node#query-the-database) examples in the Archive Node docs. ### Why am I getting this error message: "Not able to connect to the network"? This error message usually occurs due to a chain ID mismatch from running a Devnet build on Mainnet, or vice versa. -To check whether you are running a Devenet or Mainnet build, run `Mina client status`. Next, compare the output’s chain ID of your node to the expected chain ID below for the network you are trying to connect to: +To check whether you are running a Devenet or Mainnet build, run `Mina client status`. Next, compare the output's chain ID of your node to the expected chain ID below for the network you are trying to connect to: Mainnet: @@ -176,25 +173,25 @@ Devnet: ### Are there any official broadcast nodes that can be used? -No, there are no official broadcast nodes at this time, but it is possible to broadcast transactions using [https://docs.minaexplorer.com/rest-api/ref](https://docs.minaexplorer.com/rest-api/ref). You can consider this as a backup, but we recommend broadcasting transactions yourself. Minaexplorer’s service rarely goes down because they run many nodes and they rarely all break at the same time. +No, there are no official broadcast nodes at this time. However, you can broadcast transactions using [https://docs.minaexplorer.com/rest-api/ref](https://docs.minaexplorer.com/rest-api/ref). Use this method as a backup, the recommended method is to broadcast transactions yourself. The Minaexplorer service rarely goes down because it runs on many nodes. ## Staking -### Should we be staking our funds? +### Should I be staking my funds? -Since Mina is a Proof of Stake (PoS) consensus network without lockup for staked tokens, we recommend staking these funds since not staking can hurt the chain quality of the Mina network. Additionally, by not staking, you are missing out on staking rewards that you can otherwise be receiving from the Mina blockchain. +Since Mina is a Proof of Stake (PoS) consensus network without lockup for staked tokens, it is recommended to stak these funds to support the quality of the Mina network. Additionally, by not staking, you are missing out on staking rewards that you can otherwise be receiving from the Mina blockchain. -You can look into staking this wallet, either by running your own block production node, or just by delegating your funds to a staking pool on the network. Out of these two options, the latter is simpler to set up (though it does incur about a delay between 18 to 29 days before you can begin getting rewards, as explained below). +You can look into staking this wallet, either by running your own block production node or just by delegating your funds to a staking pool on the network. Delegating to a staking pool is simpler to set up. :::note -Newly staked accounts incur a delay between 18 to 29 days before you start receiving rewards. +Newly staked accounts incur a delay of 18 to 29 days before you start receiving rewards. ::: ### Why is there a delay for staking to take effect? -For purposes of ensuring consensus, there is a delay between when delegations are sent on the blockchain and when they take effect with respect to staking on the network. In other words, the staking ledger always operates between 18 to 29 days behind the live ledger. +For purposes of ensuring consensus, there is a delay between when delegations are sent on the blockchain and when they take effect with respect to staking on the network. The staking ledger always operates between 18 to 29 days behind the live ledger. ### In that case, how long is the delay and when is the next staking snapshot? @@ -211,6 +208,6 @@ You can use this Delegation Calculator tool built by Carbonara to see the next s ### What is the best way to test tooling and integration with Mina? -We strongly suggest that you test tooling and integrations on Devnet before going live on Mainnet. This includes simulating expected Mainnet conditions, such as transaction volume and frequency, to help identify and solve potential issues ahead of time. +Test tooling and integrations on Devnet before going live on Mainnet. The Devnet network is dedicated for developers building on top of the Mina protocol and is designed for testing and experimentation. Be sure to simulate expected Mainnet conditions, such as transaction volume and frequency, to help identify and solve potential issues ahead of time. -See our [instructions for connecting to DevNet](../node-operators/connecting-to-devnet). +See [Connect to Devnet](/node-operators/connecting-to-devnet). diff --git a/docs/node-operators/archive-node.mdx b/docs/node-operators/archive-node.mdx index 35db09786..793761aa7 100644 --- a/docs/node-operators/archive-node.mdx +++ b/docs/node-operators/archive-node.mdx @@ -1,5 +1,5 @@ --- -title: Overview +title: Archive Node description: Mina archive nodes maintain historical information about the network, block, and transactions. A zkApp can retrieve events and actions from one or more Mina archive nodes. keywords: - mina archive node @@ -9,7 +9,7 @@ keywords: - postgres --- -# Archive Node Overview +# Archive Node :::note diff --git a/docs/node-operators/archive-node/overview.mdx b/docs/node-operators/archive-node/overview.mdx deleted file mode 100644 index 92ac5d010..000000000 --- a/docs/node-operators/archive-node/overview.mdx +++ /dev/null @@ -1,222 +0,0 @@ ---- -title: Overview ---- - -# Archive Node Overview - -:::note - -A new version of Mina Docs is coming soon! This page will be rewritten. - -::: - - -Mina nodes are succinct by default, meaning they don't need to maintain historical information about the network, block, or transactions. -For some usecases, it is useful to maintain this historical data, which you can do by running an **Archive Node.** - -An **Archive Node** is just a regular mina daemon that is connected to a running archive process. -The daemon will regularly send blockchain data to the archive process, -which will store it in a [Postgres](https://www.postgresql.org/) database. - -Running an archive node therefore requires some knowledge of managing a Postgres database instance. -In this section, we'll set up a database, run the Archive Node, connect it to a daemon, and try some queries on the data. -Let's get started by installing what we need. - -## Installation - -1. Install the latest version of Mina. If you haven't upgraded to the latest version of the daemon, head [back to the docs](getting-started) to get the latest version. You can run `mina -help` to check if the installation succeeded. -2. Install [Postgres](https://www.postgresql.org/download/). -3. Install the archive node package. - - - Ubuntu/Debian: - - ``` - sudo apt-get install mina-archive=1.3.0-9b0369c - ``` - - - Docker: - ``` - minaprotocol/mina-archive:1.3.0-9b0369c-bullseye - ``` - -## Setup - -Below are some basic instructions on how to set up everything required to get an archive node running locally. These will be slightly different if you're connecting to a cloud instance of postgres, if your deployment uses docker, or if you want to run these processes on different machines. - - - -Note: Some of these instructions may depend on how your operating system installs postgres (and assume that it is installed in the first place). - - - -1. Start a local postgres server. This will just run it in the foreground for testing, you will likely want to run it in the background or use your OS's service manager (like systemd) to run it for you. Alternatively, you may use a postgres service hosted by a cloud provider. - -``` -postgres -p 5432 -D /usr/local/var/postgres -``` - -For macOS, run `brew services start postgres` to start a local postgres server. - -2. Create database (here called `archive`) on server and load the schema into it. This will only need to be done the first time the archive node is set up. - -``` -createdb -h localhost -p 5432 -e archive - -psql -h localhost -p 5432 -d archive -f <(curl -Ls https://raw.githubusercontent.com/MinaProtocol/mina/master/src/app/archive/create_schema.sql) -``` - -3. Start archive process on port 3086, connecting to the postgres database we started on port 5432 in step 1. - -``` -mina-archive run \ - --postgres-uri postgres://localhost:5432/archive \ - --server-port 3086 -``` - -4. Start the daemon, connecting it to the archive process that we just started on port 3086. If you want to connect to an archive process on another machine, you can specify a hostname as well, like `localhost:3086`. - -``` -mina daemon \ - ..... - --archive-address 3086\ -``` - -## Upgrading/Repairing the Archive Data - -Due to a bug in the originally released archive node version 1.1.5, some early transactions may not be represented properly in your database. See [here](https://gist.github.com/lk86/22b07d3b3f91c765f34e4e4398a84701) for complete instructions on migrating your archive database. - -## Using the Archive Node - -Now that we've got the archive node running, let's take a look at the tables in the database. - -To list the tables in the database, you can run the `\dt` command, in psql. -View the full schema of the tables [here](https://github.com/minaProtocol/mina/blob/master/src/app/archive/create_schema.sql). - -Below are some notable fields in each table. - -### Table 1: user_commands - -# - -This table keeps track of transactions made on the network. - -``` -... - user_command_type Type of transaction being made - Possible values: `'payment', 'delegation' - To see a specific type of transaction, i.e. payments or creating a token, specify this field in your queries. - source_id public key of the sender - receiver_id public key of the receiver - amount amount being sent from the sender to the receiver - token ID of a token **If you are querying for different type of token transactions, specify this field.** -``` - -### Table 2: internal_commands - -This table keeps track of rewards earned from snark work or block producing. - -``` -... - internal_command_type represents whether the command is a `fee_transfer` from snark work or a `coinbase` reward from block producing. - Use this field for information about block rewards and snark rewards (there is also an extra fee_transfer added to support sending all the transaction fees summed together to the block_creator) - receiver_id public key ID of the receiver - fee amount being sent from the protocol to the receiver - token ID of a token **If you are querying for different type of token transactions, specify this field.** -``` - -### Table 3: blocks - -``` -... - id - parent_id ID of the previous block in the blockchain - Use this field for information about block rewards and snark rewards (there is also an extra fee_transfer added to support sending all the transaction fees summed together to the block_creator) - creator_id public key of the block creator -``` - -### Join tables - -There are two join tables in the archive database, which links blocks to transactions. -By linking the block table and command tables, these tables allow you to identify -specific transactions within blocks. - -#### Join table 1: blocks_user_commands - -``` -... -block_id ID of the block containing the user command -user_command_id ID of the user command -sequence_no 0-based order of the user command among the block transactions -``` - -#### Join table 2: blocks_internal_commands - -``` -... -block_id ID of the block containing the internal command -internal_command_id ID of the internal command -sequence_no 0-based order of the internal command among the block transactions -secondary_sequence_no 0-based order of a fee transfer within a coinbase internal command -``` - -## Try a query - -Now that we've taken a look at the structure of the data, let's try a query. - -**Example 1:** Find all blocks that have been created by your public key - -``` -SELECT * -FROM blocks AS b -INNER JOIN public_keys AS pk1 ON b.creator_id = pk1.id -WHERE value = 'MY_PK' -``` - -**Example 2:** Find all payments you’ve received by your public key - -``` -SELECT * -FROM user_commands AS uc -JOIN blocks_user_commands AS buc ON uc.id = buc.user_command_id -JOIN public_keys AS pk ON uc.receiver_id = pk.id -WHERE value = 'MY_PK' -AND type = 'payment' -``` - -**Example 3:** Find the block at height 12 on the canonical chain - -``` -WITH RECURSIVE chain AS ( - (SELECT ... FROM blocks b WHERE height = (select MAX(height) from blocks) - ORDER BY timestamp ASC - LIMIT 1) - - UNION ALL - - SELECT ... FROM blocks b - INNER JOIN chain - ON b.id = chain.parent_id AND chain.id <> chain.parent_id -) SELECT ..., pk.value as creator FROM chain c - INNER JOIN public_keys pk - ON pk.id = c.creator_id - WHERE c.height = 12 -``` - -**Example 3:** List the counts of blocks created by each public key and sort them in descending order - -``` -SELECT p.value, COUNT(*) FROM blocks -INNER JOIN public_keys AS p ON creator_id = ip.id -GROUP BY p.value -ORDER BY count DESC; -``` - -**Example 4:** List the counts of applied payments created by each public key and sort them in descending order - -``` -SELECT p.value, COUNT(*) FROM user_commands -INNER JOIN public_keys AS p ON source_id = p.id -WHERE status = 'applied' -AND type = 'payment' -GROUP BY p.value ORDER BY count DESC; -``` diff --git a/docs/node-operators/mina-cli-reference.mdx b/docs/node-operators/mina-cli-reference.mdx index 0d210c51f..e94609f08 100644 --- a/docs/node-operators/mina-cli-reference.mdx +++ b/docs/node-operators/mina-cli-reference.mdx @@ -3,21 +3,15 @@ title: Mina CLI Reference hide_title: true --- -:::note - -A new version of Mina Docs is coming soon! This page will be rewritten. - -::: - # Mina CLI Reference -The Mina CLI (command-line interface) is the primary way for users to interact with the Mina network. It provides standard client functionality to create accounts, send transactions, and participate in consensus. There are also advanced client and daemon commands for power users. +The Mina CLI command line interface is the primary way for users to interact with the Mina network. It provides standard client functionality to create accounts, send transactions, and participate in consensus. There are also advanced client and daemon commands for power users. -The CLI is installed when you [install Mina](/node-operators/getting-started#installation). +The Mina CLI is installed when you [install Mina](/node-operators/getting-started#installation). :::warning -Mina APIs are still under construction, so these commands will likely change. See `mina help` for the most up-to-date version. +Mina APIs are always improving. See `mina help` for the most up-to-date version. ::: diff --git a/docs/participate/testnet-leaderboard.mdx b/docs/participate/testnet-leaderboard.mdx deleted file mode 100644 index ba1554557..000000000 --- a/docs/participate/testnet-leaderboard.mdx +++ /dev/null @@ -1,3 +0,0 @@ ---- -title: TestNet Leaderboard ---- \ No newline at end of file diff --git a/docs/z-node-operators/Developer-References/graphql-api.md b/docs/z-node-operators/Developer-References/graphql-api.md deleted file mode 100644 index 1e604b001..000000000 --- a/docs/z-node-operators/Developer-References/graphql-api.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: GraphQL API ---- - -> Warning: not secure & not meant to be exposed publicly! Security recommendation is to set up a firewall to not expose those ports to the outside world. - -### Intro - -(what is--this is the main interface for anybody who wants to control or automate their daemon, why you might need it, note it’s enabled by default), how to secure it. - -### API documentation diff --git a/docs/z-node-operators/Developer-References/mina-node-cli-reference.md b/docs/z-node-operators/Developer-References/mina-node-cli-reference.md deleted file mode 100644 index ecdee3435..000000000 --- a/docs/z-node-operators/Developer-References/mina-node-cli-reference.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Mina Node CLI ---- - -Describe what all commands do \ No newline at end of file diff --git a/docs/z-node-operators/block-production/foundation-delegation-program.md b/docs/z-node-operators/block-production/foundation-delegation-program.md deleted file mode 100644 index e3f8bb6dd..000000000 --- a/docs/z-node-operators/block-production/foundation-delegation-program.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Mina Foundation Delegation Program ---- -### Installing and running the uptime sidecar - -When participating in the Mina Foundation Delegation Program you will also need to run the uptime sidecar, so please following these instructions and set it up alongside your block producer daemon. - -### Measuring uptime performance - -The uptime sidecar sends recent blockchain data (from your bloc producer node's perspective) to a service that verifies that this recent data is indeed synced with the chain. Specifically, if you have any block producer nodes online at all within any given 10minute window (ie. both your node is synced and the uptime sidecar is sending the data) then you will be marked as online for that 10minute window. Note: You may run more than one node with the same block producer key if you want to increase your chances of remaining up. - -Your uptime is measured as a percentage of all possible 10minute windows over a 60-day period. Uptime performance is only looked at over the last 60-days -- the sooner you fix issues with your nodes and uptime sidecar then the sooner you'll be rewarded with a better uptime and a higher position on the leaderboard. - -See the uptime leaderboard for the latest realtime performance under these conditions. - -Your position on this leaderboard is an important factor in your public key being selected to receive delegation from a token provider. - -### Payout Addresses - -You must send computed rewards as described below to the token provider addresses that delegate to you. If the Foundation is delegating to you, the Foundation will pick two addresses from the Foundation address list at the bottom of the page that will appear as delegations to you. You must distribute the rewards to both those addresses. You must distribute the rewards to both addresses that are delegating to you. - -### Payout Frequency - -Rewards must be distributed at least once for a given epoch (but you can also send them more frequently), all the rewards for epoch N must be delivered (ie. accepted in a block, not just sent) no later than slot number 3,500 of the next epoch. This gives you about a week to sort out these payments. - diff --git a/docs/z-node-operators/block-production/overview.md b/docs/z-node-operators/block-production/overview.md deleted file mode 100644 index e87590253..000000000 --- a/docs/z-node-operators/block-production/overview.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Overview ---- - -* Intro - - Definition - - How to enable block production on your node (which CLI flags). Note that we don’t recommend running snarking & block production simultaneously b/c snarking is CPU intensive. - - Add a side note that you can delegate if you do not want to run a node - link to how to stake - - Delegation - Mention delegation as an option, link to earlier “How to stake / delegate” section. - -* FAQ - - Sidecar for Foundation Delegation - - Tie breaking rule 2 types of ties: - 1. Running multiple block producers with same private key - 2. How your block gets selected over blocks produced by others in the network, if they have equal strength (chain quality & height). - - Explain how/why blocks are chosen to be included in the chain. - - VRF evaluation \ No newline at end of file diff --git a/docs/z-node-operators/how-to-install-a-node/docker.md b/docs/z-node-operators/how-to-install-a-node/docker.md deleted file mode 100644 index a6c5a5725..000000000 --- a/docs/z-node-operators/how-to-install-a-node/docker.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: Docker ---- - -> If you’re considering running an archive node, use this Archive Node image (link to it). - -- First line, if you prefer use Docker, see the next instructions \ No newline at end of file diff --git a/docs/z-node-operators/how-to-install-a-node/step-by-step.md b/docs/z-node-operators/how-to-install-a-node/step-by-step.md deleted file mode 100644 index c292ae3bd..000000000 --- a/docs/z-node-operators/how-to-install-a-node/step-by-step.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Step-by-step ---- - -> If you’re considering running an archive node, use this Archive Node image (link to it). - -- First line, if you prefer use Docker, see the next instructions - -### Ubuntu 18.04 / Debian 9 -Add the Mina Debian repo and install: - -``` -echo "deb [trusted=yes] http://packages.o1test.net release main" | sudo tee /etc/apt/sources.list.d/mina.list -sudo apt-get update -sudo apt-get install -y curl unzip mina-mainnet=1.1.8-b10c0e3 -``` -Check that daemon installed correctly by running `mina version`. The output should read `Commit b10c0e3db9112a2a8aebc3eec7c6d2570fcc4044` on branch master. -