code: func (c *Client) LockUnspent(unlock bool, ops []*wire.OutPoint) error {
  	return c.LockUnspentAsync(unlock, ops).Receive()
  }
docs: // LockUnspent marks outputs as locked or unlocked, depending on the value of
  // the unlock bool.  When locked, the unspent output will not be selected as
  // input for newly created, non-raw transactions, and will not be returned in
  // future ListUnspent results, until the output is marked unlocked again.
  //
  // If unlock is false, each outpoint in ops will be marked locked.  If unlocked
  // is true and specific outputs are specified in ops (len != 0), exactly those
  // outputs will be marked unlocked.  If unlocked is true and no outpoints are
  // specified, all previous locked outputs are marked unlocked.
  //
  // The locked or unlocked state of outputs are not written to disk and after
  // restarting a wallet process, this data will be reset (every output unlocked).
  //
  // NOTE: While this method would be a bit more readable if the unlock bool was
  // reversed (that is, LockUnspent(true, ...) locked the outputs), it has been
  // left as unlock to keep compatibility with the reference client API and to
  // avoid confusion for those who are already familiar with the lockunspent RPC.