Documentation
  • INTRODUCTION
  • USERS
    • White Paper
    • Main features of CyberWay
    • Bandwidth differences between EOS and CyberWay
    • Bandwidth implementation
    • How to Launch EOS dApps on CyberWay
    • Glossary
  • DEVELOPMENT ENVIRONMENT
    • Core Concepts
    • 1 Before You Begin
    • 2 Install the CDT
    • 3 Create Development Wallet
    • 4 Start keosd and nodeos
    • 5 Create Test Accounts
  • SOFTWARE MANUALS
    • Core
      • nodeos
      • cleos
      • keosd
      • cyberway.cdt
    • How To Guides
      • How To Ban An Unwanted Account
      • How To Calculate Reward For An Author
      • How To Calculate Reward For A Beneficiary
      • How To Calculate Reward For A Curator
      • How To Create A Wallet
      • How To Create An Account
      • How To Create A Proxy Account
      • How To Create Key Pair
      • How To Delegate Resources
      • How To Deploy A Node Using A Snapshot
      • How To Deploy A Smart Contract
      • How To Get Account Information
      • How To Get Block Information
      • How To Get Transaction Information
      • How To Import A Key
      • How To Link Permission
      • How To List All Key Pair
      • How To Stake Tokens
      • How To Stop A Node Using Docker
      • How To Submit A Proposal For HardFork
      • How To Transfer Tokens To A Worker
      • How To Undelegate Resources
      • How To Unlink Permission
      • How To Unstake Tokens
      • How To Vote
    • API Reference
      • Nodeos Chain API
      • Nodeos Producer API
      • Nodeos Net API
    • Cleos Command Reference
      • Convert
      • Create
      • Get
      • Multisig
      • Net
      • Push
      • Set
      • Sign
      • System
      • Transfer
      • Version
      • Wallet
    • Explorer Command Reference
      • How To Check Your Balance
      • How To Find Out Account ID
      • How To Convert Golos To Golos Power And Vice Versa
      • How To Stake Tokens CYBER
      • How To Transfer Funds From One Account To Another
      • How To Transfer Funds From Pending to Liquid
      • How To Bay Stake
      • How To Withdraw Stake
      • How To Vote For A Validator
      • How To Revoke Your Vote For A Validator
      • How To Bay Vesting Using Explorer
      • How To Vote For A Witness
      • How To Revoke Your Vote For A Witness
  • DEVPORTAL
    • System Contracts
      • BIOS
      • Domain names
      • Govern
      • Multi-Signature
      • Stake
      • Tokens
    • Application Contracts
      • Golos Contracts
        • Charge
        • Control
        • Emission
        • Publication
        • Referral program
        • Social
        • Vesting
        • Memo-keys
        • Determining Rewards for a Post
    • Guide to Creating and Deploying an Application on CyberWay
      • 1 Preliminary Work
      • 2 Creating a Simple Contract
      • 3 Creating Tokens
      • 4 Understanding ABI Files
      • 5 Data Persistence
      • 6 Secondary Indexes
      • 7 Adding Inline Actions
      • 8 Inline Action to External Contract
      • 9 Conclusion
    • The cyberway_wallet designed for the Bittrex market
    • The Event Model
  • VALIDATORS
    • Testnet Installation Guide
      • 1 General
      • 2 Configuring the Docker Image
      • 3 Create Container
      • 4 Connecting to a Node
      • 5 List of Commands Applicable to Any Kind of Container
    • Mainnet Connection Guide
      • Docker-Compose Start-up Instructions
      • APPENDIX A
      • APPENDIX B
    • Golos Blockchain Transit
    • How to join CyberWay for those who are interested in being validators ?
    • Stake Usage Guide
    • Regulations for CyberWay validators. Voting for Validators
Powered by GitBook
On this page
  • Push Action
  • Description
  • Positional Parameters
  • Options
  • Command
  • Push Transaction
  • Description
  • Positional Parameters
  • Options
  • Command
  • Push Transactions
  • Description
  • Positional Parameters
  • Options
  • Command
  1. SOFTWARE MANUALS
  2. Cleos Command Reference

Push

PreviousNetNextSet

Last updated 5 years ago

Description The subcommands can be used to push arbitrary transactions to the blockchain.

Subcommands

  • — Retrieve an account from the blockchain.

  • — Retrieve accounts associated with a public key.

  • — Retrieve accounts associated with a public key.

Push Action

Description

Push a transaction with a single action.

Positional Parameters

  • (string) account— The account providing the contract to execute (required).

  • (string) action— A JSON string or filename defining the action to execute on the contract (required).

  • (string) data— The arguments to the contract (required).

Options

  • -x,--expiration TEXT — Set the time (in seconds) before a transaction expires, defaults to 30 s.

  • -f,--force-unique — Force the transaction to be unique. This will consume extra bandwidth and remove any protections against accidently issuing the same transaction multiple times.

  • -s,--skip-sign — Specify if unlocked wallet keys should be used to sign transaction.

  • -j,--json — Print result as JSON.

  • -d,--dont-broadcast — Do not broadcast transaction to the network (just print to stdout).

  • --return-packed — Used in conjunction with --dont-broadcast to get the packed transaction.

  • -r,--ref-block TEXT — Set the reference block num or block id used for TAPOS (Transaction as Proof-of-Stake).

  • -p,--permission TEXT — An account and permission level to authorize, as in 'account@permission'.

  • --max-cpu-usage-ms UINT — Set an upper limit on the milliseconds of CPU usage budget, for the execution of the transaction (defaults to 0 which means no limit).

  • --max-net-usage UINT — Set an upper limit on the net usage budget (in bytes) for the transaction (defaults to 0 which means no limit).

  • --max-ram-usage UINT — Set an upper limit on the ram usage budget (in bytes) for the transaction (defaults to 0 which means no limit).

  • --max-storage-usage — Set an upper limit on the storage usage budget, (in bytes) for the transaction (defaults to 0 which means no limit).

  • --delay-sec UINT — Set the delay_sec seconds, defaults to 0 s.

  • --bandwidth-provider TEXT — Set an account which provide own bandwidth for transaction.

  • --dont-declare-names — Do not add declarenames action for resolved account names.

Command

$ cleos push [OPTIONS] <account> <action> <data>

Push Transaction

Description

Push an arbitrary JSON transaction.

Positional Parameters

  • (string) transaction— The JSON string or filename defining the transaction to push (required).

Options

  • -x,--expiration TEXT — Set the time (in seconds) before a transaction expires, defaults to 30 s.

  • -f,--force-unique — Force the transaction to be unique. This will consume extra bandwidth and remove any protections against accidently issuing the same transaction multiple times.

  • -s,--skip-sign — Specify if unlocked wallet keys should be used to sign transaction.

  • -j,--json — Print result as JSON.

  • -d,--dont-broadcast — Do not broadcast transaction to the network (just print to stdout).

  • --return-packed — Used in conjunction with --dont-broadcast to get the packed transaction.

  • -r,--ref-block TEXT — Set the reference block num or block id used for TAPOS (Transaction as Proof-of-Stake).

  • -p,--permission TEXT — An account and permission level to authorize, as in 'account@permission'.

  • --max-cpu-usage-ms UINT — Set an upper limit on the milliseconds of CPU usage budget, for the execution of the transaction (defaults to 0 which means no limit).

  • --max-net-usage UINT — Set an upper limit on the net usage budget (in bytes) for the transaction (defaults to 0 which means no limit).

  • --max-ram-usage UINT — Set an upper limit on the ram usage budget (in bytes) for the transaction (defaults to 0 which means no limit).

  • --max-storage-usage — Set an upper limit on the storage usage budget, (in bytes) for the transaction (defaults to 0 which means no limit).

  • --delay-sec UINT — Set the delay_sec seconds, defaults to 0 s.

  • --bandwidth-provider TEXT — Set an account which provide own bandwidth for transaction.

  • --dont-declare-names — Do not add declarenames action for resolved account names.

Command

$ cleos push transaction [OPTIONS] <transaction>

Push Transactions

Description

Push an array of arbitrary JSON transactions.

Positional Parameters

  • (string) transaction— The JSON string or filename defining the array of the transactions to push (required).

Options

No options required fot this subcommand.

Command

Pushes an array of arbitrary JSON transactions.

$ cleos push transactions {<transaction1>...<transactionN>}
Push Action
Push Transaction
Push Transactions