@chipi-stack/backend 14.12.0 → 14.12.2
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.
- package/dist/index.d.mts +18 -6
- package/dist/index.d.ts +18 -6
- package/dist/index.js +10 -3
- package/dist/index.js.map +1 -1
- package/dist/index.mjs +10 -3
- package/dist/index.mjs.map +1 -1
- package/package.json +3 -3
package/dist/index.mjs
CHANGED
|
@@ -2915,9 +2915,16 @@ var ChipiTreasury = class {
|
|
|
2915
2915
|
* from their own server could see a quorum applied to a proposal but never
|
|
2916
2916
|
* choose it.
|
|
2917
2917
|
*
|
|
2918
|
-
* IMPORTANT: a quorum can only RAISE `requiredApprovals
|
|
2919
|
-
* on-chain threshold.
|
|
2920
|
-
*
|
|
2918
|
+
* IMPORTANT: a quorum can only RAISE `requiredApprovals`, never lower it
|
|
2919
|
+
* below the wallet's on-chain threshold. Set one below and it is SILENTLY
|
|
2920
|
+
* RAISED at propose time, not rejected and not reverted: a `routineQuorum`
|
|
2921
|
+
* of 1 on a 2-of-3 wallet is clamped to 2 and executes normally. The risk is
|
|
2922
|
+
* a policy that reads 1 everywhere while the system uses 2.
|
|
2923
|
+
*
|
|
2924
|
+
* The server now rejects that outright so the stored value means what it
|
|
2925
|
+
* says (server-side enforcement, live since 2026-08; no SDK upgrade
|
|
2926
|
+
* needed). To genuinely lower the requirement, lower the on-chain
|
|
2927
|
+
* threshold first with `propose_set_threshold` (48h timelock).
|
|
2921
2928
|
*
|
|
2922
2929
|
* Server-only: it needs a `sk_`.
|
|
2923
2930
|
*
|