Functions:
* Client Servers:
  * onboarding, account management
  * feeds clients with data extracted from network (BitShares nodes).
* Admin Servers:
  * create and aprove match proposals
  * keep settings and inject them into op memos
    * settings include child tokens for each match and trusted feeders
    * feed prices

Due the need of multiple tokens for each match, meaning the need to keep dozens of them running concurrently, i'm embrace the idea of reusing of tokens and to use normal market operations combined with GS mechanism. There will be time to retract and switch to prediction markets if they turn to be a better solution. (another reason to use normal tokens is to avoid blockchain polution with past matches ).

Byproduct of the websockets comm with nodes:
https://gitlab.com/vanissoft/profit-way

Takes every market in a token list and prints the profitable ones.
In the code there is also a seminal bot.

Making use of Litepresence's manualSIGNING to try async operative.

* listener app sends updates to d*match node
* node broadcasts to connected clients
* client send signed ops to btshares node

added video in screenshots post with a live session although random data.

Hi Elias, welcome to the board.

This is a great initiative to bring the functions of the prediction market to the average users!

Does the PM allow a different betting ratio than 1:1?

You are setting up a own full node only for PM?

Hi!   
The ratio comes from the market operations: As i'm going forward i'll make some assumptions (some may be wrong). At this moment i understand that buying an option at 0.1 is like back x10 while the inverse is borrowing and selling at 0.9, thus an x1.9 ratio for lay (and x1.1 for back at the buyer side).
For the lay bet (betting a result of 0), more than x1.9 would require another asset representing the inverse side. Thus two markets, one for back and another for lay.

As i don't have nor the hardware neither the ability to operate a node, i have to develop having in mind to be a good companion for a node. The idea is to bring a new interpretation of the blockchain data rather than modify the protocol to adapt to this use case.

cheers

Hello, Elias here.
I wish to experiment how long can i reach in develop a betting app with BitShares prediction markets.

Intro

There is almost nothing definitive but the tech:

• UI will be a mobile app, with Cordova, MobileUI, Javascript and Brython
• Development backend server with Python, UVIcorn, Starlette, FastAPI(
• Backend will facilitate the managing of markets

Vision

* Transparent betting app.
* Node companion server to avoid bloating core-api.
* Manager for betting setups, storing status in asset description.
* Hierarchical dependency of prediction market assets to allow multi-choice bets.

Work notes

* My work is based on design aproach "bi-directional top-down", being "top" the user experience and "down" the tech ground.
* Multiple programing patterns. Although i always begin with procedural with gradual refactor to oop when the code matures.
* Python centric. Always can be a time for C migration, although not in my interest.
* Aside note: Too wide opened mind and prone to break things. Thus bad core developer.

---

Short introduction of me:
* Member of community since 2017. Fall in love with a mature project that just works.
* My first personal project failed by not being able to get in sync with the blockchain and unclear goals.
* The second project (monotoken (smartasset wallet)) failed for not being according to locals laws.
* This is my third project.   



This post along screenshot post will be refreshed periocally in order to reflect status.

v.0.next
* talking with nodes
* market setups
* etc....

v.0.1.1.
* Observable pattern done in brython (Mirroring UI with atributes changes).
* Selecting bets and adding to the betslip.
 
v.0.1
* Foundation for API tech
* Foundation for UI tech