Come release notes - what changed in v3.4

Release · 17 Aug 2026 Come v3.4

Come v3.4 ships a verified install hint inside the lobby, sharper contest card math and a faster wallet refresh on slow networks. Three named fixes, one verification step.

What changed

Verification

Verified install hint - what to look for

The verified install hint is a small banner that appears on the lobby's first open, above the contest list. Verified: the banner source is the same first-party route the support desk uses, so a green "verified" badge on the lobby means the install came from /install/. Unverified: a yellow badge means the install came from a third-party mirror and the lobby does not have the verified install hint source on file.

Three badges you may see:

• Verified. The install path matches the verified route. The bonus card on the wallet is also unlocked; offers surface normally.
• Pending verification. The install is on a recent build but the package signature has not been confirmed. The hint clears after the next wallet refresh.
• Unverified. The install came from a third-party mirror. The lobby still works, but offers are held and the support desk treats tickets accordingly.

What to check if the lobby doesn't show the hint

If the verified install hint is missing on first open, the most common causes are:

1. Package signature mismatch. The installed package's SHA-256 does not match the published hash at /install/. Re-install from the verified route; the lobby shows the hint on the next launch.
2. Stale wallet state. The wallet has not refreshed since the install. Pull-to-refresh the wallet; the hint clears once the wallet state matches the installed package.
3. Pending KYC. The KYC is still pending. The hint stays hidden until the KYC is complete.

Verified: each of the three checks above is non-destructive - none of them clear bonus balances or withdraw routes. Unverified: a re-install from a third-party mirror clears the verified state, so re-install only from the verified route.

Sharper contest math - what changed on the contest card

The contest card now shows captain pick and vice-captain multipliers beside the prize pool. Verified: the same numbers feed the settlement rule at the end of the match, so the math a user sees on the contest card is the same math the settlement engine reads. Unverified: a contest card that shows different numbers from the settlement rule is a backend error and the support desk will revert the settlement row to the contest card values.

How the sharper contest math is structured:

• Captain multiplier. Captain × 2 is shown next to the captain's name on the contest card. The same multiplier feeds the settlement row at the end of the match.
• Vice-captain multiplier. Vice-captain × 1.5 is shown next to the vice-captain's name on the contest card. The same multiplier feeds the settlement row at the end of the match.
• Other roster. Other roster players are read at face value, with no multiplier. The "other roster" label is on the contest card beside the prize pool.
• Sum rule. The settlement engine sums the adjusted points across the roster, then publishes the total on the settlement row. The sum rule is on the contest card and is not a guess.

Faster wallet refresh - what changed on slow networks

The wallet refresh on Come v3.4 uses an incremental fetch on slow networks. Verified: the cached state stays consistent across deposit and withdraw flows, so a wallet refresh on a slow network returns the same fields as a refresh on a fast network. Unverified: a wallet refresh that returns a partial state is a backend error and the support desk can re-fetch against the snapshot.

How the incremental fetch works on slow networks:

1. Cache hit. The wallet reads the cached state first; if the cached state is fresh, the wallet screen renders without a network call.
2. Incremental fetch. If the cached state is stale, the wallet fetches only the fields that changed since the last refresh. The fetch is bounded by the snapshot timestamp the wallet last read.
3. Reconcile. The wallet reconciles the incremental fetch with the cached state on the user's device. The reconcile is non-destructive; no bonus balance is cleared and no withdraw route is detached.
4. Background refresh. A full refresh runs in the background after the incremental fetch completes. The user sees the incremental state first, then the full state once the background refresh settles.

What to do if the contest card math disagrees with the settlement row

If the contest card math and the settlement row disagree on a settled contest, the most common cause is a backend error rather than a user error. Verified: the support desk can resolve a settlement disagreement against the snapshot. Unverified: a third-party contest card that disagrees with the Come settlement row is not part of the verified surface; the support desk resolves the disagreement on the Come app only.

How to open a settlement ticket:

1. Open the contest card. Write down the contest card math (captain × 2, vice-captain × 1.5, other roster × 1) and the snapshot timestamp on the contest card.
2. Open the settlement row. Write down the settlement row math and the settlement timestamp. The settlement timestamp is on the same row as the total points.
3. Open a ticket at /contact/. Attach the two timestamps and the install route. The support desk can resolve the disagreement against the snapshot.