ca333
bcd6be86c5
Merge pull request #130 from KomodoPlatform/zmq_update
...
update zmq
2019-02-17 21:46:47 +01:00
ca333
7d50f06c76
add ZMQ to WIN
2019-02-17 18:21:18 +01:00
ca333
af9ff2e620
update zeromq
2019-02-17 18:20:57 +01:00
ca333
ec95ae2d65
remove ZMQ from WIN
2019-02-17 17:14:18 +01:00
ca333
4f5ba23dfc
set static ZMQ flag
2019-02-17 16:05:19 +01:00
ca333
5c6ca4c291
update ZMQ
2019-02-17 15:15:17 +01:00
ca333
459faf5fe2
Merge pull request #129 from KomodoPlatform/master
...
update zmq
2019-02-17 15:13:44 +01:00
ca333
d6309d063a
update zmq
2019-02-17 15:09:21 +01:00
ca333
728c8f1e3d
Merge pull request #119 from jl777/master
...
update master
2019-01-27 04:30:51 +01:00
ca333
b08d57ca48
resolve conflict
...
jl777:master->komodoplatform:master
2019-01-19 19:00:26 +01:00
jl777
7598204bf9
Fix bip44 code
2019-01-10 18:49:38 -11:00
ca333
a47ba0cf7a
update BIP44 cointype
...
use correct assigned BIP44 cointype
2019-01-11 05:53:17 +01:00
ca333
5119a1d3c9
Merge pull request #115 from jl777/master
...
update master
2019-01-09 14:46:41 +01:00
jl777
93b616becd
Move WITNESS_CACHE_SIZE
2019-01-09 02:32:11 -11:00
jl777
9040d03af6
Match WITNESS_CACHE_SIZE to maxreorg
2019-01-09 02:21:47 -11:00
SHossain
cdbeddb728
Merge pull request #113 from jl777/master
...
master
2019-01-09 13:06:00 +00:00
jl777
ba1b2b5c56
-Static assert
2019-01-09 01:43:10 -11:00
jl777
1f46aa58e6
Allow tunable maxreorg
2019-01-09 01:26:25 -11:00
jl777
8a5f7bdf6a
Version 0.3.3b
2019-01-09 00:05:22 -11:00
jl777
0e49163d4a
Jan 15th activation of stricter block checks
2019-01-09 00:04:30 -11:00
jl777
cb64a2dc56
Activate jan 15th
2019-01-08 23:20:34 -11:00
jl777
8e172149f6
Add context check in connectTip
2019-01-08 23:19:28 -11:00
ca333
db0dfe8fbf
Merge pull request #110 from jl777/master
...
update master
2019-01-07 21:10:37 +01:00
jl777
ce5995738b
Update version
2019-01-07 07:43:15 -11:00
jl777
7d56db54d1
Messages
2019-01-07 07:33:23 -11:00
ca333
6decb5e22b
update libsodium url
...
fix broken path
2019-01-07 19:06:21 +01:00
jl777
f68daa998d
Merge pull request #1143 from wallnutkraken/master
...
Fixed a 404'd libsodium link
2019-01-07 03:28:53 -11:00
wallnutkraken
536580bdec
Fixed a 404'd libsodium link
2019-01-06 22:10:59 +01:00
jl777
93f18db31a
Skip unspendable addresses in migrate
2018-12-19 09:25:38 -11:00
jl777
97658a0c03
z_mergetoaddress fix
2018-12-19 09:03:54 -11:00
ca333
8da329cfdb
Merge pull request #103 from jl777/master
...
update master
2018-12-18 23:04:14 +01:00
jl777
b3837525ee
New migrate
2018-12-18 09:00:04 -11:00
ca333
c034d46ef9
Merge pull request #102 from jl777/master
...
update master
2018-12-17 00:11:52 +01:00
jl777
c4e6e8b377
Merge pull request #1104 from jl777/beta
...
Beta
2018-12-16 11:05:03 -11:00
jl777
76324976dc
Merge pull request #1101 from jl777/dev
...
Dev
2018-12-16 10:16:20 -11:00
jl777
365674f38d
Merge pull request #1103 from jl777/FSM
...
FSM
2018-12-16 10:13:03 -11:00
jl777
5ef1e607d0
Merge pull request #1102 from jl777/jl777
...
Jl777
2018-12-16 10:10:56 -11:00
jl777
1f6f5c2975
Error check
2018-12-16 10:02:53 -11:00
jl777
78a4e17981
-compile script
2018-12-16 07:47:00 -11:00
jl777
4a3720060c
Merge pull request #1100 from jl777/FSM
...
FSM
2018-12-16 07:42:04 -11:00
jl777
1d4194841d
Fix stuck sync for nodes that are doing full sync
...
The sapling height is calculated near the sapling activation timestamp.
Until it is set, the node doesn’t know when sapling should be active.
Depending on the speed at which you get blocks from the future, it was
possible that you could see a sapling active block before the sapling
height was set. This would happen only if syncing from a node that
didn’t know the sapling height and a full resync with the most peers
and most variety of incoming block sources was most likely hit by this.
The net effect was that the blocks after sapling activation were marked
as invalid, so by the time the node synced up to the sapling height, it
couldn’t advance.
2018-12-16 07:41:17 -11:00
jl777
fe32a3be6c
Fix stuck sync for nodes that are doing full sync
...
The sapling height is calculated near the sapling activation timestamp.
Until it is set, the node doesn’t know when sapling should be active.
Depending on the speed at which you get blocks from the future, it was
possible that you could see a sapling active block before the sapling
height was set. This would happen only if syncing from a node that
didn’t know the sapling height and a full resync with the most peers
and most variety of incoming block sources was most likely hit by this.
The net effect was that the blocks after sapling activation were marked
as invalid, so by the time the node synced up to the sapling height, it
couldn’t advance.
2018-12-16 07:39:54 -11:00
jl777
b60630d5e3
Syntax
2018-12-16 06:51:27 -11:00
jl777
dd3e21e79d
Test
2018-12-16 06:50:26 -11:00
jl777
fe4eb7bb92
Syntax
2018-12-16 06:49:27 -11:00
jl777
58cecce562
GetHeight()
2018-12-16 06:46:53 -11:00
jl777
4c19213416
Test clean sync
2018-12-16 06:43:39 -11:00
jl777
0a07654961
Merge pull request #1095 from blackjok3rtt/FSM
...
Fix setgenerate and proclimit.
2018-12-16 06:02:05 -11:00
blackjok3r
f9260ac43f
fix
2018-12-17 00:57:23 +08:00
jl777
9df94d325c
Merge pull request #1098 from jl777/dev
...
Dev
2018-12-16 05:53:53 -11:00
