Package 

Class TransactionDataRequest.TransactionsInvolvingAddress

  • All Implemented Interfaces:
    cash.z.ecc.android.sdk.internal.model.TransactionDataRequest

    
    public final class TransactionDataRequest.TransactionsInvolvingAddress
     implements TransactionDataRequest
                        

    Information about transactions that receive or spend funds belonging to the specified transparent address is requested.

    Fully transparent transactions, and transactions that do not contain either shielded inputs or shielded outputs belonging to the wallet, may not be discovered by the process of chain scanning; as a consequence, the wallet must actively query to find transactions that spend such funds. Ideally we'd be able to query by OutPoint but this is not currently functionality that is supported by the light wallet server.

    The caller evaluating this request on behalf of the wallet backend should respond to this request by detecting transactions involving the specified address within the provided block range; if using lightwalletd for access to chain data, this may be performed using the GetTaddressTxids RPC method. It should then call ZcashRustBackend.decryptAndStoreTransaction for each transaction so detected.

    • Method Detail

      • getAddress

         final String getAddress()

        The address to request transactions and/or UTXOs for.

      • getStartHeight

         final BlockHeight getStartHeight()

        Only transactions mined at heights greater than or equal to this height should be returned.

      • getEndHeight

         final BlockHeight getEndHeight()

        If set, only transactions mined at heights less than this height should be returned.

      • getRequestAt

         final Instant getRequestAt()

        If request_at is set, the caller evaluating this request should attempt to retrieve transaction data related to the specified address at a time that is as close as practical to the specified instant, and in a fashion that decorrelates this request to a light wallet server from other requests made by the same caller.

        This may be ignored by callers that are able to satisfy the request without exposing correlations between addresses to untrusted parties; for example, a wallet application that uses a private, trusted-for-privacy supplier of chain data can safely ignore this field.

      • getOutputStatusFilter

         final OutputStatusFilter getOutputStatusFilter()

        The caller should respond to this request only with transactions containing outputs that conform to the specified output status filter.