Pavel 'PK' Kaminsky f46ae7d731 crypto.sha256 should receive a Buffer as an input rather than a string ... checked and it works with buffers. if you wanted to use string implicitly, the function parameter should be renamed from buffer to string. f4caaf42e7/src/crypto.js (L11)		2017-12-29 00:55:16 +02:00
..
fixtures	ECSignature: add toRSBuffer/fromRSBuffer	2017-10-19 13:41:35 +11:00
integration	crypto.sha256 should receive a Buffer as an input rather than a string	2017-12-29 00:55:16 +02:00
address.js	add Bech32 support to toOutputScript/fromOutputScript	2017-08-21 11:17:30 +10:00
bitcoin.core.js	tests: use safe-buffers throughout	2017-05-23 18:39:53 +10:00
block.js	block: add byteLength	2017-04-18 13:46:30 +10:00
bufferutils.js	tests: use safe-buffers throughout	2017-05-23 18:39:53 +10:00
crypto.js	tests: use safe-buffers throughout	2017-05-23 18:39:53 +10:00
ecdsa.js	tests: use safe-buffers throughout	2017-05-23 18:39:53 +10:00
ecpair.js	tests: use safe-buffers throughout	2017-05-23 18:39:53 +10:00
ecsignature.js	tests: use safe-buffers throughout	2017-05-23 18:39:53 +10:00
hdnode.js	tests: use safe-buffers throughout	2017-05-23 18:39:53 +10:00
script.js	tests: script tests can validate template fixtures too	2017-09-22 11:33:32 +10:00
script_number.js	tests: use safe-buffers throughout	2017-05-23 18:39:53 +10:00
templates.js	tests: add passing and failing tests for witness*.input.encode/decode	2017-09-27 08:30:20 +10:00
transaction.js	Testing virtualSize and weight	2017-06-21 01:38:05 +10:00
transaction_builder.js	tests: fix should warn fee fail	2017-12-01 13:06:35 +11:00
types.js	tests: use safe-buffers throughout	2017-05-23 18:39:53 +10:00