[FAB-7114] Re-enable LSCC writes

As per the original design of FAB-6042, chaincode data was no longer to be managed by LSCC, and so LSCC writes had been disabled. FAB-7114 requires LSCC writes, and so now the check is no longer necessary. Change-Id: I8f1cfa83410d86d75f6c1db15071dff74b70bd87 Signed-off-by: Alessandro Sorniotti <[email protected]>
hyperledger · Dec 9, 2017 · 751ee05 · 751ee05
1 parent 4f7ea56
commit 751ee05
Showing 1 changed file with 0 additions and 9 deletions.
diff --git a/core/committer/txvalidator/validator.go b/core/committer/txvalidator/validator.go
@@ -726,15 +726,6 @@ func (v *vsccValidatorImpl) VSCCValidateTx(payload *common.Payload, envBytes []b
 		return err, peer.TxValidationCode_INVALID_OTHER_REASON
 	}
 
-	// if we are using the config-tree-based cc lifecycle approach
-	// there's no legitimate reason why a transaction would write to
-	// lscc so we're going to block it
-	if v.support.Capabilities().LifecycleViaConfig() && writesToLSCC {
-		err := fmt.Errorf("lifecycle via config forbids writes to the lscc namespace")
-		logger.Errorf("%s", err)
-		return err, peer.TxValidationCode_ILLEGAL_WRITESET
-	}
-
 	// we've gathered all the info required to proceed to validation;
 	// validation will behave differently depending on the type of
 	// chaincode (system vs. application)