smartarray / digibyte-rosetta-server

DigiByte Server implementation using Coinbase's Rosetta (NodeJS) SDK

Hi there 👋

Lead Developer at DigiCorp Labs. Send me an email at [email protected] or get in touch with me via Twitter: @YoshiJaeger

Donations

I will gladly accept donations, either via Bitcoin or DigiByte.

Bitcoin: bc1qhe9u6a4rvf4kak0mlzwxsscrva9sx8d50u5za5

DigiByte: dgb1qr7t2jgxm0dgu6sk3wpy3l2j5cuqy5qtpl86ffm

digibyte-rosetta-server's Issues

Satoshi encoding issue

When reaching a block height of about 7.5M a specific transaction output couldn't be handled because more than 2^53 satoshis were transferred.

The current encoding doesn't allow such big numbers, causing a crash.

RPC workqueue exceeded

Sync fails with:

{ Error: Bitcoin JSON-RPC: Work queue depth exceeded
    at IncomingMessage.<anonymous> (/root/rosetta-node/node_modules/bitcoind-rpc/lib/index.js:115:29)
    at IncomingMessage.emit (events.js:203:15)
    at endReadableNT (_stream_readable.js:1145:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)
  cause:
   { Error: Bitcoin JSON-RPC: Work queue depth exceeded
       at IncomingMessage.<anonymous> (/root/rosetta-node/node_modules/bitcoind-rpc/lib/index.js:115:29)
       at IncomingMessage.emit (events.js:203:15)
       at endReadableNT (_stream_readable.js:1145:12)
       at process._tickCallback (internal/process/next_tick.js:63:19) code: 429 },
  isOperational: true,
  code: 429 }
{ error:
   { Error: Timeout of 5000ms exceeded
       at RequestBase._timeoutError (/root/rosetta-node/node_modules/superagent/lib/request-base.js:613:13)
       at Timeout.<anonymous> (/root/rosetta-node/node_modules/superagent/lib/request-base.js:628:12)
       at ontimeout (timers.js:436:11)
       at tryOnTimeout (timers.js:300:5)
       at listOnTimeout (timers.js:263:5)
       at Timer.processTimers (timers.js:223:10)
     timeout: 5000,
     code: 'ECONNABORTED',
     errno: 'ETIME',
     response: undefined } }
(node:42) UnhandledPromiseRejectionWarning: SyncerError: Unable to sync to 1536: undefined
    at RosettaSyncer.sync (/root/rosetta-node/node_modules/rosetta-node-sdk/lib/syncer/index.js:266:15)
    at process._tickCallback (internal/process/next_tick.js:68:7)
(node:42) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:42) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Submitted by Josiah Spackman

Wrong NetworkIdentifier

network in NetworkIdentifier is not set to testnet when running a testnet node.

Example output for a testnet node:

 ____  _     _ _____     _          _____             _   _          _____       _     
|    \|_|___|_| __  |_ _| |_ ___   | __  |___ ___ ___| |_| |_ ___   |   | |___ _| |___ 
|  |  | | . | | __ -| | |  _| -_|  |    -| . |_ -| -_|  _|  _| .'|  | | | | . | . | -_|
|____/|_|_  |_|_____|_  |_| |___|  |__|__|___|___|___|_| |_| |__,|  |_|___|___|___|___|
        |___|       |___|                                                              

             Version                  1.0.0
             Rosetta Version          1.3.1
             DigiByte Node Version    717
             Networks                 [{"blockchain":"dgb","network":"mainnet"}]
             Port                     8080

An environment variable needs to be set from the Dockerfile, specifying which network is being used. This environment variable should be used properly.

LevelDB IO issue

Waiting for RPC node to be ready...
/home/digibyte/rosetta/digibyte-rosetta-server/node_modules/levelup/lib/levelup.js:119
      return callback(new OpenError(err))
                      ^
OpenError: IO error: /home/digibyte/rosetta/digibyte-rosetta-server/data2/metadata/LOCK: No such file or directory

This error happens although the mentioned file exists.

Potential fix: Use only one instance of leveldb file.