Open MentalNomad opened 4 years ago
The same is true for production:
https://github.com/binance-chain/node-binary/blob/master/lightnode/prod/0.6.3/windows/lightd.exe EF1E147A8F5625880019F7E6F70E68575ED5D3E621533A3107025CE884C07A72
(Apparently the same file for production & testnet?)
https://github.com/binance-chain/node-binary/blob/master/lightnode/prod/0.6.3/windows/sha256checksum c0380f7da2de099a04dc061e727fb86ac9209603a7afae4200fe30156d403d9f lightd
It appears to be the checksum for the prior version - note:
https://github.com/binance-chain/node-binary/blob/master/lightnode/prod/0.6.2/windows/lightd.exe EF1E147A8F5625880019F7E6F70E68575ED5D3E621533A3107025CE884C07A72
https://github.com/binance-chain/node-binary/blob/master/lightnode/prod/0.6.2/windows/sha256checksum ef1e147a8f5625880019f7e6f70e68575ed5d3e621533a3107025ce884c07a72 lightd.exe
Hello, @MentalNomad
This issue is because the binaries are stored with git lfs
Am looking for the Windows light node, but the following file: https://github.com/binance-chain/node-binary/blob/master/lightnode/testnet/0.6.3/windows/lightd.exe
Has checksum of: EF1E147A8F5625880019F7E6F70E68575ED5D3E621533A3107025CE884C07A72
But the checksum indicated here: https://github.com/binance-chain/node-binary/blob/master/lightnode/testnet/0.6.3/windows/sha256checksum indicates it should be: c0380f7da2de099a04dc061e727fb86ac9209603a7afae4200fe30156d403d9f lightd