some advice on compulsory payout systems

[Altoidnerd]

hey guys. What angle can I take if I want to design a trustless fantasy sports application.

The idea is that people can compete in fantasy leagues without knowing one another, and be able to know with certainty that payouts will depend only on API calls to a given league or some layer the user interacts with... whatever that may be.

The backend though.  I could of course design something that collects inputs and mixes them and is a regular cryptobank...and then users would need to hope to not be goxxed.

How can I do better though.  I am aware of locktime...but going further, is there a way to delay outputs so that their destination can depend on some external data, like the result of a sporting event, in such a way that the tx scrips exist, but are waiting to complete...like even before the result of [the game, the league, etc].  Multisig?  

Would appreciate a stern talkin' to.  Thanks in advance.

[1713536805]

1713536805

[Altoidnerd]

Ok how about this.  Multisig payouts to all parties are written and broadcasted, but only one of them [or the correct set of them ] will actually execute and the rest expire?

Not sure if there is such a thing as expiration.  Guessed there.

Edit: no wait.  only the right one is broadcast in the end, the rest discarded? or? is that how this could go?  I'm lost.  I'm missing a critical piece here...help a brother understand.

Edit2: wait for etherium?