@1delta/data-sdk 0.0.64 → 0.0.65

package/dist/lending/alchemix.d.ts

@@ -37,9 +37,10 @@ export declare const alchemixConfig: () => AlchemixConfigType;
 export declare const alchemixBaseKey: (lender: string) => string;
 /**
  * Deployment roster for the Alchemix lender on a chain. Published metadata
- * wins; the built-in rows are the fallback (the Curvance/Ripe pattern), so the
- * provider works with no `config/alchemix.json` publish. Accepts the bare key
- * or a per-market key.
+ * (`config/alchemix.json`) wins whole when its `markets` is non-empty — no
+ * merge, so a published chain lists EVERY Alchemist on it; the built-in rows
+ * are the fallback (the Curvance/Ripe pattern). Accepts the bare key or a
+ * per-market key.
  */
 export declare const alchemixConfigFor: (lender: string, chainId: string | number) => AlchemixConfigChain | undefined;
 /** All markets on a chain, or `[]`. */

package/dist/lending/cooler.d.ts

@@ -3,8 +3,8 @@
  * collateral → USDS debt at a protocol-set rate, positions keyed by account
  * address on ONE monolithic contract. `COOLER` is both the dispatch key and
  * the market key — there is exactly one market and no roster to curate, so
- * this module follows the Curvance built-in-seed pattern: published metadata
- * wins if it ever exists, the built-in Ethereum row is the working fallback,
+ * this module follows the Curvance built-in-seed pattern: the published
+ * `config/cooler.json` row wins, the built-in Ethereum row is the fallback,
  * and there is NO `coolerMarkets` registry slot.
  *
  * Address provenance: every address verified on-chain 2026-08-19 against the
@@ -52,9 +52,8 @@ export declare const COOLER_ETHEREUM_CONFIG: CoolerConfigChain;
 export declare const coolerConfig: () => CoolerConfigType;
 /**
  * Deployment config for the Cooler lender on a chain. Published metadata
- * wins; the built-in Ethereum row is the fallback so the provider works
- * with no `config/cooler.json` publish (none is planned — the deployment
- * is a single immutable policy set).
+ * (`config/cooler.json`, published 2026-10-21) wins whole — no field merge;
+ * the built-in Ethereum row is the fallback for a failed fetch.
  */
 export declare const coolerConfigFor: (lender: string, chainId: string | number) => CoolerConfigChain | undefined;
 /**

package/dist/lending/curvance.d.ts

@@ -65,7 +65,8 @@ export type CurvanceConfigType = {
  * Built-in Monad deployment seed for Curvance.
  *
  * Same arrangement as Resupply: a published `config/curvance.json` still WINS
- * (see `curvanceConfigFor`), but the provider is live with nothing to publish
+ * (see `curvanceConfigFor`; published 2026-10-21 as a copy of this row, and
+ * the place to add a Position Manager), but the provider is live without it
  * because `centralRegistry` is an immutable protocol singleton and the whole
  * market roster is discovered from it at runtime.
  *

package/dist/lending/dolomite.d.ts

@@ -110,6 +110,10 @@ export declare const dolomiteConfigs: () => DolomiteConfigsType;
  * 8453, 42161, 57073, 80094). Probed 2026-09-18 on Arbitrum: all three are
  * `getIsGlobalOperator == true` and `isTokenConverterTrusted == true` on every
  * live isolation factory.
+ *
+ * Fallback only: lender-metadata writes all three per chain into
+ * `config/dolomite-margin.json` (from the modules deployments file), and the
+ * config's address wins in `dolomiteRouters`.
  */
 export declare const DOLOMITE_ROUTER_DEFAULTS: {
     readonly depositWithdrawalRouter: "0xf8b2c637A68cF6A17b1DF9F8992EeBeFf63d2dFf";

package/dist/lending/resupply.d.ts

@@ -52,8 +52,9 @@ export type ResupplyConfigType = {
  * `resupplyConfigFor`). The fallback exists because these are immutable
  * protocol singletons — `RouterSwapper` even hardcodes the registry address in
  * its own bytecode — and because the whole market roster is discovered from
- * `registry` at runtime. So the integration is live with nothing to publish,
- * and publishing later is a pure override.
+ * `registry` at runtime. Since 2026-10-21 lender-metadata regenerates
+ * `config/resupply.json` daily from the registry (swappers included), so a
+ * redeploy lands as a metadata publish; this seed is the fallback.
  *
  * Verified on-chain 2026-08-04 (block ~25,683,400). Deliberately NOT taken
  * from the docs' `faq/contract-addresses` page or the repo's

package/dist/lending/ripe.d.ts

@@ -14,8 +14,8 @@
  * The asset roster is NOT seeded either: `MissionControl.numAssets()` /
  * `assets(i)` enumerate it on chain, and per-asset terms change by governance.
  *
- * Follows the Cooler/Curvance built-in-seed pattern: published metadata wins
- * if it ever exists, the built-in rows are the working fallback. Addresses
+ * Follows the Cooler/Curvance built-in-seed pattern: the published
+ * `config/ripe.json` row wins whole, the built-in rows are the fallback. Addresses
  * verified on chain 2026-10-14 (RipeHq registry walk) — see RIPE.md.
  */
 export interface RipeConfigChain {

package/package.json

@@ -4,7 +4,7 @@
   "publishConfig": {
     "access": "public"
   },
-  "version": "0.0.64",
+  "version": "0.0.65",
   "description": "Hold and initialize lending protocol data across a stack",
   "files": [
     "dist"