Skip to content

Fix/privacy chain followups - #196

Merged
ByteZhang1024 merged 9 commits into
mainfrom
fix/privacy-chain-followups
Nov 4, 2026
Merged

ByteZhang1024 merged 9 commits into
mainfrom
fix/privacy-chain-followups

Conversation

@ByteZhang1024

Copy link
Copy Markdown
Contributor

No description provided.

@ByteZhang1024
ByteZhang1024 deployed to runtime-npm-publish November 3, 2026 14:27 — with GitHub Actions Active
Accounts left out of a sync step are recorded in ext_onekey_paused_accounts.
The scan floor becomes the earliest birthday of the accounts still scanning:
scanning, remaining work and spendability follow it, while queue pruning and
witness stabilization still use every account's birthday, so a paused
account's history stays queued and resumes intact.
@ByteZhang1024
ByteZhang1024 deployed to runtime-npm-publish November 3, 2026 19:15 — with GitHub Actions Active
@sidmorizon

Copy link
Copy Markdown
Contributor

Devin Cloud review ↗

@ByteZhang1024
ByteZhang1024 enabled auto-merge (squash) November 4, 2026 09:28
@ByteZhang1024
ByteZhang1024 merged commit 5802d48 into main Nov 4, 2026
19 checks passed
@ByteZhang1024
ByteZhang1024 deleted the fix/privacy-chain-followups branch November 4, 2026 10:22

This branch was successfully deployed

1 active deployment
runtime-npm-publish — 61a33bf5 Deployed Nov 3, 2026 by ByteZhang1024 via publish #22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants