# Btc-rpc-proxy

Btc-rpc-proxy is a Bitcoin Core RPC proxy that enforces per-application permissions, allowing only selected RPC calls and, optionally, a specific wallet, so self-hosters can reduce the risk of connected services. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/5324/btc-rpc-proxy

## Description

Btc-rpc-proxy is a Bitcoin Core RPC proxy that enforces per-application permissions, allowing only selected RPC calls and, optionally, a specific wallet, so self-hosters can reduce the risk of connected services overreaching on their node.

## Platform availability

Available on 0 of 10 platforms.

## Health score

58/100 (Fair), based on 4 of 5 factors.
- Maintained: 66 (last commit 95 days ago)
- Popular: 37 (72 GitHub stars)
- Easy to install: 25 (0 install platforms, install notes, Docker image)
- Security check: 100 (no serious findings, CI, tests)

## Links

- Docker Hub: https://hub.docker.com/r/dobtc/btc-rpc-proxy
- GitHub: https://github.com/Kixunil/btc-rpc-proxy

## Common questions

### What restrictions can btc-rpc-proxy place on connected apps?

It grants specific apps restricted access to funds or data, preventing connected services from seeing more information or spending more money than strictly necessary.

### Which Bitcoin node software does the repository connect it to?

It is described as providing finer-grained permission management for bitcoind.

### Which local Bitcoin Core RPC port do self-hosters ask about for RPC API requests?

The discussion asks about sending Bitcoin RPC API requests to the local Bitcoin Core port 8332 when Bitcoin Core is running.

### How can a self-hoster help with development?

You can create an account on GitHub and contribute to the repository.

---
Source: Our Local Host (https://ourlocalhost.com/app/5324/btc-rpc-proxy), the self-hosted and open-source app directory.
