Merge main into remaining appraisal spend helper

Author: karagozemin

.github/workflows/bindings-check.yml

@@ -5,6 +5,11 @@ on:
     branches: [main]
   pull_request:
 
+permissions:
+  # Los cuatro workflows solo leen el repo: clonan, instalan y corren
+  # tests. Ninguno hace push, ni comenta, ni publica, ni toca secrets.
+  contents: read
+
 concurrency:
   group: ${{ github.workflow }}-${{ github.ref }}
   cancel-in-progress: true

.github/workflows/contract.yml

@@ -5,6 +5,11 @@ on:
     branches: [main]
   pull_request:
 
+permissions:
+  # Los cuatro workflows solo leen el repo: clonan, instalan y corren
+  # tests. Ninguno hace push, ni comenta, ni publica, ni toca secrets.
+  contents: read
+
 concurrency:
   group: ${{ github.workflow }}-${{ github.ref }}
   cancel-in-progress: true

.github/workflows/coverage.yml

@@ -5,6 +5,11 @@ on:
     branches: [main]
   pull_request:
 
+permissions:
+  # Los cuatro workflows solo leen el repo: clonan, instalan y corren
+  # tests. Ninguno hace push, ni comenta, ni publica, ni toca secrets.
+  contents: read
+
 concurrency:
   group: ${{ github.workflow }}-${{ github.ref }}
   cancel-in-progress: true

.github/workflows/docs-links.yml

@@ -12,6 +12,11 @@ on:
       - 'scripts/check-links.js'
       - '.github/workflows/docs-links.yml'
 
+permissions:
+  # Los cuatro workflows solo leen el repo: clonan, instalan y corren
+  # tests. Ninguno hace push, ni comenta, ni publica, ni toca secrets.
+  contents: read
+
 jobs:
   check-links:
     runs-on: ubuntu-latest

ARCHITECTURE.md

@@ -1,3 +1,4 @@
+<!-- SPDX-License-Identifier: MIT -->
 # Sub Rosa — Architecture
 
 High-level map of the monorepo: components, trust boundaries, round lifecycle, and where each proof runs. For crypto and settlement detail see [docs/TECH_DESIGN.md](./docs/TECH_DESIGN.md).

README.md

@@ -1,3 +1,4 @@
+<!-- SPDX-License-Identifier: MIT -->
 > [!NOTE]
 > This repository is the ecosystem contribution workspace for Sub Rosa,
 > created specifically for participation in the Stellar Wave program. The main
@@ -11,23 +12,21 @@
 
 **1st Place — Hack Privacy Track, Build On Stellar Hackathon — IBW 2026**
 
-**Verifiable allocation infrastructure for Stellar grants, hackathons,
-bounties, RFPs, and sealed auctions.** Participants submit sealed scores, bids,
-or allocation decisions now; a public, unbiased Drand round unseals them later,
-verifiably and all at once. The protocol — not the operator — owns fairness.
+**Escrow-backed sealed auction infrastructure for Stellar.** Bidders lock
+Stellar assets, submit bids that stay unreadable until a public Drand reveal,
+and Soroban settles the winner payment and loser refunds deterministically.
 
 > Built on what's proven. Sealed by math, not by trust.
 
 Sub Rosa is now evolving from a hackathon-winning privacy demo into reusable
-allocation infrastructure for Stellar apps: a Soroban primitive, TypeScript
-SDK, keeper service, and integration templates for teams that need sealed
-judging, scoring, bidding, or allocation without building cryptography from
-scratch.
+auction infrastructure for Stellar apps: a Soroban primitive, TypeScript SDK,
+tlock package, keeper service, and integration templates for teams that need
+sealed bids with on-chain settlement.
 
-Target next milestone: **Stellar Community Fund Build Award**. The goal is to
-turn the current proof into production-ready developer infrastructure:
-`@sub-rosa/sdk`, optional React hooks/components, hosted keeper/reveal
-operations, hardened contracts, and mainnet launch.
+Target next milestone: a focused **ecosystem build/funding award** resubmission.
+The next application should include a named sealed-auction pilot or design
+partner, public testnet round receipts, an external funds-handling review
+milestone, and a capped mainnet beta path.
 
 Licensed under [MIT](./LICENSE).
 
@@ -49,16 +48,17 @@ See [docs/LIMITATIONS.md](./docs/LIMITATIONS.md) for honest scope (mainnet ≠ f
 
 ## Pilot plan
 
-Sub Rosa's first pilot will run with **OverBlock** as an internal
-builder/community environment for sealed judging, bounty allocation, and
-grant-style scoring workflows.
+Sub Rosa's next pilot target is a **sealed auction or competitive bid round**
+with a named Stellar ecosystem team, marketplace, asset issuer, or
+auction platform.
 
-Beyond OverBlock, we are actively preparing external pilot conversations with
-Stellar ecosystem teams, hackathon organizers, DAOs, and grant/RFP programs
-that need sealed scoring, sealed bidding, or verifiable allocation workflows.
+The pilot should prove more than "the code works": it should publish round IDs,
+participant count, total escrow, settlement/refund receipts, partner feedback,
+and a go/no-go decision for a capped mainnet beta.
 
-See [docs/PILOT_PLAYBOOK.md](./docs/PILOT_PLAYBOOK.md) for the pilot scope,
-SCF-style demo narrative, and outreach message.
+See [docs/PILOT_PLAYBOOK.md](./docs/PILOT_PLAYBOOK.md) for pilot scope and
+outreach, and [docs/FUNDING_STRATEGY.md](./docs/FUNDING_STRATEGY.md) for the
+funding/resubmission strategy.
 
 ---
 
@@ -94,8 +94,9 @@ const sealed = await sealBid({
 await client.commit({ roundId, sealed, escrow });
 ```
 
-The app layer can be a DAO tool, grants platform, auction UI, RFP workflow, or
-allocation dashboard. Sub Rosa supplies the sealed round state machine.
+The first app layer should be an auction or competitive bid UI. Other workflows
+can still embed the sealed round primitive later, but they no longer lead the
+core story.
 
 ---
 
@@ -130,15 +131,17 @@ pnpm mainnet:micro           # dry-run checklist; --execute needs MAINNET_CONFIR
 
 ## The idea
 
-Public ledgers are transparent by default, which quietly breaks fair allocation
-when participants or judges can see each other's inputs too early. That affects
-grant scoring, hackathon judging, bounty allocation, RFPs, and sealed auctions.
-The usual "fix" trusts the operator. Sub Rosa removes the operator from the
-trust path entirely:
+Public ledgers are transparent by default, which breaks sealed auctions when
+bidders can see the current clearing price before close. The usual "fix" is to
+collect bids off-chain and trust the operator. Sub Rosa removes that operator
+from the trust path:
 
 - **Seal** each bid with Drand timelock encryption (`tlock`) to a future round R.
 - **Force-open** at R: BLS12-381 verified **on-chain** — simultaneous reveal.
-- **Settle** deterministically. Identities disclosed only to the auditor.
+- **Settle** deterministically: winner escrow pays the operator; losers are
+  refunded.
+- **Disclose selectively:** bid values become public after reveal; identities
+  can remain auditor-only.
 
 See **[ARCHITECTURE.md](./ARCHITECTURE.md)** for the system map, lifecycle, trust boundaries, and monorepo layout.
 
@@ -172,8 +175,11 @@ pnpm mainnet:verify         # mainnet read-only proof
 | Doc | Purpose |
 | --- | --- |
 | **[ARCHITECTURE.md](./ARCHITECTURE.md)** | System overview, lifecycle, trust boundaries, repo map |
-| [docs/SCF_PLAN.md](./docs/SCF_PLAN.md) | SCF Build framing, tranches, deliverables, ecosystem value |
-| [docs/PILOT_PLAYBOOK.md](./docs/PILOT_PLAYBOOK.md) | OverBlock pilot scope, external pilot outreach, SCF-style demo narrative |
+| [docs/PLATFORM_PLAN.md](./docs/PLATFORM_PLAN.md) | Partner-ready protocol, SDK, template, and pilot delivery plan |
+| [docs/BUILD_PLAN.md](./docs/BUILD_PLAN.md) | Focused build/funding framing for sealed auction infrastructure |
+| [docs/GRANT_SUBMISSION.md](./docs/GRANT_SUBMISSION.md) | Grant submission narrative for the sealed auction product |
+| [docs/FUNDING_STRATEGY.md](./docs/FUNDING_STRATEGY.md) | Reviewer feedback response and resubmission strategy |
+| [docs/PILOT_PLAYBOOK.md](./docs/PILOT_PLAYBOOK.md) | Sealed auction pilot scope, outreach, and report template |
 | [docs/INTEGRATION.md](./docs/INTEGRATION.md) | How another Stellar app embeds Sub Rosa |
 | [docs/TECH_DESIGN.md](./docs/TECH_DESIGN.md) | Cryptography, storage, settlement rails |
 | [docs/THREAT_MODEL.md](./docs/THREAT_MODEL.md) | Adversaries, mitigations, honest limits |
@@ -195,19 +201,17 @@ pnpm mainnet:verify         # mainnet read-only proof
 - [x] Jury UI — one canonical testnet trace (status, bidders, R, auditor blobs, session keys)
 - [x] Watch-mode keeper (`pnpm keeper:watch`)
 
-## SCF roadmap
+## Funding roadmap
 
 | Tranche | Goal | Deliverables |
 | --- | --- | --- |
-| 1 | Developer infrastructure | Publish-ready `@sub-rosa/sdk`, integration docs, contract hardening, test vectors |
-| 2 | Testnet pilots | Hosted keeper, reusable UI hooks/components, partner pilot templates, testnet dashboards |
-| 3 | Mainnet launch | Audited/open-source contracts, mainnet deployment, production keeper ops, launch docs |
+| 1 | Auction integration package | Publish-ready `@sub-rosa/sdk`, sealed auction docs, contract hardening, test vectors |
+| 2 | Named testnet pilot | Hosted keeper, operator dashboard, public pilot report, partner feedback |
+| 3 | Capped mainnet beta | Reviewed contracts, production keeper ops, capped real-asset round, launch docs |
 
 ## Cryptographic design (Privacy track)
 
 - **Seal:** Drand tlock IBE, `bls-unchained-g1-rfc9380`
 - **Binding:** `H = sha256(value‖nonce)`
 - **Unlock:** round-R BLS verified on-chain before reveal
 - **Selective disclosure:** values public post-R; identities auditor-encrypted
-
-all done

TASKS.md

@@ -1,3 +1,4 @@
+<!-- SPDX-License-Identifier: MIT -->
 # Task List: Issue #114 Receipt Schema Version Rejection
 
 - [ ] Phase 1: Locate offline receipt verifier and inspect current error handling

apps/web/index.html

@@ -6,7 +6,7 @@
     <meta name="theme-color" content="#05070a" />
     <meta
       name="description"
-      content="Sub Rosa — verifiable allocation infrastructure for Stellar grants, hackathons, bounties, RFPs, and sealed auctions."
+      content="Sub Rosa — escrow-backed sealed auction infrastructure for Stellar."
     />
     <title>Sub Rosa</title>
     <link rel="icon" type="image/png" href="/favicon.png" />

apps/web/package.json

@@ -3,24 +3,23 @@
   "version": "0.1.0",
   "private": true,
   "type": "module",
-  "description": "Jury demo UI — lifecycle, observer, agents, x402, keeper, seal-off vs seal-on attack, mandate cap safety lab.",
+  "description": "Sealed auction demo UI — lifecycle, observer, agents, x402, keeper, seal-off vs seal-on attack, mandate cap safety lab.",
   "scripts": {
     "dev": "vite",
     "build": "vite build",
     "preview": "vite preview",
-    "test": "node --import tsx --test src/demo/trace-health-check.test.ts src/lib/config.test.ts src/dashboard/fixture-health-check.test.ts src/lib/round-status.test.ts src/components/dashboard/RoundStatusCard.test.tsx",
+    "test": "node --import tsx --test src/demo/trace-health-check.test.ts src/lib/config.test.ts src/lib/chain.test.ts src/dashboard/fixture-health-check.test.ts src/lib/round-status.test.ts src/components/dashboard/RoundStatusCard.test.tsx src/hooks/useDashboardData.test.ts",
     "typecheck": "tsc --noEmit -p tsconfig.json"
   },
   "dependencies": {
     "@stellar/freighter-api": "^6.0.1",
     "@stellar/stellar-sdk": "^15.1.0",
     "@sub-rosa/agent": "workspace:*",
     "@sub-rosa/sdk": "workspace:*",
+    "@sub-rosa/time": "workspace:*",
     "@sub-rosa/tlock": "workspace:*",
     "buffer": "^6.0.3",
-    "commander": "^11.1.0",
     "crypto-browserify": "^3.12.1",
-    "dotenv": "^16.3.1",
     "events": "^3.3.0",
     "framer-motion": "^12.40.0",
     "passkey-kit": "^0.12.0",
@@ -37,7 +36,6 @@
     "@vitejs/plugin-react": "^4.4.1",
     "tsx": "^4.22.4",
     "typescript": "^6.0.3",
-    "vite": "^6.3.5",
-    "vitest": "^1.4.0"
+    "vite": "^6.3.5"
   }
 }

apps/web/src/App.tsx

@@ -1,3 +1,4 @@
+// Copyright (c) 2026 Sub Rosa contributors
 import { useEffect, useState } from "react";
 import { getUseCase } from "./config/useCases";
 import type { UseCaseId } from "./config/useCases";
@@ -8,6 +9,7 @@ import { DashboardPage } from "./pages/DashboardPage";
 import { DemoPage } from "./pages/DemoPage";
 import { LandingPage } from "./pages/LandingPage";
 import { ToastProvider } from "./ui/Toast";
+import { TimeProvider } from "./lib/time";
 
 export default function App() {
   const [route, setRoute] = useState<RouteState>(routeFromHash);
@@ -26,10 +28,11 @@ export default function App() {
   const active = getUseCase(route.useCase);
 
   return (
-    <ToastProvider>
+    <TimeProvider>
+      <ToastProvider>
       {route.page === "landing" ? (
         <LandingPage
-          onDemo={() => navigate("demo", "grants")}
+          onDemo={() => navigate("demo", "auction")}
           onCase={(id) => navigate("demo", id)}
         />
       ) : route.page === "dashboard" ? (
@@ -48,6 +51,7 @@ export default function App() {
           )}
         </>
       )}
-    </ToastProvider>
+      </ToastProvider>
+    </TimeProvider>
   );
 }