-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Registration of accounts without signatories #4212
Labels
api-changes
Changes in the API for client libraries
iroha2-dev
The re-implementation of a BFT hyperledger in RUST
Comments
Arjentix
added a commit
to Arjentix/iroha
that referenced
this issue
Feb 20, 2024
…t signatures Signed-off-by: Daniil Polyakov <[email protected]>
Arjentix
added a commit
to Arjentix/iroha
that referenced
this issue
Feb 20, 2024
…t signatures Signed-off-by: Daniil Polyakov <[email protected]>
5 tasks
Arjentix
added a commit
to Arjentix/iroha
that referenced
this issue
Feb 21, 2024
…t signatures Signed-off-by: Daniil Polyakov <[email protected]>
Arjentix
added a commit
to Arjentix/iroha
that referenced
this issue
Feb 23, 2024
…t signatures Signed-off-by: Daniil Polyakov <[email protected]>
Arjentix
added a commit
to Arjentix/iroha
that referenced
this issue
Feb 23, 2024
…t signatures Signed-off-by: Daniil Polyakov <[email protected]>
Arjentix
added a commit
that referenced
this issue
Feb 26, 2024
Signed-off-by: Daniil Polyakov <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
api-changes
Changes in the API for client libraries
iroha2-dev
The re-implementation of a BFT hyperledger in RUST
Currently we seem to allow this, but we don't allow burning the last signatory of an account (we have a test ensuring this
public_keys_cannot_be_burned_to_nothing
). Should we also prevent creation ofAccount
/NewAccount
without signatories. If so, then I propose to make modifications to all the constructorsAccount::new
/Decode
/Deserialize
to only allow creation ofAccounts
with at least one signatoryThis might be a potentially API changing modification
The text was updated successfully, but these errors were encountered: