-
Notifications
You must be signed in to change notification settings - Fork 0
JavaScript Console
Vapory implements a javascript runtime environment (JSRE) that can be used in either interactive (console) or non-interactive (script) mode.
Vapory's Javascript console exposes the full web3 JavaScript Dapp API and the admin API.
The vapory CLI
executable gvap
has a JavaScript console (a Read, Evaluate & Print Loop = REPL exposing the JSRE), which can be started with the console
or attach
subcommand. The console
subcommands starts the gvap node and then opens the console. The attach
subcommand will not start the gvap node but instead tries to open the console on a running gvap instance.
$ gvap console
$ gvap attach
The attach node accepts an endpoint in case the gvap node is running with a non default ipc endpoint or you would like to connect over the rpc interface.
$ gvap attach ipc:/some/custom/path
$ gvap attach http://191.168.1.1:8545
$ gvap attach ws://191.168.1.1:8546
Note that by default the gvap node doesn't start the http and weboscket service and not all functionality is provided over these interfaces due to security reasons. These defaults can be overridden when the --rpcapi
and --wsapi
arguments when the gvap node is started, or with admin.startRPC and admin.startWS.
If you need log information, start with:
$ gvap --verbosity 5 console 2>> /tmp/vap.log
Otherwise mute your logs, so that it does not pollute your console:
$ gvap console 2>> /dev/null
or
$ gvap --verbosity 0 console
Gvap has support to load custom JavaScript files into the console through the --preload
argument. This can be used to load often used functions, setup web3 contract objects, or ...
gvap --preload "/my/scripts/folder/utils.js,/my/scripts/folder/contracts.js" console
It's also possible to execute files to the JavaScript interpreter. The console
and attach
subcommand accept the --exec
argument which is a javascript statement.
$ gvap --exec "vap.blockNumber" attach
This prints the current block number of a running gvap instance.
Or execute a local script with more complex statements on a remote node over http:
$ gvap --exec 'loadScript("/tmp/checkbalances.js")' attach http://123.123.123.123:8545
$ gvap --jspath "/tmp" --exec 'loadScript("checkbalances.js")' attach http://123.123.123.123:8545
Use the --jspath <path/to/my/js/root>
to set a libdir for your js scripts. Parameters to loadScript()
with no absolute path will be understood relative to this directory.
You can exit the console cleanly by typing exit
or simply with CTRL-C
.
The go-vapory JSRE uses the Otto JS VM which has some limitations:
- "use strict" will parse, but does nothing.
- The regular expression engine (re2/regexp) is not fully compatible with the ECMA5 specification.
Note that the other known limitation of Otto (namely the lack of timers) is taken care of. Vapory JSRE implements both setTimeout
and setInterval
. In addition to this, the console provides admin.sleep(seconds)
as well as a "blocktime sleep" mvapod admin.sleepBlocks(number)
.
Since web3.js
uses the bignumber.js
library (MIT Expat Licence), it is also autoloded.
In addition to the full functionality of JS (as per ECMA5), the vapory JSRE is augmented with various timers. It implements setInterval
, clearInterval
, setTimeout
, clearTimeout
you may be used to using in browser windows. It also provides implementation for admin.sleep(seconds)
and a block based timer, admin.sleepBlocks(n)
which sleeps till the number of new blocks added is equal to or greater than n
, think "wait for n confirmations".
Beside the official DApp API interface the go vapory node has support for additional management API's. These API's are offered using JSON-RPC and follow the same conventions as used in the DApp API. The go vapory package comes with a console client which has support for all additional API's.
golang <3