Skip to content

Use latest-transaction endpoint to improve EB load #244

@tdroxler

Description

@tdroxler

Currently the extension wallet is using /addresses/{address)/transactions?page=1&limit=1 every 5 minutes in background to check for new txs. Making that endpoint the most called in EB.

Image

This would be more performant for EB to use the dedicated: /addresses/{address}/latest-transaction endpoint, which only return the overview info of the latest tx:

final case class TransactionInfo(
    hash: TransactionId,
    blockHash: BlockHash,
    timestamp: TimeStamp,
    coinbase: Boolean
)

But which is enough to know if it's a new one or not.

The issue with /addresses/{address)/transactions?page=1&limit=1 is that we are also querying inputs and outputs, while they are not needed in that context AFAIK.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions