xytara 2.15.0 → 3.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (38) hide show
  1. package/BSV_TERANODE_PLATFORM_DISCONTINUITY_RUNBOOK.md +126 -0
  2. package/README.md +1155 -1115
  3. package/REAL_PAYMENT_SETUP.md +233 -162
  4. package/RELEASE_NOTES.md +10 -10
  5. package/START_HERE.md +269 -259
  6. package/XT1_EXECUTION_TRUTH_STANDARD.md +78 -0
  7. package/XYTARA_AUTONOMOUS_ENTRY_MODEL.md +124 -0
  8. package/adapters/AUTHORING_GUIDE.md +28 -27
  9. package/bin/xytara-release.js +10 -0
  10. package/index.js +8 -0
  11. package/lib/autonomous_entry_contract.js +409 -0
  12. package/lib/execution_truth_contract.js +14 -1
  13. package/lib/major_rails_lane_contract.js +61 -1
  14. package/lib/payment_rail_truth_contract.js +5 -5
  15. package/lib/phase_5_constellation_dag_runtime_pack.js +76 -0
  16. package/lib/phase_5_digibyte_dgb_runtime_pack.js +76 -0
  17. package/lib/phase_5_hedera_hbar_runtime_pack.js +76 -0
  18. package/lib/phase_5_kaspa_kas_runtime_pack.js +76 -0
  19. package/lib/phase_5_major_rails_pack.js +40 -4
  20. package/lib/phase_5_metal_runtime_pack.js +76 -0
  21. package/lib/phase_5_polkadot_dot_runtime_pack.js +76 -0
  22. package/lib/release_center.js +8 -0
  23. package/lib/release_manifest.js +0 -1
  24. package/lib/release_pack.js +0 -1
  25. package/lib/settlement_bsv_live.js +600 -582
  26. package/lib/settlement_bsv_teranode.js +117 -105
  27. package/lib/treasury_destinations_contract.js +125 -2
  28. package/package.json +102 -102
  29. package/scripts/verify_final_activation.js +191 -0
  30. package/scripts/verify_production_readiness.js +268 -251
  31. package/scripts/verify_release_candidate.js +81 -83
  32. package/scripts/verify_service.js +69 -5
  33. package/scripts/verify_tooling.js +8 -0
  34. package/server.js +127 -0
  35. package/BSV_TERANODE_SETUP.md +0 -148
  36. package/TREASURY_DESTINATIONS.example.json +0 -66
  37. package/TREASURY_DESTINATIONS.production.template.json +0 -108
  38. package/scripts/generate_treasury_destinations.js +0 -195
package/BSV_TERANODE_PLATFORM_DISCONTINUITY_RUNBOOK.md ADDED
@@ -0,0 +1,126 @@
1
+ # BSV Teranode Platform Discontinuity Runbook
2
+
3
+ Date: `2026-05-06`
4
+
5
+ ## Purpose
6
+
7
+ This runbook explains how to keep `xytara` production-safe through the announced shutdown of the legacy Teranode web platform on `2026-05-15`.
8
+
9
+ The important distinction is:
10
+
11
+ - the dashboard/control-plane website is being discontinued
12
+ - your runtime settlement contract in `xytara` should continue to depend on live ARC submission and live observation endpoints, not on the retiring dashboard
13
+
14
+ ## What The Notice Means Operationally
15
+
16
+ Treat the notice as saying:
17
+
18
+ - do not depend on `https://platform.teranode.group/` remaining available for operator workflows after `2026-05-15`
19
+ - existing API keys may continue working, but you should not treat that as your only launch-safe posture
20
+ - if you want a replacement ARC key after the shutdown, request it proactively before launch
21
+ - WhatsOnChain support and contact ownership are separate from the retiring dashboard
22
+
23
+ ## Immediate Pre-3.0.0 Actions
24
+
25
+ 1. Back up the operator information you still need from the legacy platform now.
26
+ - current API key labels
27
+ - network association
28
+ - any usage or billing screenshots you care about
29
+ - any endpoint, auth, or support notes you may need later
30
+
31
+ 2. Do not expose or rotate secrets casually.
32
+ - keep the current live ARC key in place until a tested replacement exists
33
+ - treat screenshots or copied values as sensitive
34
+
35
+ 3. Acquire a replacement or second ARC key before cutover if possible.
36
+ - that gives us a tested rollback-safe key path instead of a launch-week scramble
37
+
38
+ 4. Keep the observer path independent.
39
+ - `xytara` already defaults to WhatsOnChain for observation unless overridden
40
+ - if you want a different observer, set it explicitly
41
+
42
+ 5. Keep the runtime provider-neutral.
43
+ - prefer the neutral `XYTARA_BSV_*` aliases going forward
44
+ - legacy `XYTARA_BSV_TERANODE_*` envs remain supported for compatibility
45
+
46
+ ## Preferred Environment Shape Going Forward
47
+
48
+ Use these neutral envs where practical:
49
+
50
+ ```env
51
+ XYTARA_BSV_NETWORK=mainnet
52
+ XYTARA_BSV_SETTLEMENT_RUNTIME_MODE=arc
53
+ XYTARA_BSV_MERCHANT_ADDRESS=<real-bsv-address-or-paymail>
54
+ XYTARA_BSV_ARC_RPC_URL=<live-arc-submit-endpoint>
55
+ XYTARA_BSV_ARC_RPC_API_KEY=<live-arc-api-key>
56
+ XYTARA_BSV_ARC_RPC_AUTH_HEADER=authorization
57
+ XYTARA_BSV_ARC_RPC_AUTH_SCHEME=
58
+ XYTARA_BSV_OBSERVER_URL=https://api.whatsonchain.com/v1/bsv/main
59
+ ```
60
+
61
+ Legacy compatibility envs are still accepted:
62
+
63
+ - `XYTARA_BSV_TERANODE_NETWORK`
64
+ - `XYTARA_BSV_TERANODE_SETTLEMENT_RUNTIME_MODE`
65
+ - `XYTARA_BSV_TERANODE_MERCHANT_ADDRESS`
66
+ - `XYTARA_BSV_TERANODE_MERCHANT_PAYMAIL`
67
+ - `XYTARA_BSV_ARC_RPC_URL`
68
+ - `XYTARA_BSV_ARC_RPC_API_KEY`
69
+ - `XYTARA_BSV_ARC_RPC_AUTH_HEADER`
70
+ - `XYTARA_BSV_ARC_RPC_AUTH_SCHEME`
71
+ - legacy `XYTARA_BSV_TERANODE_RPC_*` aliases remain accepted
72
+ - `XYTARA_BSV_TERANODE_OBSERVER_URL`
73
+
74
+ ## Cutover Validation Sequence
75
+
76
+ After you have either confirmed the current key still works or obtained a replacement ARC key:
77
+
78
+ 1. update the live Render envs for `xytara`
79
+ 2. redeploy `xytara`
80
+ 3. check:
81
+
82
+ ```text
83
+ GET /v1/settlement/bsv-teranode/readiness
84
+ GET /v1/settlement/bsv-teranode
85
+ GET /v1/payment-rail-truth/summary
86
+ GET /v1/autonomous-entry/summary
87
+ ```
88
+
89
+ 4. run one real settlement path validation
90
+ - one quote
91
+ - one payment acceptance path
92
+ - one settlement record
93
+ - one submit/refresh loop
94
+
95
+ 5. confirm:
96
+ - live submission still works in `arc` mode
97
+ - live observation still works
98
+ - the runtime does not depend on the retiring dashboard
99
+
100
+ ## What To Change If The Provider Changes Endpoint Or Auth Style
101
+
102
+ If the ARC provider gives you:
103
+
104
+ - a new submit URL
105
+ - a new auth header
106
+ - a new auth scheme
107
+ - a replacement API key
108
+
109
+ you should only need to update env values, not the public `bsv_teranode` product contract.
110
+
111
+ That is exactly why the runtime should remain:
112
+
113
+ - provider-neutral in config
114
+ - stable in public naming
115
+ - explicit in readiness checks
116
+
117
+ ## Launch Rule
118
+
119
+ Do not let the old dashboard shutdown weaken the `3.0.0` product truth unnecessarily.
120
+
121
+ The right finish-line standard is:
122
+
123
+ - `bsv_teranode` remains the native public settlement name
124
+ - `xytara` remains provider-neutral behind that name
125
+ - live ARC submission and live observation remain validated at operator level
126
+ - the public product keeps working even if the original dashboard disappears