Infrastructure to build Bitcoin and blockchain-based applications for the next generation of financial technology./litecoin-project/litecore-lib Before you begin you'll need to have Node.js v4 or v0.12 installed.There are several options for installation.One method is to use nvm to easily switch between different versions, or download directly from Node.js.Spin up a full node and join the network: You can then view the Insight block explorer at the default location: http://localhost:3001/insight, and your configuration file will be found in your home directory at ~/.litecore.The complete docs are hosted here: litecore documentation.There's also a litecore API reference available generated from the JSDocs of the project, where you'll find low-level details on each litecore utility.To get community assistance and ask for help with implementation questions, please use our community forums.We're using Litecore in production, as are many others, but please use common sense when doing anything related to finances!

We take no responsibility for your implementation decisions.Please send pull requests for bug fixes, code optimization, and ideas for improvement.austin bitcoin minerFor more information on how to contribute, please refer to our CONTRIBUTING file.bitcoin price rmThis will generate files named litecore.js and litecore.min.js.make bitcoin miner virusYou can also use our pre-generated files, provided for each release along with a PGP signature by one of the project's maintainers.bitcoin mining share difficultyTo verify signatures, use the following PGP keys: Code released under the MIT license.bitcoin banco central brasil

Copyright 2013-2015 BitPay, Inc.Bitcore is a trademark maintained by BitPay, Inc.Copyright 2016 The Litecore Core Developerslitecoin mining 3 gpuManage your cryptocurrency accounts and cards on the go Mobile App Manage your cryptocurrency accounts and cards on the go Mobile App Manage your cryptocurrency accounts and cards on the go Charts Simplified real-time reporting for all major exchanges and cryptocurrencies Charts Simplified real-time reporting for all major exchanges and cryptocurrencies Merchant Turnkey solution to accept cryptocurrencies for goods or services Merchant Turnkey solution to accept cryptocurrencies for goods or services Exchange Easy way to earn with cryptocurrencies trading Exchange Easy way to earn with cryptocurrencies trading Cards Debit and virtual cards directly connected to your accounts allowing real-time cryptocurrencies conversions Cards Debit and virtual cards directly connected to your accounts allowing real-time cryptocurrencies conversions Wallet Your gateway to all CoinsBank blockchain services Wallet Your gateway to all CoinsBank blockchain services Welcome to digital money The CoinsBank Wallet provides a simple way to manage your funds when and where you want.

All it takes is the click of a button, the sending of an email or the swipe of your CoinsBank Debit Card.insight API is an open-source bitcoin blockchain REST and websocket API.Insight API runs in NodeJS and uses LevelDB for storage.This is a backend-only service.If you're looking for the web frontend application, /bitpay/insight.Insight API allows to develop bitcoin-related applications (such as wallets) that require certain information from the blockchain that bitcoind does not provide.A blockchain explorer front-end has been developed on top of Insight API.It can be downloaded at Github Insight Repository.insight API needs a trusted bitcoind node to run.insight API will connect to the node through the RPC API, bitcoin peer-to-peer protocol, and will even read its raw block .dat files for syncing.Configure bitcoind to listen to RPC calls and set txindex to true.The easiest way to do this is by copying ./etc/bitcoind/bitcoin.conf to your bitcoin data directory (usually ~/.bitcoin on Linux, %appdata%\Bitcoin\ on Windows, or ~/Library/Application Support/Bitcoin on Mac OS X).

bitcoind must be running and must have finished downloading the blockchain before running insight API.Node.js v0.10.x - Download and Install Node.js.NPM - Node.js package manager, should be automatically installed when you get node.js.Check the Prerequisites section above before installing.To install Insight API, clone the main repository: Then open a browser and go to: Please note that the app will need to sync its internal database with the blockchain state, which may take some time.You can check sync progress at http://localhost:3001/api/sync.All configuration is specified in the config folder, particularly the config.js file.There you can specify your application name and database name.Certain configuration values are pulled from environment variables if they are defined: Make sure that bitcoind is configured to accept incoming connections using 'rpcallowip'.In case the network is changed (testnet to livenet or vice versa) levelDB database needs to be deleted.

This can be performed running: util/sync.js -D and waiting for insight to synchronize again.Once the database is deleted, the sync.js process can be safely interrupted (CTRL+C) and continued from the synchronization process embedded in main app.The initial synchronization process scans the blockchain from the paired bitcoind server to update addresses and balances.insight-api needs exactly one trusted bitcoind node to run.This node must have finished downloading the blockchain before running insight-api.While insight is synchronizing the website can be accessed (the sync process is embedded in the webserver), but there may be missing data or incorrect balances for addresses.The 'sync' status is shown at the /api/sync endpoint.The blockchain can be read from bitcoind's raw .dat files or RPC interface.Reading the information from the .dat files is much faster so it's the recommended (and default) alternative..dat files are scanned in the default location for each platform (for example, ~/.bitcoin on Linux).

In case a non-standard location is used, it needs to be defined (see the Configuration section).As of June 2014, using .dat files the sync process takes 9 hrs.for livenet and 30 mins.While synchronizing the blockchain, insight-api listens for new blocks and transactions relayed by the bitcoind node.Those are also stored on insight-api's database.In case insight-api is shutdown for a period of time, restarting it will trigger a partial (historic) synchronization of the blockchain.Depending on the size of that synchronization task, a reverse RPC or forward .dat syncing strategy will be used.If bitcoind is shutdown, insight-api needs to be stopped and restarted once bitcoind is restarted.Old blockchain data can be manually synced issuing: Check util/sync.js --help for options, particulary -D to erase the current DB.NOTE: there is no need to run this manually since the historic synchronization is built in into the web application.Running insight-api normally will trigger the historic sync automatically.

To store the blockchain and address related information, insight-api uses LevelDB.Two DBs are created: txs and blocks.By default these are stored on Please note that some older versions of Insight-API store that on /db.This can be changed at config/config.js.As of June 2014, storing the livenet blockchain takes ~35GB of disk space (2GB for the testnet).To run insight locally for development with grunt: Contributions and suggestions are welcome at insight-api github repository.Since v0.2 a new cache schema has been introduced.Only information from transactions with INSIGHT_SAFE_CONFIRMATIONS settings will be cached (by default SAFE_CONFIRMATIONS=6).There are 3 different caches: Cache data is only populated on request, i.e., only after accessing the required data for the first time, the information is cached, there is not pre-caching procedure.To ignore cache by default, use INSIGHT_IGNORE_CACHE.Also, address related calls support ?noCache=1 to ignore the cache in a particular API request.

By default, insight provides a REST API at /api, but this prefix is configurable from the var apiPrefix in the config.js file.The response contains the value in Satoshis.### Unspent Outputs Please note that in case confirmations are cached (which happens by default when the number of confirmations is bigger that INSIGHT_SAFE_CONFIRMATIONS) the response will include the pair confirmationsFromCache:true, and confirmations will equal INSIGHT_SAFE_CONFIRMATIONS.See noCache and INSIGHT_IGNORE_CACHE options for details.Note: if pagination params are not specified, the result is an array of transactions.The web socket API is served using socket.io.The following are the events published by insight: 'tx': new transaction received from network.This event is published in the 'inv' room.Data will be a app/models/Transaction object.Sample output: 'block': new block received from network.Data will be a app/models/Block object.Sample output: '': new transaction concerning received from network.

This event is published in the '' room.'status': every 1% increment on the sync task, this event will be triggered.This event is published in the 'sync' room.The following html page connects to the socket.io insight API and listens for new transactions.Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.