feat: add follows SDK client#27
Conversation
…on and Signers tests
…ograms, update related configurations and documentation
… to settlement_game_poker, and clarify custody and settlement processes
|
@senamakel is attempting to deploy a commit to the Vezures Team on Vercel. A member of the Team first needs to authorize it. |
|
Warning Review limit reached
More reviews will be available in 26 minutes and 47 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (39)
Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9d2eaf7501
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| record of wins, losses, volume, and net chip movement. No poker action creates an | ||
| x402 payment, smart-contract escrow, on-chain settlement, rake, cashout, or | ||
| real-money payout. |
There was a problem hiding this comment.
Remove x402 poker paths from clients before declaring virtual play
When the backend follows this new virtual-only spec, the current web/SDK flow still treats poker as x402 escrow: useJoinRoom and useRoomAction retry 402 challenges by signing paymentAuthorization, PokerRoom still allows an arbitrary buy-in, and GameRoom still requires escrow/rake and tx-hash fields. That leaves production clients prompting/sending payment data and expecting escrow responses for a virtual fixed-entry room, so joins/actions can fail or render stale state; update those client surfaces in the same change that removes the contracts.
Useful? React with 👍 / 👎.
| PROGRAMS=( | ||
| "escrow:$CONTRACTS_DIR/target/deploy/escrow-keypair.json" | ||
| "settlement_job:$CONTRACTS_DIR/target/deploy/settlement_job-keypair.json" | ||
| "settlement_game_poker:$CONTRACTS_DIR/target/deploy/settlement_game_poker-keypair.json" | ||
| "settlement_game_lottery:$CONTRACTS_DIR/target/deploy/settlement_game_lottery-keypair.json" | ||
| ) |
There was a problem hiding this comment.
Keep removed program IDs reachable for reclaim
When running scripts/devnet/reclaim.sh against an existing devnet deployment from before this change, the script sources this PROGRAMS list and only iterates these two entries, so the already-deployed poker/lottery program accounts are no longer closed even if their keypairs still exist under target/deploy. Those upgradeable programs stay live and their rent remains unrecovered; keep a reclaim-only legacy list or otherwise close them before dropping them from the shared list.
Useful? React with 👍 / 👎.
Summary
client.followsto the TypeScript SDKValidation
pnpm --filter @tinyhumansai/tinyplace buildpnpm --filter @tinyhumansai/tinyplace lintpnpm format && pnpm lint && pnpm build