akovalenko/lnd.xprv
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
f9f9d68543
lnd.xprv/glide.yaml

74 lines
1.9 KiB
YAML
Raw Normal View History

add glide dependency management for fully reproducible builds This commit adds glide integration in order to make lnd builds fully reproducible. Rather than using “go get” users should now manually pull down the repo, use glide to fetch+install the dependancies, then manually install all related binaries. With this change we no longer have to chase dependancies making breaking API changes under us. We can manually update the managed dependancies once a new stable release of a defendant package is released. Additionally, reproducible builds are a strong requirement in order to securely distribute future major releases of lnd.
2016-07-23 04:52:36 +03:00
package: github.com/lightningnetwork/lnd
import:
- package: github.com/boltdb/bolt
version: ^1.2.1
- package: github.com/btcsuite/btclog
build: update new logging related dependancies to latest versions
2017-07-07 00:36:09 +03:00
version: 84c8d2346e9fc8c7b947e243b9c24e6df9fd206a
add glide dependency management for fully reproducible builds This commit adds glide integration in order to make lnd builds fully reproducible. Rather than using “go get” users should now manually pull down the repo, use glide to fetch+install the dependancies, then manually install all related binaries. With this change we no longer have to chase dependancies making breaking API changes under us. We can manually update the managed dependancies once a new stable release of a defendant package is released. Additionally, reproducible builds are a strong requirement in order to securely distribute future major releases of lnd.
2016-07-23 04:52:36 +03:00
- package: github.com/btcsuite/go-flags
lnd: remove seelog logger The btclog package has been changed to defining its own logging interface (rather than seelog's) and provides a default implementation for callers to use. There are two primary advantages to the new logger implementation. First, all log messages are created before the call returns. Compared to seelog, this prevents data races when mutable variables are logged. Second, the new logger does not implement any kind of artifical rate limiting (what seelog refers to as "adaptive logging"). Log messages are outputted as soon as possible and the application will appear to perform much better when watching standard output. Because log rotation is not a feature of the btclog logging implementation, it is handled by the main package by importing a file rotation package that provides an io.Reader interface for creating output to a rotating file output. The rotator has been configured with the same defaults that btcd previously used in the seelog config (10MB file limits with maximum of 3 rolls) but now compresses newly created roll files. Due to the high compressibility of log text, the compressed files typically reduce to around 15-30% of the original 10MB file.
2017-06-21 18:07:44 +03:00
- package: github.com/jrick/logrotate
build: update new logging related dependancies to latest versions
2017-07-07 00:36:09 +03:00
version: a93b200c26cbae3bb09dd0dc2c7c7fe1468a034a
add glide dependency management for fully reproducible builds This commit adds glide integration in order to make lnd builds fully reproducible. Rather than using “go get” users should now manually pull down the repo, use glide to fetch+install the dependancies, then manually install all related binaries. With this change we no longer have to chase dependancies making breaking API changes under us. We can manually update the managed dependancies once a new stable release of a defendant package is released. Additionally, reproducible builds are a strong requirement in order to securely distribute future major releases of lnd.
2016-07-23 04:52:36 +03:00
- package: github.com/davecgh/go-spew
subpackages:
- spew
- package: github.com/golang/protobuf
subpackages:
- proto
- package: github.com/howeyc/gopass
- package: github.com/roasbeef/btcd
lnd: remove seelog logger The btclog package has been changed to defining its own logging interface (rather than seelog's) and provides a default implementation for callers to use. There are two primary advantages to the new logger implementation. First, all log messages are created before the call returns. Compared to seelog, this prevents data races when mutable variables are logged. Second, the new logger does not implement any kind of artifical rate limiting (what seelog refers to as "adaptive logging"). Log messages are outputted as soon as possible and the application will appear to perform much better when watching standard output. Because log rotation is not a feature of the btclog logging implementation, it is handled by the main package by importing a file rotation package that provides an io.Reader interface for creating output to a rotating file output. The rotator has been configured with the same defaults that btcd previously used in the seelog config (10MB file limits with maximum of 3 rolls) but now compresses newly created roll files. Due to the high compressibility of log text, the compressed files typically reduce to around 15-30% of the original 10MB file.
2017-06-21 18:07:44 +03:00
version: 34fdda7d41cc47d9456550fd1147a77db89f601a
add glide dependency management for fully reproducible builds This commit adds glide integration in order to make lnd builds fully reproducible. Rather than using “go get” users should now manually pull down the repo, use glide to fetch+install the dependancies, then manually install all related binaries. With this change we no longer have to chase dependancies making breaking API changes under us. We can manually update the managed dependancies once a new stable release of a defendant package is released. Additionally, reproducible builds are a strong requirement in order to securely distribute future major releases of lnd.
2016-07-23 04:52:36 +03:00
subpackages:
- blockchain
- btcec
- btcjson
- chaincfg
- txscript
- wire
build: update glide dependancies since roasbeef/btcsuite upstream merge
2017-01-06 01:08:22 +03:00
- connmgr
add glide dependency management for fully reproducible builds This commit adds glide integration in order to make lnd builds fully reproducible. Rather than using “go get” users should now manually pull down the repo, use glide to fetch+install the dependancies, then manually install all related binaries. With this change we no longer have to chase dependancies making breaking API changes under us. We can manually update the managed dependancies once a new stable release of a defendant package is released. Additionally, reproducible builds are a strong requirement in order to securely distribute future major releases of lnd.
2016-07-23 04:52:36 +03:00
- package: github.com/roasbeef/btcrpcclient
lnd: remove seelog logger The btclog package has been changed to defining its own logging interface (rather than seelog's) and provides a default implementation for callers to use. There are two primary advantages to the new logger implementation. First, all log messages are created before the call returns. Compared to seelog, this prevents data races when mutable variables are logged. Second, the new logger does not implement any kind of artifical rate limiting (what seelog refers to as "adaptive logging"). Log messages are outputted as soon as possible and the application will appear to perform much better when watching standard output. Because log rotation is not a feature of the btclog logging implementation, it is handled by the main package by importing a file rotation package that provides an io.Reader interface for creating output to a rotating file output. The rotator has been configured with the same defaults that btcd previously used in the seelog config (10MB file limits with maximum of 3 rolls) but now compresses newly created roll files. Due to the high compressibility of log text, the compressed files typically reduce to around 15-30% of the original 10MB file.
2017-06-21 18:07:44 +03:00
version: d0f4db8b4dad0ca3d569b804f21247c3dd96acbb
add glide dependency management for fully reproducible builds This commit adds glide integration in order to make lnd builds fully reproducible. Rather than using “go get” users should now manually pull down the repo, use glide to fetch+install the dependancies, then manually install all related binaries. With this change we no longer have to chase dependancies making breaking API changes under us. We can manually update the managed dependancies once a new stable release of a defendant package is released. Additionally, reproducible builds are a strong requirement in order to securely distribute future major releases of lnd.
2016-07-23 04:52:36 +03:00
- package: github.com/roasbeef/btcutil
build: update glide files to add neutrino, latest roasbeef forks
2017-06-06 05:30:55 +03:00
version: a259eaf2ec1b54653cdd67848a41867f280797ee
add glide dependency management for fully reproducible builds This commit adds glide integration in order to make lnd builds fully reproducible. Rather than using “go get” users should now manually pull down the repo, use glide to fetch+install the dependancies, then manually install all related binaries. With this change we no longer have to chase dependancies making breaking API changes under us. We can manually update the managed dependancies once a new stable release of a defendant package is released. Additionally, reproducible builds are a strong requirement in order to securely distribute future major releases of lnd.
2016-07-23 04:52:36 +03:00
subpackages:
- bloom
- coinset
- hdkeychain
- txsort
- package: github.com/roasbeef/btcwallet
build: update glide files to add neutrino, latest roasbeef forks
2017-06-06 05:30:55 +03:00
version: 619ff8707c1d656061ab68db882205c4f63e19df
add glide dependency management for fully reproducible builds This commit adds glide integration in order to make lnd builds fully reproducible. Rather than using “go get” users should now manually pull down the repo, use glide to fetch+install the dependancies, then manually install all related binaries. With this change we no longer have to chase dependancies making breaking API changes under us. We can manually update the managed dependancies once a new stable release of a defendant package is released. Additionally, reproducible builds are a strong requirement in order to securely distribute future major releases of lnd.
2016-07-23 04:52:36 +03:00
subpackages:
- chain
- waddrmgr
- wallet
- walletdb/bdb
build: update glide dependancies
2016-07-26 20:43:11 +03:00
- package: github.com/urfave/cli
version: ^1.18.0
add glide dependency management for fully reproducible builds This commit adds glide integration in order to make lnd builds fully reproducible. Rather than using “go get” users should now manually pull down the repo, use glide to fetch+install the dependancies, then manually install all related binaries. With this change we no longer have to chase dependancies making breaking API changes under us. We can manually update the managed dependancies once a new stable release of a defendant package is released. Additionally, reproducible builds are a strong requirement in order to securely distribute future major releases of lnd.
2016-07-23 04:52:36 +03:00
- package: golang.org/x/crypto
subpackages:
- hkdf
- nacl/secretbox
- ripemd160
- scrypt
brontide: replace aead/chacha20 with x/crypto/chacha20poly1305 This commit replaces aead’s chacha20 library with the official golang implementation. We should see a bit of a performance increase on amd64 as the assembly for the library uses the SIMD AVX2 instructions in the inner loop. In the future assembly will be written for other platforms, so we’ll see a performance increase across the board. Fixes #146.
2017-03-16 05:03:19 +03:00
- chacha20poly1305
build: update glide to add usage of salsa20
2017-04-17 01:45:49 +03:00
- salsa20
add glide dependency management for fully reproducible builds This commit adds glide integration in order to make lnd builds fully reproducible. Rather than using “go get” users should now manually pull down the repo, use glide to fetch+install the dependancies, then manually install all related binaries. With this change we no longer have to chase dependancies making breaking API changes under us. We can manually update the managed dependancies once a new stable release of a defendant package is released. Additionally, reproducible builds are a strong requirement in order to securely distribute future major releases of lnd.
2016-07-23 04:52:36 +03:00
- package: golang.org/x/net
subpackages:
- context
- package: google.golang.org/grpc
glide: pin gRPC version against the commit hash of 1.2.1 We now pin gRPC against a particular commit version as it seems that glide has some trouble properly resolving the semantic versioning constraints for the latest version of gRPC.
2017-04-24 05:11:14 +03:00
version: 8050b9cbc271307e5a716a9d782803d09b0d6f2d
build: update the glide files to include the sphinx package and pin the routing package
2016-09-21 02:33:08 +03:00
- package: github.com/lightningnetwork/lightning-onion
build: update glide to point to the latest version of lighting-onion
2017-06-11 04:15:25 +03:00
version: 9a8748f89637a86586af383a5c3f9a19cff85b4f
lnrpc: add cursory REST support to the RPC server This commit adds a REST interface to the existing gRPC server by employing a simple http proxy auto-generated from the existing protobuf files. Currently full-support for any streaming RPC’s are currently untested. In addition to auto-generating a REST proxy server, a swagger.json is also generated which allows for gRPC-like native objects with higher-level clients, and also for auto-generated documentation. Due to limitations with accepting raw byte strings as parameters, some RPC’s have been modified to take both raw-bytes and string arguments. Additionally a new RPC has been added ‘NewWitnessAddress’ since the proxy doesn’t currently support enum-based arguments. Currently the proxy server is embedded within the daemon as an active HTTP server, however we may want to package the proxy server as a separate binary in the future. Similarly, we may want to add additional configuration information which controls the optional inclusion of the REST proxy. Atm, just like the current gRPC interface, the REST API is fully unauthenticated. Before moving to an initial alpha release after making the necessary changes to meet the spec drafted in Milan, authentication of the RPC interfaces will be addressed.
2016-10-16 00:38:47 +03:00
- package: github.com/grpc-ecosystem/grpc-gateway
glide: pin gRPC version against the commit hash of 1.2.1 We now pin gRPC against a particular commit version as it seems that glide has some trouble properly resolving the semantic versioning constraints for the latest version of gRPC.
2017-04-24 05:11:14 +03:00
version: 1.1.0
testing: add CT (Custom Testing) structure; create uniq point for 'lnd process errors' and 'test panic/failed errors' handling
2016-10-15 16:47:09 +03:00
- package: github.com/go-errors/errors
zpay32: create new package for encoding/decoding payment requests This commit adds a new package “zpay32”: which is used within the daemon to encode/decode payment requests. A payment request currently consists of: the public key of the payee, the payment hash to use, and finally the amount to send over the network. The encoded payment request consists of the mentioned fields concatenated to each other, a cc32 checksum is added, then the blob is finally encoded using zbas32. I call the resulting scheme “zpay32”. A number of extensions may be explored in future commits including adding a version byte, adding “hint” routing information, cryptographically signed receipts and more,
2017-01-03 02:16:57 +03:00
- package: github.com/tv42/zbase32
cmd/lncli: add ability to render graph to 'describegraph' This commit adds an ability to render the channel graph as returned by the ‘displaygraph’ command. The rendering of the graph itself is carried about the by the ‘dot’ command which eventually calls out to graphviz. Currently the graph is always saved to the same file in the local directory, but in a later commit the location of the file will be made configurable. Finally, the attributes sent to the ‘dot’ command used to render the graph are still a bit in flux. The parameters will likely be tuned once the channel graph on testnet grows a bit more.
2017-01-24 07:32:17 +03:00
- package: github.com/awalterschulze/gographviz
version: ^1.0.0
lnrpc: update protoc invocation This commit reflects an upstream change in grpc-gateway. - regenerate proto output - add genprotos dep, updated glide deps
2017-03-27 21:01:02 +03:00
- package: google.golang.org/genproto
subpackages:
build: pin btcd fork against particular commit hash in glide
2017-03-30 02:33:59 +03:00
- googleapis/api/annotations
build: update glide to pull in github.com/ltcsuite/ltcd/chaincfg
2017-05-03 05:55:47 +03:00
- package: github.com/ltcsuite/ltcd
subpackages:
- chaincfg
build: update glide files to add neutrino, latest roasbeef forks
2017-06-06 05:30:55 +03:00
- package: github.com/lightninglabs/neutrino
lnd: remove seelog logger The btclog package has been changed to defining its own logging interface (rather than seelog's) and provides a default implementation for callers to use. There are two primary advantages to the new logger implementation. First, all log messages are created before the call returns. Compared to seelog, this prevents data races when mutable variables are logged. Second, the new logger does not implement any kind of artifical rate limiting (what seelog refers to as "adaptive logging"). Log messages are outputted as soon as possible and the application will appear to perform much better when watching standard output. Because log rotation is not a feature of the btclog logging implementation, it is handled by the main package by importing a file rotation package that provides an io.Reader interface for creating output to a rotating file output. The rotator has been configured with the same defaults that btcd previously used in the seelog config (10MB file limits with maximum of 3 rolls) but now compresses newly created roll files. Due to the high compressibility of log text, the compressed files typically reduce to around 15-30% of the original 10MB file.
2017-06-21 18:07:44 +03:00
version: ccfa94a1c213e5df752c08c7edc30cb0a56d4dcf
Reference in New Issue Copy Permalink