Remove retired KEEP legacy surfaces

.github/workflows/client.yml

@@ -13,7 +13,6 @@ on:
       - "scripts/**"
       - "solidity/**"
       - "solidity-v1/**"
-      - "token-stakedrop/**"
   pull_request:
   workflow_dispatch:
     inputs:
@@ -46,7 +45,7 @@ jobs:
         with:
           filters: |
             path-filter:
-              - './!((docs-v1|docs|infrastructure|scripts|solidity|solidity-v1|token-stakedrop)/**)'
+              - './!((docs-v1|docs|infrastructure|scripts|solidity|solidity-v1)/**)'
 
   electrum-integration-detect-changes:
     runs-on: ubuntu-latest

.ubsignore

@@ -0,0 +1,5 @@
+# UBS scan exclusions
+# Test files use deep Chai assertion chains (.to.eq.BN etc.) intentionally;
+# null-guard warnings are false positives in that context.
+**/test/**
+**/tests/**

README.adoc

@@ -51,6 +51,8 @@ newest "v2" random beacon contracts can be found in
 link:solidity/random-beacon/[`solidity/random-beacon`] directory. The full
 specification of the "v2" random beacon is written in
 link:/docs/rfc/rfc-19-random-beacon-v2.adoc[`rfc-19-random-beacon-v2.adoc`].
+Retired KEEP-era packages and operational tooling are listed in
+link:docs/retired-components.md[`docs/retired-components.md`].
 
 === dApp Developers
 

docs/retired-components.md

@@ -0,0 +1,24 @@
+# Retired Legacy Components
+
+KEEP-era staking and distribution surfaces have been retired in favor of the
+Threshold Network T token and the current contracts under `solidity/`.
+
+This repository no longer carries the following legacy components:
+
+- `solidity-v1/contracts/TokenStakingEscrow.sol`
+- `token-stakedrop/`
+- `solidity-v1/scripts/withdraw-old-rewards.js`
+- `solidity-v1/dashboard/`
+- KEEP token dashboard Kubernetes manifests under `infrastructure/kube/keep-*`
+- `scripts/start_dashboard.sh`
+
+These components were removed because they are no longer part of supported
+operations, were tied to deprecated KEEP-token workflows, and had accumulated
+unmaintained security risk. In particular, the old rewards withdrawal helper
+contained a committed mainnet private key (since rotated and no longer active),
+and the retired staking escrow had no remaining ETH, KEEP, or T balance on
+Ethereum mainnet when checked before removal.
+
+Historical documents under `docs-v1/` may still mention these components for
+release history and archival context. They should not be used as operational
+runbooks for current Threshold Network deployments.