or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Do you want to remove this version name and description?
Syncing
xxxxxxxxxx
Solana Community Validator Call Agendas
26 June 2025
1 - Administrative
2 - Intro
3 - Development team updates
4 - Marinade Finance - Making malicious validators pay
5 - Block Zero
6 - Governance update
Appendix - Resources
May 2025
24 April 2025
1 - Administrative
2 - Intro
3 - Accelerate
Scale or Die (Developer-focused, applications must be approved), May 19-20 2025
Ship or Die (All welcome), May 22-23 2025
Register here
Validator specific talks and events
4 - Development team updates
5 - Intro to sandwiched.me by Chris and George
6 - Validator comms
7 - Governance and SIMDs of Interest
27 Mar 2025 (Two year anniversary)
1 - Administrative
2 - Intro
3 - Accelerate
4 - Performance discussion
5 - Development team updates
6 - Governance and SIMDs of Interest
7 - Validator comms
27 Feb 2025
1 - Administrative
2 - Intro
3 - Accelerate
4 - Client development team updates (TBC)
5 - Snapshot delivery
6 - Governance and SIMDs of Interest
7 - Validator comms
23 Jan 2025
1 - Administrative
2 - Intro
3 - Firedancer development update (Philip from Firedancer)
4 - Intro from and Q&A with the DoubleZero team (Mateo and Andrew from Malbec Labs)
5 - Governance and SIMDs of Interest
6 - Validator performance metric discussion
Appendix - Other topics
Dec 4, 2024
1 - Administrative
2 - Intros
3 - Firedancer development update
4 - Introducing the DoubleZero protocol
5 - Slashing
6 - Validator performance metric discussion
Appendix - Other topics
October 24, 2024
1 - Administrative
2 - Intros
3 - Introducing the Solana Hardware Compatibility List
4 - Tracking TVC activation
v2
5 - Firedancer development update
6 - Testnet halt post-mortem (TBC)
7 - SIMD Idea - Sharing Block Rewards and Arbitrary Lamports with Stakers
8 - Snapshot hosting
September 26, 2024
1 - Administrative
2 - Intros
3 - Block Zero Recap
4 - Tracking TVC activation
5 - Mods discussion
July 26, 2024
1 - Administrative
2 - Intros
3 - Block Zero
3 - Community Project Updates
4 - Governance next steps and feature gate activation
5 - Ideal validator set composition
June 27, 2024
1 - Administrative
2 - Intros
3 - Block Zero
4 - MEV
5 - Validator and RPC operator responsibility
6 - Feature gate activation
7 - Governance
8 - Other topics
May 30, 2024
1 - Administrative
2 - Block Zero
3 - Community Projects
4 - Governance
5 - Other topics
April 25, 2024
1 - Administrative
2 - Block Zero
3 - Governance
4 - Congestion control
5 - Other topics
March 27, 2024 (One year anniverary)
1 - Administrative
2 - Block Zero
3 - Firedancer updates
4 - Timely Vote Credits (TVC)
5 - SIMD 96
6 - SIMD organization
February 28, 2024
1 - Administrative
2 - Block Zero
3 - February 6, 2024 outage post-mortem
4 - Notes from the MTNDAO core developer meeting
5 - TVC proposal
January 24, 2024
1 - Administrative
2 - Block 0
3 - Base fees and spam
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 (Postponed to March)
Jito
5 - Governance
November 29, 2023
1 - Block 0 recap
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.
3 - Malicious validator behavior
4 - Governance
October 24, 2023
1 - State of the network
2 - Block 0 planning
Logistics update
Agenda update
3 - Governance discussion
4 - Decentralization - Nakamoto Coefficient drop (Did not discuss.)
Meeting Notes Summary
Meeting notes TBD.
September 11, 2023
1 - State of the network
2 - Block 0 planning
3 - Governance discussion
Meeting Notes Summary
Meeting notes here
July 31, 2023
1 - Block 0 Planning
2 - Governance discussion
Meeting Notes Summary
Meeting notes here
June 23, 2023
1 - Squads
2 - Block 0 Planning
3 - Governance discussion
Meeting Notes Summary
Meeting notes here
May 31, 2023
General Theme - Validator Key Management
1 - Squads
2 - Brief re-introduction to Vote Account Manager Program (VAMP)
From the README -
3 - VAMP x Squads opportunies for collaboration/integration
Other Topics
4 - Keybase replacement PR
From the PR -
5 - Testnet outage (If interest…)
Meeting Notes Summary
Meeting notes here.
April 24, 2023
1 - Discuss root cause analysis (RCA)
v1.14
upgrade based on the RCA?2 - Validator side event at Breakpoint 2023
3 - Introducing the slashing discussion
Does slashing exist on Solana
Is slashing needed and if so when?
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 here.
March 21, 2023
1 - Follow-up on outage post-mortem to-do's
Note: Expected to spend majority of time here.
2 - Discuss comms channels, what to discuss where?
Note: Pulls in discussion topic #4 from here.
3 - DDoS Mitigation or Minimum Commission discussion (time permitting)
Appendix
Meeting Notes
Meeting notes here.