The similar principles apply for channel configurations with respect to friends. When peer nodes P1 and P2 are interacting with client purposes A1 or A2 they are every utilizing the insurance policies defined inside channel configuration CC1 to control entry to the channel C1 sources. As the community and channels evolve, so will the network and channel configurations. There is a process by which this is accomplished in a managed method – involving configuration transactions which capture the change to those configurations. Every configuration change results in a model new configuration block transaction being generated, and later on this matter, we’ll see how these blocks are validated and accepted to create up to date network and channel configurations respectively.