tid + signature for all on-chain object tables
oberstet opened this issue · 1 comments
oberstet commented
Every DB table that represent an on-chain object should have these 2 fields defined in the flatbuffers table schema already:
/// Transaction hash of the transaction this change was committed to the blockchain under.
tid: [uint8] (ethhash);
/// When signed off-chain and submitted via ``XBRCatalog.createCatalogFor``.
signature: [uint8] (ethsig);
Note: the transaction id (tid) allows to associate the DB record insert/update with the on-chain ethereum transaction that originates the insert/update. The signature allows to store the signature of pre-signed transactions where the transaction submitter is different from the signer.
However, these 2 fields are not yet added to the Python DB table classes. The current list of DB tables representing XBR related on-chain objects which need to be expanded:
- xbr::Actor (schema)
- xbr::Api (schema)
- xbr::Catalog (schema)
- xbr::Consent (schema)
- xbr::Market (schema)
- xbr::Member (schema)
- xbr::TokenApproval (schema)
- xbr::TokenBalance (schema)
- xbr::TokenTransfer (schema)
- xbr::PaymentChannel (schema)