Betting - 0002 #2
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
This is going to be a lot of fun to use! When we create the wage parameters will there be specific language or how will I essentially say (New York Knicks +2.5 v Boston Celtics for $100)?
Contributor
Author
There was a problem hiding this comment.
I think we could add a recommended format to the RFC for wager descriptions, where it's recommended but not required
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an overview of the standard proposed for the betting metaprotocol. It will need to be refined slightly to be more native to simulacrum, but I believe this captures all the necessary infromation for enabling peer to peer wagering onchain view public intent broadcasting.