# Namada Shielded Expedition FAQ

*Last updated: Apr 5, 2024*

## The latest
- Shielded Expedition competition to end at Epoch 91 (Apr 11)

# About Points
- the **Nebb is broken** and will not display correct info, [see announcement](https://discord.com/channels/833618405537218590/1196488611613376574/1225810978562900049)
- always include your registered tpknam in the memo field
- [You can verify your S Class submissions here](https://docs.google.com/spreadsheets/d/1YgLo_nt-s_d-2UkrEPcluUnieeuLJtF6vSKsER9EEZU/edit#gid=0). Evaluations are done manually, so they take a long time
- S Class submissions should be [formatted according to this](https://docs.google.com/document/d/1VDc0Xaa4mZPSoyG6tVbqFBZze6HFtnjNC2BZDIQi1TU/edit#heading=h.ytmf67c7tw80).
- see [**RPC/indexer format announcement**](https://hackmd.io/_uploads/S1pM9A6k0.png)
- see [**Shielded app submissions announcement**](https://hackmd.io/_uploads/Hy195RT10.png)
- **only one mission per subclass** will actually get points in the Nebb, even if the spreadsheet says the submission qualifies
- just do **one of each subclass** for S Class missions (not multiple tasks within a subclass)
- Even if you see your submission accepted for multiple submissions, only one will count in the final result
- link all the github issues you started in one submission

## Governance and updates

- use validator address (not implicit) to help get proposals passed
- we likely won't attempt to coordinate anything after 16:00 UTC during the week (and we avoid coordinating anything on Saturday/Sunday)

## Recommended resources before proceeding:
- Shielded Expedition [announcement](https://namada.net/blog/the-namada-shielded-expedition)
- SE's WANTED Asteroids, ROIDs Point System, and Rankings [article](https://namada.net/blog/namada-shielded-expedition-wanted-asteroids-roids-point-system-and-rankings)
- NEBB [link](https://namada.net/shielded-expedition)
- S Class submissions spreadsheet: https://docs.google.com/spreadsheets/d/1YgLo_nt-s_d-2UkrEPcluUnieeuLJtF6vSKsER9EEZU/edit#gid=0
- [Fork](https://github.com/heliaxdev/hermes/tree/1.7.4-namada-long-memo) of Hermes (increased character length in the memo field)
- [Shielded Expedition Faucet](https://namada.net/shielded-expedition/faucet)
- Follow Namada on [twitter](https://twitter.com/namada) for transmissions
- Join the community on [Discord](https://discord.gg/namada)
- `#se-general` announcements
- `#shielded-expedition` for questions

## Glossary

- **NAAN** is the native token of the Namada Shielded Expedition. The token is used for staking and securing the network, as well as to pay for fees.
- **ROID** is a point in the Shielded Expedition. Pilots and - Crew Members are ranked by the ROIDs they have individually accumulated. The only way to accumulate ROIDs is by mining asteroids (completing tasks).
- **NAM** is the native token of Namada mainnet, and will not be in the Shielded Expedition.

## Phase 0: Registration

**1. I've missed the registration deadline. Can I still participate?**
- Once the network is live, you can receive NAAN from any other participant or the Shielded Expedition faucet. However, you won't appear on the Nebb and won't be eligibile for prizes.

**2. What criteria was used to select the pre-genesis pilots?**
- The criteria used to select them included: previous experience, performance, and reputation as a validator; scope of involvement in other ecosystems beyond operating infrastructure (governance stewardship, contributions as builders, etc); diversity in geographical location, structure and size (institutional, small to medium teams, independent validators); and previous involvement and contributions to the Namada ecosystem and community. We received an overwhelming total of 10,473 Pilot registrations and picking the pre-genesis Pilots was not an easy decision.

**3. What if I don't get selected as a pre-genesis pilot?**
- If you have registered as a Pilot but were not selected as a pre-genesis Pilot, you can still become a validator by staking as soon as the SE starts. All **valid** Pilot and Crew Member registrations were included in the SE's genesis block proposal ([balances.toml](https://github.com/anoma/namada-shielded-expedition/blob/main/balances.toml)).

**4. Invalid registrations**
- While reviewing all registrations, we found some `tpknam1` addresses that were invalid public keys. These registrations were filtered out.

**5. Pairs of tpknam1 and tnam1 addresses that did not correspond to each other**
- 203 registrations included a `tpknam1` and `tnam1` that did not correspond to each other. In these cases, we used the tpknam1 address as the source of truth, derived the correct tnam1 address and included them in the balances.toml file. Participants affected by this need to use the correct `tpknam1` accounts in the SE.

**6. Participants who registered using the same tpknam1 and tnam addresses in both Pilots and Crew Members' forms**
- Some participants registered the same pair of keys in both forms. In these cases, we included the pair of keys in the Pilots group and removed the pair from the Crew Members group.

## Phase 1: Preparation “Launch Control”

**1. What's the purpose of the Shielded Expedition?**
- (Mirror of [post](https://discord.com/channels/833618405537218590/1193958565531103272/1201571439464161321) on Discord) The purpose of the Shielded Expedition is to battle test the Namada Protocol before mainnet in an environment as close to real mainnet as possible (follow a decentralized process with a lot of participants including validators and users, and with economic incentives in place). This is especially important for Namada – as a custom L1 the scope of the protocol is huge across the entire stack (not just PoS and cryptography).
- Another goal is to incentivize folks to contribute to the ecosystem e.g. by building and participating in governance/PGF – at this stage there are many builder tools available and Namada would benefit a lot from people outside of core devs using them and giving feedback.

**2. What is the `balances.toml` file?**

- This file includes all accounts with `NAAN` balances in the genesis block proposal of the Shielded Expedition. All valid Pilots and Crew Members' `tpknam1` addresses were included in the `balances.toml` file, this is more than 10k Pilot addresses and almost 130k Crew Member addresses.

**3. How were the genesis files computed?**
- The genesis files are available as a [release](https://github.com/anoma/namada-shielded-expedition/releases/tag/shielded-expedition.b40d8e9055) but the source files and instructions are also available in the [README of the repository](https://github.com/anoma/namada-shielded-expedition). We encourage participants to re-build the genesis files to verify them themselves.

## Phase 2: Pre-Genesis “Afterburn”

**1. Where can I find the `balances.toml` file?**

- In the Shielded Expedition [repository](https://github.com/anoma/namada-shielded-expedition).

**2. What protocol version should be used for the pre-genesis bonding txs?**
- At least `v.30.0` (Namada protocol [releases](https://github.com/anoma/namada/releases)).

**3. What can I do to prepare for the Shielded Expedition?**
- **Pre-genesis Pilots** have to submit a valid pre-genesis bonding tx by 12PM UTC on the 29th of January 2024 to the [signed_genesis_transactions](https://github.com/anoma/namada-shielded-expedition/tree/main/signed_genesis_transactions).

**4. What are the tasks, how does the points system work, and what are the prizes?**

- Every participant should read [this article](https://namada.net/blog/namada-shielded-expedition-wanted-asteroids-roids-point-system-and-rankings) and use the information to prepare for the competition

**5. What resources can I leverage to complete S Class tasks?**
- Here's a non-exhaustive list of tools you can leverage:
- Protocol [versions](https://github.com/anoma/namada/releases)
- Namada [SDK](https://github.com/anoma/namada/tree/main/crates/sdk/src)
- Namada [Light SDK](https://github.com/anoma/namada/tree/bat/light-sdk/writing/light_sdk)
- [Namadexer](https://github.com/Zondax/namadexer)
- Namada [Interfaces](https://github.com/anoma/namada-interface) (extension, namada.me, etc)
- Namada [Faucet](https://github.com/heliaxdev/namada-faucet)
- And [integration DOCS](https://docs.namada.net/integrating-with-namada)

## Phase 3: Genesis “Orbital Injection”

**1. (Pilots) What will I need to start the validator at Genesis?**
- The [genesis files source](https://github.com/anoma/namada-shielded-expedition)
- The [genesis files release](https://github.com/anoma/namada-shielded-expedition/releases/tag/shielded-expedition.88f17d1d14)
- A `chain-id`: `shielded-expedition.88f17d1d14`
- A specific protocol release: [`v0.31.1`](https://github.com/anoma/namada/releases/tag/v0.31.1)
- CometBFT version: `0.37.2`

Genesis time is set for `2024-02-06T18:00:00.000 (UTC)`

**2. Is the latest hermes branch v1.7.4-namada-beta7 compatible with Namada +v0.31.0?**
- It's not up to date with +0.31.0 but it's based on a version that is compatible with +0.31.0.

**3. I've lost the seed phrase/keys I used for registering, can I still participate?**
- You can still participate once the network launches with a newly created account. But the new account won't be tracked on the Nebb and won't be eligible for prizes.
- Good news is that this happened on a testnet and not on mainnet.

**4. Relaunch/restarts**
- The Shielded Expedition has gone through multiple upgrades. [Use the latest release available](https://github.com/anoma/namada/releases/tag/v0.31.4) of the protocol to not fall out of consensus.

## Phase 4: Expedition “Cruising”

**0. Participate using your registered Namada account** :warning:
- Make sure to use **the same `tpknam1`/`tnam1` address you registered with**, so that the points get assigned to your profile on the Nebb.

**1. Transaction Memo Field usage** :warning:

- **Very important** whenever you make a transaction in the SE (after genesis), include your `tpknam1` address in the transaction memo field.
- Clarification (02 Feb): include your public key (tpknam) as the --memo for all transactions in order to properly gain the ROID points for your transaction. If not provided, you may not get the ROID you would otherwise be owed
- Clarification (02 Feb): the only instance in which the --memo does not properly give you ROID at the moment is for an init-validator tx or a change-consensus-key tx, which will be fixed in `v0.31.1`
- Clarification (02 Feb): Use your **testnet tpknam1** addreess, and **not** the second one, which is for receiving NAM rewards in case you win prizes.

**2. Can Pilots complete Crew Member tasks and the other way around?**

- Yes they can, but Pilots are only given points for completing tasks in the Pilots' list of tasks, and Crew Members are only given points for completing Crew Member's tasks.

**3. Can I use the Namada wallet instead of the CLI?**
- Yes, you can use whatever interface you prefer, including the CLI or the interfaces that Heliax has built or even your own. What matters is that you use the **same account you registered with** (see Question 0 above).

**4. (Pilots) Can I update my validator information?**
- Yes, you can update your validator metadata once the chain is live by sending a transaction. Bonus: the Nebb Pilot Ranking's profile should update with the PFP in your validator metadata if you include an image.

**5. Is there a faucet for NAAN?**
- Yes, you can use [this faucet](https://namada.net/shielded-expedition/faucet). The faucet comes with the following spam prevention mechanisms:
- You'll need to authenticate using a registered Pilot or Crew Member keys via the Namada extension
- Every participant can request up to 10 NAAN every 6 hours
- Rate-limited by IP to 5 requests per hour

### S Class Asteroids / Special Task Submissions

**1. How many S Class tasks will I get points for?**
- Every S Class asteroid has subclasses. The ones listed in the [tables](https://namada.net/blog/namada-shielded-expedition-wanted-asteroids-roids-point-system-and-rankings) are examples of tasks that qualify for the subclass. **A participant can only get ROIDs once per subclass for a successful task submission.**
- E.g. if a participant submits 4 successful S class tasks of Subclass "Operating Namada infrastructure as a service", the participant will only get points for 1 task.
- Every S Class subclass has a pool of ROIDs, which will be distributed among the total amount of unique participants who completed a subclass task at the time.
- Clarification(02.02.2024):
- Here's an example on how points are distributed:
- Assume that in the Subclass "Operating Namada infrastructure as a service" we had the following completion rates:
- 100 unique Pilots completed "Providing Public RPC Endpoints as a service"
- 1 unique Pilot completed "Operate a Namada indexer as a service"
- In this case, the ROIDs would be distributed 62,500,000,000 / 101

**2. S Class tasks: Does quality lead to different ROID points?**
- S Class tasks are manually checked (by a human). Quality matters in the sense that the human has to be convinced by the evidence that the task has been completed, leading to winning points.

**3. Do I need to publish “as a service” S Class missions?**
- Yes! If people don’t know that you’re providing a service, how will they know that they can use it?
- Example: an RPC endpoint could be advertised here; a seed node could be added to the https://github.com/anoma/namada-shielded-expedition/blob/main/README.md by pull request

**4.How should I prove that I completed an S Class submission?**
- A human will be reading and verifying your submissions, so provide what you think a person would need to be convinced that it was actually done
- Example: you ran a relayer, so you submit the transactions you sent (channel creation, packet relay) and a signature as proof that you own the keys

**5. What if I run a few relayers? Will I be credited for each one?**
- No, there will only be credit for one relayer. It’s nice if you wanna run 5 relayers, but there is a stronger incentive to do something else in another subclass 😉

## Phase X: Ending

## Misc. Troubleshooting

**1. Having problems with the genesis logs?**
- For anybody that is having problems with the ledger logs "genesis time ...": if you are collecting logs via jounrnalctl you need to increase RateLimitBurst to 100000 in /etc/systemd/journald.conf. Be sure to restart systemd deamon and systemd-journald service.

**2. I have a new node that won’t sync—why not?**
- It could be that the network peers are full, in which case adding “seeds” from [the readme file](https://github.com/anoma/namada-shielded-expedition?tab=readme-ov-file#seeds) should help. Note: nobody has submitted seeds yet! Pls stand by.

**3. Help! Something happened to the chain, now we’re live and I don’t know how to join with my node (again)!**

Before you do anything, always double-check if there were any special instructions in the "we are live again!"-announcement. A halted chain doesn't always require the same type of treatment, especially if it gets resumed again.

IMPORTANT: It’s better to be safe than sorry, so always backup the chain-id folder, even if you're certain that it doesn't contain anything of value. This can be done by copying the folder to a directory of your choosing. In Linux this can be achieved by doing: cp -r ~/.local/share/namada/shielded-expedition.88f17d1d14 ~/shielded-expedition.88f17d1d14. This copies the directory of chain-id shielded-expedition.88f17d1d14 to your HOME-folder. If you wish to move the folder instead, replace the cp -r command with mv.