Security News
pnpm 10.0.0 Blocks Lifecycle Scripts by Default
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
Infrastructure to build Bitcoin and blockchain-based applications for the next generation of financial technology.
Note: If you're looking for the Litecore Library please see: https://github.com/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.
npm install -g litecore
Spin up a full node and join the network:
npm install -g litecore
litecored
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
.
Create a transaction:
var litecore = require('litecore');
var transaction = new litecore.Transaction();
var transaction.from(unspent).to(address, amount);
transaction.sign(privateKey);
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.
If you find a security issue, please email security@bitpay.com.
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.
This will generate files named litecore.js
and litecore.min.js
.
You can also use our pre-generated files, provided for each release along with a PGP signature by one of the project's maintainers. To get them, checkout a release commit (for example, https://github.com/bitpay/bitcore/commit/e33b6e3ba6a1e5830a079e02d949fce69ea33546 for v0.12.6).
To verify signatures, use the following PGP keys:
D909 EFE6 70B5 F6CC 89A3 607A 9BBF 07CA C07A 276D
F3EA 8E28 29B4 EC93 88CB B0AA 4414 3098 7182 732C
F8B0 891C C459 C197 65C2 5043 3319 5D27 EF6B DB7F
25CE ED88 A1B1 0CD1 12CD 4121 9EDE 6DE4 DE53 1FAC
Code released under the MIT license.
Copyright 2013-2015 BitPay, Inc. Bitcore is a trademark maintained by BitPay, Inc. Copyright 2016 The Litecore Core Developers
FAQs
A platform to build bitcoin and blockchain-based applications.
The npm package litecore receives a total of 4 weekly downloads. As such, litecore popularity was classified as not popular.
We found that litecore demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
Product
Socket now supports uv.lock files to ensure consistent, secure dependency resolution for Python projects and enhance supply chain security.
Research
Security News
Socket researchers have discovered multiple malicious npm packages targeting Solana private keys, abusing Gmail to exfiltrate the data and drain Solana wallets.