An additional factor of the Ardor fee to pay for each transaction. Used to give advantage to this bundler when competing with other bundlers. This is a multiplier of what you will pay in terms of ARDR fee (the result of the Fee Calculator function). So if the fee is 100 ARDR and overpay is set to 0.1 you will pay 100 + 100 * 0.1 = 110 as bundling fee. Custom Fee Calculators may use this value for different purpose, or disregard it.
Zero or more additional filters applied on the bundled transactions. The transaction must satisfy the minimum fee rate and all filters in order to be processed. Filters can check various properties of the transaction like the sender, the recipient the transaction type, or even the presence of other transaction(s). A parameter can be specified for every added filter. The parameter is a filter-specific arbitrary string. Default filters provided "out-of-the-box":
|PersonalBundler||Only bundle the transactions of the bundler account|
|PropertyBundler||Only bundle transactions sent by accounts which have the "bundling" property set on them by the bundler account|
|AssetBundler||Bundles only transactions for asset with ID provided as parameter||Asset ID (numeric)|
|CurrencyBundler||Bundles only transactions for MS currency with ID provided as parameter||Currency ID (numeric). This is not the currency code|
|PurchaseBundler||Bundles only purchases of digital goods sold by an account provided as parameter||Account ID (numeric or RS format)|
|QuotaBundler||Bundles transaction until the quota per account and transaction type is reached. The quota is provided as parameter.||Max number of transactions per account and transaction type that will be accepted by the rule|
|TransactionTypeBundler||Bundles only transaction types provided as parameter.||Comma separated string, which contains the <type>:<subtype> pairs specifying the "type" and "subtype" identifier of the whitelisted transaction types. The "type" and "subtype" identifiers can be found in the transactionSubTypes field of the getConstants result. E.g. "7:1,7:2" bundles only ShufflingRegistration and ShufflingProcessing transactions.|
Additional filters can be developed as add-ons by implementing the Bundler.Filter interface. Their classes must be added to the nxt.availableBundlingFilters property.