ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
INDY-NODE
2
ResultTicketDemo linkDemo description
3
Extended Consensus protocol with BLS multi-signaturesINDY-670demo (09:40)How BLS code is organized in plenum; what tests we have
4
State Proofs supportINDY-790demo (02:26)Shows new Reply JSON with state proofs there
5
 Supported state proofs in CLIdemo (01:30)Shows that it's possible to get a result from just one Node in current CLI
6
Supported Protocol version to match communication between clients and the poolINDY-877demo (02:48)Shows how Protocol version is used for backward compatibility of old clients
(without state proofs) with new Pool (with state proofs)
7
Incubation: Support for multiple pool networks / proper directories layoutINDY-831demo (02:05)Shows new layout for files and folders
8
INDY-832
9
INDY-833
10
Incubation: Splint CI and CD pipelinesINDY-834
INDY-835
INDY-836		demo (03:02)Shows new Jenkinsfiles in the code (one for public CI; one for private CD)
11
Incubation: Rebranding to Indy in plenum, node, anoncreds, sovrinINDY-829
INDY-830
INDY-855		demo (15:10)Describes how we get rid of all sovrin branding
12
 Implemented rebranding migration of walletINDY-830demo (01:36)Describes rebranding support in wallets and environments (docker, vagrant)
13
 Supported rebranding in Docker and Vagrant environments of sovrin-environmentsINDY-891
14
Supported new repo for indy-crypto in CI/CDINDY-882demo (02:37)Shows CI/CD for indy-crypto library
15
Fixed some bugs related to Upgrade
16
Fixed some bugs related to Stability
17
Updated documentation in indy-nodeINDY-754
18
19
INDY-SDK
20
ResultTicketDemo link
21
Implemented generic-keys based crypto support (in code review)IS-357demo (02:14)Before it was possible to only use keys assigned to DIDs and crypto functions were only allowed to perform only DID-based encryption and signatures creation. Starting from next libindy release it will be possible to create, store and use keys detached from DIDs
22
DID-based crypto becomes a subset of generic-keys based crypto (in code review)IS-357Creation of my did causes creation of generic-key in a compatible format. The key id can be resolved with the key_for_did method and used in any generic-keys based functions. Functions for DID-based crypto are still here but will be replaced in the future with generic-keys based crypto functions.
23
Implemented the new approach for agents communication (in code review)IS-357The approach of agents communication is completely changed. Instead of using proprietary secure transport layer protocol libindy will provide generic helpers to create authenticated and encrypted messages. This messages exchange doesn't require a complex handshake-based protocol. Messages can be sent through an insecure channel (http, unencrypted zmq)
24
Implemented helper-methods to securely store any application-specific metadata with the key, did or pairwise (in code review)IS-357
25
Tests and wrappers update to support API changes (in code review)IS-387
26
Updated Default Wallets To Use SQLCipher (in code review)IS-373
27
Bug fixes:
28
 CI for RC branch (rc and stable builds) is broken after splitting to CI and CDIS-389
29
 indy_set_pairwise_metadata does not allow null or empty values for metadataIS-378
30
 Unable to connect to pool with libindy if genesis file has quotes around port numbersIS-388Available only in "rc" branch now
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100