transaction_handle
: handle of the transaction builderop
: the operation in JSON formathandle
: handle of the transaction builderoperation_index
: the index of the old operation in the builder to be replacednew_op
: the new operation in JSON formathandle
: handle of the transaction builderfee_asset
: name or ID of an asset that to be used to pay feeshandle
: handle of the transaction buildertransaction_handle
: handle of the transaction builderbroadcast
: whether to broadcast the signed transaction to the networkpropose_builder_transaction2()
instead.handle
: handle of the transaction builderexpiration
: when the proposal will expirereview_period_seconds
: review period of the proposal in secondsbroadcast
: whether to broadcast the signed transaction to the networkhandle
: handle of the transaction builderaccount_name_or_id
: name or ID of the account who would pay fees for creating the proposalexpiration
: when the proposal will expirereview_period_seconds
: review period of the proposal in secondsbroadcast
: whether to broadcast the signed transaction to the networkhandle
: handle of the transaction buildertx
: the transaction to serializetx
: the unsigned transactionbroadcast
: true if you wish to broadcast the transactionadd_operation_to_builder_transaction()
, but to do that from the CLI you need to know what the JSON form of the operation looks like. This will give you a template you can fill in. It’s better than nothing.operation_type
: the type of operation to return, must be one of the operations defined in graphene/protocol/operations.hpp
(e.g., “global_parameters_update_operation”)