dlog v1 finalization: an extra signer in the metadata should be an AuditableIdentity

[adecaro]

In token/driver/request.go, both IssueMetadata and TransferMetadata structs contain the field ExtraSigners []Identity.
Identity should be replaced by AuditableIdentity itself defined in the same token/driver/request.go file.
This allows any third party with access to the metadata to audit also this identity when needed.

[SurbhiAgarwal1]

Hi @adecaro, I've been looking into the DLog v1 finalization logic and noticed a potential improvement for the ExtraSigners field in IssueMetadata and TransferMetadata. Could you please assign this issue to me?

Right now, ExtraSigners (secondary approvers in a transaction) are being recorded as basic, non-auditable Identity types. This creates a gap in the auditability chain—since standard identities can't be selectively unmasked, authorized auditors have no way to verify who these extra signers are in a private transaction.

I propose a targeted refactor in token/driver/request.go to replace ExtraSigners []Identity with ExtraSigners []AuditableIdentity.

This is a clean, surgical type-swap that ensures these secondary signers provide the necessary cryptographic metadata for selective auditing, without compromising their privacy to the general network. It would bring the ExtraSigners handling in line with the already auditable Issuer and Owner patterns we use elsewhere in the SDK.

I'd be happy to start working on a PR for this if you agree with this approach!

[adecaro]

Hi @SurbhiAgarwal1 , still willing to work on this? Thanks for offering and sorry for the late reply 🙏

[SurbhiAgarwal1]

Hi @adecaro, thanks for following up!
Yes, I’d still love to work on this. I’ll start by reviewing the current implementation around ExtraSigners and draft a PR with the proposed change to AuditableIdentity.
I’ll share an initial draft PR soon for feedback.

[adecaro]

Hi @SurbhiAgarwal1 , then go ahead. Thanks much 🙏