Bitcoin Forum
June 07, 2024, 06:08:51 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Bitcoin Insight API for an alt-coin - Auroracoin  (Read 1892 times)
rippledj (OP)
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
January 03, 2015, 10:34:40 PM
 #1

Hello eveyone,

I'm trying to modify the bitcoin insight API for an altcoin (Auroracoin).  I have tried to follow the instructions on this site (http://devtome.com/doku.php?id=insightforaltcoins), and I'm an intermediate level programmer.

I have installed node, installed the bitcion-insight-api github repo and modified the networks.js file to match the genesis block of Auroracoin (http://explorer.auroracoin.eu/b/1NC5uWRdz)

Here is my networks.js

However, when I try to run insight.js using the following command I get the following error:

-$ node insight.js

info: insight server listening on port 3001 in development mode
{ '0': [Error: Could not connect to bitcoin via RPC: connect ECONNREFUSED] }
error: Could not connect to bitcoin via RPC: connect ECONNREFUSED
{ '0': 'connecting to 127.0.0.1:18333' }
{ '0': 'connection refused for 127.0.0.1:18333' }
{ '0': 'unkown error with peer 127.0.0.1:18333 (disconnecting): Error: connect ECONNREFUSED' }
{ '0': 'disconnected from peer 127.0.0.1:18333' }

Any help with modifying the bitcoin-insight-api core to look for an alt-coin instead of bitcoin would be greatly appreciated!

Joseph
SlipperySlope
Hero Member
*****
Offline Offline

Activity: 686
Merit: 501

Stephen Reed


View Profile
January 06, 2015, 06:50:35 PM
 #2

I modified Insight to work with the altcoin that I am developing.

Your problem communicating with your altcoin's version of bitcoind. Most likely it is not configured to accept RPC connections from Insight.

Here is the configuration file that I used OK.
Code:
# this instance accepts incoming connections
listen=1
# listening port
port=8333
# maintain an extra transaction index that allows the RPC getrawtransaction call to operate
txindex=1
# allow the local Insight process to send commands to this instance
rpcconnect=127.0.0.1
# allow rpc commands
server=1
# change these to what you want - they must match what is coded in Insight
rpcuser=rpctestuser
rpcpassword=rpctestpassword



PM me for more help as I am not watching this forum daily.
-Steve
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!