exw3 v0.4.0 ExW3.Contract View Source
Link to this section Summary
Functions
Returns the current Contract GenServer’s address
Sets the address for the contract specified by the name argument
Use a Contract’s method with an eth_call
Returns a specification to start this module under a supervisor
Deploys contracts with given arguments
Installs a filter on the Ethereum node. This also formats the parameters, and saves relevant information to format event logs
Using saved information related to the filter id, event logs are formatted properly
Invoked when the server is started. start_link/3
or start/3
will
block until it returns
Registers the contract with the ContractManager process. Only :abi is required field
Use a Contract’s method with an eth_sendTransaction
Begins the Contract process to manage all interactions with smart contracts
Returns a formatted transaction receipt for the given transaction hash(id)
Uninstalls the filter, and deletes the data associated with the filter id
Link to this section Functions
Returns the current Contract GenServer’s address
Sets the address for the contract specified by the name argument
Use a Contract’s method with an eth_call
Returns a specification to start this module under a supervisor.
See Supervisor
.
Deploys contracts with given arguments
Installs a filter on the Ethereum node. This also formats the parameters, and saves relevant information to format event logs.
get_filter_changes(binary()) :: {:ok, []}
Using saved information related to the filter id, event logs are formatted properly
Invoked when the server is started. start_link/3
or start/3
will
block until it returns.
args
is the argument term (second argument) passed to start_link/3
.
Returning {:ok, state}
will cause start_link/3
to return
{:ok, pid}
and the process to enter its loop.
Returning {:ok, state, timeout}
is similar to {:ok, state}
except handle_info(:timeout, state)
will be called after timeout
milliseconds if no messages are received within the timeout.
Returning {:ok, state, :hibernate}
is similar to {:ok, state}
except the process is hibernated before entering the loop. See
c:handle_call/3
for more information on hibernation.
Returning {:ok, state, {:continue, continue}}
is similar to
{:ok, state}
except that immediately after entering the loop
the c:handle_continue/2
callback will be invoked with the value
continue
as first argument.
Returning :ignore
will cause start_link/3
to return :ignore
and
the process will exit normally without entering the loop or calling
c:terminate/2
. If used when part of a supervision tree the parent
supervisor will not fail to start nor immediately try to restart the
GenServer
. The remainder of the supervision tree will be started
and so the GenServer
should not be required by other processes.
It can be started later with Supervisor.restart_child/2
as the child
specification is saved in the parent supervisor. The main use cases for
this are:
- The
GenServer
is disabled by configuration but might be enabled later. - An error occurred and it will be handled by a different mechanism than the
Supervisor
. Likely this approach involves callingSupervisor.restart_child/2
after a delay to attempt a restart.
Returning {:stop, reason}
will cause start_link/3
to return
{:error, reason}
and the process to exit with reason reason
without
entering the loop or calling c:terminate/2
.
Callback implementation for GenServer.init/1
.
Registers the contract with the ContractManager process. Only :abi is required field.
Use a Contract’s method with an eth_sendTransaction
Begins the Contract process to manage all interactions with smart contracts
Returns a formatted transaction receipt for the given transaction hash(id)
Uninstalls the filter, and deletes the data associated with the filter id