skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
adityaakr/polybaskets223 installs

basket-settle

Use when the agent has the settler role and needs to propose a basket settlement via vara-wallet, or needs to finalize an already proposed settlement after the challenge deadline. Do not use for regular user actions.

How do I install this agent skill?

npx skills add https://github.com/adityaakr/polybaskets --skill basket-settle
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill manages blockchain basket settlements using the vara-wallet CLI and data from the Polymarket API. While its core functionality is legitimate, it involves a vulnerability surface where data from an external API is interpolated into shell commands without explicit sanitization, posing a risk of indirect injection.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 2 issues

What does this agent skill do?

Basket Settle

Propose and finalize settlement for PolyBaskets baskets. ProposeSettlement requires the settler role. FinalizeSettlement does not require the settler role, but only works after the challenge deadline has passed.

Setup

MAINNET ONLY. Run vara-wallet config set network mainnet before anything else. NEVER switch to testnet — there are no contracts there.

vara-wallet config set network mainnet
BASKET_MARKET="0xea8373e8b4441ef6e95325c1044d23ebf615b43fdef60a48623836a15ca7a25a"
_PB="${POLYBASKETS_SKILLS_DIR:-skills}"
IDL="$_PB/idl/polymarket-mirror.idl"

Verify Settler Role

Only the address assigned as settler_role in the contract config can call ProposeSettlement.

# Check who has settler role
vara-wallet call $BASKET_MARKET BasketMarket/GetConfig --args '[]' --idl $IDL | jq -r '.result.settler_role'

# Check agent's hex actor id
MY_ADDR=$(vara-wallet balance --account agent | jq -r .address)
echo "$MY_ADDR"

If your address does not match settler_role, you cannot propose a new settlement. You may still finalize an already proposed settlement after challenge_deadline.

Settlement Flow

1. Check basket is Active
2. Verify all items have resolved on Polymarket
3. ProposeSettlement → starts the configured challenge window
4. Wait for challenge_deadline to pass
5. FinalizeSettlement → basket becomes Settled, users can claim

Step 1: Check Basket Status

vara-wallet call $BASKET_MARKET BasketMarket/GetBasket \
  --args '[<basket_id>]' --idl $IDL | jq '.result.ok.status'

Must be "Active".

Step 2: Check Polymarket Resolution

For each item in the basket, check if the market has resolved on Polymarket:

curl -s "https://gamma-api.polymarket.com/markets?slug=<poly_slug>" | jq '.[0] | {closed, outcomePrices}'

All items must be resolved (closed: true) with final prices near 0 or 1.

Step 3: Propose Settlement

Build the item_resolutions array — one ItemResolution per basket item:

{
  "item_index": 0,
  "resolved": "YES",
  "poly_slug": "will-btc-hit-100k",
  "poly_condition_id": "0xabc123...",
  "poly_price_yes": 9900,
  "poly_price_no": 100
}

Rules:

  • Provide exactly one resolution per basket item
  • item_index is 0-based, must be unique, and within basket items range
  • poly_slug must match the basket item's slug exactly
  • poly_price_yes + poly_price_no should reflect final Polymarket prices in bps
  • resolved is the final outcome: "YES" or "NO"
  • poly_condition_id is optional

Example: Propose settlement for a 2-item basket

vara-wallet --account agent call $BASKET_MARKET BasketMarket/ProposeSettlement --voucher $VOUCHER_ID \
  --args '[
    0,
    [
      {
        "item_index": 0,
        "resolved": "YES",
        "poly_slug": "will-btc-hit-100k",
        "poly_condition_id": null,
        "poly_price_yes": 9900,
        "poly_price_no": 100
      },
      {
        "item_index": 1,
        "resolved": "NO",
        "poly_slug": "will-eth-hit-5k",
        "poly_condition_id": null,
        "poly_price_yes": 200,
        "poly_price_no": 9800
      }
    ],
    "Resolved via Polymarket API"
  ]' \
  --idl $IDL

After proposal, the basket enters SettlementPending status and the configured challenge window begins.

Step 4: Wait for Challenge Window

# Check challenge deadline
vara-wallet call $BASKET_MARKET BasketMarket/GetSettlement \
  --args '[<basket_id>]' --idl $IDL | jq '.result.ok | {status, challenge_deadline, proposed_at}'

The challenge_deadline is a block timestamp. The liveness window is configured in BasketMarket/GetConfig.liveness_ms; do not hardcode a duration.

Wait until the current block timestamp exceeds challenge_deadline.

Step 5: Finalize Settlement

vara-wallet --account agent call $BASKET_MARKET BasketMarket/FinalizeSettlement --voucher $VOUCHER_ID \
  --args '[<basket_id>]' --idl $IDL

After finalization:

  • Basket status becomes Settled
  • finalized_at is set
  • Users can now claim payouts via ../basket-claim/SKILL.md

Verify

vara-wallet call $BASKET_MARKET BasketMarket/GetSettlement \
  --args '[<basket_id>]' --idl $IDL | jq '.result.ok | {status, payout_per_share, finalized_at}'

Common Errors

ErrorCauseFix
UnauthorizedNot the settler role for ProposeSettlementCheck config for settler_role address
BasketNotActiveBasket already in settlementCheck status
SettlementAlreadyExistsAlready proposedWait and finalize
InvalidResolutionCountWrong number of resolutionsProvide one per item
ResolutionSlugMismatchSlug doesn't match basket itemUse exact slug from basket
DuplicateResolutionIndexSame item_index twiceMake indices unique
ResolutionIndexOutOfBoundsIndex >= items countUse 0 to items.length-1
ChallengeDeadlineNotPassedToo early to finalizeWait for challenge window
SettlementNotProposedNo proposal existsPropose first

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/adityaakr/polybaskets/basket-settle">View basket-settle on skillZs</a>