diff --git a/protocol/0016-PFUT-product_builtin_future.md b/protocol/0016-PFUT-product_builtin_future.md
index b3dbe1246..e1b4444ac 100644
--- a/protocol/0016-PFUT-product_builtin_future.md
+++ b/protocol/0016-PFUT-product_builtin_future.md
@@ -92,6 +92,8 @@ Validation:
- `fully-collateralised mode` is only allowed when there is a `max_price` specified
- `binary_settlement` is only allowed when there is a `max_price` specified
+Note that these fields are not specified on the market update types. Once a capped future is created and set to fully collateralised (and/or binary settlement), it cannot be changed.
+
## Acceptance Criteria
1. Create a Cash Settled Future with trading termination triggered by a date/time based data source (0016-PFUT-001)
@@ -125,4 +127,3 @@ Optional parameters:
1. Futures market can be created with a with [hardcoded risk factors](./0018-RSKM-quant_risk_models.ipynb). (0016-PFUT-026)
1. Updating a risk model on a futures market with regular risk model to with [hardcoded risk factors](./0018-RSKM-quant_risk_models.ipynb) results in recalculation of all margin levels in line with hardcoded values and collateral search/release where appropriate. (0016-PFUT-027)
1. Updating a risk model on a futures market with [hardcoded risk factors](./0018-RSKM-quant_risk_models.ipynb) to a regular risk model results in recalculation of all margin levels in line with the specified risk model (hardcoded value are no longer used) and collateral search/release where appropriate. (0016-PFUT-028)
-1. It's not possible to modify the `fully-collateralised` flag with a market update transaction. (0016-PFUT-029)
diff --git a/protocol/features.json b/protocol/features.json
index 6d1532139..e64160657 100644
--- a/protocol/features.json
+++ b/protocol/features.json
@@ -622,8 +622,7 @@
"0019-MCAL-157",
"0019-MCAL-158",
"0019-MCAL-170",
- "0019-MCAL-171",
- "0016-PFUT-029"
+ "0019-MCAL-171"
]
},
"Model-free alternatives": {
@@ -820,4 +819,4 @@
"milestone": "unknown",
"acs": []
}
-}
\ No newline at end of file
+}