feat: 🎸 Drop v7 support - #1621
Draft
prashantasdeveloper wants to merge 2 commits into
Draft
Conversation
prashantasdeveloper
force-pushed
the
feat/drop-v7-support
branch
from
July 24, 2026 12:26
63047ce to
498a5e1
Compare
|
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
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.




Description
Drops all v7 chain support/backward-compatibility code, now that the SDK only targets v8. Removes
Context.isV7, all v7/v8 branching, and every feature that only existed for v7 chains.Removed entities/features (v7-only, no v8 equivalent):
ChildIdentityentity and all child-identity APIs:Identity.getChildIdentities,Identity.unlinkChild,Identity.isChild,createChildIdentity/createChildIdentities/unlinkChildIdentityprocedures,Context.getChildIdentity.Claims.getCddClaims,Identity.hasValidCdd,CddClaimhandling,RoleType.CddProvider/isCddProviderRole(superseded byDidRegistrarrole, which is now used unconditionally instead of the v7cddServiceProviderspallet).consumeAddRelayerPayingKeyAuthorizationprocedure andAuthorizationType.AddRelayerPayingKey(theOldAddRelayerPayingKeytype/flow remains; accepting the removed type now throwsNotSupportedpointing users atAccountManagement.approveSubsidy).InstructionAffirmationOperation.Withdraw/WithdrawAsMediatorandInstruction.withdraw/withdrawAsMediator(usereject/rejectAsMediatorinstead).Nft.controllerTransfer's deprecateddestinationPortfolioparam (usedestination).AcceptPrimaryKeyRotationParams.cddAuthand the associated CDD-authorization validation/consumption inacceptPrimaryKeyRotation.SetStakingControllerParams—Staking.setControlleris now a no-arg procedure since v8 always makes the stash its own controller; likewisebondPolyxno longer accepts/sends acontrollerargument.Simplified now-unconditional behavior (previously branched on
context.isV7):Context.getAccountBalanceonly uses the v8FrameSystemAccountInfoshape (AccountInfo/legacy assembly removed).transferPolyxalways usesbalances.transferWithMemowith an optional memo (v7's memo-lessbalances.transferpath removed).Instruction.generateOffChainAffirmationTransactionRaw:expiresAtis now always mandatory, and the payload always includes the v8 receipt format.Identity.checkRoleForDid/isGcMemberalways querydidRegistrars.activeMembers(the v7cddServiceProviders.activeMembersfallback is gone).SUPPORTED_SPEC_VERSION_RANGEnarrowed from'7.0 || 7.1 || 7.2 || 7.3 || 8.0'to'8.0'.isV7Specutil removed along withContext.isV7.Docs/typos:
CreateMultiSigParamsnote updated from "Signer must be an Account as of v7" to "Signer must be an Account".Breaking Changes
JIRA Link
Checklist