Operate adapter specification.

An adapter is responsible for loading tapes and ops from a datasource - potentially a web API, a database or even a Bitcoin node. Operate ships with two default adapters, although these can be swapped out with any other adpater by changing the configuration:

children = [
  {Operate, [
    tape_adapter: Operate.Adapter.Bob,
    op_adapter: Operate.Adapter.OpApi
  ]}
]
Supervisor.start_link(children, strategy: :one_for_one)

Creating an adapter

An adapter must implement one or more of the following callbacks:

• fetch_tx/2 - function that takes a txid and returns a Operate.BPU.Transaction.t/0.
• fetch_tx_by/2 - function that takes a map and returns a list of Operate.BPU.Transaction.t/0 tx.
• fetch_ops/2 - function that takes a list of Op references and returns a list of Operate.Op.t/0 functions.

Example:

defmodule MyAdapter do
  use Operate.Adapter

  def fetch_tx(txid, opts) do
    key = Keyword.get(opts, :api_key)
    BitcoinApi.load_tx(txid, api_key: key)
    |> to_bpu
  end

  defp to_bpu(tx) do
    # Map tx object to `Operate.BPU.Transaction.t`
  end
end

Using the above example, Operate can be configured with:

{Operate, [
  tape_adapter: {MyAdapter, [api_key: "myapikey"]}
]}