From a785628e87460a47cc55dba8aaa4916e68feaaaa Mon Sep 17 00:00:00 2001
From: 0xNineteen <0x39015319@gmail.com>
Date: Wed, 7 Jun 2023 11:55:44 -0400
Subject: [PATCH 1/3] init

---
 proposals/00xx-sysvar-get-active-stake.md | 64 +++++++++++++++++++++++
 1 file changed, 64 insertions(+)
 create mode 100644 proposals/00xx-sysvar-get-active-stake.md

diff --git a/proposals/00xx-sysvar-get-active-stake.md b/proposals/00xx-sysvar-get-active-stake.md
new file mode 100644
index 00000000..bdadccd8
--- /dev/null
+++ b/proposals/00xx-sysvar-get-active-stake.md
@@ -0,0 +1,64 @@
+---
+simd: '0000'
+title: Sysvar for active stake
+authors:
+  - x19
+category: Standard
+type: Core
+status: Draft
+created: 2023-06-7
+feature: (fill in with feature tracking issues once accepted)
+---
+
+## Summary
+
+We propose to add a new sysvar that contains vote account pubkeys and 
+their corresponding active stake.
+
+## Motivation
+
+Currently, if a validator wants to prove its active stake to a program, 
+it needs to 
+pass in all of the stake accounts which have delegated to it. This is 
+infeasible due to the large number of stake accounts this would require.
+
+Using the proposed sysvar, a program can look up the corresponding 
+vote account and verify the amount of active stake it has delegated to it.
+
+This sysvar would unlock new use cases which use stake amount in their logic 
+including on-chain governance, attestations, and more.
+
+## Alternatives Considered
+
+None
+
+## New Terminology
+
+None
+
+## Detailed Design
+
+- sysvar structure: `Vec<(vote_account: Pubkey, active_stake_in_lamports: u64)>`
+- sysvar address: `SysvarStakeWeight11111111111111111111111111`
+
+Stake weight information should already be available on full node clients 
+since it's required to construct the leader schedule. Since stake weights 
+can only be
+modified on a per-epoch basis, validators will only need to update this 
+account on epoch boundaries.
+
+We would also need a new feature gate to activate this sysvar.
+
+## Impact
+
+Implementing the proposed sysvar will enable new types of programs which are 
+not possible now,
+improving Solana's ecosystem.
+
+## Security Considerations
+
+None 
+
+## Backwards Compatibility
+
+Existing programs are not impacted at all.
\ No newline at end of file

From 7a19372aa5e1957e3da32cdf4325aa01ad6e431f Mon Sep 17 00:00:00 2001
From: 0xNineteen <0x39015319@gmail.com>
Date: Wed, 7 Jun 2023 11:57:45 -0400
Subject: [PATCH 2/3] update

---
 ...svar-get-active-stake.md => 0054-sysvar-get-active-stake.md} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename proposals/{00xx-sysvar-get-active-stake.md => 0054-sysvar-get-active-stake.md} (99%)

diff --git a/proposals/00xx-sysvar-get-active-stake.md b/proposals/0054-sysvar-get-active-stake.md
similarity index 99%
rename from proposals/00xx-sysvar-get-active-stake.md
rename to proposals/0054-sysvar-get-active-stake.md
index bdadccd8..1d6ccc69 100644
--- a/proposals/00xx-sysvar-get-active-stake.md
+++ b/proposals/0054-sysvar-get-active-stake.md
@@ -1,5 +1,5 @@
 ---
-simd: '0000'
+simd: '0054'
 title: Sysvar for active stake
 authors:
   - x19

From b4a9b79659950d16b87f005168145972945c26df Mon Sep 17 00:00:00 2001
From: 0xNineteen <0x39015319@gmail.com>
Date: Wed, 7 Jun 2023 15:31:21 -0400
Subject: [PATCH 3/3] incorp comments

---
 proposals/0054-sysvar-get-active-stake.md | 25 +++++++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/proposals/0054-sysvar-get-active-stake.md b/proposals/0054-sysvar-get-active-stake.md
index 1d6ccc69..c8c7267f 100644
--- a/proposals/0054-sysvar-get-active-stake.md
+++ b/proposals/0054-sysvar-get-active-stake.md
@@ -41,6 +41,31 @@ None
 - sysvar structure: `Vec<(vote_account: Pubkey, active_stake_in_lamports: u64)>`
 - sysvar address: `SysvarStakeWeight11111111111111111111111111`
 
+
+### Ordering
+
+The sysvar structure would be sorted by `vote_account` in ascending order
+to improve look-up speeds. There will also never be any 
+duplicate `vote_account` entries.
+
+### Serialization
+
+The serialization format of the sysvar will use a u64 
+for the vector's length, followed by 40 bytes per entry 
+(32 bytes for the Pubkey and 8 for the active stake). 
+
+### Maximum Sysvar Size
+
+We also need to consider a maximum data size for the sysvar. 
+Currently, there are 3422 vote accounts on mainnet (1818 active and 1604 delinquint),
+so we can use a maximum limit of 4096 entries and still include 
+all the vote accounts for now.
+Using 4096 as the max number of entries the size would be (8 + 40 * 4096) = 
+163,848 bytes. Once the number of entries exceeds the max allowed, 
+vote accounts with the least amount of stake will be removed from the sysvar. 
+
+### Changes Required
+
 Stake weight information should already be available on full node clients 
 since it's required to construct the leader schedule. Since stake weights 
 can only be