kjetil/predi
Watch
1
0
Fork
You've already forked predi
 0
Code Issues 24 Pull requests Projects Releases Packages Wiki Activity Actions

Multiple sets of contracts in a market #5

New issue
Closed
opened 2014-11-27 19:18:34 +01:00 by kjetil · 2 comments
kjetil commented 2014-11-27 19:18:34 +01:00 (Migrated from gitlab.lallis.org)
Copy link

Currently a market will contain one set of voteshare contracts. We want to make it possible to have several sets of contracts in each market. This is a necessity for probability markets.

All the data that currently is defined on the market level will apply to one set of contracts. So we need to rename the map called market to contractset or something similar, and then we need a new top level market.

Currently a market will contain one set of voteshare contracts. We want to make it possible to have several sets of contracts in each market. This is a necessity for probability markets. All the data that currently is defined on the market level will apply to one set of contracts. So we need to rename the map called market to contractset or something similar, and then we need a new top level market.
kjetil commented 2014-12-08 22:21:15 +01:00 (Migrated from gitlab.lallis.org)
Copy link

mentioned in issue #15

mentioned in issue #15
kjetil commented 2014-12-18 10:08:15 +01:00 (Migrated from gitlab.lallis.org)
Copy link

Status changed to closed

Status changed to closed
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
master
feature/start-market
feature/ui_performance
feature/alternative_layout
feature/error_messages
feature/image_upload
feature/improve_user_ui
feature/leaderboards
feature/filter
feature/router
feature/rest-api
feature/tagesanzeiger_login
feature/fix_sliders
feature/fix_chart
feature/adminui
feature/jade
i18n
feature/fix_packages
GraphExperiments
1.7.1
1.7.0
1.6.25
1.6.24
1.6.23
1.6.22
1.6.21
1.6.20
1.6.19
1.6.18
1.6.17
1.6.16
1.6.15
1.6.14
1.6.13
1.6.12
1.6.11
1.6.10
1.6.9
1.6.8
1.6.7
1.6.6
1.6.5
1.6.4
1.6.2
1.6.3
1.6.1
Labels
Clear labels   
admin

   
bug

   
confirmed

   
critical

   
discussion

   
enhancement

   
feature

   
long-term

   
technical
No labels
admin
bug
confirmed
critical
discussion
enhancement
feature
long-term
technical
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kjetil/predi#5
No description provided.