Right now the Actions table has been coopted so that Warrants are stored alongside Actions. We do funny things like storing the action hash of the warrant in the prev_hash field of the Action table, and we allow the hash to be either an ActionHash or a WarrantHash accordingly.
We should either put Warrants in their own table, or at least rename the existing table and fields to make it clearer that it contains two disparate data types.
Right now the Actions table has been coopted so that Warrants are stored alongside Actions. We do funny things like storing the action hash of the warrant in the
prev_hashfield of the Action table, and we allow thehashto be either anActionHashor aWarrantHashaccordingly.We should either put Warrants in their own table, or at least rename the existing table and fields to make it clearer that it contains two disparate data types.