> For the complete documentation index, see [llms.txt](https://block-convey.gitbook.io/block-convey/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://block-convey.gitbook.io/block-convey/network-topology.md).

# Network Topology

A blockchain network is a technical infrastructure that provides applications ledger and smart contract services. Primarily, smart contracts are used to generate transactions which are subsequently distributed to every peer node in the network, where they are immutably recorded on their copy of the ledger. The users of applications might be end-users using client applications or blockchain network administrators.

**Let us see how we create a network in BlockConvey’s Blockchain.**

**1.  Defining a network:** An ordering service that serves as an initial administration point defines a network. The definition contains the policies that describe the starting set of administrative capabilities for the network.

**2.  Authority for Certification:** This node is the network's certificate authority or master admin. They issue certificates to other node validators based on the principles set forth. In Networks like Hyperledger, the mapping of certificates to member organizations is achieved by a membership service provider (MSP) structure. We have a similar structure of network participants.

**3. Adding Network Master Nodes:** Once the authority nodes are added, the network would allow administrative rights to the master nodes. In this next phase, the authority organization updates the network configuration to make the other organizations administrators. After this, both the master nodes and authority nodes have the same ledger. Except that authority nodes can add the blocks, whereas master nodes cannot add blocks.

**4. Defining a Consortium:** The master administrator defines the consortium that contains two member interactions between the master nodes and the light nodes. The consortium definition is stored in the network configuration and will be used at the next stage of network development.

**5. Creating a channel for the consortium:** A channel is a primary communications mechanism by which the members of a consortium can communicate with each other. There can be multiple channels in a network.

**6. Peers and Ledgers:** In the next stage of the network development, we see that our network has two new components of peer node (light nodes) and the ledger instance. Peer nodes are the network components where copies of the blockchain ledger are hosted. Ledger is physically hosted in the peer nodes, but the logic is hosted by the channel and consortium.

**7.Addition of a new channel:** Now, you define a new consortium with another participant if there are multiple parties adding up to the network.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://block-convey.gitbook.io/block-convey/network-topology.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.