Unlike REST uploadDarFile reading filesystem paths, this helper forwards darFile Buffer contents straight through InteractiveSubmissionUploadDarParams.
Receiver: await canton.ledger.interactiveSubmissionUploadDar
Setup
import { Canton } from '@fairmint/canton-node-sdk';
import fs from 'node:fs';
const canton = new Canton({
network: 'devnet',
provider: '5n',
partyId: 'OWN_PARTY_ID',
});
Minimal example
await canton.ledger.interactiveSubmissionUploadDar({
darFile: fs.readFileSync('./artifact.dar'),
});
Parameters — InteractiveSubmissionUploadDarParams
darFile(required buffer-like contents validated viaDarFileSchema)
Returns — InteractiveSubmissionUploadDarResponse
Currently {} in SDK typing—follow Canton HTTP semantics around uploads/vetting state transitions.
Errors and pitfalls
Large payloads consume bandwidth/timeouts—tune HTTP limits upstream.
Auth and party
Bearer credential parity with interactive submission surfaces.