There is no networkFee option specified in TransactionArguments for the createTransaction even though it is stated in documentation.
export interface TransactionArguments {
assetId?: string;
source?: TransferPeerPath;
destination?: DestinationTransferPeerPath;
amount?: number | string;
operation?: TransactionOperation;
fee?: number | string;
feeLevel?: FeeLevel;
failOnLowFee?: boolean;
maxFee?: string;
priorityFee?: number | string;
gasPrice?: number | string;
gasLimit?: number | string;
note?: string;
cpuStaking?: number;
networkStaking?: number;
autoStaking?: boolean;
customerRefId?: string;
extraParameters?: object;
destinations?: TransactionDestination;
replaceTxByHash?: string;
externalTxId?: string;
treatAsGrossAmount?: boolean;
forceSweep?: boolean;
feePayerInfo?: TransactionArgumentsFeePayerInfo;
travelRuleMessage?: TravelRule;
}
networkFee
For EVM-based blockchains only. The total transaction fee in the blockchain’s largest unit. Note: Only two of the three arguments can be specified in a single transaction: gasLimit
, gasPrice
and networkFee
. Fireblocks recommends using a numeric string for accurate precision. Although a number input exists, it is deprecated. - The transaction blockchain fee.
- For Ethereum, you can’t pass gasPrice, gasLimit and networkFee all together.
- A numeric value representation is required.
Providing it doesn’t change anything.