Skip to content

πŸ—œοΈ What format could we use to cache "control book data" for easier Horizon reference?Β #2

@JFWooten4

Description

@JFWooten4

The current control-book authorization and reporting information involves scanning through all the past transactions to identify operations which interact with the issuer address. This isn't super perfect, and my understanding of the staff source is that the Commission thinks presently that our analysis here comes from the examination of StellarExpert summary charts of supply outstanding. Obviously this isn't ideal, so I'd like to brainstorm and implement a means to achieve the control book changes suggested:

Caching internally the issuer-linked transactions

The staff mentioned that it was "common to see Journal format"1 of these changes, which aligns with the existing ledger structure and CB database cache. They also directly referenced very early MSF designs (inter alia_) from the examples. This design should supersede these early interfaces which ought be limited to onboarding uptake only for now per the written PSV documentation in the Exam.

Footnotes

  1. "for the issuances, okay" in past legacy implementation, "but I'd like a more thoughtful approach" πŸ˜‰ ↩

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