Skip to content

[Feature] Slashing Upgrade#366

Draft
uditdc wants to merge 110 commits intodevfrom
feature/slashing-upgrade
Draft

[Feature] Slashing Upgrade#366
uditdc wants to merge 110 commits intodevfrom
feature/slashing-upgrade

Conversation

@uditdc
Copy link
Copy Markdown
Member

@uditdc uditdc commented Mar 13, 2025

No description provided.

surbhit14 and others added 30 commits January 15, 2025 21:14
…nts-and-metric

Slashing Upgrade for Withdrawal Endpoints
@uditdc uditdc changed the title Feature/slashing upgrade [Feature] Slashing Upgrade May 6, 2025
uditdc added 9 commits May 15, 2025 13:06
# Conflicts:
#       packages/api/src/routes/avs/avsController.ts
#       packages/api/src/routes/avs/avsRoutes.ts
#       packages/seeder/src/events/seedLogsAVSMetadata.ts
#       packages/seeder/src/index.ts
#       packages/seeder/src/metrics/seedMetricsWithdrawal.ts
…ator-id-check

Avs allocation operator id check fix
…cy-slashing-branch

Modify seeding frequency slashing branch
…cy-slashing-branch

Consolidate eigen full data and logs
# Conflicts:
#       packages/api/src/routes/avs/avsController.ts
#       packages/api/src/routes/avs/avsRoutes.ts
#       packages/api/src/routes/operators/operatorController.ts
#       packages/prisma/schema.prisma
#       packages/seeder/src/data/address/eigenHoleskyContracts.ts
#       packages/seeder/src/data/address/eigenMainnetContracts.ts
#       packages/seeder/src/data/address/index.ts
#       packages/seeder/src/index.ts
Replace forEach with proper for loop to handle async operations sequentially
in withdrawal strategy processing. This prevents potential data inconsistencies
during withdrawal metrics calculation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants