BloXmove Dev : Claims / Credential Exchange

BloXmove generally uses a 1-step process when requesting an action, e.g. when requesting a rental.

export class RentalRequest implements IRentalRequest {

  constructor(vehicleDID: string,
              consumerDID: string,
              packageId: number,
              timestamp?: number,
              consumerSignature?: string,
              verifiablePresentation?: IVerifiablePresentation | string) {
    this.vehicleDID = vehicleDID;
    this.consumerDID = consumerDID;
    this.packageId = packageId;
    this.timestamp = timestamp;
    this.consumerSignature = consumerSignature;
    this.verifiablePresentation = verifiablePresentation;

This allow the request to be processed immediately as the requesting participant is required to provide sufficient information for the service participant to verify her authorization.

Alternative Flows for a Claims / Credential Exchange

Decentralized Identity Foundation

The DIF lists several approaches for requesting and presenting credentials:

The presentation exchange is described here: with a library in typescript: A further sample is by the DIF

The DIF further proposes a mechanism to describe the requested information from a validating participant to a wallet: Their description of the exchange protocol has not advanced beyond draft status: WACI PeX (Wallet And Credential Interactions Presentation Exchange),AreWeWaciYet%3F,-Repo.


Hyperledger Aries

Aries has developed a series of standards (current: proposed: superseded: that describe a flow where both parties can initiate the credential exchange. However, even if the requesting participant is initiating the exchange, the exact scope of information requested is defined by the validating participant:

Hyperledger Aries & BBS+ Signatures


The (draft) defines capabilities that enable third-party Web applications to handle credential requests and storage (ie. how to build Wallets for Websites).


uPort defines the Selective disclosure flow for an app requesting credentials from the uPort wallet.

Jolocom is also defining a validator-initiated request flow for credentials:

// An instance of an identityWallet is required at this point
const credentialRequest = await identityWallet.create.interactionTokens.request.share({
  callbackURL: '',
  credentialRequirements: [{
    type: ['Credential', 'ProofOfEmailCredential'],
    constraints: []
}, password)