• Rising Sophomore at UCLA, bunch of personal projects, react & typescript
  • Backend like Rust, Java, C#
• Any questions
  • To add a moderator feature

Want to incorporate Manifold more consistently throughout; use it each day, and have it be the primary platform for trading, especially for numerical (futures) contracts up

• Manifold would be the only trading platform, entirely where stuff happens, as soon as Monday
• Know that’s a short timeline
• Order of prioritization of things to roll out

1. Is there a way to make an admin role of sorts that I (/Ross/Sydney) could inhabit? In particular, things I'd love to have power to do are:

• [ ] (a) be able to reorder questions on the home page,
  • Sometimes: Have a challenge, post 20 equivalent questions, about different games
    • 20 spikeball games
    • People create them in an order, g1, g2, g3, reverse order on the homepage, so it looks aesthetically nicer, low priority. not important
• [ ] (b) be able to edit / change questions after they're posted (e.g. to fix typos),
• [ ] (c) be able to delete questions, both my own and someone else's,
• [ ] (d) be able to easily see a ledger of everyone's clip balances at once, and
• [ ] (e) be able to adjust someone's clip balance (fine if this isn't doable though)
• Want this by the end, nice to have (decreases instructor time)
• Can transfer clips manually —
• Admin role reduces friction to things can do otherwise
  • Adding clips is useful, but subtracting clips is better (move clips back and forth between discord bot and Manifold interface)
  • How are clips tracked in Firebase
    • For each discord, collection represents user and number
    • No auth, done by roles
  • Number goes up in Discord - and also have
    • If we can do this, don’t need admin role
• [ ] (f) ability to resolve markets of someone else
  • Different instructors — log in to, multiple instructors with different question, resolving
  • (Mostly resolving each others, mostly not resolving a student’s)
    • Logged into a specific email.
• [x] 2. be able to duplicate a question (with a chance to edit it first), to speed up the process of creating many nearly identical questions
  • Created a question, and a duplicated version (not yet published)
  • If it would be easier, preferable - upload a CSV that has question description, type of question, and that has a whole bunch of questions
  • A lot of questions for one kind of thing
• [x] 3. Maybe this is too tricky, but I'd love to have a third type of question (separate from yes/no and free response) such that the answer resolves to a number chosen by the question asker. The way I envision this working is: someone posts a question like "how many participants are in Atlas session 2". People can buy/sell for whatever prices they'd like, with market makers existing +-20% of the last trade or something. If someone buys for a price of 12, and the answer settles to 25, that person makes $13. If someone sells for a price of 15, and the answer settles to 200, they lose $185. I think this question type should only be posed by admins (because otherwise participants could make ~infinite money), and maybe would need to have a (large) upper and lower bound (e.g. [-100000, +100000] or something. I'm happy to help scope out the specifics of how this would work and explain a few proposed implementations on the market structure side—I recognize this is unlikely to be doable but figured in case you happen to have something equivalent behind the scenes anyway it's worth bringing up.
  • Unbounded property
  • Min and Max being very large (10 to 7th or higher would be ideal)
  • Range should include negative numbers
  • Other question: linear vs log scaling: buy for a price of 98, pushes up percentage less
    • When you scale it out, what the fade function/spread of market maker price is
      • how the act of buying share
  • Long/Short position - is this mathematically different. is there a practical difference that you see.
  • Better use of time - write down math proposals of different versions of conceptualizations
    • One where the market maker bot has an underlying fair value, and a spread around the value
    • Another: percent width around. Ricki to send a doc with scratch notes on what this looks like, and trades under this framework.
• [ ] 4. I'd love to have our own "about" section with the equivalent of what you have here: https://docs.manifold.markets/$how-to ideally editable by me (/Ross/Sydney), though the main changes I'd want to make would be to tweak the language to be atlas/clips specific, and add a couple examples (or even an examples section) which walks through what betting on a question looks like and resolves to
  • What is the best interface, change the language
  • Manifold Dollars to clips, giving an example that has to do a bet they might do, spiekball, names as instructors, aesthetics. Nothing stuck out as incorrect
  • Add a few examples of what it would look like back and forth
    • Add some examples that would help. Also improving market making info-sheet
  • In a perfect world, besides AMM, would have a limit book that let people put their own orders into (just sit as)
    • (very excited about limit orders)
• [ ] 5. It would be nice to be able to "unresolve" markets (maybe via admin privilege), sometimes participants would hit the wrong button by mistake
  • Not necessary. If participant fat-fingered it
  • Effectively undo; totally none

Discord Bot

• Add, Subtract, Give Points

• Action Item: Source Code, Firebase Instance

• Typical invocation of add command: Moderator-configed

  • Add command, validate (can’t add negative),
  • Check user who sent it (if their roleId matches admin role stored in firebase, increment firebase for specified user)

• Role:

  • A tag you can add on many users
  • Instructor Role, Cohort 1 Role, Cohort 2, Cohort 3,
  • When you give points: inside cohorts, can’t add points directly, use give command.
  • User sending it and the sent to have the same cohort
  • No security rules
    • Have to go through discord. Discord Bot - only discord will send events, discord events come from discord
  • Hosted on AWS server that Govind has access to

• Will take care of some admin problems (increasing & decreasing clips)

• Admin role - don’t use Discord Role, use the Manifold role

  • Discord stuff can get confusing,
  • Different cohorts are different instances

• One collection called Guilds

  • Each Guild is a server
    • Each Guild has a users collection, each user has a points field

  

  • Get ID out of Discord thing

Action Items:

• Govind: Integrate Discord and Manifold accounting systems
  • Includes mapping users back and forth
• Ricki: Checking out how the market maker function should work
  • Send Austin a writeup