Skip to content

Rescathena Network

Inspired by the Sample Network explained in the official documentation of hyperledger fabric documentation, this is a simplified version of the initial state of the Rescathena Network, which will evolve over time as new features and functionalities are added.

Rescathena Network

In this initial stage of the Rescathena Network, we have the following components:

  • The Organizations ROA (Rescathena Organization Donors) and ROA (Rescathena Organization Administrators ⭐️) stablish the network of channel RC (Rescathena Channel).

  • The RCC (Rescathena Configuration Channel) is an initial configuration that all the ROA's peers have agrred to and which list the definition of the organizations as well as the policies which define the roles each organization will play on the channel.

  • The Ordering Service OSR (Ordering Service Rescathena) which owner is the ROA organization, is in charge of ordering the transactions and creating the blocks.

  • ROAP1 and ROAP2 are the peers of the ROA organization. They are the ones responsible for maintaining the infrastructure of the network. In other words, they are the technical experts that ensure the network runs smoothly. It does not means that they are the only ones that cand endorse transactions of configurations changes on the channel, as this is defined by the policies of the channel and requires the endorsement of the rest of the organizations' peers.

  • ROAD1 and ROAD2 are the peers of the ROD organization. They are a representation of the donors that will fund the initiatives published by the Rescaetha Organizations NGOs that will be part of the network in the future.

  • ROAA1, ROAA2, RODA1 and RODA2 are the applications that interact with the network on behalf of the peers. They can be web applications, mobile applications, or any other type of application that can send transactions to the network.

  • RL (Rescathena Ledger) is the distributed ledger that stores all the transactions and states of the network. It is maintained by all the peers in the network and is replicated across all of them to ensure consistency and reliability.

Adding a new NGO Organization to the Rescathena Network

Note that rights and permissions are defined at a channel level. Just because an organization is an administrator of one channel does not mean its pairs are the only one that can endorse transactions on that channel.

Adding a new NGO Organization to the Rescathena Network

When a new Animal Rescue Organization (NGO) wants to join the Rescathena Network, the following steps are taken:

  • Decide on the new organization's permissions and role. The full scope of these rights must be agreed before the RONGO1 organization is added to the channel RC. It comprises the same kind of questions as in the initial configuration of the channel but more tailored to a NGO organization that will publish initiatives and report back to the donors.
  • Update the channel, including the relevant chaincodes, to reflect these decisions.
  • The NGO organisation RONGO1 establishes its peers RONGOP1 and RONGOP2, as well as the applications RONGOA1 and RONGOA2, which will interact with the network on behalf of the peers.It is illogical for an NGO organisation to have more than two peers, such that the peers are solely responsible for interacting with the Rescatehna Network on behalf of the NGO.