Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
The wallet (cli_wallet) requires a running full node to connect to because it does not offer P2P or blockchain capabilities directly.
If you have not set up your wallet yet, you can find more information here: CLI Wallet Setup.
These methods are used for stealth transfers This method can be used to set a label for a public key
Note: No two keys can have the same label.
key: a public key
label: a user-defined string as label
True if the label was set, otherwise false
Get label of a public key.
key: a public key
The label if already set by set_key_label(), or an empty string if not set
Get the public key associated with a given label
label: a label
The public key associated with the given label.
Get all blind accounts.
All blind accounts
Get all blind accounts for which this wallet has the private key.
All blind accounts for which this wallet has the private key.
Return the total balances of all blinded commitments that can be claimed by the given account key or label.
key_or_label: a public key in Base58 format or a label
The total balances of all blinded commitments that can be claimed by the given account key or label
Generates a new blind account for the given brain key and assigns it the given label
label: a label
brain_key: the brain key to be used to generate a new blind account
The public key of the new account
Transfers a public balance from from_account_id_or_name to one or more blinded balances using a stealth transfer.
from_account_id_or_name: ID or name of an account to transfer from
asset_symbol: symbol or ID of the asset to be transferred
to_amounts: map from key or label to amount
broadcast: true to broadcast the transaction on the network
A blind confirmation
Transfers funds from a set of blinded balances to a public account balance.
from_blind_account_key_or_label: a public key in Base58 format or a label to transfer from
to_account_id_or_name: ID or name of an account to transfer to
amount: the amount to be transferred
asset_symbol: symbol or ID of the asset to be transferred
broadcast: true to broadcast the transaction on the network
A blind confirmation.
Transfer from one set of blinded balances to another.
from_key_or_label: a public key in Base58 format or a label to transfer from
to_key_or_label: a public key in Base58 format or a label to transfer to
amount: the amount to be transferred
symbol: symbol or ID of the asset to be transferred
broadcast: true to broadcast the transaction on the network
A blind confirmation
Get all blind receipts to/form a particular account.
key_or_account: a public key in Base58 format or an account
All blind receipts to/form the account.
Given a confirmation receipt, this method will parse it for a blinded balance and confirm that it exists in the blockchain. If it exists then it will report the amount received and who sent it.
confirmation_receipt: a base58 encoded stealth confirmation
opt_from: if not empty and the sender is a unknown public key, then the unknown public key will be given the label opt_from
opt_memo: a self-defined label for this transfer to be saved in local wallet file
A blind receipt.
Lists all accounts controlled by this wallet. This returns a list of the full account objects for all accounts whose private keys we possess
A list of account objects
Lists all accounts registered in the blockchain. This returns a list of all account names and their account ids, sorted by account name.
Use the lowerbound and limit parameters to page through the list. To retrieve all accounts, start by setting lowerbound to the empty string "", and then each iteration, pass the last account name returned as the lowerbound for the next list_accounts() call.
lowerbound: the name of the first account to return. If the named account does not exist, the list will start at the account that comes after lowerbound
limit: the maximum number of accounts to return (max: 1000)
A list of accounts mapping account names to account ids.
List the balances of an account. Each account can have multiple balances, one for each type of asset owned by that account. The returned list will only contain assets for which the account has a non-zero balance.
id: the name or id of the account whose balances you want
A list of the given account’s balances
Registers a third party’s account on the blockchain.
This function is used to register an account for which you do not own the private keys. When acting as a registrar, an end user will generate their own private keys and send you the public keys. The registrar will use this function to register the account on behalf of the end user.
See also create_account_with_brain_key()
name: the name of the account, must be unique on the blockchain. Shorter names are more expensive to register; the rules are still in flux, but in general names of more than 8 characters with at least one digit will be cheap.
owner: the owner key for the new account
active: the active key for the new account
registrar_account: the account which will pay the fee to register the user
referrer_account: the account who is acting as a referrer, and may receive a portion of the user’s transaction fees. This can be the same as the registrar_account if there is no referrer.
referrer_percent: the percentage (0 - 100) of the new user’s transaction fees not claimed by the blockchain that will be distributed to the referrer; the rest will be sent to the registrar. Will be multiplied by GRAPHENE_1_PERCENT when constructing the transaction.
broadcast: true to broadcast the transaction on the network
The signed transaction registering the account
Upgrades an account to prime status. This makes the account holder a ‘lifetime member’.
name: the name or id of the account to upgrade
broadcast: true to broadcast the transaction on the network
The signed transaction upgrading the account
Creates a new account and registers it on the blockchain.
See also suggest_brain_key(), register_account()
brain_key: the brain key used for generating the account’s private keys
account_name: the name of the account, must be unique on the blockchain. Shorter names are more expensive to register; the rules are still in flux, but in general names of more than 8 characters with at least one digit will be cheap.
registrar_account: the account which will pay the fee to register the user
referrer_account: the account who is acting as a referrer, and may receive a portion of the user’s transaction fees. This can be the same as the registrar_account if there is no referrer.
broadcast: true to broadcast the transaction on the network
The signed transaction registering the account
Transfer an amount from one account to another.
from: the name or id of the account sending the funds
to: the name or id of the account receiving the funds
amount: the amount to send (in nominal units to send half of a BTS, specify 0.5)
asset_symbol: the symbol or id of the asset to send
memo: a memo to attach to the transaction. The memo will be encrypted in the transaction and readable for the receiver. There is no length limit other than the limit imposed by maximum transaction size, but transaction increase with transaction size
broadcast: true to broadcast the transaction on the network
The signed transaction transferring funds
This method works just like transfer, except it always broadcasts and returns the transaction ID (hash) along with the signed transaction.
from: the name or id of the account sending the funds
to: the name or id of the account receiving the funds
amount: the amount to send (in nominal units to send half of a BTS, specify 0.5)
asset_symbol: the symbol or id of the asset to send
memo: a memo to attach to the transaction. The memo will be encrypted in the transaction and readable for the receiver. There is no length limit other than the limit imposed by maximum transaction size, but transaction increase with transaction size
The transaction ID (hash) along with the signed transaction transferring funds
Whitelist and blacklist accounts, primarily for transacting in whitelisted assets.
Accounts can freely specify opinions about other accounts, in the form of either whitelisting or blacklisting them. This information is used in chain validation only to determine whether an account is authorized to transact in an asset type which enforces a whitelist, but third parties can use this information for other uses as well, as long as it does not conflict with the use of whitelisted assets.
An asset which enforces a whitelist specifies a list of accounts to maintain its whitelist, and a list of accounts to maintain its blacklist. In order for a given account A to hold and transact in a whitelisted asset S, A must be whitelisted by at least one of S’s whitelist_authorities and blacklisted by none of S’s blacklist_authorities. If A receives a balance of S, and is later removed from the whitelist(s) which allowed it to hold S, or added to any blacklist S specifies as authoritative, A’s balance of S will be frozen until A’s authorization is reinstated.
authorizing_account: the account who is doing the whitelisting
account_to_list: the account being whitelisted
new_listing_status: the new whitelisting status
broadcast: true to broadcast the transaction on the network
The signed transaction changing the whitelisting status
Get information about a vesting balance object or vesting balance objects owned by an account.
account_name: An account name, account ID, or vesting balance object ID.
A list of vesting balance objects with additional info
Withdraw a vesting balance.
witness_name: The account name of the witness, also accepts account ID or vesting balance ID type.
amount: The amount to withdraw.
asset_symbol: The symbol of the asset to withdraw.
broadcast: true if you wish to broadcast the transaction
The signed transaction
Returns information about the given account.
account_name_or_id: the name or ID of the account to provide information about
The public account data stored in the blockchain
Lookup the id of a named account.
account_name_or_id: the name or ID of the account to look up
The id of the named account
Returns the most recent operations on the named account.
This returns a list of operation history objects, which describe activity on the account.
name: the name or id of the account
limit: the number of entries to return (starting from the most recent)
A list of operation_history_objects
Approve or disapprove a proposal.
fee_paying_account: The account paying the fee for the op.
proposal_id: The proposal to modify.
delta: Members contain approvals to create or remove. In JSON you can leave empty members undefined.
broadcast: true if you wish to broadcast the transaction
The signed version of the transaction
Creates a committee_member object owned by the given account.
An account can have at most one committee_member object.
owner_account: the name or id of the account which is creating the committee_member
url: a URL to include in the committee_member record in the blockchain. Clients may display this when showing a list of committee_members. May be blank.
broadcast: true to broadcast the transaction on the network
The signed transaction registering a committee_member
Returns information about the given witness.
owner_account: the name or id of the witness account owner, or the id of the witness
The information about the witness stored in the block chain.
Returns information about the given committee_member.
owner_account: the name or id of the committee_member account owner, or the id of the committee_member.
The information about the committee_member stored in the block chain
Lists all Witnesses registered in the blockchain. This returns a list of all account names that own Witnesses, and the associated witness id, sorted by name. This lists Witnesses whether they are currently voted in or not.
Use the lowerbound and limit parameters to page through the list. To retrieve all Witness's, start by setting lowerbound to the empty string "", and then each iteration, pass the last witness name returned as the lowerbound for the next list_witnesss() call.
lowerbound: the name of the first Witness to return. If the named Witness does not exist, the list will start at the witness that comes after lowerbound
limit: the maximum number of Witness's to return (max: 1000)
A list of Witness's mapping witness names to witness ids
Lists all committee_members registered in the blockchain. This returns a list of all account names that own committee_members, and the associated committee_member id, sorted by name. This lists committee_members whether they are currently voted in or not.
Use the lowerbound and limit parameters to page through the list. To retrieve all committee_members, start by setting lowerbound to the empty string "", and then each iteration, pass the last committee_member name returned as the lowerbound for the next list_committee_members() call.
lowerbound: the name of the first committee_member to return. If the named committee_member does not exist, the list will start at the committee_member that comes after lowerbound
limit: the maximum number of committee_members to return (max: 1000)
A list of committee_members mapping committee_member names to committee_member ids
Creates a witness object owned by the given account.
An account can have at most one witness object.
owner_account: the name or id of the account which is creating the witness
url: a URL to include in the witness record in the blockchain. Clients may display this when showing a list of witnesses. May be blank.
broadcast: true to broadcast the transaction on the network
The signed transaction registering a witness
Update a witness object owned by the given account.
witness_name: The name of the witness’s owner account. Also accepts the ID of the owner account or the ID of the witness.
url: Same as for create_witness. The empty string makes it remain the same.
block_signing_key: The new block signing public key. The empty string makes it remain the same.
broadcast: true if you wish to broadcast the transaction.
The signed transaction
Create a worker object.
owner_account: The account which owns the worker and will be paid
work_begin_date: When the work begins
work_end_date: When the work ends
daily_pay: Amount of pay per day (NOT per maint interval)
name: Any text
url: Any text
worker_settings: {“type” : “burn”|”refund”|”vesting”, “pay_vesting_period_days” : x}
broadcast: true if you wish to broadcast the transaction.
The signed transaction
Update your votes for workers.
account: The account which will pay the fee and update votes.
delta: {“vote_for” : […], “vote_against” : […], “vote_abstain” : […]}
broadcast: true if you wish to broadcast the transaction.
The signed transaction
Vote for a given committee_member.
An account can publish a list of all committee_members they approve of. This command allows you to add or remove committee_members from this list. Each account’s vote is weighted according to the number of shares of the core asset owned by that account at the time the votes are tallied.
Note: You can't vote against a committee_member, you can only vote for the committee_member or not vote for the committee_member.
voting_account: the name or id of the account who is voting with their shares
committee_member: the name or id of the committee_member’ owner account
approve: true if you wish to vote in favour of that committee_member, false to remove your vote in favour of that committee_member
broadcast: true if you wish to broadcast the transaction
The signed transaction changing your vote for the given committee_member.
Vote for a given witness.
An account can publish a list of all witnesses they approve of. This command allows you to add or remove witnesses from this list. Each account’s vote is weighted according to the number of shares of the core asset owned by that account at the time the votes are tallied.
Note: You can't vote against a witness, you can only vote for the witness or not vote for the witness.
voting_account: the name or id of the account who is voting with their shares
witness: the name or id of the witness’ owner account
approve: true if you wish to vote in favour of that witness, false to remove your vote in favour of that witness
broadcast: true if you wish to broadcast the transaction
The signed transaction changing your vote for the given witness
Set the voting proxy for an account.
If a user does not wish to take an active part in voting, they can choose to allow another account to vote their stake.
Setting a vote proxy does not remove your previous votes from the blockchain, they remain there but are ignored. If you later null out your vote proxy, your previous votes will take effect again.
This setting can be changed at any time.
account_to_modify: the name or id of the account to update
voting_account: the name or id of an account authorized to vote account_to_modify’s shares, or null to vote your own shares
broadcast: true if you wish to broadcast the transaction
The signed transaction changing your vote proxy settings
Set your vote for the number of witnesses and committee_members in the system.
Each account can voice their opinion on how many committee_members and how many witnesses there should be in the active committee_member/active witness list. These are independent of each other. You must vote your approval of at least as many committee_members or witnesses as you claim there should be (you can’t say that there should be 20 committee_members but only vote for 10).
There are maximum values for each set in the blockchain parameters (currently defaulting to 1001).
This setting can be changed at any time. If your account has a voting proxy set, your preferences will be ignored.
account_to_modify: the name or id of the account to update
desired_number_of_witnesses: desired number of active witnesses
desired_number_of_committee_members: desired number of active committee members
broadcast: true if you wish to broadcast the transaction
The signed transaction changing your vote proxy settings
Creates a transaction to propose a parameter change.
Multiple parameters can be specified if an atomic change is desired.
proposing_account: The account paying the fee to propose the tx
expiration_time: Timestamp specifying when the proposal will either take effect or expire.
changed_values: The values to change; all other chain parameters are filled in with default values
broadcast: true if you wish to broadcast the transaction
The signed version of the transaction
Propose a fee change.
proposing_account: The account paying the fee to propose the tx
expiration_time: Timestamp specifying when the proposal will either take effect or expire.
changed_values: Map of operation type to new fee. Operations may be specified by name or ID. The “scale” key changes the scale. All other operations will maintain current values.
broadcast: true if you wish to broadcast the transaction
The signed version of the transaction
Create a new transaction builder.
Handle of the new transaction builder.
Append a new operation to a transaction builder.
transaction_handle: handle of the transaction builder
op: the operation in JSON format
Replace an operation in a transaction builder with a new operation.
handle: handle of the transaction builder
operation_index: the index of the old operation in the builder to be replaced
new_op: the new operation in JSON format
Calculate and update fees for the operations in a transaction builder.
handle: handle of the transaction builder
fee_asset: name or ID of an asset that to be used to pay fees
Total fees.
Show content of a transaction builder.
handle: handle of the transaction builder
A transaction.
Sign the transaction in a transaction builder and optionally broadcast to the network.
transaction_handle: handle of the transaction builder
broadcast: whether to broadcast the signed transaction to the network
A signed transaction.
Create a proposal containing the operations in a transaction builder (create a new proposal_create operation, then replace the transaction builder with the new operation), then sign the transaction and optionally broadcast to the network.
Note: this command is not effective because you're unable to specify a proposer. It will be deprecated in a future release. Use propose_builder_transaction2() instead.
handle: handle of the transaction builder
expiration: when the proposal will expire
review_period_seconds: review period of the proposal in seconds
broadcast: whether to broadcast the signed transaction to the network
A signed transaction.
Create a proposal containing the operations in a transaction builder (create a new proposal_create operation, then replace the transaction builder with the new operation), then sign the transaction and optionally broadcast to the network.
handle: handle of the transaction builder
account_name_or_id: name or ID of the account who would pay fees for creating the proposal
expiration: when the proposal will expire
review_period_seconds: review period of the proposal in seconds
broadcast: whether to broadcast the signed transaction to the network
A signed transaction.
Destroy a transaction builder.
handle: handle of the transaction builder
Converts a signed_transaction in JSON form to its binary representation.
tx: the transaction to serialize
The binary form of the transaction. It will not be hex encoded, this returns a raw string that may have null characters embedded in it
Signs a transaction.
Given a fully-formed transaction that is only lacking signatures, this signs the transaction with the necessary keys and optionally broadcasts the transaction.
tx: the unsigned transaction
broadcast: true if you wish to broadcast the transaction
The signed version of the transaction
Returns an uninitialized object representing a given blockchain operation.
This returns a default-initialized object of the given type; it can be used during early development of the wallet when we don’t yet have custom commands for creating all of the operations the blockchain supports.
Any operation the blockchain supports can be created using the transaction builder’s add_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”)
A default-constructed operation of the given type.
Checks whether the wallet has just been created and has not yet had a password set.
Calling set_password will transition the wallet to the locked state.
True if the wallet is new.
Checks whether the wallet is locked (is unable to use its private keys).
This state can be changed by calling lock() or unlock()
True if the wallet is locked
Locks the wallet immediately.
Unlocks the wallet.
The wallet remain unlocked until the lock is called or the program exits.
When used in command line, if typed “unlock” without a password followed, the user will be prompted to input a password without echo.
password: the password previously set with set_password()
Sets a new password on the wallet.
The wallet must be either ‘new’ or ‘unlocked’ to execute this command.
When used in command line, if typed “set_password” without a password followed, the user will be prompted to input a password without echo.
password: a new password
Dumps all private keys owned by the wallet.
The keys are printed in WIF format. You can import these keys into another wallet using import_key()
A map containing the private keys, indexed by their public key
Imports the private key for an existing account.
The private key must match either an owner key or an active key for the named account.
See also dump_private_keys()
account_name_or_id: the account owning the key
wif_key: the private key in WIF format
true if the key was imported
Imports accounts from a Peerplays 0.x wallet file. Current wallet file must be unlocked to perform the import.
filename: the Peerplays 0.x wallet file to import
password: the password to encrypt the Peerplays 0.x wallet file
A map containing the accounts found and whether imported.
Imports from a Peerplays 0.x wallet file, find keys that were bound to a given account name on the Peerplays 0.x chain, rebind them to an account name on the 2.0 chain. Current wallet file must be unlocked to perform the import.
filename: the Peerplays 0.x wallet file to import
password: the password to encrypt the Peerplays 0.x wallet file
src_account_name: name of the account on Peerplays 0.x chain
dest_account_name: name of the account on Peerplays 2.0 chain, can be same or different to src_account_name
Whether the import has succeeded
This call will construct transaction(s) that will claim all balances controlled by wif_keys and deposit them into the given account.
account_name_or_id: name or ID of an account that to claim balances to
wif_keys: private WIF keys of balance objects to claim balances from
broadcast: true to broadcast the transaction on the network
Suggests a safe brain key to use for creating your account. create_account_with_brain_key() requires you to specify a ‘brain key’, a long passphrase that provides enough entropy to generate cryptographic keys.
This function will suggest a suitably random string that should be easy to write down (and, with effort, memorize).
A suggested brain_key
This method is used to convert a JSON transaction to its transacting ID.
trx: a JSON transaction
The ID (hash) of the transaction.
Get the WIF private key corresponding to a public key. The private key must already be in the wallet.
pubkey: a public key in Base58 format
The WIF private key
Loads a specified Graphene wallet.
The current wallet is closed before the new wallet is loaded.
Important: This does not change the filename that will be used for future wallet writes, so this may cause you to overwrite your original wallet unless you also call set_wallet_filename()
wallet_filename: the filename of the wallet JSON file to load. If wallet_filename is empty, it reloads the existing wallet file.
True if the specified wallet is loaded.
Transforms a brain key to reduce the chance of errors when re-entering the key from memory.
This takes a user-supplied brain key and normalizes it into the form used for generating private keys. In particular, this upper-cases all ASCII characters and collapses multiple spaces into one.
s: the brain key as supplied by the user
The brain key in its normalized form.
Saves the current wallet to the given filename.
Important: This does not change the wallet filename that will be used for future writes, so think of this function as ‘Save a Copy As…’ instead of ‘Save As…’. Use set_wallet_filename() to make the filename persist.
wallet_filename: the filename of the new wallet JSON file to create or overwrite. If wallet_filename is empty, save to the current filename.
Place a limit order attempting to sell one asset for another.
Buying and selling are the same operation on Graphene; if you want to buy BTS with USD, you should sell USD for BTS.
The blockchain will attempt to sell the symbol_to_sell for as much symbol_to_receive as possible, as long as the price is at least min_to_receive / amount_to_sell.
In addition to the transaction fees, market fees will apply as specified by the issuer of both the selling asset and the receiving asset as a percentage of the amount exchanged.
If either the selling asset or the receiving asset is whitelist restricted, the order will only be created if the seller is on the whitelist of the restricted asset type.
Market orders are matched in the order they are included in the block chain.
seller_account: the account providing the asset being sold, and which will receive the proceeds of the sale.
amount_to_sell: the amount of the asset being sold to sell (in nominal units)
symbol_to_sell: the name or id of the asset to sell
min_to_receive: the minimum amount you are willing to receive in return for selling the entire amount_to_sell
symbol_to_receive: the name or id of the asset you wish to receive
timeout_sec: if the order does not fill immediately, this is the length of time the order will remain on the order books before it is cancelled and the un-spent funds are returned to the seller’s account
fill_or_kill: if true, the order will only be included in the blockchain if it is filled immediately; if false, an open order will be left on the books to fill any amount that cannot be filled immediately.
broadcast: true to broadcast the transaction on the network
The signed transaction selling the funds.
Borrow an asset or update the debt/collateral ratio for the loan.
This is the first step in shorting an asset.
Call sell_asset() to complete the short.
borrower_name: the name or id of the account associated with the transaction.
amount_to_borrow: the amount of the asset being borrowed. Make this value negative to pay back debt.
asset_symbol: the symbol or id of the asset being borrowed.
amount_of_collateral: the amount of the backing asset to add to your collateral position. Make this negative to claim back some of your collateral. The backing asset is defined in the bitasset_options for the asset being borrowed.
broadcast: true to broadcast the transaction on the network
The signed transaction borrowing the asset
Cancel an existing order.
order_id: the id of order to be cancelled
broadcast: true to broadcast the transaction on the network
The signed transaction canceling the order
Schedules a market-issued asset for automatic settlement.
Holders of market-issued assets may request a forced settlement for some amount of their asset. This means that the specified sum will be locked by the chain and held for the settlement period, after which time the chain will choose a margin position holder and buy the settled asset using the margin’s collateral.
The price of this sale will be based on the feed price for the market-issued asset being settled. The exact settlement price will be the feed price at the time of settlement with an offset in favour of the margin position, where the offset is a blockchain parameter set in the global_property_object.
account_to_settle: the name or id of the account owning the asset
amount_to_settle: the amount of the named asset to schedule for settlement
symbol: the name or id of the asset to settle
broadcast: true to broadcast the transaction on the network
The signed transaction settling the named asset.
Get OHLCV data of a trading pair in a time range.
symbol: name or ID of the base asset
symbol2: name or ID of the quote asset
bucket: length of each time bucket in seconds.
start: the start of a time range, E.G. “2018-01-01T00:00:00”
end: the end of the time range
A list of OHLCV data, in “least recent first” order.
Get limit orders in a given market.
a: symbol or ID of asset being sold
b: symbol or ID of asset being purchased
limit: Maximum number of orders to retrieve
The limit orders, ordered from least price to greatest.
Get call orders (aka margin positions) for a given asset.
a: symbol name or ID of the debt asset
limit: Maximum number of orders to retrieve
The call orders, ordered from earliest to be called to latest
Get forced settlement orders in a given asset.
a: Symbol or ID of asset being settled
limit: Maximum number of orders to retrieve
The settle orders, ordered from earliest settlement date to latest
Lists all assets registered on the blockchain.
To list all assets, pass the empty string "" for the lowerbound to start at the beginning of the list, and iterate as necessary.
lowerbound: the symbol of the first asset to include in the list.
limit: the maximum number of assets to return (max: 100)
The list of asset objects, ordered by symbol.
Creates a new user-issued or market-issued asset.
Many options can be changed later using update_asset()
Note: Right now this function is difficult to use because you must provide raw JSON data structures for the options objects, and those include prices and asset ids.
issuer: the name or id of the account who will pay the fee and become the issuer of the new asset. This can be updated later
symbol: the ticker symbol of the new asset
precision: the number of digits of precision to the right of the decimal point, must be less than or equal to 12
common: asset options required for all new assets. Note that core_exchange_rate technically needs to store the asset ID of this new asset. Since this ID is not known at the time this operation is created, create this price as though the new asset has instance ID 1, and the chain will overwrite it with the new asset’s ID.
bitasset_opts: options specific to BitAssets. This may be null unless the market_issued flag is set in common.flags
broadcast: true to broadcast the transaction on the network
The signed transaction creating a new asset.
Update the core options on an asset. There are a number of options which all assets in the network use. These options are enumerated in the asset_object::asset_options struct.
This command is used to update these options for an existing asset.
symbol: the name or id of the asset to update
new_issuer: if changing the asset’s issuer, the name or id of the new issuer. null if you wish to remain the issuer of the asset
new_options: the new asset_options object, which will entirely replace the existing options.
broadcast: true to broadcast the transaction on the network
The signed transaction updating the asset
Update the options specific to a BitAsset.
BitAssets have some options which are not relevant to other asset types. This operation is used to update those options an an existing BitAsset.
See update_asset()
symbol: the name or id of the asset to update, which must be a market-issued asset
new_options: the new bitasset_options object, which will entirely replace the existing options.
broadcast: true to broadcast the transaction on the network
The signed transaction updating the Bitasset
Update the set of feed-producing accounts for a BitAsset.
BitAssets have price feeds selected by taking the median values of recommendations from a set of feed producers. This command is used to specify which accounts may produce feeds for a given BitAsset.
symbol: the name or id of the asset to update
new_feed_producers: a list of account names or ids which are authorized to produce feeds for the asset. this list will completely replace the existing list
broadcast: true to broadcast the transaction on the network
The signed transaction updating the BitAsset’s feed producers
Publishes a price feed for the named asset.
Price feed providers use this command to publish their price feeds for market-issued assets. A price feed is used to tune the market for a particular market-issued asset. For each value in the feed, the median across all committee_member feeds for that asset is calculated and the market for the asset is configured with the median of that value.
The feed object in this command contains three prices:
A call price limit
A short price limit,
A settlement price
The call limit price is structured as (collateral asset) / (debt asset) and the short limit price is structured as (asset for sale) / (collateral asset).
Note: The asset IDs are opposite to each other, so if we’re publishing a feed for USD, the call limit price will be CORE/USD and the short limit price will be USD/CORE.
The settlement price may be flipped either direction, as long as it is a ratio between the market-issued asset and its collateral.
publishing_account: the account publishing the price feed
symbol: the name or id of the asset whose feed we’re publishing
feed: the price_feed object containing the three prices making up the feed
broadcast: true to broadcast the transaction on the network
The signed transaction updating the price feed for the given asset.
Issue new shares of an asset.
to_account: the name or id of the account to receive the new shares
amount: the amount to issue, in nominal units
symbol: the ticker symbol of the asset to issue
memo: a memo to include in the transaction, readable by the recipient
broadcast: true to broadcast the transaction on the network
The signed transaction issuing the new shares
Returns information about the given asset.
asset_name_or_id: the symbol or id of the asset in question
The information about the asset stored in the block chain.
Returns the BitAsset-specific data for a given asset. Market-issued assets’s behaviour are determined both by their “BitAsset Data” and their basic asset data, as returned by get_asset()
asset_name_or_id: the symbol or id of the BitAsset in question
The BitAsset-specific data for this asset
Pay into the fee pool for the given asset.
User-issued assets can optionally have a pool of the core asset which is automatically used to pay transaction fees for any transaction using that asset (using the asset’s core exchange rate).
This command allows anyone to deposit the core asset into this fee pool.
from: the name or id of the account sending the core asset
symbol: the name or id of the asset whose fee pool you wish to fund
amount: the amount of the core asset to deposit
broadcast: true to broadcast the transaction on the network
The signed transaction funding the fee pool.
Burns an amount of given asset.
This command burns an amount of given asset to reduce the amount in circulation.
Note: You can't burn market-issued assets.
from: the account containing the asset you wish to burn
amount: the amount to burn, in nominal units
symbol: the name or id of the asset to burn
broadcast: true to broadcast the transaction on the network
The signed transaction burning the asset
Forces a global settling of the given asset (black swan or prediction markets).
In order to use this operation, asset_to_settle must have the global_settle flag set
When this operation is executed all open margin positions are called at the settle price. A pool will be formed containing the collateral got from the margin positions. Users owning an amount of the asset may use settle_asset() to claim collateral instantly at the settle price from the pool.
If this asset is used as backing for other BitAssets, those BitAssets will not be affected.
Note: This operation is used only by the asset issuer.
symbol: the name or id of the asset to globally settle
settle_price: the price at which to settle
broadcast: true to broadcast the transaction on the network
The signed transaction settling the named asset
Returns info about a specified block.
num: height of the block to retrieve
Info about the block, or null if not found.
Returns the number of accounts registered on the blockchain.
The number of registered accounts
Returns the block chain’s slowly-changing settings.
This object contains all of the properties of the blockchain that are fixed or that change only once per maintenance interval (daily) such as the current list of witnesses, committee_members, block interval, etc.
See get_dynamic_global_properties() for frequently changing properties.
The global properties.
Returns the block chain’s rapidly-changing properties. The returned object contains information that changes every block interval such as the head block number, the next witness, etc.See
get_global_properties() for less-frequently changing properties
The dynamic global properties.
Returns the blockchain object corresponding to the given id.
This generic function can be used to retrieve any object from the blockchain that is assigned an ID. Certain types of objects have specialized convenience functions to return their objects e.g., assets have get_asset(), accounts have get_account(), but this function will work for any object.
id: the id of the object to return.
The requested object.
Returns a list of all commands supported by the wallet API.
This lists each command, along with its arguments and return types. For more detailed help on a single command, use
A multi-line string suitable for displaying on a terminal.
Returns detailed help on a single API command.
method: the name of the API command you want help with
A multi-line string suitable for displaying on a terminal.
Returns info about head block, chain_id, maintenance, participation, current active witnesses and committee members.
Runtime info about the blockchain
Returns info such as client version, git version of graphene/fc, version of boost, openssl etc.
Compile time info and client and dependencies versions.
nodes: Nodes to be added.
List of connected peers.