Fork sync - #36
Open
mateumiralles wants to merge 1242 commits into
Open
Fork sync#36mateumiralles wants to merge 1242 commits into
mateumiralles wants to merge 1242 commits into
Conversation
|
⏳ Building package for commit A build has been triggered. The install link will appear here when ready. (by tropibot/build) |
… address boxes, icons
Bump csm-sdk to alpha.72, which splits WALLET_RPC into distinct codes (WALLET_TIMEOUT, RATE_LIMITED, WALLET_UNAUTHORIZED, METHOD_NOT_SUPPORTED, BATCH_NOT_ATOMIC, DUPLICATE_BUNDLE_ID, NONCE/FEE/GAS, AA validation/paymaster). Map all 11 new SDK codes into the widget taxonomy: dedicated buckets for the common, user-actionable faults; shared buckets for wallet-capability and smart-account edge cases. RATE_LIMITED now owns the genuine 'Too many requests' case, so WALLET_RPC copy no longer claims it. WALLET_TIMEOUT logs at debug.
Add a dedicated DISABLE_DEPOSIT_DATA_SIGNATURE_VALIDATION feature flag (URL param disable-deposit-signature-validation) that skips only BLS signature verification via the skipSignature option added in lido-csm-sdk alpha-73, while keeping structure, withdrawal-credentials, duplicate and keys-limit checks. The existing DISABLE_DEPOSIT_DATA_VALIDATION flag is unchanged and still skips the entire validation. Bumps @lidofinance/lido-csm-sdk 2.0.0-alpha.70 -> 2.0.0-alpha.73.
- @lidofinance/* family 0.59.0 -> 0.61.0 - reef-knot 8.1.1 -> 8.2.0
# Conflicts: # config/feature-flags/types.ts # config/feature-flags/utils.ts # features/qa-config/qa-feature-flags.tsx # package.json # providers/modify-provider.tsx # yarn.lock
chore: bump matomo/analytics and reef-knot packages
Mirror the per-module manifest pattern for favicons: track explicit favicon-csm.* and favicon-cm.* source sets, generate the canonical favicon.* files at build time in build-dynamics.mjs based on MODULE, and gitignore the generated outputs.
* feat: add flag to skip deposit data signature validation Add a dedicated DISABLE_DEPOSIT_DATA_SIGNATURE_VALIDATION feature flag (URL param disable-deposit-signature-validation) that skips only BLS signature verification via the skipSignature option added in lido-csm-sdk alpha-73, while keeping structure, withdrawal-credentials, duplicate and keys-limit checks. The existing DISABLE_DEPOSIT_DATA_VALIDATION flag is unchanged and still skips the entire validation. Bumps @lidofinance/lido-csm-sdk 2.0.0-alpha.70 -> 2.0.0-alpha.73. * fix: update help text for 'Keys limit' parameter in headerBadge.spec.ts * fix: update duplicatedKeys tests to disable deposit data signature validation --------- Co-authored-by: exromany <exromany@lido.fi>
# Conflicts: # package.json
Key limit reached message compared targetLimit with uploaded keys (totalAddedKeys - totalWithdrawnKeys) instead of deposited validators, producing false positives while depositable slots remained.
enabled did not check isActive, so stale cached filled data kept the banner visible after the window closed. In that state isDismissed (isBefore(now, end)) is always false, so the close button could never hide it. Gate enabled on isActive to align with the filled query and dismiss window.
buildDynamics() runs at next.config.mjs module-load, so it reruns at next start (as user node) and rewrites public/favicon.* and manifest.json. Only manifest.json was chowned to node; the CM favicons stayed root-owned, so next start crashed with EACCES on copyFileSync. Chown all of public/.
(cherry picked from commit 9739c75)
fix: last fixes
DKG upload and members auto-init failures render custom failed tx-stages that bypass getErrorCode, so they were never tracked. Add trackMatomoRawError at those catch sites (tags dkg_upload_page/_create/_add_keys, members_init) and a trackMatomoSurveySigninDenied event fired on DENIED_SIG during create-IDVTC / claim-IDVTC sign-in.
feat(idvtc): DKG + members/rotation on generated SDK
feat: track IDVTC survey-API failures and sign-in denials in Matomo
chore: sync develop → main
- raise KEYS_UPLOAD_TX_LIMIT from 25 to 75 - validate only the first 75 keys via SDK; keys beyond the limit get a per-row error and the form error is tooManyKeys - update @lidofinance/lido-csm-sdk to 2.0.0-alpha.75
…my-operators-page # Conflicts: # shared/hooks/use-survey-enabled.ts
- title and suggestion text use primary text color - CSM_02 cards show ETH under every keys bucket (depositable = count x 32 ETH) - suggestion notification sizing per Figma - jest SDK shim exposes MIN/MAX_EFFECTIVE_BALANCE
fix: revalidate bond/curve quotes instead of caching forever
…rs-page feat: My Operators page and cross-operator notes
…ts-of-csm-to-fork feat: move all tests to fork
…tup-all-csm-tests-for-mainnet
* feat: update CI workflows and configurations for mainnet testing * feat: add 'prod' and 'staging' options to stand_type input in tests workflow * feat: update navigation methods to use openWithRetry for keys view and submit pages
chore: update lido-csm-sdk to 2.4.0
feat: enhance My Operators functionality with bond balance summary and page updates
…-column feat(rewards-history): balance column for CM and 0x02 operators
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fork sync