Cross-platform EOSIO command-line swiss-army-knife (EOS, BOS, Telos, Worbli, etc.)
eoscEOSIO command-line swiss-army-knife
eoscis a cross-platform (Windows, Mac and Linux) command-line tool for interacting with an EOS.IO blockchain.
eos-golibrary, and is easy to extend.
go get -u -v github.com/eoscanada/eosc/eosc
brew install eoscanada/tap/eosc
Once installed run:
eosc vault create --import
to import your keys and follow instructions.
Then set your environment variable to the API URL of your choice, optionally setting some HTTP headers:
export EOSC_GLOBAL_HTTP_HEADER_0="Authorization: bearer abcdef12323453452565676589" export EOSC_GLOBAL_HTTP_HEADER_1="Origin: https://something...
Then you can run commands on the chain, ex:
eosc get info eosc transfer fromaccnt toaccnt 0.0001 --memo "Sent with eosc"
These are supported environment variables:
All global flags (those you get from eosc –help) can be set with the following pattern: EOSCGLOBALFLAG_NAME. The most useful are:
All (sub)command flags map to the following pattern: EOSCCOMMANDSUBCOMMANDCMDFLAGNAME (ex: `EOSCFORUMPOSTCMDREPLYTO
->eosc forum post --reply-to=...`
Special cases: *
EOSC_GLOBAL_INSECURE_VAULT_PASSPHRASEallows you to input the passphrase directly in an environment variable (useful for test automation, risky for most other uses) *
EOSC_GLOBAL_HTTP_HEADER_0(available for indexes 0 to 25)
You can inspect the crypto code in our codebase regarding the
passphraseimplementation: it is 61 lines, including blanks and comments.
Q: Why not use
cleosis hard to compile, being in C++, as it requires a huge toolchain.
eoscworks on Windows where
eosccontains a wallet inside, and is able to use it to sign some transactions,
cleosinterfaces with yet another program (
keosd) in order to sign transactions, making it more complex to use.
cleostogether in a swiss-army-knify package.