@bitsocial/bitsocial-cli 0.19.39

package/README.md

@@ -0,0 +1,706 @@
+[![Commitizen friendly](https://img.shields.io/badge/commitizen-friendly-brightgreen.svg)](http://commitizen.github.io/cz-cli/)
+
+# bitsocial-cli: A Bitsocial Node with WebSocket and Command Line Interface
+
+<p align="left">
+  <img src="./docs/assets/readme/cli-banner.jpg" alt="CLI banner" height="100" />
+</p>
+
+## Table of contents
+
+-   [What is Bitsocial?](#what-is-bitsocial)
+-   [What is bitsocial-cli?](#what-is-bitsocial-cli)
+-   [Install](#install)
+-   [Docker](#docker)
+-   [Usage](#usage)
+-   [Commands](#commands)
+-   [Contribution](#contribution)
+-   [Feedback](#feedback)
+
+## What is Bitsocial?
+
+Bitsocial is p2p and decentralized social media protocol built completely with IPFS/IPNS/pubsub. It doesn't use any central server, central database, public HTTP endpoint or DNS, it is pure peer to peer and fully content addressable. It will allow community owners to retain full ownership over their community. Whitepaper [here](https://github.com/plebbit/whitepaper/discussions/2)
+
+## What is bitsocial-cli?
+
+`bitsocial-cli` is an interface to the backend of PKC protocol using [pkc-js](https://github.com/pkcprotocol/pkc-js). Users can run and manage their communities using it. It is written in Typescript and designed to receive commands via CLI and WebSocket.
+
+-   Runs an IPFS and Bitsocial node
+-   Command Line interface to manage Bitsocial communities
+-   WebSocket RPC to access and control your communities and publications
+-   Includes Web UIs like Seedit where you can browse the network and manage your community
+
+## Install
+
+Requires [Node.js 22](https://nodejs.org/) or later.
+
+```sh-session
+npm install -g @bitsocial/bitsocial-cli
+```
+
+To install a specific version:
+
+```sh-session
+npm install -g @bitsocial/bitsocial-cli@0.19.39
+```
+
+To update to the latest version:
+
+```sh-session
+bitsocial update install
+```
+
+### Build from source (optional)
+
+If you want to build from source directly:
+
+```
+git clone https://github.com/bitsocialnet/bitsocial-cli
+cd bitsocial-cli
+npm ci
+npm run build
+npx oclif manifest
+npm run ci:download-web-uis
+./bin/run --help
+```
+
+After running the last command you should be able to run commands directly against `./bin/run`, for example `./bin/run daemon`
+
+## Docker
+
+You can run bitsocial-cli as a Docker container. The container runs the daemon and exposes the RPC + web UI on port 9138, the Kubo IPFS API on port 50019, and the IPFS Gateway on port 6473.
+
+Once your container is running, you can use one of the bundled web UIs to browse the Bitsocial network and manage your communities -- no CLI commands needed. The web UIs provide a full-featured interface for creating communities, moderating, and browsing content entirely through your browser. All the Web UIs are interopable so you can post and read from whichever you like and you can see your own content on each client.
+
+If you're a power user, you can also run CLI commands against the running container with `docker exec`:
+
+```sh-session
+docker exec bitsocial bitsocial community list
+```
+
+### Data paths inside the container
+
+| Path | Description |
+|---|---|
+| `/data/bitsocial` | Bitsocial data directory |
+| `/data/bitsocial/subplebbits` | Community SQLite databases |
+| `/data/bitsocial/.bitsocial-cli.ipfs` | Kubo IPFS repository |
+| `/logs/bitsocial` | Log files |
+
+The Docker volumes `bitsocial-data:/data` and `bitsocial-logs:/logs` are mapped to `/data` and `/logs` inside the container. The `bitsocial` subdirectory is created automatically by the application.
+
+### Docker Compose (recommended)
+
+Copy the example compose file and start the node:
+
+```sh-session
+cp docker-compose.example.yml docker-compose.yml
+docker compose up -d
+```
+
+View the startup logs to find your auth key URL:
+
+```sh-session
+docker compose logs -f
+```
+
+The output will include lines like:
+
+```
+plebbit rpc: listening on ws://localhost:9138/<auth-key> (secret auth key for remote connections)
+WebUI (seedit - Similar to old reddit UI): http://<your-ip>:9138/<auth-key>/seedit (secret auth key for remote connections)
+```
+
+Open the WebUI URL in your browser to start using Bitsocial.
+
+#### Viewing logs
+
+There are two ways to view logs from a Docker container:
+
+**Quick logs** — shows stdout output only (startup messages, errors):
+
+```sh-session
+docker compose logs -f          # Docker Compose
+docker logs -f bitsocial        # Docker Run
+```
+
+**Full debug logs** — shows the complete daemon log including debug/trace output:
+
+```sh-session
+docker exec bitsocial bitsocial logs -f
+```
+
+The `bitsocial logs` command supports several filtering flags:
+
+```sh-session
+docker exec bitsocial bitsocial logs -f              # follow (stream new lines)
+docker exec bitsocial bitsocial logs -n 100           # last 100 lines
+docker exec bitsocial bitsocial logs --since 1h       # entries from the last hour
+docker exec bitsocial bitsocial logs --until 30m      # entries up to 30 minutes ago
+```
+
+Debug and trace logs are written only to the log file, not to stdout, so `docker logs` will not show them. Use `bitsocial logs` inside the container for the full picture.
+
+#### Example docker-compose.yml
+
+```yaml
+services:
+  bitsocial:
+    image: ghcr.io/bitsocialnet/bitsocial-cli:latest
+    container_name: bitsocial
+    restart: unless-stopped
+    ports:
+      - "9138:9138"    # PKC RPC + Web UI
+      - "50019:50019"  # Kubo IPFS API
+      - "6473:6473"    # IPFS Gateway
+    volumes:
+      - bitsocial-data:/data
+      - bitsocial-logs:/logs
+    environment:
+      - DEBUG=bitsocial*, pkc*, -pkc*trace
+      # Set a fixed auth key (useful for bookmarking the web UI URL).
+      # If left unset, a random key is generated on first start.
+      # - PKC_RPC_AUTH_KEY=your-custom-auth-key-here
+      # Override Kubo IPFS bind addresses / ports:
+      # - KUBO_RPC_URL=http://0.0.0.0:50019/api/v0
+      # - IPFS_GATEWAY_URL=http://0.0.0.0:6473
+
+volumes:
+  bitsocial-data:
+  bitsocial-logs:
+```
+
+### Docker Run
+
+```sh-session
+docker run -d \
+  --name bitsocial \
+  --restart unless-stopped \
+  -p 9138:9138 \
+  -p 50019:50019 \
+  -p 6473:6473 \
+  -v bitsocial-data:/data \
+  -v bitsocial-logs:/logs \
+  ghcr.io/bitsocialnet/bitsocial-cli:latest
+```
+
+With a custom auth key:
+
+```sh-session
+docker run -d \
+  --name bitsocial \
+  --restart unless-stopped \
+  -p 9138:9138 \
+  -p 50019:50019 \
+  -p 6473:6473 \
+  -v bitsocial-data:/data \
+  -v bitsocial-logs:/logs \
+  -e PKC_RPC_AUTH_KEY=my-secret-key \
+  ghcr.io/bitsocialnet/bitsocial-cli:latest
+```
+
+### Building the Docker image locally
+
+```sh-session
+docker build -t bitsocial-cli .
+docker run -p 9138:9138 -p 50019:50019 -p 6473:6473 bitsocial-cli
+```
+
+## Usage
+
+### The data/config directory of Bitsocial
+
+This is the default directory where bitsocial-cli will keep its config, as well as data for local communities:
+
+-   macOS: ~/Library/Application Support/bitsocial
+-   Windows: %LOCALAPPDATA%\bitsocial
+-   Linux: ~/.local/share/bitsocial
+
+### The logs directory of Bitsocial
+
+bitsocial-cli will keep logs in this directory, with a cap of 10M per log file.
+
+-   macOS: ~/Library/Logs/bitsocial
+-   Windows: %LOCALAPPDATA%\bitsocial\Log
+-   Linux: ~/.local/state/bitsocial
+
+### Running Daemon
+
+In Bash (or powershell if you're on Windows), run `bitsocial daemon` to able to connect to the network. You need to have the `bitsocial daemon` terminal running to be able to execute other commands.
+
+```sh-session
+$ bitsocial daemon
+IPFS API listening on: http://localhost:5001/api/v0
+IPFS Gateway listening on: http://localhost:6473
+plebbit rpc: listening on ws://localhost:9138 (local connections only)
+plebbit rpc: listening on ws://localhost:9138/MHA1tm2QWG19z0bnkRarDNWIajDobl7iN2eM2PmL (secret auth key for remote connections)
+Bitsocial data path: /root/.local/share/bitsocial
+Communities in data path:  [ 'pleblore.bso' ]
+WebUI (plebones - A bare bones UI client): http://localhost:9138/MHA1tm2QWG19z0bnkRarDNWIajDobl7iN2eM2PmL/plebones (local connections only)
+WebUI (plebones - A bare bones UI client): http://192.168.1.60:9138/MHA1tm2QWG19z0bnkRarDNWIajDobl7iN2eM2PmL/plebones (secret auth key for remote connections)
+WebUI (seedit - Similar to old reddit UI): http://localhost:9138/MHA1tm2QWG19z0bnkRarDNWIajDobl7iN2eM2PmL/seedit (local connections only)
+WebUI (seedit - Similar to old reddit UI): http://192.168.1.60:9138/MHA1tm2QWG19z0bnkRarDNWIajDobl7iN2eM2PmL/seedit (secret auth key for remote connections)
+
+```
+
+Once `bitsocial daemon` is running, you can create and manage your communities through the web interfaces, either seedit or plebones. All the interfaces are interopable. If you're a power user and prefer CLI, then you can take a look at the commands below.
+
+If you need to view detailed protocol or IPFS logs for debugging, you can use `bitsocial logs`. For example, `bitsocial logs --tail 50` shows the last 50 lines, or `bitsocial logs --since 1h` shows logs from the past hour.
+
+#### Creating your first community
+
+```sh-session
+$ bitsocial community create --title "Hello World!" --description "This is gonna be great"
+12D3KooWG3XbzoVyAE6Y9vHZKF64Yuuu4TjdgQKedk14iYmTEPWu
+```
+
+#### Listing all your communities
+
+```sh-session
+$ bitsocial community list
+Address                                              Started
+ ──────────────────────────────────────────────────── ───────
+ 12D3KooWG3XbzoVyAE6Y9vHZKF64Yuuu4TjdgQKedk14iYmTEPWu true
+ business-and-finance.bso                             true
+ censorship-watch.bso                                 true
+ health-nutrition-science.bso                         true
+ movies-tv-anime.bso                                  true
+ pleblore.bso                                         true
+ politically-incorrect.bso                            true
+ reddit-screenshots.bso                               false
+ videos-livestreams-podcasts.bso                      false
+```
+
+#### Adding a role moderator to your community
+
+```sh-session
+$ bitsocial community edit mysub.bso '--roles["author-address.bso"].role' moderator
+```
+
+#### Adding a role owner to your community
+
+```sh-session
+$ bitsocial community edit mysub.bso '--roles["author-address.bso"].role' owner
+```
+
+#### Adding a role admin to your community
+
+```sh-session
+$ bitsocial community edit mysub.bso '--roles["author-address.bso"].role' admin
+```
+
+#### Removing a role
+
+```sh-session
+$ bitsocial community edit mysub.bso '--roles["author-address.bso"]' null
+```
+
+## Commands
+
+<!-- commands -->
+* [`bitsocial challenge install PACKAGE`](#bitsocial-challenge-install-package)
+* [`bitsocial challenge list`](#bitsocial-challenge-list)
+* [`bitsocial challenge remove NAME`](#bitsocial-challenge-remove-name)
+* [`bitsocial community create`](#bitsocial-community-create)
+* [`bitsocial community delete ADDRESSES`](#bitsocial-community-delete-addresses)
+* [`bitsocial community edit ADDRESS`](#bitsocial-community-edit-address)
+* [`bitsocial community get ADDRESS`](#bitsocial-community-get-address)
+* [`bitsocial community list`](#bitsocial-community-list)
+* [`bitsocial community start ADDRESSES`](#bitsocial-community-start-addresses)
+* [`bitsocial community stop ADDRESSES`](#bitsocial-community-stop-addresses)
+* [`bitsocial daemon`](#bitsocial-daemon)
+* [`bitsocial help [COMMAND]`](#bitsocial-help-command)
+* [`bitsocial logs`](#bitsocial-logs)
+
+## `bitsocial challenge install PACKAGE`
+
+Install a challenge package (npm package name, git URL, tarball URL, or local path)
+
+```
+USAGE
+  $ bitsocial challenge install PACKAGE [--pkcOptions.dataPath <value>]
+
+ARGUMENTS
+  PACKAGE  Package specifier — anything npm can install (name, name@version, git URL, tarball URL, local path)
+
+FLAGS
+  --pkcOptions.dataPath=<value>  Data path to install the challenge into
+
+DESCRIPTION
+  Install a challenge package (npm package name, git URL, tarball URL, or local path)
+
+EXAMPLES
+  $ bitsocial challenge install @bitsocial/mintpass-challenge
+
+  $ bitsocial challenge install @bitsocial/mintpass-challenge@1.0.0
+
+  $ bitsocial challenge install github:user/repo
+
+  $ bitsocial challenge install https://example.com/my-challenge-1.0.0.tar.gz
+
+  $ bitsocial challenge install ./my-local-challenge
+```
+
+_See code: [src/cli/commands/challenge/install.ts](https://github.com/bitsocialnet/bitsocial-cli/blob/v0.19.38/src/cli/commands/challenge/install.ts)_
+
+## `bitsocial challenge list`
+
+List installed challenge packages
+
+```
+USAGE
+  $ bitsocial challenge list [-q] [--pkcOptions.dataPath <value>]
+
+FLAGS
+  -q, --quiet                        Only display challenge names
+      --pkcOptions.dataPath=<value>  Data path where challenges are installed
+
+DESCRIPTION
+  List installed challenge packages
+
+EXAMPLES
+  $ bitsocial challenge list
+
+  $ bitsocial challenge list -q
+```
+
+_See code: [src/cli/commands/challenge/list.ts](https://github.com/bitsocialnet/bitsocial-cli/blob/v0.19.38/src/cli/commands/challenge/list.ts)_
+
+## `bitsocial challenge remove NAME`
+
+Remove an installed challenge package
+
+```
+USAGE
+  $ bitsocial challenge remove NAME [--pkcOptions.dataPath <value>]
+
+ARGUMENTS
+  NAME  The challenge package name (e.g., my-challenge or @scope/my-challenge)
+
+FLAGS
+  --pkcOptions.dataPath=<value>  Data path where challenges are installed
+
+DESCRIPTION
+  Remove an installed challenge package
+
+EXAMPLES
+  $ bitsocial challenge remove my-challenge
+
+  $ bitsocial challenge remove @scope/my-challenge
+```
+
+_See code: [src/cli/commands/challenge/remove.ts](https://github.com/bitsocialnet/bitsocial-cli/blob/v0.19.38/src/cli/commands/challenge/remove.ts)_
+
+## `bitsocial community create`
+
+Create a community with specific properties. A newly created community will be started after creation and be able to receive publications. For a list of properties, visit https://github.com/pkcprotocol/pkc-js
+
+```
+USAGE
+  $ bitsocial community create --pkcRpcUrl <value> [--privateKeyPath <value>]
+
+FLAGS
+  --pkcRpcUrl=<value>       (required) [default: ws://localhost:9138/] URL to PKC RPC
+  --privateKeyPath=<value>  Private key (PEM) of the community signer that will be used to determine address (if address
+                            is not a domain). If it's not provided then PKC will generate a private key
+
+DESCRIPTION
+  Create a community with specific properties. A newly created community will be started after creation and be able to
+  receive publications. For a list of properties, visit https://github.com/pkcprotocol/pkc-js
+
+EXAMPLES
+  Create a community with title 'Hello Plebs' and description 'Welcome'
+
+    $ bitsocial community create --title 'Hello Plebs' --description 'Welcome'
+```
+
+_See code: [src/cli/commands/community/create.ts](https://github.com/bitsocialnet/bitsocial-cli/blob/v0.19.38/src/cli/commands/community/create.ts)_
+
+## `bitsocial community delete ADDRESSES`
+
+Delete a community permanently.
+
+```
+USAGE
+  $ bitsocial community delete ADDRESSES... --pkcRpcUrl <value>
+
+ARGUMENTS
+  ADDRESSES...  Addresses of communities to delete. Separated by space
+
+FLAGS
+  --pkcRpcUrl=<value>  (required) [default: ws://localhost:9138/] URL to PKC RPC
+
+DESCRIPTION
+  Delete a community permanently.
+
+EXAMPLES
+  $ bitsocial community delete plebbit.bso
+
+  $ bitsocial community delete 12D3KooWG3XbzoVyAE6Y9vHZKF64Yuuu4TjdgQKedk14iYmTEPWu
+```
+
+_See code: [src/cli/commands/community/delete.ts](https://github.com/bitsocialnet/bitsocial-cli/blob/v0.19.38/src/cli/commands/community/delete.ts)_
+
+## `bitsocial community edit ADDRESS`
+
+Edit a community's properties. For a list of properties, visit https://github.com/pkcprotocol/pkc-js
+
+```
+USAGE
+  $ bitsocial community edit ADDRESS --pkcRpcUrl <value>
+
+ARGUMENTS
+  ADDRESS  Address of the community to edit
+
+FLAGS
+  --pkcRpcUrl=<value>  (required) [default: ws://localhost:9138/] URL to PKC RPC
+
+DESCRIPTION
+  Edit a community's properties. For a list of properties, visit https://github.com/pkcprotocol/pkc-js
+
+EXAMPLES
+  Change the address of the community to a new domain address
+
+    $ bitsocial community edit 12D3KooWG3XbzoVyAE6Y9vHZKF64Yuuu4TjdgQKedk14iYmTEPWu --address newAddress.bso
+
+  Add the author address 'esteban.bso' as an admin on the community
+
+    $ bitsocial community edit mysub.bso '--roles["esteban.bso"].role' admin
+
+  Add two challenges to the community. The first challenge will be a question and answer, and the second will be an
+  image captcha
+
+    $ bitsocial community edit mysub.bso --settings.challenges[0].name question \
+      --settings.challenges[0].options.question "what is the password?" --settings.challenges[0].options.answer \
+      thepassword --settings.challenges[1].name captcha-canvas-v3
+
+  Change the title and description
+
+    $ bitsocial community edit mysub.bso --title "This is the new title" --description "This is the new description"
+
+  Remove a role from a moderator/admin/owner
+
+    $ bitsocial community edit plebbit.bso --roles['rinse12.bso'] null
+
+  Enable settings.fetchThumbnailUrls to fetch the thumbnail of url submitted by authors
+
+    $ bitsocial community edit plebbit.bso --settings.fetchThumbnailUrls
+
+  disable settings.fetchThumbnailUrls
+
+    $ bitsocial community edit plebbit.bso --settings.fetchThumbnailUrls=false
+```
+
+_See code: [src/cli/commands/community/edit.ts](https://github.com/bitsocialnet/bitsocial-cli/blob/v0.19.38/src/cli/commands/community/edit.ts)_
+
+## `bitsocial community get ADDRESS`
+
+Fetch a local or remote community, and print its json in the terminal
+
+```
+USAGE
+  $ bitsocial community get ADDRESS --pkcRpcUrl <value>
+
+ARGUMENTS
+  ADDRESS  Address of the community to fetch
+
+FLAGS
+  --pkcRpcUrl=<value>  (required) [default: ws://localhost:9138/] URL to PKC RPC
+
+DESCRIPTION
+  Fetch a local or remote community, and print its json in the terminal
+
+EXAMPLES
+  $ bitsocial community get plebmusic.bso
+
+  $ bitsocial community get 12D3KooWG3XbzoVyAE6Y9vHZKF64Yuuu4TjdgQKedk14iYmTEPWu
+```
+
+_See code: [src/cli/commands/community/get.ts](https://github.com/bitsocialnet/bitsocial-cli/blob/v0.19.38/src/cli/commands/community/get.ts)_
+
+## `bitsocial community list`
+
+List your communities
+
+```
+USAGE
+  $ bitsocial community list --pkcRpcUrl <value> [-q]
+
+FLAGS
+  -q, --quiet              Only display community addresses
+      --pkcRpcUrl=<value>  (required) [default: ws://localhost:9138/] URL to PKC RPC
+
+DESCRIPTION
+  List your communities
+
+EXAMPLES
+  $ bitsocial community list -q
+
+  $ bitsocial community list
+```
+
+_See code: [src/cli/commands/community/list.ts](https://github.com/bitsocialnet/bitsocial-cli/blob/v0.19.38/src/cli/commands/community/list.ts)_
+
+## `bitsocial community start ADDRESSES`
+
+Start a community
+
+```
+USAGE
+  $ bitsocial community start ADDRESSES... --pkcRpcUrl <value>
+
+ARGUMENTS
+  ADDRESSES...  Addresses of communities to start. Separated by space
+
+FLAGS
+  --pkcRpcUrl=<value>  (required) [default: ws://localhost:9138/] URL to PKC RPC
+
+DESCRIPTION
+  Start a community
+
+EXAMPLES
+  $ bitsocial community start plebbit.bso
+
+  $ bitsocial community start 12D3KooWG3XbzoVyAE6Y9vHZKF64Yuuu4TjdgQKedk14iYmTEPWu
+
+  Start all communities in your data path
+
+    $ bitsocial community start $(bitsocial community list -q)
+```
+
+_See code: [src/cli/commands/community/start.ts](https://github.com/bitsocialnet/bitsocial-cli/blob/v0.19.38/src/cli/commands/community/start.ts)_
+
+## `bitsocial community stop ADDRESSES`
+
+Stop a community. The community will not publish or receive any publications until it is started again.
+
+```
+USAGE
+  $ bitsocial community stop ADDRESSES... --pkcRpcUrl <value>
+
+ARGUMENTS
+  ADDRESSES...  Addresses of communities to stop. Separated by space
+
+FLAGS
+  --pkcRpcUrl=<value>  (required) [default: ws://localhost:9138/] URL to PKC RPC
+
+DESCRIPTION
+  Stop a community. The community will not publish or receive any publications until it is started again.
+
+EXAMPLES
+  $ bitsocial community stop plebbit.bso
+
+  $ bitsocial community stop Qmb99crTbSUfKXamXwZBe829Vf6w5w5TktPkb6WstC9RFW
+```
+
+_See code: [src/cli/commands/community/stop.ts](https://github.com/bitsocialnet/bitsocial-cli/blob/v0.19.38/src/cli/commands/community/stop.ts)_
+
+## `bitsocial daemon`
+
+Run a network-connected Bitsocial node. Once the daemon is running you can create and start your communities and receive publications from users. The daemon will also serve web ui on http that can be accessed through a browser on any machine. Within the web ui users are able to browse, create and manage their communities fully P2P.
+
+```
+USAGE
+  $ bitsocial daemon --pkcRpcUrl <value> --logPath <value> [--chainProviderUrls <value>...]
+
+FLAGS
+  --chainProviderUrls=<value>...  [default: viem,https://ethrpc.xyz] Ethereum RPC URL(s) for .bso/.eth name resolution.
+                                  Can be specified multiple times. Defaults to viem public transport and
+                                  https://ethrpc.xyz
+  --logPath=<value>               (required) [default: /home/runner/.local/state/bitsocial] Specify a directory which
+                                  will be used to store logs
+  --pkcRpcUrl=<value>             (required) [default: ws://localhost:9138/] Specify PKC RPC URL to listen on
+
+DESCRIPTION
+  Run a network-connected Bitsocial node. Once the daemon is running you can create and start your communities and
+  receive publications from users. The daemon will also serve web ui on http that can be accessed through a browser on
+  any machine. Within the web ui users are able to browse, create and manage their communities fully P2P.
+  Options can be passed to the RPC's instance through flag --pkcOptions.optionName. For a list of pkc options
+  (https://github.com/pkcprotocol/pkc-js?tab=readme-ov-file#pkcoptions)
+  If you need to modify ipfs config, you should head to {bitsocial-data-path}/.ipfs-bitsocial-cli/config and modify the
+  config file
+
+
+EXAMPLES
+  $ bitsocial daemon
+
+  $ bitsocial daemon --pkcRpcUrl ws://localhost:53812
+
+  $ bitsocial daemon --pkcOptions.dataPath /tmp/bitsocial-datapath/
+
+  $ bitsocial daemon --pkcOptions.kuboRpcClientsOptions[0] https://remoteipfsnode.com
+
+  $ bitsocial daemon --chainProviderUrls https://mainnet.infura.io/v3/YOUR_KEY
+
+  $ bitsocial daemon --chainProviderUrls viem --chainProviderUrls https://mainnet.infura.io/v3/YOUR_KEY
+```
+
+_See code: [src/cli/commands/daemon.ts](https://github.com/bitsocialnet/bitsocial-cli/blob/v0.19.38/src/cli/commands/daemon.ts)_
+
+## `bitsocial help [COMMAND]`
+
+Display help for bitsocial.
+
+```
+USAGE
+  $ bitsocial help [COMMAND...] [-n]
+
+ARGUMENTS
+  [COMMAND...]  Command to show help for.
+
+FLAGS
+  -n, --nested-commands  Include all nested commands in the output.
+
+DESCRIPTION
+  Display help for bitsocial.
+```
+
+_See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/v6.2.36/src/cli/commands/help.ts)_
+
+## `bitsocial logs`
+
+View the latest BitSocial daemon log file. By default dumps the full log and exits. Use --follow to stream new output in real-time (like tail -f).
+
+```
+USAGE
+  $ bitsocial logs [-f] [-n <value>] [--since <value>] [--until <value>]
+
+FLAGS
+  -f, --follow         Follow log output in real-time (like tail -f)
+  -n, --tail=<value>   [default: all] Number of log entries to show from the end. Use "all" to show everything.
+      --since=<value>  Show logs since timestamp (ISO 8601, e.g. 2026-01-02T13:23:37Z) or relative time (e.g. 30s, 42m,
+                       2h, 1d)
+      --until=<value>  Show logs before timestamp (ISO 8601, e.g. 2026-01-02T13:23:37Z) or relative time (e.g. 30s, 42m,
+                       2h, 1d)
+
+DESCRIPTION
+  View the latest BitSocial daemon log file. By default dumps the full log and exits. Use --follow to stream new output
+  in real-time (like tail -f).
+
+EXAMPLES
+  $ bitsocial logs
+
+  $ bitsocial logs -f
+
+  $ bitsocial logs -n 50
+
+  $ bitsocial logs --since 5m
+
+  $ bitsocial logs --since 2026-01-02T13:23:37Z --until 2026-01-02T14:00:00Z
+
+  $ bitsocial logs --since 1h -f
+```
+
+_See code: [src/cli/commands/logs.ts](https://github.com/bitsocialnet/bitsocial-cli/blob/v0.19.38/src/cli/commands/logs.ts)_
+<!-- commandsstop -->
+
+## Contribution
+
+We're always happy to receive pull requests. Few things to keep in mind:
+
+-   This repo follows [Angular commit conventions](https://github.com/angular/angular/blob/main/CONTRIBUTING.md). Easiest way to follow these conventions is by using `npm run commit` instead of `git commit`
+-   If you're adding a feature, make sure to add tests to your pull requests
+
+## Feedback
+
+We would love your feedback on our community channels