OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Exchanges & Trading

Bitvision

Bitvision is a JavaScript terminal application for viewing Bitstamp data, charting Bitcoin prices, and placing manual or automated trades. Its automated engine uses logistic regression with historical candlestick, technical-indicator and blockchain data to forecast the direction of the next day's Bitcoin price change.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Bitvision — OpenViST project profile in Exchanges & Trading.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Bitvision when you want a terminal-based view of Bitstamp and Bitcoin-related data, or when you specifically need its manual order or automated-trading controls.

Who it is for

  • Bitstamp users who want to view Bitcoin charts, account information and transaction history in a terminal.
  • Traders who want to place manual orders or explore an automated, model-driven trading option.

Documented uses

  • View a daily Bitcoin exchange-rate graph alongside related news, technical indicators and blockchain data.
  • Review current account balance and previous transactions.
  • Place manual buy or sell orders through Bitstamp.
  • Enable a daily forecasting process that can place risk-adjusted trades.
Before you choose

Requirements & limits

The documented installation uses npm and requires Node.js 10 or later and Python 3.7. Trading access requires Bitstamp API credentials with specified permissions; credentials are stored locally.

  • The dashboard is terminal-based rather than a graphical web interface.
  • Automated trading is distinct from viewing forecasts: when enabled, the daily process can place buy or sell orders.
  • The README says the application is in alpha, warns that some trading features are buggy and not fully tested, and marks portfolio metrics as under construction.
  • The application uses Blessed.js for its command-line interface, the SciPy stack for charting and trading services, and a local JSON-file store.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Install and open the Bitvision dashboard

Install Bitvision globally and launch its terminal interface.

Before you start

  • Node.js 10 or later
  • Python 3.7
  • npm

Steps

  1. Install the package globally with the command below.

    Documented command
    npm i bitvision -g

  2. Run bitvision to start the dashboard.

Expected outcome

The Bitvision dashboard opens in the terminal.

Guide limitations

  • The README describes Bitvision as alpha and warns that some trading features are buggy and not fully tested.
Documentation 1 ↗
Source-based practical guide

Connect a Bitstamp account for trading

Create and enter Bitstamp API credentials so the dashboard can access trading functions.

Before you start

  • A Bitstamp account
  • Bitvision installed and running
  • A Bitstamp API key and secret with permissions for account balance, user transactions, open orders, and buy and sell orders

Steps

  1. In Bitstamp, open Security → API Access and create a key with the required permissions.

  2. Activate the key and confirm activation through the email link from Bitstamp.

  3. In Bitvision, press L and enter the customer ID, API key and secret.

Expected outcome

Bitvision has the credentials it needs for its documented account and trading functions.

Guide limitations

  • Credentials are stored locally on the machine; the README advises keeping them secure.
  • The README warns that some trading features are buggy and not fully tested.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
16 October 2026
Original website title
shobrook/BitVision · Official homepage title · retained in its source language
How we review sourcesSuggest a correction