Translations: Tutorial on custom bundlers for child chain transactions/3/en

From ArdorDocs
Jump to: navigation, search

Remember these are some common options to make adoption easier for businesses — but if these do not meet your needs, the option to write your own custom bundler is always available. Default filters provided "out-of-the-box":

Name Description Parameter
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.