Updates for (or in conjunction with) FWSS 1.4.0

[rvagg]

Things that need updating and deploying soon that I can think of:

• perf: adjustments based on usage pattern observation #100 and feat: handle PiecesAddedV2 event #101 are merged but not deployed
• There's more events that came in feat: handle PiecesAddedV2 event #101 that we need to index
• feat: index PoRep Market as first-class #102 needs to be merged, I've noticed agents struggling a little because the PoRep service is taking up a nontrivial amount of FP volume now and I've seen agents get a bit fussy about the unknown rail validators and how FWSS isn't as dominant
• system-context needs something more to point agents to consider one-time fixed payments when looking at settlements, if you ask for settlement information it reaches for rate-based rails only; there's some nuance that's not being communicated
  • As part of looking at this ^ I was considering breaking up the system context into modules that agents have to load when they are looking at different parts of the system because the current context is getting too large and having to be increasingly terse is not scaling well
• Ponder's delayed transaction handling is hurting us in tracking recent data involving transaction information, a query can miss recent transaction data of up to 2 x finality because of the way ponder collects transactions and then bulk migrates them to be permanent and we only expose the permanent table to queries
  • Current idea is to make our own tx table and just collect it all there and join by tx_hash
  • Space-efficient version of that ^ idea is to GC it at some point beyond 2 x finality and have a view that joins both it and ponder's tx table so we don't have to double-up (Kuba says space isn't as much of a concern now we are on bare metal in our infra though)

[rvagg]

Also the new deletions flow, are there new events to index? How do we account for those? And explain them in the system context.