Skip to content

[kotlin-sdk] Expose an identity credit top-up surface in IdentityRegistration #4077

Closed

Description

@bfoss765

Priority: P1 — blocks migrating the identity registration/top-up/recovery state machine off the legacy BlockchainIdentity (app workaround: top-ups stay on the legacy stack, which keeps the legacy library pinned).

Kotlin identity/IdentityRegistration exposes registerWithWalletFunding, registerFromAddresses, discoverIdentities, registerDpnsName — but no explicit credit top-up entry point equivalent to the legacy BlockchainIdentity top-up path (asset-lock funded).

Ask: expose a top-up surface (or document the intended asset-lock-bridge recipe for top-ups) so the wallet can route registration AND top-up through the SDK behind one flag.

Context: dash-wallet migration plan Phase 3h step 1 (dashpay/dash-wallet#1507). cc @QuantumExplorer

Activity

  1. HashEngineering commented on Nov 9, 2026

    @HashEngineering
    Collaborator

    Fixed by #3999. IdentityCredits.topUpFromCore(...) builds an asset lock and tops up the identity, and resumeTopUpWithExistingAssetLock covers resume. It lives in IdentityCredits rather than IdentityRegistration. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions