Jan 16, 2019

Hi @evoskuil, I know you are travelling soon. But just a small question about payment_record and how we want to use it when cataloging payments. There's a couple of conflicting comments that are confusing me a bit. Is the following the list of things we want to store as payment records for both inputs and outputs keyed by the relevant script hashes? 1. input or output flag 2. link (i.e. the offset into the transaction database for the tx that is the source of the input or the output) 3. Index into the inputs or outputs for the transaction 4. Point checksum With this change, we don't store the point hash or the height where the transaction is found. Replacing both of them with the direct link to the transaction record in the transaction database. Hope I am not miles off target with my understanding.