So for the actual voting, there will not be a smart contract. So there is no transaction per vote.
The oracle platform I want to make initially will be a centralized application. That’s okay. That’s just to prove the concept of the decentralized/distributed supply.
The only transactions that happen (I think) are when an account needs to be slashed, and when a truth needs to be told.
My oracle platform works with a voting system. People vote on the “truth” of something in the real world.
But there are different types of truths and I wanted to be sure I covered all my bases and a that I’ve thought of the best ways to accommodate the format of both.
So there are “one time truths”, like “Who won the basketball game on October 31st?” That will be decided one time.
But then there are “ongoing truths”. “What’s the weather at location x,y,z?”
For the first, I can imagine that participants in the voting process will have to vote on what they’ve observed by a certain time. After that, anyone who hasn’t voted or voted incorrectly against the majority is slashed.
For the second, I imagine a “window of time” to submit answers and potentially a “tolerance gradient” associated with slashing.
I think I could be missing another concept for time. There’s “once” and “ongoing”. Maybe there’s something else. Assuming a voting system is always fair, what else can oracles do? What other rules systems need to be implemented?