Wallet Type Delegation Information Not Returned by SDK Methods

[anthony-urbina]

Issue:

Delegation Information Not Returned by SDK Methods

Description:

We’re experiencing an issue where delegation information is visible on the Delegate.xyz registry but is not being returned by the SDK methods in Check Delgations or Fetch Delegations. We’re using SDK version 0.5.2.

Details:

• Issuer Wallet: 0x549022aD5Cd11816Eb7cE6EA15Ae61C1Fb4Edb8A
• Delegate Wallet: 0x59304fB8d5973587d07763D1543d29C624Bab11F
• SDK Version: 0.5.2
• Methods Used: getOutgoingDelegations, getIncomingDelegations, checkDelegateForAll, checkDelegateForContract
• Registry URL: Delegate.xyz Registry

Steps to Reproduce:

• Use the checkDelegateForAll method with the issuer wallet 0x549022aD5Cd11816Eb7cE6EA15Ae61C1Fb4Edb8A and delegate wallet 0x59304fB8d5973587d07763D1543d29C624Bab11F.

• Observe that no delegation information is returned.

• Compare with the data visible on the registry.

• Use the checkDelegateForContract method with the from wallet 0x549022aD5Cd11816Eb7cE6EA15Ae61C1Fb4Edb8A, to wallet 0x59304fB8d5973587d07763D1543d29C624Bab11F, and contract address 0xb7abcc333209f3e8af129ab99ee2a470a2ac5bae.

• Observe that false is returned.

• Compare with the data visible on the registry.

• Use the getIncomingDelegations method with the to wallet 0x59304fB8d5973587d07763D1543d29C624Bab11F.

• Observe that [ ] is returned.

• Compare with the data visible on the registry.

• Use the getOutgoingDelegations method with the from wallet 0x549022aD5Cd11816Eb7cE6EA15Ae61C1Fb4Edb8A.

• Observe that [ ] is returned.

• Compare with the data visible on the registry.

Expected Result:

The delegation information between the issuer and delegate wallets, that is visible on the registry, should be returned by the SDK methods.

Actual Result:

• No delegation information is returned by the SDK methods (either empty array or false is returned)

Additional Information:

• Double-checked parameters and confirmed that they are correct.
• Tried updating to the latest SDK version, but the issue persists.

P.S. Thanks team, let me know if there are any additional questions