feat: data requirements thoughts

CHANGELOG.md

@@ -1,6 +1,19 @@
 # Changelog
 
+## v8
+
+- Data requirements analysis
+- Ability to handle multiple squid processors:
+    - [main.ts](src%2Fmain.ts)
+    - [processor.ts](src%2Fprocessor.ts)
+- `curve` processor & template
+    - processing by day historically and then realtime thereafter
+- schema spread out into multiple `graphql` files and built via `yarn codegen`
+- created otoken processor to handle OUSD and OETH contract processing
+- `ousd` processing added, however the data has not yet been validated
+    - We're unable to process as far back as we want to due to an archive server bug. (reported to them)
+
 ## v7
 
-- APY numbers have been changed to return proper percentages. (v6 value / 100)
+- APY numbers have been changed to return proper percentages. (v6 value / 100) **BREAKING**
 - Added `ExchangeRate` entities.

README.md

@@ -42,9 +42,12 @@ Full description of `schema.graphql` dialect is available [here](https://docs.su
 
 Mapping developers use TypeORM [EntityManager](https://typeorm.io/#/working-with-entity-manager)
 to interact with target database during data processing. All necessary entity classes are
-generated by the squid framework from `schema.graphql`. This is done by running `sqd codegen`
+generated by the squid framework from `schema.graphql`. This is done by running `yarn codegen`
 command.
 
+NOTE: We don't directly use the `sqd codegen` command because we generate our schema.graphql file first in
+the `yarn codegen` script.
+
 ### 3. Generate database migrations
 
 All database changes are applied through migration files located at `db/migrations`.