Common use of Node Set-up Clause in Contracts

Node Set-up. Upon joining the Council, a Member will work with Xxxxxx’s DevOps team to finalize a plan for operating its Node. A Member will be required to manage its Node independently within 90 days of joining the Council1. Prior to the member independently operating a node, Xxxxxx may set up a Node on behalf of such Member and such Member will accept shared control with Hedera of such Node (a Node under such shared control, a “Transitional Node.”) Xxxxxx, and not the Member, will be responsible for the costs or IT support relating to the management of a Transitional Node. During any period in which a Member has a Transitional Node, the Member will not be eligible to receive any of the fees and/or rewards described in paragraph B.5 below. Members shall provide Hedera with the current location (minimally region and country) where their node is operating. Members shall provide updates to Hedera within 90 days of a change in hosting location. Hedera may publish the location of Hedera nodes operating on Mainnet along with the attribution of members to their specific node.

Node Set-up. Upon joining the Council, a Member will work with Xxxxxx’s DevOps team to finalize a plan for operating its Node. A Member will be required to manage its Node independently within 90 days of joining the Council1Council. Prior to When the member is not independently operating a node, Xxxxxx may set up a Node on behalf of such Member and such Member will accept shared control with Hedera of such Node (a Node under such shared control, a “Transitional Node.”) Xxxxxx, and not the Member, will be responsible for the costs or IT support relating to the management of a Transitional Node. During any period in which a Member has a Transitional Node, the Member will not be eligible to receive any of the fees and/or rewards described in paragraph B.5 below. Members shall provide Hedera with the current location (minimally region and country) where their node is operating. Members shall provide updates to Hedera within 90 days of a change in hosting location. Hedera may publish the location of Hedera nodes operating on Mainnet along with the attribution of members to their specific node.

Node Set-up. Upon joining the Council, a Member will work with XxxxxxHedera’s DevOps team to finalize a plan for operating its Node. A Member will be required to manage its Node independently within 90 days of joining the Council1. Prior to the member independently operating a node, Xxxxxx Hedera may set up a Node on behalf of such Member and such Member will accept shared control with Hedera of such Node (a Node under such shared control, a “Transitional Node.”) XxxxxxHedera, and not the Member, will be responsible for the costs or IT support relating to the management of a Transitional Node. During any period in which a Member has a Transitional Node, the Member will not be eligible to receive any of the fees and/or rewards described in paragraph B.5 below. Members shall provide Hedera with the current location (minimally region and country) where their node is operating. Members shall provide updates to Hedera within 90 days of a change in hosting location. Hedera may publish the location of Hedera nodes operating on Mainnet along with the attribution of members to their specific node.