ADCS Testnet Details

This document provides essential details for accessing and interacting with the Autheo DCS (ADCS) Testnet. It defines core network components and lists the specific URLs and configuration parameters required for connection and development.

1. Key Highlights

This section defines the core components of the ADCS Testnet architecture:

Component	Description
Bootstrap Nodes	Initial network endpoints that an ADCS client or node connects to. They are well-connected, always-online nodes that help new ADCS nodes discover and join the network. They actively maintain the Distributed Hash Table (DHT), which is crucial for peer discovery and content routing.
Autheo DCS (ADCS) Nodes	Standard nodes in the ADCS network that participate in storing, retrieving, and sharing content. They can connect to other peers, host content, and respond to data requests.
Public Gateways	A web-accessible HTTP endpoint that allows users to retrieve Autheo DCS content using a traditional browser, without needing to run a local node.
Web UI	A browser-based graphical interface used to manage and monitor a local ADCS node. It allows users to add or view files, explore the network, inspect peers, check bandwidth usage, and manage settings without using the command line.

2. Endpoint Details

The following table lists the access URLs for the primary services deployed on the ADCS Testnet.

Service	URL
ADCS Node 1 (HTTP)	`https://adcs-testnet.node1.zeeve.net`
ADCS Node 1 (Web UI)	[WebUI \| ADCS TESTNET TESTNET]
ADCS Node 2 (HTTP)	`https://adcs-testnet.node2.zeeve.net/`
ADCS Node 2 (Web UI)	[WebUI \| ADCS TESTNET TESTNET]
ADCS Public Gateway	`https://adcs-testnet.gateway.zeeve.net`

3. Network Details

This table provides the essential parameters and scale of the ADCS Testnet.

Item	Value
Protocol ID	`adcstestnet`
Protocol Used Behind	`IPFS`
Number of ADCS Nodes	2
Number of Bootstrap ADCS Nodes	3