# Solana Community Validator Call Agendas ## April 25, 2024 * Thursday, April 25 at 18:00 UTC * Meeting link https://meet.google.com/oxt-avji-yvz ### 1 - Administrative * These community validator calls are held on the 4th Wednesday of each month * Contact Max Sherwood if you'd like a meeting invite * Not recorded * Open to the public ### 2 - Block Zero * Agreement signed and commitment made * Will happen Sept 18th in Singapore * Shouldn't conflict with Network State this year * Breakpoint evening reception happens on Sept 19th * Planning kicks into gear next week * Looking for (more details coming soon) * Talk ideas * Sponsors * Busy week in Singapore, book travel early * Breakpoint * Token 2049 * Formula 1 ### 3 - Governance * Futarchy intro * TVC status and next steps * Up next * SIMD 96 * Instant restaking? ### 4 - Congestion control * Near term solution * Traffic filtering * [Stake levels and incoming packet counts](https://github.com/rpcpool/tpu-traffic-classifier) * [Activity within QUIC connections](https://discord.com/channels/428295358100013066/689412830075551748/1230550821876531272) * Longer term solution * SWQOS, good, bad or other? * Community led investigation into protocol changes to protect validators from tx spam, [context here](https://discord.com/channels/428295358100013066/689412830075551748/1232377421647315014) ### 5 - Other topics * Security Council * Gated validator roles ## March 27, 2024 (One year anniverary) * Wednesday, March 27 at 19:00 UTC * Meeting link https://meet.google.com/zpo-prxa-fnr ### 1 - Administrative * Original plan was to hold these calls on the 4th Wednesday of each month moving forward * Establish consistency * Try to avoid overlapping weeks with Tim's call * Should we move the call to the 4th Thursday of each month, to establish consistency with the Foundation call schedule? * Will publish schedule once day is decided on * Contact Max Sherwood if you'd like a meeting invite ### 2 - Block Zero * Agreement signed and commitment made * Will happen Sept 18th in Singapore * Shouldn't conflict with Network State this year * Breakpoint evening reception happens on Sept 19th * Planning will kick into gear toward the end of March and no later than early April * Looking for (more details coming soon) * Talk ideas * Sponsors * Busy week in Singapore, book travel early * Breakpoint * Token 2049 * Formula 1 ### 3 - Firedancer updates * Frankendancer updates * Road to Firedancer updates ### 4 - Timely Vote Credits (TVC) * Current status and timeline (Dates are rough estimates) * Epoch 588 - 594 (3/27): Discussion period * Proposal [here](https://forum.solana.com/t/proposal-for-enabling-the-timely-vote-credits-mechanism-on-solana-mainnet/1179) * Currently 12 validators have commented, 719 views * Epoch 595 (3/31-4/3): stake weights captured and published, discussion/confirmation of stake weights * Epoch 596 (4/4-4/6): voting token distribution, vote addresses created, voting begins * Epochs 596 - 599 (4/7-4/19): voting continues and completes * Epoch 600 (4/20): voting is finished and the resulting tally determines the outcome * Related tool intro by Zan from Shinobi * Before/after analysis [here](https://www.shinobi-systems.com/tvc/590.html) * Stake weight snapshot verification tool [here](https://discord.com/channels/428295358100013066/1207686462041104474/1220584233358069810) ### 5 - SIMD 96 * Title: Reward Collected Priority Fee In Entirety * Summary: Reward 100% of priority fee to validator * Full SIMD [here](https://github.com/solana-foundation/solana-improvement-documents/blob/main/proposals/0096-reward-collected-priority-fee-in-entirety.md) * Current status ([merged](https://github.com/solana-foundation/solana-improvement-documents/pull/96)) and envisaged activation timeline? * Should a governance signaling vote be held? ### 6 - SIMD organization * How it's done today and who's involved * Suggested gaps * Identifying what's being worked on currently * Identifying what's going to be worked on next * Align with governance process? * Path forward and next steps ## February 28, 2024 * Wednesday, February 28 at 19:00 UTC * Meeting link [here](https://meet.google.com/zpo-prxa-fnr) * Meeting notes [here](https://docs.google.com/document/d/1xH3u2HRYB801EuIazcvnVnQqklALUBsok-oERzVwB6Q/edit#heading=h.fynnq842pnrv) ### 1 - Administrative * These calls will be held on the 4th Wednesday of each month moving forward * Establish consistency * Try to avoid overlapping weeks with Tim's call * Contact Max Sherwood if you'd like a meeting invite ### 2 - Block Zero * Agreement signed and commitment made * Will happen Sept 18th in Singapore * Shouldn't conflict with Network State this year * Breakpoint evening reception happens on Sept 19th * Planning will kick into gear toward the end of March and no later than early April ### 3 - February 6, 2024 outage post-mortem * Timeline * 09:53 UTC - Halt * 12:34 UTC - Release binaries and restart instructions published * 14:55 UTC - Consensus progress resumed * [Cause](https://solana.com/news/02-06-24-solana-mainnet-beta-outage-report) * tl;dr The deploy-evict-request cycle of a legacy loader program triggered an infinite recompile loop in the JIT cache. * Restart process * Satisfactory? * Suggested improvements ### 4 - Notes from the MTNDAO core developer meeting * Release engineering * Desire to center coordination on SIMD process * Improvements to SIMD process needed * Identify which SIMDs are being worked on current * Identify which SIMDs will be worked on, i.e. are high priority * Add more testing to the process * New TPM hired by the Foundation may be able to help here * Labs -> Anza transition * Labs and Anza clients will be released in paralled until TBD date * Will then transition solely to Anza client, i.e. Agave after parallel period ends * Firedancer * Team open to giving occasional updates on progress during community-led validator calls * Working on improving the release process * Making releases more visible * Clarifying which releases are compatible with which Labs/Anza release * Governance * Viewed as potentially useful to help coordinate client teams around release process * Two types * Internal - Among client teams * External - To include validators ### 5 - TVC proposal * Current status * Discussed at MTNDAO core developer meeting * General agreement in place to activate pending governance vote * Testing * Recap * Results * [Report by Zantetsu](https://hackmd.io/@Zantetsu/rkHZeFq36) * Next steps * Draft proposal * Determine timeline * Conduct voting ## January 24, 2024 * Wednesday, January 24th at 19:00 UTC * Meeting link https://meet.google.com/zpo-prxa-fnr ### 1 - Administrative * These calls will be held on the 4th Wednesday of each month moving forward * Establish consistency * Try to avoid overlapping weeks with Tim's call * Contact Max Sherwood if you'd like a meeting invite ### 2 - Block 0 * Planning is underway (yes, already) * Organized by Brian @ BlockLogic, Brian @ Jito, Chris @ Chainflow, Michael @ Laine * Feedback * What did you like from last year? * What could have gone better last year or what's one thing you would have changed? * Track/agenda suggestions ### 3 - Base fees and spam * Suggested by ZenLlama * Coordinated with Overclock ### 4 - Community projects of interest This is a new section added last November. If there are any projects you'd like to see present in future calls, let Chris know. * [Light Protocol](https://lightprotocol.com/) (Postponed to March) * Shielded voting is a project Light Protocol's developing in parallel with their core product * What is the group's interest in shielded voting? (Can defer to governance discussion.) * Jito * [StakeNet](https://buffalu.substack.com/p/wtf-is-stakenet) * Is StakeNet a viable source of stake weight information? * Relayer architecture ### 5 - Governance * Focusing on the ["What"](https://sg.laine.one/exploration/what#current-proposal-s) now * Should we align with the existing [SIMD process](https://github.com/solana-foundation/solana-improvement-documents/pulls?) * Example, [SIMD-0096: Reward full priority fee to validators](https://github.com/solana-foundation/solana-improvement-documents/pull/96) * Suggestion made to hold a signaling vote * SIMD approved and merged in the meantime * Other current candidates? * Talk governance at MTNDAO? ## November 29, 2023 * Wednesday, November 29, 2023 1900 UTC * Meeting link [here](https://meet.google.com/gih-zkjz-jmz) * Meeting notes [here](https://docs.google.com/document/d/1zKyT0ON1D46NhitgjcCz4FOmi64BwTk5h8gDUAGBFWs/edit) ### 1 - Block 0 recap * Brief recap for those that didn't attend * Feedback from those who did attend ### 2 - Community projects of interest This is a new section being added this month. If there are any projects you'd like to see present in future calls, let Chris know. These two projects relate to governance and are being presented to learn whether there might be intersections with the ongoing validator governance development process. * [AthensDAOx - Dean](https://twitter.com/AthensDAOx) * [ArmadaFI](https://twitter.com/ArmadaFi) - [NFTtaylor](https://twitter.com/NFTtaylor) ### 3 - Malicious validator behavior * Introduction to most recent findings by Shinobi Systems * Response discussion ### 4 - Governance * Recap of where we stand today * Discuss next steps to reinvigorate the process ## October 24, 2023 * Tuesday, October 24, 2023 1800 UTC * Meeting link [here](https://meet.google.com/dmo-oiou-xmu) ### 1 - State of the network * The v1.16.18 release is now recommended for general use by MainnetBeta validators. [Link](https://discord.com/channels/428295358100013066/669406841830244375/1166128432590110760) * There are currently 212 nodes running v1.17.* on mainnet-beta. v1.17 is not currently recommended or supported for mainnet-beta. Anyone who made that upgrade unintentionally is encouraged to adopt v1.16.18. [Link](https://discord.com/channels/428295358100013066/669406841830244375/1166130470732447855) ### 2 - Block 0 planning * Logistics update * Pre-registration * Transportation * Check-in * Venue setup and configuration * Agenda update * Workshops * Roundtable discussions * Breakouts ### 3 - Governance discussion * Results of first vote * First result post-mortem * Next steps * Squads tooling presentation and discussion ### 4 - Decentralization - Nakamoto Coefficient drop (Did not discuss.) * Potential reasons for the drop * Potential implications * Steps to address * Near-term * Longer-term ### Meeting Notes Summary Meeting notes TBD. ## September 11, 2023 ### 1 - State of the network * Call to [upgrade to v1.14.27 / v1.16.13](https://discord.com/channels/428295358100013066/669406841830244375/1149801414105763901) * v1.16 upgrade * Performance improvements * Paused on more than 10% upgrading during ongoing troubleshooting? (currently at ~11%) * FTX liquidation, more activity than usual anticipated? ### 2 - Block 0 planning * Call for 2-3 additional sponsors to lighten the load on existing sponsors * 3 validators * 3 infrastructure providers * 1 developer * 1 finance * 1 legal * Working to finalize [agenda](https://hackmd.io/@KFEZk8oMTz6vBlwADz0M4A/HJf8_sEwn#Schedule--Agenda), feedback window closing soon ### 3 - Governance discussion * [Who](https://sg.laine.one/exploration/who), three proposals on the table * [What](https://sg.laine.one/exploration/what), two proposals on the table * How, do we select among the Who and What proposals? * Time to start making decisions * Can use an interim solution * Realms/SPL governance discussion ### Meeting Notes Summary Meeting notes [here](https://docs.google.com/document/d/1LvDyIO89T46HeHlaIpQQwFk-W8P7G0U8DQTosaLx_uQ/edit) ## July 31, 2023 ### 1 - Block 0 Planning * Planing [doc here](https://hackmd.io/@KFEZk8oMTz6vBlwADz0M4A/HJf8_sEwn) * Sponsor update * Attendee update * Agenda update and discussion ### 2 - Governance discussion * [Gitbook](https://laine-1.gitbook.io/solana-governance-think-tank) development * Who maintains? * How to contribute? * [Telegram](https://t.me/+CNvn2-hKQRRiMWVk) discussion * Scope discussion, i.e. what is the governance process scope for the first implementation phase (Phase 1)? ### Meeting Notes Summary Meeting notes [here](https://docs.google.com/document/d/1mF-vQdOWIUZl3RTmu7YvtQtexeOV7LVk8j93dlz2E98/edit?usp=sharing) ## June 23, 2023 ### 1 - Squads * Update on community suggestions from May 31 call ### 2 - Block 0 Planning * Planing [doc here](https://hackmd.io/@KFEZk8oMTz6vBlwADz0M4A/HJf8_sEwn) ### 3 - Governance discussion ### Meeting Notes Summary Meeting notes [here](https://docs.google.com/document/d/1A7J9JO8dy2uLCc_8WLHlsxzLMiAtbOJTzkxqhT03n5Q/) ## May 31, 2023 ### General Theme - Validator Key Management ### 1 - Squads * Intro [here](https://squads.so/) * Validator key management capabilities [here](https://docs.squads.so/squads-v3-docs/navigating-your-squad/developers/validators) ### 2 - Brief re-introduction to Vote Account Manager Program (VAMP) * By [Shinobi Systems](https://www.shinobi-systems.com/) * Link to repo [here](https://github.com/bji/vote-account-manager) * Link to previous video walkthrough [here](https://www.youtube.com/watch?t=516&v=y_ee9mq0kPk&feature=youtu.be&themeRefresh=1) From the README - > This repository implements the Vote Account Manager on-chain program. It implements a controlled mechanism for managing a Solana vote account with enhanced security and support features. ### 3 - VAMP x Squads opportunies for collaboration/integration ### Other Topics ### 4 - Keybase replacement PR * Submitted by [Stakewiz](https://stakewiz.com/) * Link to PR [here](https://github.com/solana-labs/solana/pull/31852) From the PR - > Problem > > * keybase.pub service has been sunset > * validators need to use --force to publish a keybase username via CLI > * Longevity of remaining keybase ecosystem is uncertain and dependence on it unnecessary ### 5 - Testnet outage (If interest...) ### Meeting Notes Summary Meeting notes [here](https://docs.google.com/document/d/1v5J4o5lHCGbtVP8pzbIK_7eQVuV0p6kLndEXFOgTS-Y/). ## April 24, 2023 ### 1 - Discuss root cause analysis (RCA) * RCA [here](https://solana.com/news/02-25-23-solana-mainnet-beta-outage-report) * Is the RCA sufficient, are there any open questions? * Are there any hesitations regarding the ``v1.14`` upgrade based on the RCA? ### 2 - Validator side event at Breakpoint 2023 * Introduction - overview of general concept/idea * Logistics * Intial agenda brainstorming ### 3 - Introducing the slashing discussion * Does slashing exist on Solana * In protocol * Out of protocol * Is slashing needed and if so when? * Downtime * Malicious actvity/intention * Operator error ### Meeting Notes Summary - On April 25th, the Solana validator community held its third community-led call, as announced in the Solana discord server. The majority of discussion happened around the topic of slashing on Solana, and whether slashing and/or downtime penalties should be introduced. Chris Remus from Chainflow proposed an agenda and moderated the discussion. Max Sherwood from H2O Nodes took notes. Tim Garcia from the Solana Foundation was also present and contributed to the discussion. - Some participants argued that slashing is needed on Solana, pointing out that slashable offenses have been committed in the past, but have gone unpunished. It is difficult to differentiate between mistakes and malicious behavior that is masquerading as a mistake. - There was discussion around whether slashing should reduce only rewards, or also the principle stake amount. It was pointed out that reducing the principle staked amount reduces a bad actor’s ability to continue malicious behavior. - Fundamentally, slashing should solve the “nothing at stake” problem, to stop validators from voting on multiple forks. Examples of slashable offenses could include: lockout violation, producing duplicate blocks, failing to produce blocks, or failure to forward transactions. - Quadratic slashing mechanisms are complicated, but could ensure that slashed validators don't lose all their money… There was some reluctance to punish delegators, but it was pointed out that this is necessary in order to encourage delegators to more thoughtfully choose validators to stake with, and hold validators accountable. - It was pointed out that slashing could lead to increased decentralization of stake, (delegators spreading out of stake to multiple validators to reduce risk) or conversely slashing could increased centralization of stake. (Delegators choose to stake with large/centralized providers who are considered “safe”.) - In either case, it will be necessary to educate delegators far in advance around the slashing mechanism, explaining that this will protect and strengthen the network going forward. - The implementation of slashing and specifics around penalties should be discussed via a SIMD and subject to a governance vote. An SIMD currently exists on how to track data on-chain in order to build slashing: https://github.com/solana-foundation/solana-improvement-documents/pull/9 Full meeting notes by [Max @ H20 Nodes](https://twitter.com/WholegrainMax) [here](https://docs.google.com/document/d/1K2WnN-kfssmThBCJ4BkrqV0B0waHGYMggS0mEaRTlTc). ## March 21, 2023 ### 1 - Follow-up on outage post-mortem to-do's * Review progress * Gauge interest to continue and discuss next steps * Use of these calls moving forward Note: Expected to spend majority of time here. ### 2 - Discuss comms channels, what to discuss where? * Main Solana server * Solana community server * Forum Note: Pulls in discussion topic #4 from [here](https://hackmd.io/@KFEZk8oMTz6vBlwADz0M4A/HyM-4DAyh). ### 3 - DDoS Mitigation or Minimum Commission discussion (time permitting) * Topics taken from [here](https://hackmd.io/@KFEZk8oMTz6vBlwADz0M4A/HyM-4DAyh) ### Appendix * [Handling Common Solana Outages](https://docs.google.com/document/d/1RkNAyz-5aKvv5FF44b8SoKifChKB705y5SdcEoqMPIc/edit#heading=h.3n4r2183s43v) reference/context link [here](https://discord.com/channels/428295358100013066/489504501749907468/1083808880003399700) ### Meeting Notes Meeting notes [here](https://docs.google.com/document/d/19HQm8pC-C_pzOXVxyI2rKLxBGbGelXlAi7RG7w2so8s/edit).
Last changed by  
 
cfl0ws / chainflow
Building Solana infrastructure for a better future at Chainflow 🌞 Please delegate to us and support our work http://solana.chainflow.io/staking 🙏
1779

Read more

Purpose

There will be a community-run validator conference directly before Breakpoint in Amsterdam. The goal is for the validator community to discuss the evolution of the network and reinforce the social layer.

5/7/2024
Chainflow Firedancer Notes and Logs

Caused by:failed to load manifest for dependency solana-gossip

5/2/2024
Timely vote credits proposal voting coordination

There is a general agreement among key stakeholders that timely vote credits should be activated on mainnet. There's also support to hold a community signaling vote prior to activation.

2/15/2024
Jito StakeNet Twitter Space Summary

What is Stakenet?Stakenet is a self-sustaining protocol designed for Solana LSTs, comprising on-chain programs including the steward program, on-chain history program, and keeper bots. Operating on the Solana mainnet, Stakenet aims to assume complete management of Jito Sol. The steward program acts as the stakepool manager, determining the scoring of validators and facilitating dynamic stake management, including the movement of deposits and the handling of undelegating from underperforming validators each new epoch. The validator history program serves as an oracle or database, capable of storing three years of mainnet validators’ data, encompassing historical performance, commission rates, IPs, and client types. Executing instructions permissionlessly, the keeper bots, open to anyone, perform essential operations every epoch to sustain the system, requiring only a small amount of SOL for maintenance.

1/30/2024
Read more from cfl0ws / chainflow
Published on HackMD