> For the complete documentation index, see [llms.txt](https://docs.astrakode.tech/akb-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.astrakode.tech/akb-wiki/astrakode-wiki/network-composer/components/peer.md).

# Peer

## Introduction

A Peer is a Network entity that maintains ledgers and runs chaincode containers in order to perform read/write operations on a ledger they maintain. Peers are owned by Organizations, and act as an Organization's endpoint to transact on the Channels to which they are connected to.

<figure><img src="https://t-images.imgix.net/https%3A%2F%2Fapp-us-east-1.t-cdn.net%2F5f96e1a6e5864f172c21948d%2Fposts%2F61e5a3be184b21410479a799%2F61e5a3be184b21410479a799_65397.png?width=1240&#x26;w=1240&#x26;auto=format%2Ccompress&#x26;ixlib=js-2.3.1&#x26;s=81b56273b8d86f08a64649a707a381f3" alt=""><figcaption></figcaption></figure>

## Configuration

Double click the Peer to edit it.

### Settings

#### General

* **Owner**: defines to which Organization this Peer belongs (Owner Organization must be set);
* **Service Call**: defines which Interface is utilized for Service Calls to this Peer (the interface can be “REST” or “SOAP”);
* **Chaincode Port**: defines the port at which the Chaincode hosted by this Peer can be reached (Port must be numeric and within acceptable range \[100 - 35000]);
* **Anchor**: defines whether this Peer is an Anchor Peer, i.e. an endpoint for gossip to make sure Peers in different Organizations know about each other (It is advised to set at least one Anchor Peer per Channel for each Member Organization).

#### Network

* **Name**: defines this node’s name;
* **IP Address**: defines the IP Address for the machine on which the node’s docker container will be deployed. Numeric IPv4 is advised.
* **Port**: defines the Port at which the node can be reached.


---

# 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://docs.astrakode.tech/akb-wiki/astrakode-wiki/network-composer/components/peer.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.