1.0.3 • Published 5 years ago

@ravendevkit/ravencore v1.0.3

Weekly downloads
-
License
MIT
Repository
github
Last release
5 years ago

Ravencore

This is OverstockMedici's fork of Under's fork of Bitpay's Bitcore that currently uses Ravencoin 2.1.0.0. It has a limited segwit support. Known supported os: Ubuntu 16.04.

It is HIGHLY recommended to use https://github.com/RavenDevKit/ravencore-deb to build and deploy packages for production use.


Getting Started

Deploying Ravencore full-stack manually:

mkdir insight
mkdir ~/.ravencore
mkdir ~/.ravencore/data
cd insight
sudo apt-get update
sudo apt-get -y install libevent-dev libboost-all-dev libminiupnpc10 libzmq5 software-properties-common curl git build-essential libzmq3-dev
sudo add-apt-repository ppa:bitcoin/bitcoin
sudo apt-get update
sudo apt-get -y install libdb4.8-dev libdb4.8++-dev
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.11/install.sh | bash
##(restart your shell/os)##
nvm install stable
nvm install-latest-npm
nvm use stable
##(install mongodb)##
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 2930ADAE8CAF5059EE73BB4B58712A2291FA4AD5
echo "deb [ arch=amd64,arm64 ] https://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.6 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-3.6.list
sudo apt-get update
sudo apt-get install -y mongodb-org
sudo systemctl enable mongod.service
##(restart your shell/os)##
##(install ravencore)##
git clone https://github.com/RavenDevKit/ravencore.git
npm install -g ravencore --production

Create and copy the following into a file named ~/.ravencore/ravencore-node.json (be sure to customize username and password values under the insight-api secion - these will need to match those in the setup unique mongo credentials section below.)

{
  "network": "livenet",
  "port": 3001,
  "services": [
    "ravend",
    "web",
    "insight-api",
    "insight-ui"
  ],
  "allowedOriginRegexp": "^https://<yourdomain>\\.<yourTLD>$",  // delete this line to run a local server instance
  "messageLog": "",
  "servicesConfig": {
    "web": {
      "disablePolling": false,
      "enableSocketRPC": true
    },
    "insight-ui": {
      "routePrefix": "",
      "apiPrefix": "api"
    },
    "insight-api": {
      "routePrefix": "api",
      "coinTicker" : "https://api.coinmarketcap.com/v1/ticker/ravencoin/?convert=USD",
      "coinShort": "RVN",
      "db": {
        "host": "127.0.0.1",
        "port": "27017",
        "database": "raven-api-livenet",
        "user": "test",
        "password": "test1234"
      }
    },
    "ravend": {
      "sendTxLog": "/home/ubuntu/.ravencore/pushtx.log",
      "spawn": {
        "datadir": "/home/ubuntu/.ravencore/data",
        "exec": "/home/ubuntu/insight/ravencore/node_modules/ravencore-node/bin/ravend",
        "rpcqueue": 1000,
        "rpcport": 8766,
        "zmqpubrawtx": "tcp://127.0.0.1:28332",
        "zmqpubhashblock": "tcp://127.0.0.1:28332",
        "rpcuser": "ravencoin",
        "rpcpassword": "local321"
      }
    }
  }
}

Quick note on allowing socket.io from other services.

  • If you would like to have a seperate services be able to query your api with live updates, remove the "allowedOriginRegexp": setting and change "disablePolling": to false.
  • "enableSocketRPC" should remain false unless you can control who is connecting to your socket.io service.
  • The allowed OriginRegexp does not follow standard regex rules. If you have a subdomain, the format would be(without angle brackets<>):
"allowedOriginRegexp": "^https://<yoursubdomain>\\.<yourdomain>\\.<yourTLD>$",

To setup unique mongo credentials:

mongo
>use raven-api-livenet
>db.createUser( { user: "test", pwd: "test1234", roles: [ "readWrite" ] } )
>exit

(then add these unique credentials to your ~/.ravencore/ravencore-node.json file)

Create and copy the following into a file named ~/.ravencore/data/raven.conf NOTE: If you change the rpcuser or rpcpassword in this file be sure to also change it in the ~/.ravencore/ravencore-node.json file as well.

server=1
whitelist=127.0.0.1
txindex=1
addressindex=1
timestampindex=1
spentindex=1
zmqpubrawtx=tcp://127.0.0.1:28332
zmqpubhashblock=tcp://127.0.0.1:28332
rpcport=8766
rpcallowip=127.0.0.1
rpcuser=ravencoin
rpcpassword=local321
uacomment=ravencore-sl

mempoolexpiry=72 # Default 336
rpcworkqueue=1100
maxmempool=2000
dbcache=1000
maxtxfee=1.0
dbmaxfilesize=64

If you got this far, launch your copy of ravencore:

ravencored

You can then view the Ravencoin block explorer at the location: http://localhost:3001

Troubleshooting: Here are a few known issues that have come up and workarounds.

If the mongod isn't running some users have fixed it with these steps: 1. change mongo host from 127.0.0.1 --> 0.0.0.0 in /etc/mongod.conf 2. restart with sudo service mongod restart

If npm is having trouble with node-x16r: 1. sudo apt-get install node-gyp 2. run node-gyp rebuild from ravencore/node_modules/node-x16r 3. run npm install from ravencore/node_modules/node-x16r

If node is having trouble with "zmq.node": 1. run npm install zeromq in ravencore 2. or, run npm rebuild zeromq in ravencore

There may still be some lurking problems with the Ravencoin download script:

  • unknown host breaks download into interactive mode
  • the ln doesn't seem to work (but works manually afterwards)
  • there's a path setting problem if ravencore isn't in your home directory

Create an Nginx proxy to forward port 80 and 443(with a snakeoil ssl cert)traffic:

IMPORTANT: this "nginx-ravencore" config is not meant for production use see this guide here for production usage

sudo apt-get install -y nginx ssl-cert

copy the following into a file named "nginx-ravencore" and place it in /etc/nginx/sites-available/

server {
    listen 80;
    listen 443 ssl;

    include snippets/snakeoil.conf;
    root /home/ravencore/www;
    access_log /var/log/nginx/ravencore-access.log;
    error_log /var/log/nginx/ravencore-error.log;
    location / {
        proxy_pass http://127.0.0.1:3001;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
        proxy_connect_timeout 10;
        proxy_send_timeout 10;
        proxy_read_timeout 100; # 100s is timeout of Cloudflare
        send_timeout 10;
    }
    location /robots.txt {
       add_header Content-Type text/plain;
       return 200 "User-agent: *\nallow: /\n";
    }
    location /ravencore-hostname.txt {
        alias /var/www/html/ravencore-hostname.txt;
    }
}

Then enable your site:

sudo ln -s /etc/nginx/sites-available/nginx-ravencore /etc/nginx/sites-enabled
sudo rm -f /etc/nginx/sites-enabled/default /etc/nginx/sites-available/default
sudo mkdir /etc/systemd/system/nginx.service.d
sudo printf "[Service]\nExecStartPost=/bin/sleep 0.1\n" | sudo tee /etc/systemd/system/nginx.service.d/override.conf
sudo systemctl daemon-reload
sudo systemctl restart nginx

Upgrading Ravencore full-stack manually:

  • This will leave the local blockchain copy intact: Shutdown the ravencored application first, and backup your unique raven.conf and ravencore-node.json
$cd ~/
$rm -rf .npm .node-gyp ravencore
$rm .ravencore/data/raven.conf .ravencore/ravencore-node.json
##reboot##
$git clone https://github.com/RavenDevKit/ravencore.git
$npm install -g ravencore --production

(recreate your unique raven.conf and ravencore-node.json)

  • This will redownload a new blockchain copy: (Some updates may require you to reindex the blockchain data. If this is the case, redownloading the blockchain only takes 20 minutes) Shutdown the ravencored application first, and backup your unique raven.conf and ravencore-node.json
$cd ~/
$rm -rf .npm .node-gyp ravencore
$rm -rf .ravencore
##reboot##
$git clone https://github.com/RavenDevKit/ravencore.git
$npm install -g ravencore --production

(recreate your unique raven.conf and ravencore-node.json)

#reboot

git clone https://github.com/underdarkskies/ravencore.git cd ravencore && git checkout lightweight npm install -g --production

(recreate your unique raven.conf and ravencore-node.json)

Undeploying Ravencore full-stack manually:
----

nvm deactivate nvm uninstall 10.5.0 rm -rf .npm .node-gyp ravencore rm .ravencore/data/raven.conf .ravencore/ravencore-node.json mongo

use raven-api-livenet db.dropDatabase() exit

Applications

  • Node - A full node with extended capabilities using Ravencoin Core
  • Insight API - A blockchain explorer HTTP API
  • Insight UI - A blockchain explorer web user interface
  • (to-do) Wallet Service - A multisig HD service for wallets
  • (to-do) Wallet Client - A client for the wallet service
  • (to-do) CLI Wallet - A command-line based wallet client
  • (to-do) Angular Wallet Client - An Angular based wallet client
  • (to-do) Copay - An easy-to-use, multiplatform, multisignature, secure ravencoin wallet

Libraries

  • Lib - All of the core Ravencoin primatives including transactions, private key management and others
  • (to-do) Payment Protocol - A protocol for communication between a merchant and customer
  • P2P - The peer-to-peer networking protocol
  • (to-do) Mnemonic - Implements mnemonic code for generating deterministic keys
  • (to-do) Channel - Micropayment channels for rapidly adjusting ravencoin transactions
  • Message - Ravencoin message verification and signing
  • (to-do) ECIES - Uses ECIES symmetric key negotiation from public keys to encrypt arbitrarily long data streams.

Security

We're using Ravencore in production, but please use common sense when doing anything related to finances! We take no responsibility for your implementation decisions.

Contributing

Please send pull requests for bug fixes, code optimization, and ideas for improvement. For more information on how to contribute, please refer to our CONTRIBUTING file.

To verify signatures, use the following PGP keys:

  • TBD

License

Code released under the MIT license.