Certs devlog | Notion

November 4, 2022 12:07 PM (EDT) Seems like OpenAI stuff is bork for create market; probably needs a new key for local dev setup…

Annoying:
- Thinking about how to structure/use the TXN table, new pattern
- Mismatch between client-side Firestore access and server-side Firestore admin access patterns, means queries aren’t shared…
- How would an ideal web3-ish pattern look? Smart Contracts on Web2 v0?
Annoying:
- Working with an end to end Firestore requires creating files for:
  1. common/ data structure
  2. functions/src/ Backend modification
    1. Then, a new backend API is a lot more work
  3. web/lib/firestore/ Firestore queries for:
  4. web/hooks use hook
  5. web/ frontend views
- Ideally: Single file to specify all of these?
  - Or two, 1. backend data manipulation stuff; 2. frontend how it looks stuff.
Annoying: Adding a new API using the server approach requires
- See https://github.com/manifoldmarkets/manifold/pull/1104/commits/c03d4536bc1ad782f37a837aa2ed2df5fb909094
- functions/src/increment
- functions/src/serve.ts
- web/lib/firebase/api.ts
Vs Vercel functions which just need:
- See https://github.com/manifoldmarkets/manifold/pull/1104/commits/b1f27406c187f7cd1274f61b3b74f8057d774648
- web/pages/api/v0/increment.ts

Bet vs Txn
- How to track profits in certs? Not integrated into the code that uses bets
- API: Should this actually just use resolve-market, place-bet?
Cert vs Contract
- Should certs be contracts?
- certId vs contractId
Grouped transactions representation, vs loose txns?
- SwapEvent?
- ResolveEvent?
Are negative shares okay in a TXN?
- … probably not?
- Pro: reduces number of types of transactions; we can just check toId instead of fromId to validate these TXNs
- Con: Bit harder to reason about; now we have to check fromId sometimes
Ideally: All changes to db are logged, and we have full rollback capability
- Database is a series of diffs