This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description

This is a simple script that acts as an RPC proxy to the BitShares client and provides simple access control to it, allowing to restrict access to certain methods of the client only in a flexible way.

If you like this tool, please vote for my delegate to support further development, and feel free to visit my page for other delegate proposals at Thanks!


To install, run:

$ pip install bts_proxy

preferably (but not required) in a virtualenv.

Running the proxy

Just run the bts-proxy script on the command line.

Configuration file with listening port and users/passwords alongside with allowed methods can be found in the same data dir as the one for the BitShares client. Config file is named proxy.json, and will be created automatically the first time you run bts-proxy if it doesn’t exist yet.

You can specify a different data dir than the default one for the BitShares client as the first argument to the bts-proxy script, e.g.:

$ bts-proxy ~/.BitShares

Configuration file format

The configuration file is a simple JSON file, looking like this:

    "port": 5681,

    "users": [
            "name": "username",
            "password": "secret-password",
            "methods_allowed": ["*"]

port is the port number on which the proxy will be listening. Make sure to use a different port than the one on which the BitShares client is listening!

users is a list of objects containing the following fields:

  • name: the name of the user
  • password: the password for that user
  • methods_allowed: the list of methods allowed. You can used shell-like pattern matching here (eg: "wallet_*" will allow all methods starting with "wallet_")
  • methods_forbidden (optional): the list of forbidden methods. You can also use shell-like pattern matching here.

Note that by default, methods are forbidden, so the proxy will allow you to call a method if and only if it appears in the methods_allowed field and not in the methods_forbidden field.

Security best practices

It is highly recommended to run both the BitShares client and the RPC proxy as their own separate user, rather than your common one, and to restrict read access to the BitShares client data dir to only this user.

This should come by default with BitShares >= 0.5.0, otherwise you can do the following:

$ chmod 700 ~/.BitShares
Release History

Release History


This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
bts_proxy-0.1.tar.gz (5.3 kB) Copy SHA256 Checksum SHA256 Source Jan 10, 2015

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting