Written by Spork on Sep 16, 2024 Last updated: Oct 7, 2024 by Gavin Looking for validator instructions? https://hackmd.io/@ian-knowable/H1XlWIq5A Quick reference Find your NAM balance: https://raw.githubusercontent.com/anoma/namada-genesis/main/balances.toml Pre-genesis delegation instructions: https://hackmd.io/hrSE8cvaREivp4CYTe55Tw Pre-genesis delegation interface: https://namada-genesis.kintsugi-nodes.com Testnet explorers:

Part 2 - Aug 9 Part 1 - Aug 2 General sentiment: While we are wary of all tokens being unlocked, it would help to better understand the plans and commitments for the different proposed categories of tokens. Synthesis of questions and concerns discussed in Namada community Discord, hot topic found here Distribution and control Can you please break out the allocation categories more granularly with more specific quantities so that it's more clear how much of the Namada genesis token supply different stakeholders will control? a) Early Core Contributors - eg. how much is Heliax getting from this? Knowable & Luminara? b) Protocol maintenance, R&D, ecosystem.. etc - how much is Heliax and Anoma Foundation getting? Knowable & Luminara?

These are some of the questions and concerns that the Namada Shielded Expedition participants would like reviewed ahead the end of the Shielded Expedition competition and before finalizing the results of the competition. We intend to gather and work with these concerns in an announcements thread to make a clear & concise set of questions / concerns below. Questions / Concerns Uptime competition concerns: a) unjailing bug and other client/chain instabilities b) the uptime calculation c) assymetries in NAAN distribution and operations informationProposed solution: the two uptime missions should be removed from the scoring due to 1a. Client issues prevented a significant number of participants from competing for uptime. Those who were able to achieve high uptime should still be rewarded, but outside of the competition. Governance proposal task completion concern: a) assymetries in NAAN distributionAwaiting response from Anoma Foundation Sybilling question & concern:

Overview Announce proposed Shielded Expedition schedule (Gavin) Set up relayers for three one IBC channel (Ian) - OSMO, USDC, ATOM :heavy_check_mark: Set up faucet bot to distribute testnet ATOM (Bengt?) Inject the SSR governance proposal for ATOM (Ian) End the Shielded Expedition chain & S Class submissions Schedule ASAP - Gavin announces proposed Shielded Expedition schedule

Schedule ASAP - Gavin proposes hard fork coordination plan in announcements Thursday Mar 21 Brent refines hard fork guide and publishes as markdown file in https://github.com/anoma/namada-shielded-expedition/ Gavin announces hard fork guide in #se-100-announcements asking for feedbackshare in #shielded-expedition channel and ask for feedback Gavin injects Fork Proposal during Epoch 49 and announces:

Fork Proposal key details from Epoch 30 to 34 context: briefly explain what a hard fork is propose we halt the chain Mar 14 @ 14:00 UTC (block height??) propose that we upgrade to v0.32.0 (note the commit hash) share link to a placeholder location where upgrade guide/instructions will be Proposal

previous: Namada SE 2 Patch 4 TLDR; There was a bug where IBC events were not dropped properly after a failed tx which, when combined with a second bug where gas-metering differed between versions, lead to divergence in state. The current network has progressed to block 90044, which halted due to the aformentioned problem. In order to fix it a majority of validator voting power must upgrade to v0.31.9. Steps to upgrade :warning:ABOVE ALL ELSE, DON'T DELETE PRE-GENESIS DIR OR THE PRIV_VALIDATOR_STATE.JSON:warning: We suggest the following steps to upgrade:

Namada Private Library series Aug 8, 2023 Hosted by Gavin & Park in Namada Discord Increasing numbers of people are concerned with their digital privacy, and companies like Meta and Twitter are adopting end-to-end encryption. In a data-driven world, securing data is ever-more important. And we shouldn't need to justify our right to privacy--the onus is on others to justify the failure to secure it. But privacy can be hard to talk about generally because it tends to be so personal: what I may deem private may not be for you, and vice versa. Each week (typically Tuesday at 16:00 UTC), we chat together about an important privacy topic. This week, let's discuss what can only grow in a privacy-preserving digital environment.

!! this page is in the process of being adapted !! Gavin & Pan are experimenting with hosting sessions that optimize for valuable, meaningful engagement from a diverse set of participant so that these sessions can be hosted with minimal overhead. Ideally the people who join will get a high amount of value for their time, will find points of connection, and will be inspired to host a future session and/or take something to the next level. Session Format The host breaks the topic into sections. For each section, host(s) give a brief intro and then invites questions. We swiftly move on to the next question and topic sections so that we can save lengthy discussions for after the session. Sessions are totally optional! There’s never any pressure to attend or stay—only stay if you are getting value. Preparing for the session know a bit about what people care about to have an engaging session, based on conversations (prev sessions, Discord chats, newsworthy event, etc)