feat: pectra compatibility #1053

ypatil12 · 2025-01-28T17:14:45Z

Updates checkpoint proof system to be Pectra compatible. The breaking change to EigenPods is the BeaconState container increasing to have 37 fields, which results in the tree height to be > 5.

Overview

We need to solve for the following cases:

Prevent deneb proofs from being submitted to pectra blocks
Ensure that the PECTRA_FORK_TIMESTAMP is the first timestamp at or after the pectra hard fork for which there is a non missed slot

To do this, here is the upgrade process:

Pause checkpoint starting & credential proofs
Upgrade after fork is hit
Run script to detect the first timestamp at or after the pectra hard fork for which there is a non missed slot
Set pectra fork timestamp to the first timestamp at which there is a pectra block header
Unpause

EigenPod

Updated balance container and validator container proofs to pass in a proof timestamp & pectra fork timestamp to check against which tree height to use for the beacon state
Modify storing variables in memory to handle stack too deep errors
Note that since the 4788 oracle returns the PARENT beacon block root, our check against the pectra fork timestamp returns the previous tree length for proofs that are <= pectraForkTimestamp

Deprecation Plan

Post pectra, we can upgrade the EigenPod to deprecate the fork timestamp case handling once all in progress pre-Pectra checkpoints have been completed

TODOs

Unit Tests
Integration Tests simulating upgrade
Mekong Deployment
Update Integration Test User to use validators >32 ETH

eigenmikem

AFAIK the fork timestamp has never been altered once broadcast, at least not in the last few years, so I think hardcoding it is fine

wadealexc · 2025-02-05T15:57:42Z

src/contracts/pods/EigenPod.sol

@@ -254,6 +255,7 @@ contract EigenPod is Initializable, ReentrancyGuardUpgradeable, EigenPodPausingC
        for (uint256 i = 0; i < validatorIndices.length; i++) {
            // forgefmt: disable-next-item
            totalAmountToBeRestakedWei += _verifyWithdrawalCredentials(
+                beaconTimestamp,


Hmm, I wonder about the usage of getParentBlockRoot above.

Can beaconTimestamp belong to the block after the fork, but the proof itself is over the parent block (aka pre-fork)?

For the record I think I'm correct here. 2 scenarios:

I try to verify withdrawal credentials the block after the hard fork. getParentBlockRoot grabs a block from before the hard fork; that's what my proof needs to be against.

I start a checkpoint just after the hard fork. The checkpoint block root used for proofs is from a block just before the hard fork.

Naive solution: have the fork selector logic in the proofs library check proofTimestamp - 12. However, this runs into potential issues with skipped slots -- I might have a proof timestamp 2 blocks after the hard fork, but there was a skipped slot right at the fork, so the proof block is from before the fork.

I think, unfortunately, we need to pause proofs just before the fork, and unpause just after the fork (once we see the first valid block). Although I'm not sure this entirely fixes the issue... will think more.

Maybe we need to pause + upgrade just after the fork + unpause? ugh.

Synced offline, here is what we need to do:

Prevent deneb proofs from being submitted to pectra blocks

Ensure that the PECTRA_FORK_TIMESTAMP is the first timestamp at or after the pectra hard fork for which there is a non-missed slot. Checkpoint proofs store the proof timestamp. If there are missed slots at the hard fork timestamp, it's possible, like Alex mentions above, that the beaconTimestamp is post pectra but the block header is deneb.

To do this, here is the process:

Pause checkpoint starting & credential proofs

Upgrade after fork is hit

Set pectra fork timestamp to the first timestamp at which there is a pectra block header

Unpause

Using the image above, we want to determine what proof type to use, given the proof timestamp tp. Because tp is used to look up a parent block in the EIP-4788 oracle, its proof type corresponds to the last non-skipped block. So, if:

tp > t1, use pectra logic

tp <= t1, use dencun logic

Given our beacon state tree height getter: https://github.com/layr-labs/eigenlayer-contracts/blob/b4852c74cdbe43fea2f7330ea0dc752fcf10b6e9/src/contracts/libraries/BeaconChainProofs.sol#L327-L334

... pectraForkTimestamp should be set to the first valid, non-skipped block after the Pectra hard fork.

wadealexc

Is this PR targeting testnet?

We're going to need a different PR for mainnet, since that's landing before slashing, right? (This EigenPod file is compatible with testnet slashing, but not mainnet)

ypatil12 · 2025-02-05T17:35:13Z

Is this PR targeting testnet?

Yup, targeting testnet. There will be a separate mainnet PR. cc @wadealexc

src/contracts/libraries/BeaconChainProofs.sol

Updated Impl

src/contracts/interfaces/IEigenPod.sol

src/contracts/interfaces/IEigenPodManager.sol

ypatil12 · 2025-02-24T07:01:51Z

Deneb tests against pectra: a8dd876

8sunyuan

LGTM

**Motivation:** Upgrade script for Prooftra. Based on #1053, has to follow the following process: 1. Pause checkpoint starting & credential proofs 2. Upgrade after fork is hit 3. Run script to detect the first timestamp at or after the pectra hard fork for which there is a non missed slot 4. Set pectra fork timestamp to the first timestamp at which there is a pectra block header 5. Unpause **Modifications:** `v1.2.0` upgrade script. Key part is the offchain script **Result:** Prooftra upgrade.

Updates checkpoint proof system to be Pectra compatible. The breaking change to EigenPods is the `BeaconState` container increasing to have 37 fields, which results in the tree height to be > 5. We need to solve for the following cases: - Prevent deneb proofs from being submitted to pectra blocks - Ensure that the PECTRA_FORK_TIMESTAMP is the first timestamp at or after the pectra hard fork for which there is a non missed slot To do this, here is the upgrade process: 1. Pause checkpoint starting & credential proofs 2. Upgrade after fork is hit 3. Run script to detect the first timestamp at or after the pectra hard fork for which there is a non missed slot 4. Set pectra fork timestamp to the first timestamp at which there is a pectra block header 5. Unpause - Updated balance container and validator container proofs to pass in a proof timestamp & pectra fork timestamp to check against which tree height to use for the beacon state - Modify storing variables in memory to handle stack too deep errors - Note that since the 4788 oracle returns the PARENT beacon block root, our check against the pectra fork timestamp returns the previous tree length for proofs that are <= `pectraForkTimestamp` - Post pectra, we can upgrade the EigenPod to deprecate the fork timestamp case handling once all in progress pre-Pectra checkpoints have been completed - [x] Unit Tests - [x] Integration Tests simulating upgrade - [x] Mekong Deployment - [x] Update Integration Test User to use validators >32 ETH

**Motivation:** Upgrade script for Prooftra. Based on #1053, has to follow the following process: 1. Pause checkpoint starting & credential proofs 2. Upgrade after fork is hit 3. Run script to detect the first timestamp at or after the pectra hard fork for which there is a non missed slot 4. Set pectra fork timestamp to the first timestamp at which there is a pectra block header 5. Unpause **Modifications:** `v1.2.0` upgrade script. Key part is the offchain script **Result:** Prooftra upgrade.

Updates checkpoint proof system to be Pectra compatible. The breaking change to EigenPods is the `BeaconState` container increasing to have 37 fields, which results in the tree height to be > 5. ### Overview We need to solve for the following cases: - Prevent deneb proofs from being submitted to pectra blocks - Ensure that the PECTRA_FORK_TIMESTAMP is the first timestamp at or after the pectra hard fork for which there is a non missed slot To do this, here is the upgrade process: 1. Pause checkpoint starting & credential proofs 2. Upgrade after fork is hit 3. Run script to detect the first timestamp at or after the pectra hard fork for which there is a non missed slot 4. Set pectra fork timestamp to the first timestamp at which there is a pectra block header 5. Unpause ### EigenPod - Updated balance container and validator container proofs to pass in a proof timestamp & pectra fork timestamp to check against which tree height to use for the beacon state - Modify storing variables in memory to handle stack too deep errors - Note that since the 4788 oracle returns the PARENT beacon block root, our check against the pectra fork timestamp returns the previous tree length for proofs that are <= `pectraForkTimestamp` ### Deprecation Plan - Post pectra, we can upgrade the EigenPod to deprecate the fork timestamp case handling once all in progress pre-Pectra checkpoints have been completed ### TODOs - [x] Unit Tests - [x] Integration Tests simulating upgrade - [x] Mekong Deployment - [x] Update Integration Test User to use validators >32 ETH

**Motivation:** Upgrade script for Prooftra. Based on #1053, has to follow the following process: 1. Pause checkpoint starting & credential proofs 2. Upgrade after fork is hit 3. Run script to detect the first timestamp at or after the pectra hard fork for which there is a non missed slot 4. Set pectra fork timestamp to the first timestamp at which there is a pectra block header 5. Unpause **Modifications:** `v1.2.0` upgrade script. Key part is the offchain script **Result:** Prooftra upgrade.

Updates checkpoint proof system to be Pectra compatible. The breaking change to EigenPods is the `BeaconState` container increasing to have 37 fields, which results in the tree height to be > 5. ### Overview We need to solve for the following cases: - Prevent deneb proofs from being submitted to pectra blocks - Ensure that the PECTRA_FORK_TIMESTAMP is the first timestamp at or after the pectra hard fork for which there is a non missed slot To do this, here is the upgrade process: 1. Pause checkpoint starting & credential proofs 2. Upgrade after fork is hit 3. Run script to detect the first timestamp at or after the pectra hard fork for which there is a non missed slot 4. Set pectra fork timestamp to the first timestamp at which there is a pectra block header 5. Unpause ### EigenPod - Updated balance container and validator container proofs to pass in a proof timestamp & pectra fork timestamp to check against which tree height to use for the beacon state - Modify storing variables in memory to handle stack too deep errors - Note that since the 4788 oracle returns the PARENT beacon block root, our check against the pectra fork timestamp returns the previous tree length for proofs that are <= `pectraForkTimestamp` ### Deprecation Plan - Post pectra, we can upgrade the EigenPod to deprecate the fork timestamp case handling once all in progress pre-Pectra checkpoints have been completed ### TODOs - [x] Unit Tests - [x] Integration Tests simulating upgrade - [x] Mekong Deployment - [x] Update Integration Test User to use validators >32 ETH

**Motivation:** Upgrade script for Prooftra. Based on #1053, has to follow the following process: 1. Pause checkpoint starting & credential proofs 2. Upgrade after fork is hit 3. Run script to detect the first timestamp at or after the pectra hard fork for which there is a non missed slot 4. Set pectra fork timestamp to the first timestamp at which there is a pectra block header 5. Unpause **Modifications:** `v1.2.0` upgrade script. Key part is the offchain script **Result:** Prooftra upgrade.

Updates checkpoint proof system to be Pectra compatible. The breaking change to EigenPods is the `BeaconState` container increasing to have 37 fields, which results in the tree height to be > 5. ### Overview We need to solve for the following cases: - Prevent deneb proofs from being submitted to pectra blocks - Ensure that the PECTRA_FORK_TIMESTAMP is the first timestamp at or after the pectra hard fork for which there is a non missed slot To do this, here is the upgrade process: 1. Pause checkpoint starting & credential proofs 2. Upgrade after fork is hit 3. Run script to detect the first timestamp at or after the pectra hard fork for which there is a non missed slot 4. Set pectra fork timestamp to the first timestamp at which there is a pectra block header 5. Unpause ### EigenPod - Updated balance container and validator container proofs to pass in a proof timestamp & pectra fork timestamp to check against which tree height to use for the beacon state - Modify storing variables in memory to handle stack too deep errors - Note that since the 4788 oracle returns the PARENT beacon block root, our check against the pectra fork timestamp returns the previous tree length for proofs that are <= `pectraForkTimestamp` ### Deprecation Plan - Post pectra, we can upgrade the EigenPod to deprecate the fork timestamp case handling once all in progress pre-Pectra checkpoints have been completed ### TODOs - [x] Unit Tests - [x] Integration Tests simulating upgrade - [x] Mekong Deployment - [x] Update Integration Test User to use validators >32 ETH

**Motivation:** Upgrade script for Prooftra. Based on #1053, has to follow the following process: 1. Pause checkpoint starting & credential proofs 2. Upgrade after fork is hit 3. Run script to detect the first timestamp at or after the pectra hard fork for which there is a non missed slot 4. Set pectra fork timestamp to the first timestamp at which there is a pectra block header 5. Unpause **Modifications:** `v1.2.0` upgrade script. Key part is the offchain script **Result:** Prooftra upgrade. feat: write phase 6 script timestamp to file

Updates checkpoint proof system to be Pectra compatible. The breaking change to EigenPods is the `BeaconState` container increasing to have 37 fields, which results in the tree height to be > 5. We need to solve for the following cases: - Prevent deneb proofs from being submitted to pectra blocks - Ensure that the PECTRA_FORK_TIMESTAMP is the first timestamp at or after the pectra hard fork for which there is a non missed slot To do this, here is the upgrade process: 1. Pause checkpoint starting & credential proofs 2. Upgrade after fork is hit 3. Run script to detect the first timestamp at or after the pectra hard fork for which there is a non missed slot 4. Set pectra fork timestamp to the first timestamp at which there is a pectra block header 5. Unpause - Updated balance container and validator container proofs to pass in a proof timestamp & pectra fork timestamp to check against which tree height to use for the beacon state - Modify storing variables in memory to handle stack too deep errors - Note that since the 4788 oracle returns the PARENT beacon block root, our check against the pectra fork timestamp returns the previous tree length for proofs that are <= `pectraForkTimestamp` - Post pectra, we can upgrade the EigenPod to deprecate the fork timestamp case handling once all in progress pre-Pectra checkpoints have been completed - [x] Unit Tests - [x] Integration Tests simulating upgrade - [x] Mekong Deployment - [x] Update Integration Test User to use validators >32 ETH

**Motivation:** Upgrade script for Prooftra. Based on #1053, has to follow the following process: 1. Pause checkpoint starting & credential proofs 2. Upgrade after fork is hit 3. Run script to detect the first timestamp at or after the pectra hard fork for which there is a non missed slot 4. Set pectra fork timestamp to the first timestamp at which there is a pectra block header 5. Unpause **Modifications:** `v1.2.0` upgrade script. Key part is the offchain script **Result:** Prooftra upgrade. feat: write phase 6 script timestamp to file

Updates checkpoint proof system to be Pectra compatible. The breaking change to EigenPods is the `BeaconState` container increasing to have 37 fields, which results in the tree height to be > 5. We need to solve for the following cases: - Prevent deneb proofs from being submitted to pectra blocks - Ensure that the PECTRA_FORK_TIMESTAMP is the first timestamp at or after the pectra hard fork for which there is a non missed slot To do this, here is the upgrade process: 1. Pause checkpoint starting & credential proofs 2. Upgrade after fork is hit 3. Run script to detect the first timestamp at or after the pectra hard fork for which there is a non missed slot 4. Set pectra fork timestamp to the first timestamp at which there is a pectra block header 5. Unpause - Updated balance container and validator container proofs to pass in a proof timestamp & pectra fork timestamp to check against which tree height to use for the beacon state - Modify storing variables in memory to handle stack too deep errors - Note that since the 4788 oracle returns the PARENT beacon block root, our check against the pectra fork timestamp returns the previous tree length for proofs that are <= `pectraForkTimestamp` - Post pectra, we can upgrade the EigenPod to deprecate the fork timestamp case handling once all in progress pre-Pectra checkpoints have been completed - [x] Unit Tests - [x] Integration Tests simulating upgrade - [x] Mekong Deployment - [x] Update Integration Test User to use validators >32 ETH

**Motivation:** Upgrade script for Prooftra. Based on #1053, has to follow the following process: 1. Pause checkpoint starting & credential proofs 2. Upgrade after fork is hit 3. Run script to detect the first timestamp at or after the pectra hard fork for which there is a non missed slot 4. Set pectra fork timestamp to the first timestamp at which there is a pectra block header 5. Unpause **Modifications:** `v1.2.0` upgrade script. Key part is the offchain script **Result:** Prooftra upgrade. feat: write phase 6 script timestamp to file

Updates checkpoint proof system to be Pectra compatible. The breaking change to EigenPods is the `BeaconState` container increasing to have 37 fields, which results in the tree height to be > 5. We need to solve for the following cases: - Prevent deneb proofs from being submitted to pectra blocks - Ensure that the PECTRA_FORK_TIMESTAMP is the first timestamp at or after the pectra hard fork for which there is a non missed slot To do this, here is the upgrade process: 1. Pause checkpoint starting & credential proofs 2. Upgrade after fork is hit 3. Run script to detect the first timestamp at or after the pectra hard fork for which there is a non missed slot 4. Set pectra fork timestamp to the first timestamp at which there is a pectra block header 5. Unpause - Updated balance container and validator container proofs to pass in a proof timestamp & pectra fork timestamp to check against which tree height to use for the beacon state - Modify storing variables in memory to handle stack too deep errors - Note that since the 4788 oracle returns the PARENT beacon block root, our check against the pectra fork timestamp returns the previous tree length for proofs that are <= `pectraForkTimestamp` - Post pectra, we can upgrade the EigenPod to deprecate the fork timestamp case handling once all in progress pre-Pectra checkpoints have been completed - [x] Unit Tests - [x] Integration Tests simulating upgrade - [x] Mekong Deployment - [x] Update Integration Test User to use validators >32 ETH

**Motivation:** Upgrade script for Prooftra. Based on #1053, has to follow the following process: 1. Pause checkpoint starting & credential proofs 2. Upgrade after fork is hit 3. Run script to detect the first timestamp at or after the pectra hard fork for which there is a non missed slot 4. Set pectra fork timestamp to the first timestamp at which there is a pectra block header 5. Unpause **Modifications:** `v1.2.0` upgrade script. Key part is the offchain script **Result:** Prooftra upgrade. feat: write phase 6 script timestamp to file

**Motivation:** Updates the EigenPod proof system to be pectra compatible. This includes updating container heights and support 0x02 withdrawal credentials. All other Pectra updates will be addressed in a post-slashing upgrade. **Modifications:** - Functionality: #1053 - Upgrade Script: #1067 **Result:** `v1.4.0`. _Note: The commits for the the `v1.4.0` deployment are cherry-picked onto `v1.1.1` for testnet due to audit fixes not being deployed yet. See: #1156 for the diff`

Updates checkpoint proof system to be Pectra compatible. The breaking change to EigenPods is the `BeaconState` container increasing to have 37 fields, which results in the tree height to be > 5. We need to solve for the following cases: - Prevent deneb proofs from being submitted to pectra blocks - Ensure that the PECTRA_FORK_TIMESTAMP is the first timestamp at or after the pectra hard fork for which there is a non missed slot To do this, here is the upgrade process: 1. Pause checkpoint starting & credential proofs 2. Upgrade after fork is hit 3. Run script to detect the first timestamp at or after the pectra hard fork for which there is a non missed slot 4. Set pectra fork timestamp to the first timestamp at which there is a pectra block header 5. Unpause - Updated balance container and validator container proofs to pass in a proof timestamp & pectra fork timestamp to check against which tree height to use for the beacon state - Modify storing variables in memory to handle stack too deep errors - Note that since the 4788 oracle returns the PARENT beacon block root, our check against the pectra fork timestamp returns the previous tree length for proofs that are <= `pectraForkTimestamp` - Post pectra, we can upgrade the EigenPod to deprecate the fork timestamp case handling once all in progress pre-Pectra checkpoints have been completed - [x] Unit Tests - [x] Integration Tests simulating upgrade - [x] Mekong Deployment - [x] Update Integration Test User to use validators >32 ETH

**Motivation:** Upgrade script for Prooftra. Based on #1053, has to follow the following process: 1. Pause checkpoint starting & credential proofs 2. Upgrade after fork is hit 3. Run script to detect the first timestamp at or after the pectra hard fork for which there is a non missed slot 4. Set pectra fork timestamp to the first timestamp at which there is a pectra block header 5. Unpause **Modifications:** `v1.2.0` upgrade script. Key part is the offchain script **Result:** Prooftra upgrade. feat: write phase 6 script timestamp to file

ypatil12 mentioned this pull request Jan 28, 2025

feat: pectra compatability #893

Closed

3 tasks

ypatil12 force-pushed the slashing-magnitudes branch from 7a6f8a6 to fbe5ee2 Compare January 28, 2025 18:23

ypatil12 changed the base branch from slashing-magnitudes to dev January 28, 2025 21:48

ypatil12 force-pushed the yash/pectra-compatibility branch 4 times, most recently from 8b3076f to 8679ebb Compare January 28, 2025 21:55

ypatil12 changed the base branch from dev to feat/prooftra January 29, 2025 22:11

ypatil12 changed the base branch from feat/prooftra to dev January 29, 2025 22:31

ypatil12 force-pushed the yash/pectra-compatibility branch from 8679ebb to 392022e Compare January 30, 2025 01:14

ypatil12 changed the base branch from dev to feat/prooftra January 30, 2025 01:15

ypatil12 force-pushed the yash/pectra-compatibility branch 4 times, most recently from d71e908 to 2e9ab01 Compare January 30, 2025 02:12

ypatil12 marked this pull request as ready for review January 30, 2025 20:34

ypatil12 requested review from 8sunyuan, wadealexc and eigenmikem January 30, 2025 20:36

eigenmikem previously approved these changes Feb 4, 2025

View reviewed changes

ypatil12 force-pushed the feat/prooftra branch from 8beb418 to d63fded Compare February 4, 2025 22:42

ypatil12 force-pushed the yash/pectra-compatibility branch from d849720 to f5dbfb8 Compare February 4, 2025 23:16

wadealexc reviewed Feb 5, 2025

View reviewed changes

wadealexc reviewed Feb 6, 2025

View reviewed changes

src/contracts/libraries/BeaconChainProofs.sol Outdated Show resolved Hide resolved

ypatil12 mentioned this pull request Feb 7, 2025

feat: prooftra upgrade script #1067

Merged

wadealexc reviewed Feb 7, 2025

View reviewed changes

src/contracts/interfaces/IEigenPod.sol Outdated Show resolved Hide resolved

wadealexc reviewed Feb 7, 2025

View reviewed changes

src/contracts/interfaces/IEigenPodManager.sol Show resolved Hide resolved

test: add tests for proving deneb against pectra

a8dd876

ypatil12 added 3 commits February 23, 2025 23:08

chore: cleanup using deneb on all non-prooftra upgrade tests

36093f7

fix: storage gap

f0c68e1

fix: set fork timestamp for fork tests

494cb19

ypatil12 mentioned this pull request Feb 24, 2025

feat: pectra compatibility #1155

Merged

8sunyuan approved these changes Feb 24, 2025

View reviewed changes

ypatil12 merged commit b215ea7 into feat/prooftra Feb 24, 2025
10 checks passed

ypatil12 deleted the yash/pectra-compatibility branch February 24, 2025 16:46

ypatil12 mentioned this pull request Feb 24, 2025

[DO NOT MERGE]: v1.2.0 on v1.1.1 #1156

Draft

0xClandestine added the ✨ Enhancement New feature or request. label Feb 26, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat: pectra compatibility #1053

feat: pectra compatibility #1053

Uh oh!

ypatil12 commented Jan 28, 2025 •

edited

Loading

Uh oh!

eigenmikem left a comment

Uh oh!

wadealexc Feb 5, 2025

Uh oh!

wadealexc Feb 6, 2025

Uh oh!

wadealexc Feb 6, 2025

Uh oh!

ypatil12 Feb 6, 2025 •

edited

Loading

Uh oh!

wadealexc Feb 7, 2025

Uh oh!

wadealexc Feb 7, 2025

Uh oh!

wadealexc left a comment

Uh oh!

ypatil12 commented Feb 5, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

ypatil12 commented Feb 24, 2025

Uh oh!

8sunyuan left a comment

Uh oh!

Uh oh!

Uh oh!

feat: pectra compatibility #1053

feat: pectra compatibility #1053

Uh oh!

Conversation

ypatil12 commented Jan 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Overview

EigenPod

Deprecation Plan

TODOs

Uh oh!

eigenmikem left a comment

Choose a reason for hiding this comment

Uh oh!

wadealexc Feb 5, 2025

Choose a reason for hiding this comment

Uh oh!

wadealexc Feb 6, 2025

Choose a reason for hiding this comment

Uh oh!

wadealexc Feb 6, 2025

Choose a reason for hiding this comment

Uh oh!

ypatil12 Feb 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

wadealexc Feb 7, 2025

Choose a reason for hiding this comment

Uh oh!

wadealexc Feb 7, 2025

Choose a reason for hiding this comment

Uh oh!

wadealexc left a comment

Choose a reason for hiding this comment

Uh oh!

ypatil12 commented Feb 5, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

ypatil12 commented Feb 24, 2025

Uh oh!

8sunyuan left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

ypatil12 commented Jan 28, 2025 •

edited

Loading

ypatil12 Feb 6, 2025 •

edited

Loading