Import Tour de SOL docs (#8516)
* Import Tour de SOL docs * Fix checks * Fix docs/build.sh
This commit is contained in:
Justin Starry
GitHub
parent
4831c7b9af
commit
82c6992d6f
Binary file not shown.
|
After Width: | Height: | Size: 193 KiB |
Binary file not shown.
|
|
@ -17,6 +17,27 @@
|
|||
* [Anatomy of a Transaction](transaction.md)
|
||||
* [JSON RPC API](apps/jsonrpc-api.md)
|
||||
* [JavaScript API](apps/javascript-api.md)
|
||||
* [Participating in Tour de SOL](tour-de-sol/README.md)
|
||||
* [Useful Links & Discussion](tour-de-sol/useful-links.md)
|
||||
* [Registration](tour-de-sol/registration/README.md)
|
||||
* [How To Register](tour-de-sol/registration/how-to-register.md)
|
||||
* [Terms of Participation](tour-de-sol/registration/terms-of-participation.md)
|
||||
* [Rewards](tour-de-sol/registration/rewards.md)
|
||||
* [Confidentiality](tour-de-sol/registration/confidentiality.md)
|
||||
* [Registration FAQ](tour-de-sol/registration/validator-registration-and-rewards-faq.md)
|
||||
* [Participation](tour-de-sol/participation/README.md)
|
||||
* [Requirements to run a validator](tour-de-sol/participation/validator-technical-requirements.md)
|
||||
* [Steps to create a validator](tour-de-sol/participation/steps-to-create-a-validator/README.md)
|
||||
* [Install the Solana software](tour-de-sol/participation/steps-to-create-a-validator/install-the-solana-software.md)
|
||||
* [Create a validator public key](tour-de-sol/participation/steps-to-create-a-validator/validator-public-key-registration.md)
|
||||
* [Create and configure a Solana validator](tour-de-sol/participation/steps-to-create-a-validator/connecting-your-validator.md)
|
||||
* [Confirm the Solana network is running](tour-de-sol/participation/steps-to-create-a-validator/confirm-the-solana-network-is-running.md)
|
||||
* [Connect to the Solana network](tour-de-sol/participation/steps-to-create-a-validator/connect-to-the-solana-network.md)
|
||||
* [Validator catch-up](tour-de-sol/participation/steps-to-create-a-validator/monitoring-your-validator.md)
|
||||
* [Staking](tour-de-sol/participation/steps-to-create-a-validator/delegating-stake.md)
|
||||
* [Publish information about your validator](tour-de-sol/participation/steps-to-create-a-validator/publishing-information-about-your-validator.md)
|
||||
* [Dry Run 6](tour-de-sol/participation/dry-run-6.md)
|
||||
* [Submitting Bugs](tour-de-sol/submitting-bugs.md)
|
||||
* [Running a Validator](running-validator/README.md)
|
||||
* [Validator Requirements](running-validator/validator-reqs.md)
|
||||
* [Choosing a Testnet](running-validator/validator-testnet.md)
|
||||
|
|
|
|||
|
|
@ -0,0 +1,9 @@
|
|||
# Introduction
|
||||
|
||||
## Welcome!
|
||||
|
||||
This guide contains information about how to participate in Solana's Tour de SOL. Questions? Comments? Email ryan@solana.com
|
||||
|
||||
### [Learn more about Tour de SOL](https://solana.com/tds/)
|
||||
|
||||
If you haven't registered yet, complete the form at [https://solana.com/tds/](https://solana.com/tds/) first.
|
||||
|
|
@ -0,0 +1,5 @@
|
|||
---
|
||||
description: Setup configuration
|
||||
---
|
||||
|
||||
# Participation
|
||||
|
|
@ -0,0 +1,30 @@
|
|||
# Dry Run 6
|
||||
|
||||
Dry Run 6 will test the performance of a heterogeneous cluster of validators under heavier transaction load. It will be structured as a series of increasing rounds of transactions per second \(TPS\). At the end of each round the validators that survive and produce a block in at least 80% of their leader slots will receive additional stake for the next round. The rounds will continue until the cluster stops making progress.
|
||||
|
||||
|
||||
|
||||
## Cluster Parameters:
|
||||
|
||||
* GPUs optional
|
||||
* Solana software version: v0.22.2
|
||||
* Target transaction rate of first round: 2,000 TPS
|
||||
* Transaction rate round increment: 2,000 TPS
|
||||
* Epoch duration: 4096 slots \(approximately 27 minutes\)
|
||||
* Transaction signature fee: 0 lamport
|
||||
* Genesis allotment to each validator: 2 SOL \(1 SOL for initial delegation, 1 SOL for transaction fees\)
|
||||
* Round duration: 20 minutes of transactions, followed by 2-3 epochs for stake warm up
|
||||
|
||||
## Timeline
|
||||
|
||||
### 24 hour onboarding period: Connect, delegate, stake warmup \(approximately 24 hours\)
|
||||
|
||||
When the cluster boots, validators will have over 24 hours to connect and delegate 1 SOL of stake to themselves
|
||||
|
||||
### Ramp TPS rounds begin! \(approx. 1-2 hours per round\)
|
||||
|
||||
Now that all validator stake is active, the Ramp TPS program will begin running the rounds of increasing transactions-per-second until the cluster fails to maintain consensus or TPS cannot be pushed any higher. Each round starts with of 20 minutes of solid transactions. After 20 minutes all validators that remain with the cluster will receive an additional stake delegation. This new stake will also take 3-4 epochs to warm up, and once warm up is complete the next round commences with an increased transaction rate.
|
||||
|
||||
## References
|
||||
|
||||
* [Ramp TPS program](https://github.com/solana-labs/tour-de-sol/tree/master/ramp-tps)
|
||||
|
|
@ -0,0 +1,12 @@
|
|||
# Steps to create a validator
|
||||
|
||||
To create a Solana validator, complete the following steps, using the instructions that follow this section.
|
||||
|
||||
* [Install the Solana software](install-the-solana-software.md)
|
||||
* [Create your validator public key](validator-public-key-registration.md)
|
||||
* [Create and configure your validator](connecting-your-validator.md)
|
||||
* [Confirm the Solana network is running](confirm-the-solana-network-is-running.md)
|
||||
* [Connect your validator to the Solana network](connect-to-the-solana-network.md)
|
||||
* [Validator catch-up](monitoring-your-validator.md)
|
||||
* [Execute core validator functions](delegating-stake.md)
|
||||
* [Publish validator info \(optional\)](publishing-information-about-your-validator.md)
|
||||
|
|
@ -0,0 +1,23 @@
|
|||
# Confirm the Solana network is running
|
||||
|
||||
Before you connect your validator to the Solana network, confirm the network is running. To do this, view the existing nodes in the network using:
|
||||
|
||||
```bash
|
||||
solana-gossip spy --entrypoint tds.solana.com:8001
|
||||
```
|
||||
|
||||
If you see more than 1 node listed in the output of the above command, the network is running.
|
||||
|
||||
To view the current active stake of all validators, run:
|
||||
|
||||
```bash
|
||||
solana show-validators
|
||||
```
|
||||
|
||||
Finally the `ping` command can be used to check that the cluster is able to process transactions:
|
||||
|
||||
```bash
|
||||
solana ping
|
||||
```
|
||||
|
||||
This command sends a tiny transaction every 2 seconds and reports how long it takes to confirm it.
|
||||
|
|
@ -0,0 +1,41 @@
|
|||
# Connect to the Solana network
|
||||
|
||||
## Create Vote Account
|
||||
|
||||
Once you’ve confirmed the network is running, it’s time to connect your validator to the network.
|
||||
|
||||
If you haven’t already done so, create a vote-account keypair and create the vote account on the network. If you have completed this step, you should see the “validator-vote-keypair.json” in your Solana runtime directory:
|
||||
|
||||
```bash
|
||||
solana-keygen new -o ~/validator-vote-keypair.json
|
||||
```
|
||||
|
||||
Create your vote account on the blockchain:
|
||||
|
||||
```bash
|
||||
solana create-vote-account ~/validator-vote-keypair.json ~/validator-keypair.json
|
||||
```
|
||||
|
||||
## Connect Your Validator
|
||||
|
||||
Connect to the Tour de SOL cluster by running:
|
||||
|
||||
```bash
|
||||
export SOLANA_METRICS_CONFIG="host=https://metrics.solana.com:8086,db=tds,u=tds_writer,p=dry_run"
|
||||
```
|
||||
|
||||
```bash
|
||||
solana-validator --identity-keypair ~/validator-keypair.json --voting-keypair ~/validator-vote-keypair.json \
|
||||
--ledger ~/validator-ledger --rpc-port 8899 --entrypoint tds.solana.com:8001 \
|
||||
--limit-ledger-size
|
||||
```
|
||||
|
||||
To force validator logging to the console add a `--log -` argument, otherwise the validator will automatically log to a file.
|
||||
|
||||
Confirm your validator connected to the network by running:
|
||||
|
||||
```bash
|
||||
solana-gossip spy --entrypoint tds.solana.com:8001
|
||||
```
|
||||
|
||||
This command will display all the nodes that are visible to the TdS network’s entrypoint. If your validator is connected, its public key and IP address will appear in the list.
|
||||
|
|
@ -0,0 +1,43 @@
|
|||
# Create and configure a Solana validator
|
||||
|
||||
The validator identity keypair [you created](validator-public-key-registration.md) identifies your validator. Your validator public key, which you registered for the TdS, will receive an allotment of lamports in the genesis block that can be used to start your validator node. _Note that airdrops have been disabled so the `solana airdrop` command will fail._
|
||||
|
||||
## Configure Solana
|
||||
|
||||
Configure solana for your validator identity and Tour de SOL:
|
||||
|
||||
```bash
|
||||
solana config set --url http://tds.solana.com --keypair ~/validator-keypair.json
|
||||
```
|
||||
|
||||
You should see the following output:
|
||||
|
||||
```text
|
||||
Wallet Config Updated: /home/solana/.config/solana/wallet/config.yml
|
||||
* url: http://tds.solana.com
|
||||
* keypair: /home/solana/validator-keypair.json
|
||||
```
|
||||
|
||||
You can see the wallet configuration at any time by running:
|
||||
|
||||
```text
|
||||
solana config get
|
||||
```
|
||||
|
||||
## Check Validator Balance
|
||||
|
||||
To view your current balance:
|
||||
|
||||
```text
|
||||
solana balance
|
||||
```
|
||||
|
||||
Or to see in finer detail:
|
||||
|
||||
```text
|
||||
solana balance --lamports
|
||||
```
|
||||
|
||||
If your validator identity keypair is created and the above command shows a non-zero balance, your validator is created and configured for TdS.
|
||||
|
||||
Your starting balance will be 500 SOL. Read more about the [difference between SOL and lamports here](../../../introduction.md#what-are-sols).
|
||||
|
|
@ -0,0 +1,82 @@
|
|||
# Staking
|
||||
|
||||
**By default your validator will have no stake.** This means it will be ineligible to become leader.
|
||||
To delegate stake, first make sure your validator is running and has [caught up to the cluster](monitoring-your-validator.md#validator-catch-up).
|
||||
|
||||
More information about staking on solana can be found [here](../../../running-validator/validator-stake.md).
|
||||
|
||||
## Create Stake Keypair
|
||||
|
||||
If you haven’t already done so, create a staking keypair. If you have completed this step, you should see the “validator-stake-keypair.json” in your Solana runtime directory.
|
||||
|
||||
```bash
|
||||
solana-keygen new -o ~/validator-stake-keypair.json
|
||||
```
|
||||
|
||||
## Delegate Stake
|
||||
|
||||
Now delegate 1 SOL to your validator by first creating your stake account:
|
||||
|
||||
```bash
|
||||
solana create-stake-account ~/validator-stake-keypair.json 1
|
||||
```
|
||||
|
||||
and then delegating that stake to your validator:
|
||||
|
||||
```bash
|
||||
solana delegate-stake ~/validator-stake-keypair.json ~/validator-vote-keypair.json
|
||||
```
|
||||
|
||||
{% hint style="warning" %}
|
||||
Don’t delegate all your SOL as your validator identity account requires some to submit votes.
|
||||
{% endhint %}
|
||||
|
||||
At the end of each slot, a validator is expected to send a vote transaction. These vote transactions are paid for by lamports from a validator's identity account.
|
||||
|
||||
This is a normal transaction so the standard transaction fee will apply. The transaction fee range is defined by the genesis block. The actual fee will fluctuate based on transaction load. You can determine the current fee via the [RPC API “getRecentBlockhash”](../../../apps/jsonrpc-api.md#getrecentblockhash) before submitting a transaction.
|
||||
|
||||
Learn more about [transaction fees here](../../../implemented-proposals/transaction-fees.md).
|
||||
|
||||
## Validator Stake Warm-up
|
||||
|
||||
Stakes need to warm up, and warmup increments are applied at Epoch boundaries, so it can take an hour or more for stake to come fully online.
|
||||
|
||||
To monitor your validator during its warmup period:
|
||||
|
||||
* View your vote account:`solana vote-account ~/validator-vote-keypair.json` This displays the current state of all the votes the validator has submitted to the network.
|
||||
* View your stake account, the delegation preference and details of your stake:`solana stake-account ~/validator-stake-keypair.json`
|
||||
* `solana validators` displays the current active stake of all validators, including yours
|
||||
* `solana stake-history ` shows the history of stake warming up and cooling down over recent epochs
|
||||
* Look for log messages on your validator indicating your next leader slot: `[2019-09-27T20:16:00.319721164Z INFO solana_core::replay_stage] <VALIDATOR_IDENTITY_PUBKEY> voted and reset PoH at tick height ####. My next leader slot is ####`
|
||||
* Once your stake is warmed up, you will see a stake balance listed for your validator on the [Solana Network Explorer](http://explorer.solana.com/validators)
|
||||
|
||||
## Monitor Your Staked Validator
|
||||
|
||||
Confirm your validator becomes a [leader](../../../terminology.md#leader)
|
||||
|
||||
* After your validator is caught up, use the `$ solana balance` command to monitor the earnings as your validator is selected as leader and collects transaction fees
|
||||
* Solana nodes offer a number of useful JSON-RPC methods to return information about the network and your validator's participation. Make a request by using curl \(or another http client of your choosing\), specifying the desired method in JSON-RPC-formatted data. For example:
|
||||
|
||||
```bash
|
||||
// Request
|
||||
curl -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1, "method":"getEpochInfo"}' http://localhost:8899
|
||||
|
||||
// Result
|
||||
{"jsonrpc":"2.0","result":{"epoch":3,"slotIndex":126,"slotsInEpoch":256},"id":1}
|
||||
```
|
||||
|
||||
Helpful JSON-RPC methods:
|
||||
|
||||
* `getEpochInfo`[ An epoch](../../../terminology.md#epoch) is the time, i.e. number of [slots](../../../terminology.md?highlight=epoch#slot), for which a [leader schedule](../../../terminology.md?highlight=epoch#leader-schedule) is valid. This will tell you what the current epoch is and how far into it the cluster is.
|
||||
* `getVoteAccounts` This will tell you how much active stake your validator currently has. A % of the validator's stake is activated on an epoch boundary. You can learn more about staking on Solana [here](../../../cluster/stake-delegation-and-rewards.md).
|
||||
* `getLeaderSchedule` At any given moment, the network expects only one validator to produce ledger entries. The [validator currently selected to produce ledger entries](../../../cluster/leader-rotation.md) is called the “leader”. This will return the complete leader schedule \(on a slot-by-slot basis\) for the current epoch. If you validator is scheduled to be leader based on its currently activated stake, the identity pubkey will show up 1 or more times here.
|
||||
|
||||
## Deactivating Stake
|
||||
|
||||
Before detaching your validator from the TdS cluster, you should deactivate the stake that was previously delegated by running:
|
||||
|
||||
```bash
|
||||
solana deactivate-stake ~/validator-stake-keypair.json
|
||||
```
|
||||
|
||||
Stake is not deactivated immediately and instead cools down in a similar fashion as stake warm up. Your validator should remain attached to the cluster while the stake is cooling down. More information about the stake cool down can be found [here](../../../running-validator/validator-stake.md)
|
||||
|
|
@ -0,0 +1,21 @@
|
|||
# Install the Solana software
|
||||
|
||||
Before attempting to connect your validator to the Tour de SOL cluster, be familiar with connecting a validator to the Public Testnet as described [here](../../../running-validator/README.md).
|
||||
|
||||
You can confirm the version running on the cluster entrypoint by running:
|
||||
|
||||
```text
|
||||
curl -X POST -H "Content-Type: application/json" -d '{"jsonrpc": "2.0","id":1,"method":"getVersion"}' tds.solana.com:8899
|
||||
```
|
||||
|
||||
Note the version number
|
||||
|
||||
## Install Software
|
||||
|
||||
Install the Solana release [v0.23.7](https://github.com/solana-labs/solana/releases/tag/v0.23.7) on your machine by running:
|
||||
|
||||
```bash
|
||||
curl -sSf https://raw.githubusercontent.com/solana-labs/solana/v0.22.2/install/solana-install-init.sh | sh -s - 0.23.7
|
||||
```
|
||||
|
||||
then run `solana --version` to confirm the expected version number.
|
||||
|
|
@ -0,0 +1,12 @@
|
|||
# Validator catch-up
|
||||
|
||||
Once your validator is connected and voting, it should appear on the [Solana Network Explorer](http://explorer.solana.com/validators). \(Switch to the Tour de SOL network in the top right\)
|
||||
|
||||
But your validator may take some time to catch up with the cluster. Use the `catchup` command to monitor this process:
|
||||
```bash
|
||||
solana catchup ~/validator-keypair.json
|
||||
```
|
||||
|
||||
Until your validator has caught up, it will not be able to vote successfully and stake cannot be delegated to it.
|
||||
|
||||
Also if you find the network's slot advancing faster than yours, you will likely never catch up. This typically implies some kind of networking issue between your validator and the rest of the network.
|
||||
|
|
@ -0,0 +1,23 @@
|
|||
# Publish information about your validator
|
||||
|
||||
See [here](../../../running-validator/validator-info.md) for background:
|
||||
|
||||
Example publish command:
|
||||
|
||||
```bash
|
||||
solana validator-info publish "Elvis Validator" -n elvis -w "https://elvis-validates.com"
|
||||
```
|
||||
|
||||
Example query command:
|
||||
|
||||
```bash
|
||||
solana validator-info get
|
||||
```
|
||||
|
||||
which outputs
|
||||
|
||||
```text
|
||||
Validator info from 8WdJvDz6obhADdxpGCiJKZsDYwTLNEDFizayqziDc9ah
|
||||
Validator pubkey: 6dMH3u76qZ7XG4bVboVRnBHR2FfrxEqTTTyj4xmyDMWo
|
||||
Info: {"keybaseUsername":"elvis","name":"Elvis Validator","website":"https://elvis-validates.com"}
|
||||
```
|
||||
|
|
@ -0,0 +1,48 @@
|
|||
# Create a validator public key
|
||||
|
||||
In order to participate in any Tour de SOL dry-runs or stages, you need to register for the Tour de SOL.
|
||||
|
||||
See [Registration info](../../registration/).
|
||||
|
||||
In order to obtain your allotment of lamports at the start of a Tour de SOL stage or dry run, you need to publish your validator's identity public key under your keybase.io account.
|
||||
|
||||
**If these steps are not completed by the cut-off time you will not be able to participate.**
|
||||
|
||||
## **Generate Keypair**
|
||||
|
||||
1. If you haven't already, generate your validator's identity keypair by running:
|
||||
|
||||
```bash
|
||||
solana-keygen new -o ~/validator-keypair.json
|
||||
```
|
||||
|
||||
2. The identity public key can now be viewed by running:
|
||||
|
||||
```bash
|
||||
solana-keygen pubkey ~/validator-keypair.json
|
||||
```
|
||||
|
||||
{% hint style="info" %}
|
||||
Note: The "validator-keypair.json” file is also your \(ed25519\) private key.
|
||||
{% endhint %}
|
||||
|
||||
Your validator identity keypair uniquely identifies your validator within the network. **It is crucial to back-up this information.**
|
||||
|
||||
If you don’t back up this information, you WILL NOT BE ABLE TO RECOVER YOUR VALIDATOR, if you lose access to it. If this happens, YOU WILL LOSE YOUR ALLOCATION OF LAMPORTS TOO.
|
||||
|
||||
To back-up your validator identify keypair, **back-up your "validator-keypair.json” file to a secure location.**
|
||||
|
||||
## Link your Solana pubkey to a Keybase account
|
||||
|
||||
You must link your Solana pubkey to a Keybase.io account. The following instructions describe how to do that by installing Keybase on your server.
|
||||
|
||||
1. Install [Keybase](https://keybase.io/download) on your machine.
|
||||
2. Log in to your Keybase account on your server. Create a Keybase account first if you don’t already have one. Here’s a [list of basic Keybase CLI commands](https://keybase.io/docs/command_line/basics).
|
||||
3. Create a Solana directory in your public file folder: `mkdir /keybase/public/<KEYBASE_USERNAME>/solana`
|
||||
4. Publish your validator's identity public key by creating an empty file in your Keybase public file folder in the following format: `/keybase/public/<KEYBASE_USERNAME>/solana/validator-<BASE58_PUBKEY>`. For example:
|
||||
|
||||
```bash
|
||||
touch /keybase/public/<KEYBASE_USERNAME>/solana/validator-<BASE58_PUBKEY>
|
||||
```
|
||||
|
||||
5. To check your public key was published, ensure you can successfully browse to `https://keybase.pub/<KEYBASE_USERNAME>/solana/validator-<BASE58_PUBKEY>`
|
||||
|
|
@ -0,0 +1,26 @@
|
|||
# Requirements to run a validator
|
||||
|
||||
## Hardware
|
||||
|
||||
See [suggested hardware configuration here](../../running-validator/validator-reqs.md).
|
||||
|
||||
* CPU Recommendations
|
||||
* We recommend a CPU with the highest number of cores as possible. AMD Threadripper or Intel Server \(Xeon\) CPUs are fine.
|
||||
* We recommend AMD Threadripper as you get a larger number of cores for parallelization compared to Intel.
|
||||
* Threadripper also has a cost-per-core advantage and a greater number of PCIe lanes compared to the equivalent Intel part. PoH \(Proof of History\) is based on sha256 and Threadripper also supports sha256 hardware instructions.
|
||||
* SSD size and I/O style \(SATA vs NVMe/M.2\)
for a validator
|
||||
* Minimum example - Samsung 860 Evo 2TB
|
||||
* Mid-range example - Samsung 860 Evo 4TB
|
||||
* High-end example - Samsung 860 Evo 4TB
|
||||
* GPUs
|
||||
* **Validator** nodes will be required to run with GPUs starting at Stage 1 of Tour de SOL. Without GPUs, a validator will not be able to catch up to the ledger once the network is launched. GPUs are NOT required for validators during Stage 0/Dry Runs of Tour de SOL.
|
||||
* What kind of GPU?
|
||||
* We recommend Nvidia 2080Ti or 1080Ti series consumer GPU or Tesla series server GPUs.
|
||||
* We do not currently support OpenCL and therefore do not support AMD GPUs. We have a bounty out for someone to port us to OpenCL. Interested? [Check out our GitHub.](https://github.com/solana-labs/solana)
|
||||
* Power Consumption
|
||||
* Approximate power consumption for a validator node running an AMD Threadripper 2950W and 2x 2080Ti GPUs is 800-1000W.
|
||||
|
||||
## **Software**
|
||||
|
||||
* We build and run on Ubuntu 18.04. Some users have had trouble when running on Ubuntu 16.04
|
||||
* See [Connecting Your Validator](steps-to-create-a-validator/connecting-your-validator.md#install-software) for the current Solana software release.
|
||||
|
|
@ -0,0 +1 @@
|
|||
# Registration
|
||||
|
|
@ -0,0 +1,5 @@
|
|||
# Confidentiality
|
||||
|
||||
**Section 8 of the** [**TOUR DE SOL PARTICIPATION TERMS**](https://drive.google.com/file/d/15ueLG6VJoQ5Hx4rnpjFeuL3pG5DbrBbE/view) **references confidentiality.**
|
||||
|
||||
Solana doesn’t intend to share any confidential information during the Tour de SOL. However, if we do, it will be called out as such within our communications verbally, by email, etc. Unless information is specifically called out as such, the information should not be considered confidential and we welcome you to share it.
|
||||
|
|
@ -0,0 +1,11 @@
|
|||
# How To Register
|
||||
|
||||
1. **Registration Form** Submit the form [here](https://forms.gle/gGS2z4jTXq6hAZ2X9). Once the form is submitted, our team will review the information and insert the information into a publicly viewable spreadsheet for tracking.
|
||||
2. **KYC/AML**
|
||||
Complete KYC/AML [here](https://tsm.coinlist.co/solana-tour-de-sol/new). \(**Ignore all the references to investment** on the portal; we just used their default template. Apologies for the confusion!\)
|
||||
|
||||
We have prepared a guide to the KYC/AML process [here](https://docs.google.com/presentation/d/1gz8e34piUzzwzCMKwVrKKbZiPXV64Uq2-Izt4-VcMR4/edit?usp=sharing). Note that KYC/AML is mandatory **before** participating in any stage, and compensation is conditional upon you passing KYC/AML.
|
||||
|
||||
3. **Participation Agreement** Instructions for completing the participation agreement W-9 will be emailed out to the email you provided, to be filled out and returned to us.
|
||||
4. **Tax Documents: W-8 BEN or W9** Once your Coinlist KYC application is approved, our team will send either a W-8 BEN for international participants or a W9 via DocuSign. Fill out the form with the same information you used with CoinList.
|
||||
5. **Status** The status of your participation agreement will be tracked along with the other registration information. We’ll also try to notify you upon completion or rejection of any submitted participation agreements.
|
||||
|
|
@ -0,0 +1,27 @@
|
|||
# Rewards
|
||||
|
||||
## Reward Calculation <a id="how-are-rewards-calculated"></a>
|
||||
|
||||
Rewards will be calculated according to the compensation design described in [this forum post](https://forums.solana.com/t/tour-de-sol-stage-1-preliminary-compensation-design/79) and [this spreadsheet](https://docs.google.com/spreadsheets/d/11puBSw2THdO4wU-uyDEic-D03jg4ZAooVpcZU0w_4gI/edit#gid=218406032).
|
||||
|
||||
Please also see section “2\(f\) Tour de Sol Details” of the [TOUR DE SOL PARTICIPATION TERMS](https://drive.google.com/file/d/15ueLG6VJoQ5Hx4rnpjFeuL3pG5DbrBbE/view) for additional rewards details.
|
||||
|
||||
## Requirements to Receive Rewards <a id="what-are-the-requirements-to-receive-rewards"></a>
|
||||
|
||||
Participants must have signed the Tour de SOL participation agreement, passed KYC/AML as an individual via CoinList’s platform, as well as filled out the W-8 BEN or W-9 tax form \(depending on your residency\) prior to participating in the Tour. A participant may participate in any and all stages that begin after they complete registration. The final registrations dates will be announced publicly on a stage-by-stage basis.
|
||||
|
||||
Lastly, participants must sign Solana’s standard [Token Agreement](https://drive.google.com/open?id=1O4cEUZzeSNoVcncbHcEegAqPgjT-7hcy). The Token Agreement will be made available by Solana prior to the rewards issuance date.
|
||||
|
||||
Please also see sections “2\(i\) & 2\(j\) Tour de Sol Details” of the [TOUR DE SOL PARTICIPATION TERMS](https://drive.google.com/file/d/15ueLG6VJoQ5Hx4rnpjFeuL3pG5DbrBbE/view) for additional details related to receiving rewards.
|
||||
|
||||
## Tax Implications <a id="what-are-the-tax-implications-of-the-rewards"></a>
|
||||
|
||||
Participants are entering into a service agreement with Solana with discretionary compensation associated with the services. They are not considered to be a full-time employee of the company and therefore Solana is collecting W-9 and W-8 BEN forms in order to support tax reporting obligations, if applicable. Solana recommends participants consult with a tax accountant to understand any potential tax implications.
|
||||
|
||||
Also, as stated in Sections 2i, 2k and 10c of the [TOUR DE SOL PARTICIPATION TERMS](https://drive.google.com/file/d/15ueLG6VJoQ5Hx4rnpjFeuL3pG5DbrBbE/view):
|
||||
|
||||
> 2i - To receive any SOL Reward, a Finalist must sign the Company’s standard form of SOL Reward Agreement which will include the terms and conditions governing the ownership and use of the SOL that are issued as the SOL Reward, including but not limited to applicable lockups required by securities laws, blackout dates and tax reporting information.
|
||||
|
||||
> 2k - To receive any SOL Reward, a Finalist must sign the Company’s standard form of SOL Reward Agreement which will include the terms and conditions governing the ownership and use of the SOL that are issued as the SOL Reward, including but not limited to applicable lockups required by securities laws, blackout dates and tax reporting information.
|
||||
|
||||
> 10c - You are responsible for complying with all laws and regulations applicable to your transactions on any Protocol, including, but not limited to, the Commodity Exchange Act and the regulations promulgated thereunder by the U.S. Commodity Futures Trading Commission \(“CFTC”\), the federal securities laws and the regulations promulgated thereunder by the U.S. Securities and Exchange Commission \(“SEC”\), and the tax laws applicable to any remuneration received by you from Company.
|
||||
|
|
@ -0,0 +1,6 @@
|
|||
# Terms of Participation
|
||||
|
||||
Please see the official [TOUR DE SOL PARTICIPATION TERMS](https://drive.google.com/a/solana.com/file/d/15ueLG6VJoQ5Hx4rnpjFeuL3pG5DbrBbE/view?usp=sharing) for complete details.
|
||||
Download below:
|
||||
|
||||
{% file src="../../.gitbook/assets/solana-tour-de-sol-participation-terms-20190723.pdf" caption="Tour de SOL Participation Terms" %}
|
||||
|
|
@ -0,0 +1,51 @@
|
|||
# Registration FAQ
|
||||
|
||||
The [TOUR DE SOL PARTICIPATION TERMS](https://drive.google.com/a/solana.com/file/d/15ueLG6VJoQ5Hx4rnpjFeuL3pG5DbrBbE/view?usp=sharing) should be considered the authoritative resource for any participation questions.
|
||||
|
||||
## Is registration mandatory?
|
||||
|
||||
Yes. Registration is mandatory. If you do not register before Stage 1 of the Tour de Sol, you cannot participate in the Tour de Sol. [Registration information lives here](how-to-register.md).
|
||||
|
||||
## Who’s eligible to participate?
|
||||
|
||||
Please see section “1 Eligibility; KYC Requirements” of the [TOUR DE SOL PARTICIPATION TERMS](https://drive.google.com/a/solana.com/file/d/15ueLG6VJoQ5Hx4rnpjFeuL3pG5DbrBbE/view?usp=sharing) for details.
|
||||
|
||||
## Do I have to complete the KYC/AML process to participate?
|
||||
|
||||
Yes. Completing the KYC/AML process is mandatory. If you do not complete the process before Stage 1 of the Tour de SOL, you cannot participate in the Tour de SOL.
|
||||
|
||||
We’ve partnered with Coinlist to manage the Tour de Sol KYC/AML process. You can find a [walk-through of the process here](https://docs.google.com/presentation/d/1gz8e34piUzzwzCMKwVrKKbZiPXV64Uq2-Izt4-VcMR4/) and [complete your process here](https://docs.google.com/presentation/d/1gz8e34piUzzwzCMKwVrKKbZiPXV64Uq2-Izt4-VcMR4/edit#slide=id.g5dff17f5e5_0_44).
|
||||
|
||||
## What are my responsibilities as a Tour de Sol participant?
|
||||
|
||||
Please see section “2c Tour de SOL Details” of the [TOUR DE SOL PARTICIPATION TERMS](https://drive.google.com/file/d/15ueLG6VJoQ5Hx4rnpjFeuL3pG5DbrBbE/view) for details.
|
||||
|
||||
### How is the “50% of the active Tour event time” responsibility calculated?
|
||||
|
||||
To be eligible for rewards in a given stage, a validator must submit votes in >= 50% of that stage’s slots.
|
||||
|
||||
If a validator isn’t able to submit >= 50% of votes for a stage and still feels they should receive awards for that stage, they can petition Solana for reconsideration.
|
||||
|
||||
## Is there a relationship between the Tour de Sol testnet tokens and Solana mainnet tokens?
|
||||
|
||||
No. Please see section ”2d Tour de SOL Details” of the [TOUR DE SOL PARTICIPATION TERMS](https://drive.google.com/file/d/15ueLG6VJoQ5Hx4rnpjFeuL3pG5DbrBbE/view) for details.
|
||||
|
||||
## Can a validator be disqualified from the Tour de Sol?
|
||||
|
||||
Yes. A validator be disqualified from the Tour de SOL if they engage in prohibited conduct and/or fails to provide the minimum level of services described in question \#4 above.
|
||||
|
||||
Please also see Section “4 Prohibited Conduct” of the [TOUR DE SOL PARTICIPATION TERMS](https://drive.google.com/file/d/15ueLG6VJoQ5Hx4rnpjFeuL3pG5DbrBbE/view) for a more detailed description of prohibited conduct.
|
||||
|
||||
### More questions related to Prohibited Conduct:
|
||||
|
||||
#### As referenced in section “4 Prohibited Conduct”, what would be an example of providing Tour Services from a jurisdiction other than the jurisdiction of my residence? Does this mean my server has to reside in the jurisdiction of my residence?
|
||||
|
||||
No. Servers can be in other jurisdictions that differ from a participant’s residency. By signing the [TOUR DE SOL PARTICIPATION TERMS](https://drive.google.com/file/d/15ueLG6VJoQ5Hx4rnpjFeuL3pG5DbrBbE/view) the participant has represented that they are delivering their services from the US if they reside there or from outside the US if they are not residing within the US.
|
||||
|
||||
## How are rewards calculated?
|
||||
|
||||
Please see the [Rewards section](rewards.md) for details
|
||||
|
||||
## How will we know what information we can and cannot share publicly?
|
||||
|
||||
Please see [Confidentiality](confidentiality.md).
|
||||
|
|
@ -0,0 +1,5 @@
|
|||
# Submitting Bugs
|
||||
|
||||
Please submit all bugs and feedback as [issues in this Github repo](https://github.com/solana-labs/tour-de-sol/issues).
|
||||
|
||||
Given the fast pace of communication in the [Discord channels](useful-links.md), it’s likely issues reported in them may be lost in the information flow. Filing the issues in the Github repo is the only way to ensure the issues get logged and addressed.
|
||||
|
|
@ -0,0 +1,21 @@
|
|||
---
|
||||
description: Where to go after you've read this guide
|
||||
---
|
||||
|
||||
# Useful Links & Discussion
|
||||
|
||||
* [Solana Docs](https://docs.solana.com/)
|
||||
* [Network Explorer](http://explorer.solana.com/)
|
||||
* [TdS metrics dashboard](https://metrics.solana.com:3000/d/testnet/testnet-monitor?refresh=1m&from=now-15m&to=now&orgId=2&var-datasource=Solana%20Metrics%20(read-only)&var-testnet=tds&var-hostid=All9)
|
||||
* Validator chat channels
|
||||
* [\#validator-support](https://discord.gg/rZsenD) General support channel for any Validator related queries that don’t fall under Tour de SOL.
|
||||
* [\#tourdesol](https://discord.gg/BdujK2) Discussion and support channel for Tour de SOL participants.
|
||||
* [\#tourdesol-announcements](https://discord.gg/Q5TxEC) The single source of truth for critical information relating to Tour de SOL
|
||||
* [\#tourdesol-stage0](https://discord.gg/Xf8tES) Discussion for events within Tour de SOL Stage 0. Stage 0 includes all the dry-run
|
||||
* [Core software repo](https://github.com/solana-labs/solana)
|
||||
* [Current Testnet/TdS repo](https://github.com/solana-labs/tour-de-sol)
|
||||
* [Submit bugs and feedback in this repo](https://github.com/solana-labs/tour-de-sol/issues)
|
||||
|
||||
{% hint style="info" %}
|
||||
Can't find what you're looking for? Send an email to ryan@solana.com or reach out to @rshea\#2622 on Discord.
|
||||
{% endhint %}
|
||||
Loading…
Reference in New Issue