Correct social-bet model: held stakes, not escrow/multisig - #20
Merged
Conversation
BankrBot has no escrow, multisig, or custom-market rails. Per docs.bankr.bot/features/polymarket it bets on listed Polymarket markets only (search, bet, positions, redeem) and moves funds by transfer to a handle or address. SKILL.md instructed it to deploy escrow contracts, create 2-of-3 multisigs, and route to custom markets — actions it cannot execute. Rewrite the social-bet path to the honest model: - Listed market first — the only trustless path that exists today. - Otherwise a trust-based side bet: stakes go to an agreed stake-holder via a BankrBot transfer, PolyRobin adjudicates against the agreed resolution statement, settlement is a confirmed human-issued transfer, and the trust assumption is stated up front, never buried. - No holder and no market -> the bet can't be run safely; stand down. Updated: frontmatter description, the "What PolyRobin is (and isn't)" bullet, the Social & Friend Bets section (path selection, tracking/ settlement, worked example, fairness rules), the example command, and the two social-bet edge cases. The only remaining escrow/multisig mentions are explicit negations of those rails. Unchanged: parsing, resolution statement, refusal of ambiguous/ manipulable bets, objective-source requirement, gate-5 confirmation, and the bad-faith guard — none of that value depended on rails that don't exist. Also adds a Changed entry under [Unreleased] in CHANGELOG.md. Validated with scripts/validate.sh. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Why
SKILL.md instructed BankrBot to do three things it cannot do: deploy peer-to-peer escrow contracts, create 2-of-3 multisigs, and route bets to custom Polymarket markets.
Per docs.bankr.bot/features/polymarket, BankrBot's Polymarket support is listed markets only — search, place bets, view positions, redeem — and it moves funds by transfer to a handle or address. It has no escrow, multisig, or market-creation rails. The spec was telling it to perform actions with no underlying capability.
The honest model
Changed
descriptionset up a P2P escrowline)CHANGELOG.md: entry under[Unreleased] → ChangedThe only remaining
escrow/multisigmentions are explicit negations of those rails.Unchanged (the actual value)
Parsing, the resolution statement, refusal to run ambiguous/manipulable bets, the objective-source requirement, gate-5 confirmation, and the bad-faith guard — none of that depended on rails that don't exist.
Validation
./scripts/validate.sh→ all checks pass.No version bump / tag / release — versioning to be decided separately.
🤖 Generated with Claude Code