Why is PrivateFor required during contract creation? Would passing privatefor during function calls suffice?
Inconsistent state observed. A contract was created by node 1 intended for node 2 and node 7 (privateFor node 2 and node 7). Node 3 and Node 4 was able to update the state but not retrieve it -- not able to retrieve the variable is understandable but being able to update the state variable cannot be understood as this contract was created intended for node 2 and node 7. After updating the state variable via node 3 & 4, node 2 and node 7 was getting the most updated value i.e., correct. However, node 1 was still getting the old, i.e., stale value.
Any thoughts and ideas for the above questions?