BOS redesign - scope #11

New issue

Closed

opened 2020-06-19 20:12:51 +00:00 by bobinson · 4 comments

bobinson commented

2020-06-19 20:12:51 +00:00

(Migrated from gitlab.com)

Redesign Bookie Oracle Suite (BOS) in such a way that the current software can be seamlessly replaced without making changes to the Bookie-Exchange dApp. All the components of the BOS - Feed providers, Data Proxy, as well as the BOS components must be replaced with emphasis on decentralised, trust-less solution that works with little or no manual intervention. The sports data collection which is now handled by fetching data from feed providers must be changed with a crowd-sourced solution. The data thus collected will include match specific data as well as the match schedules (represented by BookieSports) will have to be collected, cleaned and sent to the chain for processing. Storage requirements of the chain or the witnesses should not increase dramatically and the data collected must be stored in separate indexes. Bookie-Exchange dApp uses various prediction markets related to sports and are represented on the chain. Changes to the chain data structures should be avoided to ensure seamless integration with Bookie-Exchange dApp.

Definitions

Well formed data : Conscience and final event (sports) data that can be used decide outcomes without disputes.

Betting Markets, Market groups : Refer BOS documentation

Interfaces to be provided

Collect external sports data
Expose an interface to send cleaned, well formed data to the chain

Action items

Provide means to collect sports data
Economics ensuring the sustainability of data providers
Ensure authenticity of the data collected using the wisdom of the crowd
The manual intervention which is handled with MINT module should be made minimal as possible.
The peer verified data must be presented to the chain as proposals

UI suggestions

There must be intuitive UI which must be using TLS-PKI provided by the Peerplays blockchain as opposed to the traditional CAs. The UI itself is out of scope but the technical interface design instructions must be provided.

Deliverables

Detailed Design document with all the interfaces and action items clearly defined. This design can be used as a developers to re-design BOS & all associated components.

References:

https://www.peerplays.tech/bookie-oracle-suite-bos/intro-bos

https://peerplays.atlassian.net/wiki/spaces/PROJECTS/pages/1933348/Bookie

Status: awaiting review from @jbahai & @whelaneoin

Redesign Bookie Oracle Suite ([BOS](https://www.peerplays.tech/bookie-oracle-suite-bos/intro-bos)) in such a way that the current software can be seamlessly replaced without making changes to the Bookie-Exchange dApp. All the components of the BOS - Feed providers, Data Proxy, as well as the BOS components must be replaced with emphasis on decentralised, trust-less solution that works with little or no manual intervention. The sports data collection which is now handled by fetching data from feed providers must be changed with a crowd-sourced solution. The data thus collected will include match specific data as well as the match schedules (represented by BookieSports) will have to be collected, cleaned and sent to the chain for processing. Storage requirements of the chain or the witnesses should not increase dramatically and the data collected must be stored in separate indexes. Bookie-Exchange dApp uses various prediction markets related to sports and are represented on the chain. Changes to the chain data structures should be avoided to ensure seamless integration with Bookie-Exchange dApp. ## **Definitions** **Well formed data** : Conscience and final event (sports) data that can be used decide outcomes without disputes. Betting Markets, Market groups : Refer BOS documentation ## **Interfaces to be provided** - Collect external sports data - Expose an interface to send cleaned, well formed data to the chain ## **Action items** - Provide means to collect sports data - Economics ensuring the sustainability of data providers - Ensure authenticity of the data collected using the wisdom of the crowd - The manual intervention which is handled with MINT module should be made minimal as possible. - The peer verified data must be presented to the chain as proposals ## **UI suggestions** There must be intuitive UI which must be using TLS-PKI provided by the Peerplays blockchain as opposed to the traditional CAs. The UI itself is out of scope but the technical interface design instructions must be provided. ## **Deliverables** Detailed Design document with all the interfaces and action items clearly defined. This design can be used as a developers to re-design BOS & all associated components. **References:** https://www.peerplays.tech/bookie-oracle-suite-bos/intro-bos https://peerplays.atlassian.net/wiki/spaces/PROJECTS/pages/1933348/Bookie Status: awaiting review from @jbahai & @whelaneoin

bobinson commented

2020-06-19 20:13:57 +00:00

(Migrated from gitlab.com)

changed the description

bobinson commented

2020-06-19 20:46:22 +00:00

(Migrated from gitlab.com)

changed the description

bobinson commented

2020-06-24 17:32:48 +00:00

(Migrated from gitlab.com)

assigned to @nathanhourt