Skip to content
This repository has been archived by the owner on Jun 7, 2023. It is now read-only.

Allow usage of other sec levels in accounts #172

Open
kwek20 opened this issue May 30, 2019 · 0 comments
Open

Allow usage of other sec levels in accounts #172

kwek20 opened this issue May 30, 2019 · 0 comments

Comments

@kwek20
Copy link
Contributor

kwek20 commented May 30, 2019

Currently when you are running security level 3, using previously generated CDA for security 1 or 2, will generate invalid signature bundles. (we add 2 six tx instead of 0/1, and possibly some signature generation mistake)
kwek20 pushed a commit to kwek20/iota-java that referenced this issue May 30, 2019
Fixed error in test forwrong sec level, made ticket iotaledger#172
efecd1a
kwek20 added a commit that referenced this issue May 30, 2019
@kwek20
Test revamp (#173)
4ffd09c 
* Added and updated unit tests, moved files around

* Added javadoc to important classes, updated plugin implementation

* Added balance tests, fixed issues that arose

* Added getter for api options, fixed local POW, Added try/catch over local POW

* Updated comments

* Split account test in 2 separate classes

* Updated tests

* Set default sec level to 3

* Fixed error in test for wrong sec level, made ticket #172

* Moved NotPromotableError back to IotaAPI

* Made some tests regression tagged, removed System.out as outputstream for accounts

* Updated all imports and blocked warnings which are intended
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kwek20