Indy-node

Latest version: v1.13.2

Safety actively analyzes 626157 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 7 of 10

1.2.42

1.2.34

1.2.29

1.1.89

Additional Information:

**There are possible OOM issues during 3+ hours of target load or large catch-ups at 8 GB RAM nodes pool so 32 GB is recommended.**

Major Changes
- NYM dynamic validation check transaction w/out verkey or role

Detailed Changelog

Changes and Additions
| Description | Additional Information | Ticket Number |
| --- | --- | --- |
| NYM dynamic validation check transaction w/out verkey or role | | |

1.1.81

Additional Information:

**There are possible OOM issues during 3+ hours of target load or large catch-ups at 8 GB RAM nodes pool so 32 GB is recommended.**

Major Changes
- Bug fix

Detailed Changelog

Major Fixes
| Description | Additional Information | Ticket Number |
| --- | --- | --- |
| TAA signature's validation fix (milliseconds sending broke the primary) | | |

1.1.71

Additional Information:

**Stop indy-node service on demoted nodes to avoid a minor issue with client's requests processing (see Known Issues for details).**

**There are possible OOM issues during 3+ hours of target load or large catch-ups at 8 GB RAM nodes pool so 32 GB is recommended.**

Major Changes
- Stability fixes

Detailed Changelog

Major Fixes
| Description | Additional Information | Ticket Number |
| --- | --- | --- |
| WARNING messages incorrectly logged if tokens are not used | | [INDY-2221](https://jira.hyperledger.org/browse/INDY-2221) |
| REV_REG_DEF `tag` field is not validated | | [INDY-2314](https://jira.hyperledger.org/browse/INDY-2314) |
| A node may re-send messages in a loop in case of connection issues | | [INDY-2318](https://jira.hyperledger.org/browse/INDY-2318) |
| Up to F Nodes may not be able to finish View Change if there are uncommitted NODE txns | | [INDY-2319](https://jira.hyperledger.org/browse/INDY-2319) |
| A node lagging behind may not be able to finish view change if nodes have been added/demoted | | [INDY-2308](https://jira.hyperledger.org/browse/INDY-2308) |
| A lagging node may use wrong N and F quorum values and never finish view change if there are NODE txns being processed | | [INDY-2320](https://jira.hyperledger.org/browse/INDY-2320) |
| A lagging node may be the only one who started view change in case of F Nodes added/promoted in 1 batch | | [INDY-2322](https://jira.hyperledger.org/browse/INDY-2322) |
| Debug View Change when nodes added/demoted/promoted | | [INDY-2326](https://jira.hyperledger.org/browse/INDY-2326) |

Known Issues
| Description | Additional Information | Ticket Number |
| --- | --- | --- |
| Demoted Node should not process client's requests | | [INDY-2334](https://jira.hyperledger.org/browse/INDY-2334) |

Page 7 of 10

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.