bodhiproject / bodhi-core Goto Github PK

If there are no winning bets, the losers QTUM will get locked up in the contract.

1. Can a created event information queried correctly?
2. Can an account bet normally before endingBlock?
3. Will the betting be disabled when endingBlock has been mined?
4. Can creator set result correctly?
5. If out of range index is set, what happens?
6. Can winner users withdraw reward normally?
7. Will be loser be prevented to withdraw fund?
8. If a user bet both on all results, will this user withdraw correct fund?

We need to write down what we have discussed on Monday before memory fades away. @dwalintukan could you draw a flow chart to show Oracle flow?

1. Creator use EventCreator to create a following event
   Name: Which team will win in XYZ competition, A or B?
   Result1: A
   Result2: B

2. Other users start to sent ETH (aka. QTUM) to bet on either result.

3. Creator set the result after the competition is finished.

4. Winner users are able to withdraw their betting + winning tokens.

Unable to get the return value from QT wallet.

Do we need to deploy both EventFactory and OracleFactory each time if only one of them change?

• needs same params as Topic
• staking
• choosing result
• revealing result at end of decision block

Might need this after we switch versions to stop any new Events being created, but to allow users to previously withdraw from existing events.

Frank could you define data schema of bodhi-contracts in MySQL? I created an issue in core so we can match it up with contract designs.

keep at index 0 for all result options

All Events needed:

topicEventCreated(...)
voteEventCreated(...)
bettingOnEvent(betterAddr, eventAddr, resultIdx, amout)
resultSetOnEvent(...)
finalResultSetOnTopic(...)

• TopicEvent.getOracle()
• ReentrancyGuard
• getEventName()
• getEventResultName()
• string param in getFinalResult()
• string param in getResult()
• BytesUtils

1. Avoid noises from previous events with the same signature
2. Generic enough to upgrade our smart contract

Per discussion yesterday, we need to create a tutorial to demonstrate topic use case with qtum-qt interface. This will be the very first version of our application. @dwalintukan Let me know if you need my help with this.

This is for the qweb3 side to have named values in the return.
bodhiproject/qweb3.js#15

in EventFactory, name is type: byte32[10]
https://github.com/bodhiproject/bodhi-core/blob/master/contracts/events/EventFactory.sol#L11

in TopicEvent, name is type: string
https://github.com/bodhiproject/bodhi-core/blob/master/contracts/events/TopicEvent.sol#L26

Have a contract that stores all addresses of different contracts:

1. Bodhi Token
2. Oracle
3. etc...

This allows for updating of contracts.

We need to figure out a way to parse out each created topic from Qtum blockchain's blocks so that we can save on sever side and show up on website.

• Add methods to withdraw
• Pass owner address to TopicEvent
• Use onlyOwner modifier for these methods

EventFactory calls AddressManager.getOracleFactory() but can affect the entire flow as it should be paired with the same version that is deployed.