Skip to content

Release: develop -> main - #4

Merged
TaprootFreak merged 4 commits into
mainfrom
develop
May 9, 2026
Merged

Release: develop -> main#4
TaprootFreak merged 4 commits into
mainfrom
develop

Conversation

@github-actions

@github-actions github-actions Bot commented May 7, 2026

Copy link
Copy Markdown

Automatic Release PR

Commits: 1 new commit(s)

  • Review all changes
  • Verify CI passes
  • Merge when ready for production

- risks.md: SP1 CPU prover is live (not mock), keys are encrypted
  (AES-GCM in IndexedDB, not plaintext localStorage)
- wallet.md: add seed phrase + passkey auth options, update feature
  table (encrypted storage, signed sends live), fix API endpoints,
  fix repo URL and package manager (npm not yarn)
- key-management.md: deterministic address derivation (SHA-256 of
  pubkey, no random blinding), encrypted IndexedDB storage, two
  auth methods (BIP-39 + WebAuthn PRF)
- transaction-flow.md: update account creation flow with auth
  method selection and encrypted storage
- tech-decisions.md: SP1 CPU prover in production, mock for dev only
- backend.md: add all 8 API endpoints, update env vars (IS_MAINNET,
  NETWORK_NAME, prover modes)
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented May 7, 2026

Copy link
Copy Markdown

Deploying zkcoins-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: 511160b
Status: ✅  Deploy successful!
Preview URL: https://55e6ea0f.zkcoins-docs.pages.dev
Branch Preview URL: https://develop.zkcoins-docs.pages.dev

View logs

Three-phase plan: human-readable aliases with .well-known/lnurlp
endpoint (Phase 1), full Lightning Address compatibility (Phase 2),
and UMA support for USDT→WUSDT bridging (Phase 3).
- Default address is auto-derived {8-hex}@zkcoins.app, no registration
- Custom username claim is optional with Schnorr signature auth
- Actual API paths (/api/username/resolve, /api/username/claim)
- Hex prefix fallback resolution documented
- Wallet behavior: display, copy, QR all use zkcoins format
- Phase 3 UMA: no $ prefix for default, $ only for UMA compat
@TaprootFreak
TaprootFreak merged commit f49e015 into main May 9, 2026
10 checks passed
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.

2 participants