Skip to content

Reference

PaymentStreams.partyMigrationProposal

Approve a party migration proposal, migrate active or proposed payment streams onto new parties, or archive the migration proposal.

Party migration is a dedicated DAML workflow (PartyMigrationProposal) for moving payment-stream roles between parties. Builders cover approval and migration exercises against active or proposed stream contracts plus archival of the proposal when done.

Receiver

ocp.PaymentStreams.partyMigrationProposal

buildApproveCommand

  • migrationProposalContractId (required)
  • actor (required)

Returns: CommandPartyMigrationProposal_Approve.

buildMigrateActivePaymentStreamCommand

  • migrationProposalContractId (required)
  • actor (required)
  • activePaymentStreamCid (required)

Returns: CommandPartyMigrationProposal_MigrateActivePaymentStream.

buildMigrateProposedPaymentStreamCommand

  • migrationProposalContractId (required)
  • actor (required)
  • proposedPaymentStreamCid (required)

Returns: CommandPartyMigrationProposal_MigrateProposedPaymentStream.

buildArchiveCommand

  • migrationProposalContractId (required)
  • actor (required)
  • description (optional) — passed through when set (see SDK implementation)

Returns: CommandPartyMigrationProposal_Archive.

Errors

Builders do not throw Ocp*. Preconditions (every party signed, contracts in the right state) are enforced on the ledger.

See also

Source