Skip to content

Identity still linked to the source account after a changeOwnerKey operation if validator

Tested on docker image duniter-v2s-gdev-800 Duniter version 0.10.1-unknown

Bob is a smith (authority/validator), which seems the cause of the problem.

After a changeOwnerKey operation from Bob to account 5DnWJYCLXYWTXqMhXhJ8oi2oQQikHnSBUQBq5NmyD46VZAHG, the identity 2 is still linked to the source account !

The identity 2 has the target account as owner and Bob as previous owner:

{
  data: {
    firstEligibleUd: 1
  }
  nextCreatableIdentityOn: 0
  oldOwnerKey: [
    5FHneW46xGXgs5mUiveU4sbTyGBzmstUspZC92UhjJM694ty
    5
  ]
  ownerKey: 5DnWJYCLXYWTXqMhXhJ8oi2oQQikHnSBUQBq5NmyD46VZAHG
  nextScheduled: 0
  status: Member
}

The target account has been linked to the identity correctly:

5DnWJYCLXYWTXqMhXhJ8oi2oQQikHnSBUQBq5NmyD46VZAHG : 
{
  nonce: 0
  consumers: 0
  providers: 2
  sufficients: 1
  data: {
    free: 900
    reserved: 0
    feeFrozen: 0
    linkedIdty: 2
  }
}

But Bob is still linked to the identity 2:

{
  nonce: 2
  consumers: 1
  providers: 1
  sufficients: 1
  data: {
    free: 100
    reserved: 0
    feeFrozen: 0
    linkedIdty: 2
  }
}
Edited by Vincent Texier
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information