ac85264a28
Address().fromBuffer(buf);
2014-09-17 14:22:18 -07:00
8a52e6c316
Block
2014-09-16 18:42:11 -07:00
0d180810de
Blockheader
2014-09-16 17:28:00 -07:00
7ea66e032f
add real-world tx to transaction test
2014-09-16 14:39:51 -07:00
5b25679e15
Transaction
2014-09-16 14:35:26 -07:00
03291f9f89
add ECDSA example
2014-09-16 11:54:38 -07:00
6c42969d01
improve error message
2014-09-16 11:44:51 -07:00
6e9755b009
sign, verify convenience functions
2014-09-16 11:34:28 -07:00
ed335f35f7
throw error if hashbuf is not 32 bytes
2014-09-16 11:33:49 -07:00
0dd078a280
Merge pull request #511 from chjj/fix_paypro_example
...
paypro: fix example server for no-tx argument.
2014-09-16 10:37:04 -07:00
3daeabaf30
"undefined"s are unnecessary
2014-09-16 10:10:06 -07:00
a426ecb9b8
paypro: fix example server for no-tx argument.
2014-09-15 19:07:28 -07:00
ced35a07eb
Txout
2014-09-15 18:38:21 -07:00
42130c78a0
Txin
2014-09-15 17:08:09 -07:00
4594cbb9e7
add bn support to varint class
2014-09-15 15:29:39 -07:00
2f9bc222e5
expose varint in bitcore bundle
2014-09-15 15:10:24 -07:00
3fa651e553
disable examples in browser
2014-09-15 15:09:50 -07:00
f6a8878aa2
Varint class
...
...will be useful in transactions. Note that we already have a primitive
understanding of Varints in the BufferReader and BufferWriter classes. However,
the new Varint class is a varint object which actually depends on BufferReader
and BufferWriter for reading and writing varints. This class is for keeping
track of the raw buffer that is read in from a buffer.
2014-09-15 15:05:54 -07:00
54e705f7e8
missing semicolon
2014-09-15 14:53:42 -07:00
9cb31ebb6a
extra semicolon
2014-09-15 14:52:43 -07:00
4bb9105b2d
varInt -> varint
...
I don't like having to capitalize things unnecessarily
2014-09-15 14:41:46 -07:00
30c96721a0
varIntNum
2014-09-15 14:36:31 -07:00
d363956ba1
add readVarIntBuf function
...
...will be useful for new Varint class
2014-09-15 14:27:42 -07:00
3c668c9cf0
readVarInt -> readVarIntNum
...
"varInt" refers to the varInt object, which is not actually implemented yet.
This function should therefore really be called readVarIntNum.
2014-09-15 14:19:08 -07:00
8e959426e2
support reading varInt nums up to js precision
...
Javascript only supports 64 bit floating points, which have uint precision up
to Math.pow(2, 53). We now support reading variable sized numbers up to that
size. If the number is bigger than that, then we need to use BN.
2014-09-15 13:58:24 -07:00
cf4668f501
typo
2014-09-15 13:56:42 -07:00
9d5d136993
"function" not used
2014-09-15 13:48:51 -07:00
adbb260e70
also have keys and messages
2014-09-15 13:35:50 -07:00
543762bc67
fromBuffer convenience function for pubkey
2014-09-15 11:32:39 -07:00
385edbcc92
simplify ECIES interface
...
the toKeypair doesn't really need to be a keypair. upon encrypting, it merely
needs to be a pubkey. and upon decrypting, it needs to be a privkey.
2014-09-15 11:19:18 -07:00
8dc6a5023a
test the case when no fromkeypair is used
...
...during encryption, and make sure you can still decrypt the message.
2014-09-15 10:52:32 -07:00
fbfa64582c
autogenerated fromkeypair if not present
2014-09-15 10:43:14 -07:00
4a027e260a
Address().fromScript(script)
...
It is convenient to be able to derive an address directly from a script for
p2sh transactions.
2014-09-12 17:49:01 -07:00
79d79012d4
fix bug where you can't use isForMe without payloadKeypair
...
It should be possible to check to see if a message isForMe with only the
scanKeypair, and not the payloadKeypair. There was a bug where only the
scanKeypair was being used to produce the receiveKeypair, but this was a
mistake. Both the scanPubkey and payloadPubkey should be necessary to produce
the receivePubkey, and both the scanPrivkey and payloadPrivkey should be
necessary to produce the receivePrivkey. If an online computer has only the
public keys of both (and the scanPrivkey), then that is good enough to check
for isForMe.
2014-09-12 17:24:00 -07:00
a095341a07
print the public key
2014-09-12 13:37:22 -07:00
8b875a5926
making a keypair is unnecessary
2014-09-12 13:26:14 -07:00
aa4251bff6
typo
2014-09-12 13:00:52 -07:00
88f3690ef6
StealthMessage example
2014-09-12 12:55:11 -07:00
5a86a1a5c6
StealthMessage
...
This code should be regarded as being a proof-of-concept, and needs more review
before being used in production code. At least one thing is guaranteed to
change, and that is the format of a stealth address.
2014-09-10 14:00:53 -07:00
19d7befc5e
Merge pull request #508 from chjj/pem_fix
...
PEM parsing fix
2014-09-10 12:42:58 -07:00
2a696b5b6f
root-certs: ensure JSON parses properly.
2014-09-10 10:20:11 -07:00
59ac7079b1
paypro: convert root certs to json.
2014-09-09 17:52:13 -07:00
3a3c546310
root-certs: move function out of root certs file.
2014-09-09 17:15:13 -07:00
d088e0d7f2
v0.1.36
2014-09-08 15:51:14 -07:00
d5618c186f
syntax fix - typeof is not a function, it's an operator
...
following the comment of @shesek here: https://github.com/bitpay/bitcore/pull/500/files#r16642032
`typeof(foo)` should be `typeof foo`
2014-09-06 00:47:44 -04:00
5145272575
paypro: handle concatenated pems in pem parser.
2014-09-05 17:56:13 -07:00
8593ad461e
paypro: pem parsing - rename variables.
2014-09-05 17:52:14 -07:00
6e329b15bb
paypro: add a full PEM parsing function.
2014-09-05 17:52:14 -07:00
9dbe45ad03
paypro: account for PEM metadata as per rfc1424.
2014-09-05 17:52:14 -07:00
90f99fe744
Merge pull request #506 from chjj/paypro
...
Payment Protocol: Improvements.
2014-09-04 16:12:10 -07:00
Ryan X. Charles
Ryan X. Charles
Christopher Jeffrey
Sagiv Ofek