Time to claim for initial rep distribution is 6 months before inactivity kicks in

Need to prevent going dormant after already revealed report in second half of period to prevent dormancy to skip rep penalization. And what if I go dormant - do I have to do rbcr and not reporting cr for all past periods? How's that work? Shouldnt have to do during dormant period

Penalization catchup etc for dormant and not dormant rep - make rr be done before converting to and back so no one loses any dormant rep from that beyond the dormant decay rate

Make sure rr up to date before doing dormant back and forth conversions

Dormant rep loses only if round 2 or forking [or maybe just forking?] not reported on [and loss is n% of the y% rep that is dormant], otherwise just gets no fees.

when handling dormant rep stuff:
# if a person reported on a round 2 event, they cannot convert their rep to dormant or send rep until they've finished the resolution process for that round 2 event
# unless this just happened to them last period and they reported correctly then

reportingdone early shouldn't be allowed b/c prevents bonds, num reports/expected may not be needed

is reporting happening on orig. branch for forked events or no? when / if / should a forked event's setmoved be set/ when /if should its branch be moved? which branch do i re report on a forked event on?

• always subtract first before updating / sending stuff, only do that later on

Allow MM to adjust priors mid market per Abe's doc.

Entire codebase needs to be refactored into two sets of contracts:

1. data structures and getters and setters for them
2. business logic functions that call these contracts to get & set data

Post-beta concern (imo) but worth starting to think about.

Pre-loading all markets during the initial UI load will become prohibitively slow as the number of markets grows. These are good candidates for services that could be provided as a separate contract: search/sort are read-only operations and can use eth_call "gas".

Redeem tx needs refactoring and to be put on chain

Making an issue for this because why not

The import syntax makes it a headache to upload contracts manually in the event that load_contracts.py fails. It should be replaced with Serpent's extern syntax.

Use the log sum of exp trick to calculate ls-lmsr at higher numbers in the exp.

So, instead of 1, 2^64, instead of 2, 2*2^64, etc.

- If at anytime after expiry an event's market's odds are <.99, someone can prove it and push it into next reporting period

(and don't allow rbrr for original exp period of this market, actually, don't allow this regardless)

- Should probably still have an option to pay to resolve in case something somehow goes wrong here or people really want a market resolved.

• make fork + round 1 pushback wait 48 hr instead of 24
• make so can't report in last 48 hr of period
• Market has tags, description (where someone has to put a title at minimum), and should have an additional optional information section where they can either put all the additional information they want there and/or add link(s).
• Event has a question and should have a resolution source
• Handle: Report threshold is raised so anyone can report on it if it has no reports in last 24 hr
• if 0 reports on an event either push back or indeterminate?
• want reporters to report on 2x min reports number
• No auto pushback for .5, must be challenged
• add moving events to new period in case fall behind in beta w/ shorter cycles
• When selecting to report make sure based off of total active rep, not including dormant
• finalize rep transfer api
• Assign reporters based on shares outstanding when expiration date arrives, not volume
• when to allow / prohibit trading and how it fits into outstanding shares at the end of a market
• mm pay cost to close markets ahead of time in a fee instead of forcing users to do it: closing gas cost [1.1194M + 1M per addl. event]
• get list of events to report on for a user w/ a call function
• Keep reporters low below some $ in volume amount according to fee on market
  • need to keep track of amount of fees charged in a market for this
  • calc. # of reporters per outstanding shares [old version was volume]
  • calc. ability to pay for reporting fees calculated from fees from market for how many reporters it can pay for
  • whichever is less is # of reporters targeted towards the market
• it should be exactly what is needed for reporters to report on the market should no traders show up:
  • (decent labor compensation rate for reporters) + (gas cost for these reporters)
  • (Initial_Liquidity_Requirement * 0.5 * Fee) + Base_Reporter_Quantity * (Gas cost of commit [1.055M] + Gas cost of reveal [1.358M] + Gas cost of penalize [1.08M])
• multiple of adj. cost for appeal bond?
• round 2 bond cost discussion
• make sure round 2 bond formulas correct
• make sure reporting selection formula correct
• reporting penalty based on market size? round 1 penalties at all? reporting penalties change/make less severe [see V discussion]
• check for anything called that should take sender as a param but doesn't atm
• users for min(30, numevents) when reporting paid to report... hmmm
  • Gas rewards to reporters as in minimum creation fee used to directly pay people who reported on a given event for gas fee rebates. Make sure to account for how many a market has paid for already and cap it at that
  • penalization catchup - what if actually not selected to report
  • prove voted on less than actually could have and <.5 of shouldve
  • must report on max(selected estimate/2, 1 if actually selected)
  • if couldve reported on more to meet .5 or max req above but didnt lose rep if someone proves it
  • need at least 1 rep to vote
  • only commit for round 2 and fork events perhaps?
• Handle penalization automatically so UI doesn't have to (how to do in case of fork or round 2 event?). If these aren't done you can't send rep, convert rep, or report
  • penalizeNotEnoughReports(branch) - once in first half of a period per reporter, so if not done do that
  • closeMarket if event doesn't have an outcome via EVENTS.getOutcome(event) yet. Closing any one market associated w/ the event [you can get a list of markets associated w/ an event via getMarkets(event)] will finalize the event's outcome. And round 2 resolve for those events
  • penalizeWrong(branch, event) for each event reported on in first half of a period
  • do penalizationCatchup(branch) if further behind automatically in submitreporthash or any of the rep sending / converting functions
  • collectFees(branch) - once in second half of a period [so during first submit report]
  • round 2 penalize rep sending etc

  • todo: make it 0.98 * old rep + 0.02 * new rep

  • (1-k) * old rep + k * new rep where k = 0.2 / (number of events you reported on last period) for penalization and pen. rate for forking and backstop 1

• go over any various todos i missed
• msg.sender vs tx.origin
• Handle 1.5 vs .5 vs .5 in fxp + 1 for binary, scalar, and categorical events
• other tests where api changed
• make exp events data struct more efficient
• categorical .5 single market handling
• ph note
• pushed forward round 2 / fork handling

Refactor:

• markets.se
• consensus.se [and make cheaper]
• backstops.se [and make cheaper]
• buy&sellshares.se
• closemarket.se
• createmarket.se
• forking.se [and make cheaper]
• makereports.se
• marketcreatortrading.se

Check that the market actually has that outcome as a possible outcome when buying/selling.

Need to check / make sure can’t break anything by using an invalid input

Test claim initial rep for a fork

Below are some market methods i wrote in the demo-stub contact object while flushing out the UI design and functionality in the past few weeks. These either need to exist in some fashion or alternatives created. Some of these can be stored in a RESTful document data store like MongoDB. They are broken up like this with the limitations of evm data fetching in mind, but if put somewhere else, i would ideally combine them as they are most often (always?) fetched together when getting a market.

// placing here for for demo purposes
getMarketComments: function(id) {
   return demo.markets[id]['comments'];
},
getMarketHistory: function(id) {
   return demo.markets[id]['priceHistory'];
},
getMarketVolume: function(id) {
   return demo.markets[id]['volume'];
},
getMarketShares: function(id, account) {
   return demo.markets[id]['sharesHeld'][account];
}
getMarketImage: function(id) {
   return demo.markets[id]['imageUr'];
}

When I try to run test_load_contracts.py, I get this error:

(master) jack@vent:~/src/augur-core/tests$ ./test_load_contracts.py 
Setting up node environment.
  Cloning go-ethereum
  Building geth
  Done
Starting node. To open a console:
  geth attach rpc:http://localhost:9696
Mining coins...
python: can't open file 'load_contracts.py': [Errno 2] No such file or directory
Traceback (most recent call last):
  File "./test_load_contracts.py", line 124, in <module>
    test_compile_imports()
  File "./test_load_contracts.py", line 89, in test_compile_imports
    '-s', 'foobar'])
  File "/usr/lib/python2.7/subprocess.py", line 540, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['python', 'load_contracts.py', '-C', '.', '-p', '9696', '-b', '2', '-d', 'test_load_contracts.json', '-s', 'foobar']' returned non-zero exit status 2

(As opposed to doing them for all traders at once)

Block.number needs to be added to both createEvent & createMarket again once web3.js callbacks are working (or UI uses Jack's script)

Get gas cost for all these to < a penny or < 1/10th a penny ideally.

Allow trading fee adjustment

Locking in fees when trading/buy/sell?

Allow generalization of OST to create more than one tree within the same contract.

Confirm that they work as intended

add creation date to market

createMarket should accept an array of initial shares

Store report/no-report separate from the matrix of report values, to disambiguate the absence of a report (0) from a numerical answer of 0.

Logs need to be created for contracts to provide useful data to UI

load_contracts.py gets stuck on the expiringEvents contract.

since the core has changed a bunch recently and these were working just fine before then, i'm assuming that this issue goes here.

Bad POW macro returns 1 no matter what on chain

Handle market moving to a new fork after the network forks.

Switch everything using cash to using generic subcurrencies once the new subcurrency API is final
remove setcash/add/remove cash when doing this

• tx.origin vs msg.sender

The new many-contracts data model needs to be integrated with the redeem and consensus contracts.

savvy traders will want price history and lovely graphs