NEWT-176 (Threshold Decryption with Feldman VSS) is now complete. The dkg module implements the full threshold
HPKE decryption pipeline:

1. dealer.rs — Feldman VSS: trusted dealer generates polynomial, evaluates shares at operator indices, publishes
   commitments for verification. Horner's method for polynomial evaluation.
2. dleq.rs — Non-interactive DLEQ proofs via Fiat-Shamir with SHA-256. Each operator proves log_G(pk_i) ==
   log_{enc}(D_i) — same secret share used for both their public key and partial decryption. This is the foundation
   for slashing (NEWT-629): a bad DLEQ proof is cryptographic evidence of misbehavior.
3. combine.rs — Lagrange interpolation in the exponent. The gateway combines t valid partial decryptions D_i = s_i

• enc into the full DH output sk * enc without ever reconstructing the master secret. This feeds into
  decrypt_with_precomputed_dh (NEWT-638) to complete the post-DH HPKE pipeline.
  ─────────────────────────────────────────────────

Here's the status of the critical path:

┌──────────┬────────────────────────────────────┬─────────────────┐
│ Ticket │ Description │ Status │
├──────────┼────────────────────────────────────┼─────────────────┤
│ NEWT-638 │ HPKE decrypt_with_precomputed_dh │ Done (10 tests) │
├──────────┼────────────────────────────────────┼─────────────────┤
│ NEWT-176 │ Threshold Decryption (Feldman VSS) │ Done (28 tests) │
├──────────┼────────────────────────────────────┼─────────────────┤
│ NEWT-178 │ Two-Phase Consensus Integration │ Next │
├──────────┼────────────────────────────────────┼─────────────────┤
│ NEWT-630 │ On-chain Aggregation Commitments │ Pending │
├──────────┼────────────────────────────────────┼─────────────────┤
│ NEWT-629 │ Privacy-specific Operator Slashing │ Pending │
└──────────┴────────────────────────────────────┴─────────────────┘

Next step is NEWT-178: integrating threshold decryption into the Two-Phase Consensus Prepare phase. This involves
modifying the gateway to distribute key shares to operators, collect partial decryptions during the Prepare phase,
combine them via Lagrange interpolation, and then decrypt the HPKE ciphertext before broadcasting plaintext in
the Commit phase. Want me to proceed?

Done (code changes):

┌─────┬─────────────────────┬──────────────────────────────────────────────────────┐
│ # │ Item │ Status │
├─────┼─────────────────────┼──────────────────────────────────────────────────────┤
│ │ Google Search │ │
│ 1 │ Console │ Added to docs.json │
│ │ verification tag │ │
├─────┼─────────────────────┼──────────────────────────────────────────────────────┤
│ 2 │ Image alt text │ Fixed iframe title (about.mdx) + 3 token chart │
│ │ audit │ images │
├─────┼─────────────────────┼──────────────────────────────────────────────────────┤
│ │ │ Already correct (Mintlify auto-generates FAQPage │
│ 3 │ FAQ page schema │ JSON-LD from Accordion pattern). Fixed stale mainnet │
│ │ │ reference, added keywords. │
├─────┼─────────────────────┼──────────────────────────────────────────────────────┤
│ │ │ Design task — frontmatter ready, needs image assets │
│ 4 │ Per-page OG images │ created (1200x630px) for quickstart, about, │
│ │ │ core-concepts, integration-guide │
├─────┼─────────────────────┼──────────────────────────────────────────────────────┤
│ 5 │ External backlinks │ Added Documentation section with 4 links to │
│ │ — README │ docs.newton.xyz │
├─────┼─────────────────────┼──────────────────────────────────────────────────────┤
│ 5b │ External backlinks │ Action item for you — add links from newton.xyz to │
│ │ — landing page │ use-case pages and quickstart │
├─────┼─────────────────────┼──────────────────────────────────────────────────────┤
│ 6 │ Content gap │ Pending — needs Search Console data (available ~1 │
│ │ analysis │ week after verification) │
├─────┼─────────────────────┼──────────────────────────────────────────────────────┤
│ 7 │ Old domain │ Already handled — 301 from docs.newt.foundation → │
│ │ redirects │ docs.newton.xyz confirmed │
└─────┴─────────────────────┴──────────────────────────────────────────────────────┘

Your next steps:

1. Complete Search Console setup — go to search.google.com/search-console, add
   https://docs.newton.xyz, verify with the meta tag (will deploy with this PR), then
   submit sitemap https://docs.newton.xyz/sitemap.xml
2. Create per-page OG images for the 4 high-traffic pages (or delegate to design)
3. Add backlinks from newton.xyz landing page to docs use-case pages
4. In ~1 week, check Search Console for content gap opportunities

⏺ That's the most effective method. Google will fetch and index the sitemap within the
next few hours. You can check back in Search Console tomorrow — the sitemap status
should update to "Success" and you'll start seeing pages in the index.

In the meantime, everything on our end is done. Here's the final status:

Completed:

• Per-page SEO metadata (titles, descriptions, keywords) across all pages
• 3 new use-case pages (institutional DeFi, stablecoins, agent security)
• Content flow optimization on 4 high-traffic pages
• Internal cross-linking throughout docs
• Google Search Console verified + sitemap submitted
• Image alt text fixed
• FAQ page keywords + stale content fixed
• README backlinks to docs.newton.xyz
• Domain redirect (docs.newt.foundation → docs.newton.xyz) confirmed

Follow-ups (non-code):

• Recheck sitemap status tomorrow in Search Console
• Per-page OG images (design task)
• Landing page backlinks to docs use-case pages
• Content gap analysis (~1 week, once Search Console has data)

1. Stale URLs — docs.newt.foundation should be docs.newton.xyz

The domain has migrated (301 redirect confirmed), but the landing page still hardcodes
the old domain in 5 places in site.config.ts:

┌─────────────────────┬────────────────────────────────────────────┬───────────────┐
│ Location │ Current URL │ Should be │
├─────────────────────┼────────────────────────────────────────────┼───────────────┤
│ nav.items[0] (Quick │ docs.newt.foundation/developers/overview/q │ docs.newton.x │
│ Start) │ uickstart │ yz/... │
├─────────────────────┼────────────────────────────────────────────┼───────────────┤
│ nav.items[0] │ docs.newt.foundation/developers/overview/a │ docs.newton.x │
│ (Documentation) │ bout │ yz/... │
├─────────────────────┼────────────────────────────────────────────┼───────────────┤
│ trustModel.ctas[1] │ docs.newt.foundation/developers/overview/a │ docs.newton.x │
│ (Learn more) │ bout │ yz/... │
├─────────────────────┼────────────────────────────────────────────┼───────────────┤
│ policyCapabilities. │ docs.newt.foundation/developers/advanced/p │ docs.newton.x │
│ ctas[1] (Learn │ olicy-data-oracles │ yz/... │
│ more) │ │ │
├─────────────────────┼────────────────────────────────────────────┼───────────────┤
│ footer.columns.Deve │ docs.newt.foundation/ │ docs.newton.x │
│ loper[0] (Docs) │ │ yz/ │
└─────────────────────┴────────────────────────────────────────────┴───────────────┘

The 301 redirect works, but this hurts SEO (redirect chains lose link equity) and adds
latency.

2. Missing backlinks to docs use-case pages

The UseCases section has 5 items but none link to the corresponding docs pages. These
are the backlinks we discussed:

┌───────────────────┬───────────────────────────────────────────────────────────────┐
│ Use Case │ Should link to │
├───────────────────┼───────────────────────────────────────────────────────────────┤
│ Stablecoins & │ docs.newton.xyz/developers/use-cases/stablecoins-and-payments │
│ RWAs │ │
├───────────────────┼───────────────────────────────────────────────────────────────┤
│ Institutional │ docs.newton.xyz/developers/use-cases/institutional-defi │
│ DeFi & Vaults │ │
├───────────────────┼───────────────────────────────────────────────────────────────┤
│ AI Agent Commerce │ docs.newton.xyz/developers/use-cases/agent-security │
└───────────────────┴───────────────────────────────────────────────────────────────┘

3. "Trusted By" includes Magic Labs

logos.items lists Magic Labs alongside EigenLayer, Base, and M0. Magic Labs is the
parent company — listing it as "Trusted By" is self-referential. Consider replacing
with an actual customer/partner, or changing the heading to "Ecosystem" or "Built
With".

4. No developer CTA on the main page

The page is entirely enterprise/business oriented. The "Build" dropdown links to docs,
but there's no visible developer section or code snippet on the landing page itself.
The docs site about page has a code snippet — a similar one on the landing page could
attract developer traffic directly.

5. CTA buttons don't include docs quickstart

Both CTA groups (ValueProp and CTABanner) offer "Talk to an expert" + "Download
Whitepaper". There's no "Start Building" or "Try Quickstart" CTA anywhere on the page
body. The "Try Demo" is only in the header nav. For developers landing on newton.xyz,
the path to getting started is buried in a dropdown.

6. Market stats may be stale

The marketStats.items values ($298B+ stablecoin cap, $700B+ monthly volume, $21B+ RWA,
$206B compliance costs) are static. These are likely from when the page was built.
Worth verifying they're still accurate — stablecoin market cap has been growing
rapidly.

7. Missing narratives

• No mainnet mention — if mainnet is live (per the docs update), the landing page
  doesn't call this out. A "Live on Mainnet" badge or announcement could build
  credibility.
• No usage/traction metrics — no numbers about tasks evaluated, policies deployed, or
  operators active. Even testnet metrics would add social proof.
• No NEWT token section — the token is only mentioned in the announcement banner. For a
  protocol with a live token, this feels like a gap. Even a brief section or footer
  reference to tokenomics/staking would help.
• No regulatory framework detail — the "Why Now" section mentions GENIUS Act, MiCA,
  FATF Travel Rule but doesn't explain what Newton does for each. A brief mapping
  (regulation → Newton capability) would strengthen the narrative.

8. Minor content issues

• howItWorks.steps[1].description: "Adding a lightweight snippet" — should be "Add a
  lightweight snippet" (imperative, consistent with other step titles)
• announcement.text: "Staking $NEWT? Looking for Newton agents?" — two unrelated
  questions in one banner. Could be clearer.
• explorer.newt.foundation links (trustModel, footer) — should these also migrate to
  explorer.newton.xyz?

Want me to start fixing these? The URL migration (#1) is the most impactful and
quickest to execute.

✻ Sautéed for 1m 18s

❯ Note that @/projects/landing-page/ also has its own agent files in
@/projects/landing-page/.claude folder and @/projects/landing-page/CLAUDE.md,
following the same agent file management structure/rules as in this repo or other newton
project repos like @/projects/newton-prover-avs/ or
@~/projects/newton-prover-avs-deploy/, etc.
⎿  Listed directory ../landing-page/
⎿  Listed directory ../landing-page/.claude/
⎿  Read ../landing-page/CLAUDE.md (121 lines)
⎿  Listed directory ../newton-prover-avs/
⎿  Listed directory ../newton-prover-avs-deploy/
⎿  Async hook Stop completed

⏺ Understood — the landing-page repo has its own fully set up agent files. Since the most
impactful fix is the URL migration (#1 from my review), and those changes would be in
the landing-page repo, do you want me to switch over to ~/projects/landing-page/ and
start fixing those stale docs.newt.foundation URLs in site.config.ts? That's a quick
win that improves SEO link equity and eliminates redirect latency.

Or would you prefer to tackle these in a specific order / prioritize certain items from
the review?

❯ First, draft and present a full plan with your in-depth analysis on what we should do
to improve the landing page (landing-page repo) or the developer docs (this repo). And
if all task items are for the landing page, then yes lets switch over to
~/projects/landing-page/ and start fixing those stale docs.newt.foundation URLs in
site.config.ts
⎿  Async hook Stop completed

⏺ Here's the full plan, split by repo:

Newton SDK repo (this repo) — No remaining items

All docs site work is complete. SEO metadata, content flow, cross-linking, Search
Console, image alt text, README backlinks — all shipped in PRs #128 and #129.

Landing Page repo (~/projects/landing-page/) — All items below

Critical (SEO/functionality impact)

┌─────┬────────────────────────────────┬────────────────┬──────────────────────────┐
│ # │ Item │ File │ Impact │
├─────┼────────────────────────────────┼────────────────┼──────────────────────────┤
│ │ Migrate all │ │ 5 links forcing 301 │
│ 1 │ docs.newt.foundation URLs to │ site.config.ts │ redirects — hurts SEO │
│ │ docs.newton.xyz │ │ link equity, adds ~100ms │
│ │ │ │ latency per click │
├─────┼────────────────────────────────┼────────────────┼──────────────────────────┤
│ │ Check if │ │ 2 links (trustModel CTA, │
│ 2 │ explorer.newt.foundation │ site.config.ts │ footer) — same redirect │
│ │ should also migrate │ │ concern │
└─────┴────────────────────────────────┴────────────────┴──────────────────────────┘

High (content/narrative gaps)

#: 3
Item: Add backlinks from use-case cards to docs use-case pages
File: site.config.ts (useCases items)
Impact: Direct SEO backlinks to new docs pages; gives users a "learn more" path from
each use case
────────────────────────────────────────
#: 4
Item: Add a developer-oriented CTA in CTA sections
File: site.config.ts (valueProp.ctas or ctaBanner.ctas)
Impact: Currently both CTA groups are enterprise-only ("Talk to expert" +
"Whitepaper").
Adding "Start Building" → quickstart would serve developer traffic
────────────────────────────────────────
#: 5
Item: Fix "Trusted By" — remove or reposition Magic Labs
File: site.config.ts (logos.items)
Impact: Self-referential — Magic Labs is the parent company, not an external trust
signal. Move to "Built By" section or replace with an actual partner

Medium (content accuracy/freshness)

#: 6
Item: Fix grammar: "Adding a lightweight snippet" → "Add a lightweight snippet"
File: site.config.ts (howItWorks.steps[1])
Impact: Inconsistent with imperative voice in other steps
────────────────────────────────────────
#: 7
Item: Verify market stats are current
File: site.config.ts (marketStats.items)
Impact: $298B stablecoin cap, $700B monthly volume, $21B RWA, $206B compliance — need
to
verify these haven't shifted significantly
────────────────────────────────────────
#: 8
Item: Add "Live on Mainnet" signal
File: site.config.ts (announcement or hero)
Impact: If mainnet is live, the landing page should say so. Currently no mention
anywhere.

Low (nice-to-have improvements)

#: 9
Item: Add regulation → capability mapping to "Why Now" section
File: Section component or site.config.ts
Impact: GENIUS Act, MiCA, FATF Travel Rule are mentioned but not mapped to what Newton
does for each
────────────────────────────────────────
#: 10
Item: Add NEWT token section or reference
File: site.config.ts
Impact: Token only appears in announcement banner. A brief staking/tokenomics mention
could help with token-related search traffic
────────────────────────────────────────
#: 11
Item: Clarify announcement banner
File: site.config.ts (announcement.text)
Impact: "Staking $NEWT? Looking for Newton agents?" — two unrelated questions. Could be

more focused

All 11 items are in the landing-page repo. Items 1-2 are pure site.config.ts URL
changes I can fix immediately. Items 3-6 are also site.config.ts content changes. Items
7-11 need your input on content/direction.

Want me to switch to ~/projects/landing-page/ and start executing items 1 through 6?

Committed and pushed to main: 789d87a.

Changes in this commit:

• Updated 3 market stats (stablecoin cap $313B+, monthly volume $4T+, RWA $25B+)
• Softened "FATF Travel Rule" → "FATF sanctions screening"
• Simplified banner to demo-focused CTA

All landing page items are resolved. Remaining follow-ups:

┌─────┬─────────────────────────────────────┬──────────────────────────────────┐
│ # │ Item │ Status │
├─────┼─────────────────────────────────────┼──────────────────────────────────┤
│ 8 │ "Live on Mainnet" signal │ Follow up after launch next week │
├─────┼─────────────────────────────────────┼──────────────────────────────────┤
│ 10 │ NEWT token prominence │ Hold — tokenomics TBD │
├─────┼─────────────────────────────────────┼──────────────────────────────────┤
│ — │ Per-page OG images │ Design task │
├─────┼─────────────────────────────────────┼──────────────────────────────────┤
│ — │ Search Console content gap analysis │ Check in ~1 week │
├─────┼─────────────────────────────────────┼──────────────────────────────────┤
│ — │ Recheck sitemap indexing │ Check in ~1 week │
└─────┴─────────────────────────────────────┴──────────────────────────────────┘

Committed and pushed: 7fbc267 — 12 files changed, 80 insertions, 251 deletions.

Changes included:

• SDK reference: removed fake exports, fixed error enums, corrected constructor
  signatures
• Gateway URLs: migrated all newt.foundation → newton.xyz across 6 docs pages
• License: MIT → Apache-2.0 in package.json
• README: fixed evaluateIntent → evaluateIntentDirect, added missing apiKey param
• Explorer URL: explorer.newt.foundation → explorer.newton.xyz

Remaining follow-ups:

• Mainnet signal — add "Live on Mainnet" after launch (this week)
• NEWT token prominence — hold until tokenomics finalized
• Dependabot alerts — 11 vulnerabilities flagged by GitHub (7 high, 3 moderate, 1 low)
• Search Console — recheck sitemap indexing in ~1 week