cryptobadge::revokecert action doesn't allow to update encrypted data
#25
Comments
danielvo11
added a commit
that referenced
this issue
Dec 14, 2020
danielvo11
added a commit
that referenced
this issue
Dec 14, 2020
danielvo11
added a commit
that referenced
this issue
Dec 14, 2020
quocle108
pushed a commit
that referenced
this issue
Dec 23, 2020
quocle108
added a commit
that referenced
this issue
Feb 4, 2021
* required 2 signatures to create-issue a badge * release v1.0.0 (#4) (#5) * release v1.0.0 * fixed remove unused * fix/correct params name and revove encrypted data in state data (#10) * Revert "fix/correct params name and revove encrypted data in state data (#10)" (#11) This reverts commit 55ab08d. * fix/correct params name and remove encrypted data in cert state data (#13) * feat/gitlab#127 contract owner should be able to set governance contract name (#14) * Feat/issue badge non can account (#9) * issue badge to non CAN account * allow 3rd party pay RAM for all transactions * rename action issuecert to issuebadge * add claimbadge+logissue to ricardian contract * feat/#15 add unit test (#16) * Pull from master (#20) * Merge master (#27) * release v1.0.0 (#4) * release v1.0.0 * Release Note v2.0.0 (#18) * required 2 signatures to create-issue a badge * release v1.0.0 (#4) (#5) * release v1.0.0 * fixed remove unused * fix/correct params name and revove encrypted data in state data (#10) * Revert "fix/correct params name and revove encrypted data in state data (#10)" (#11) This reverts commit 55ab08d. * fix/correct params name and remove encrypted data in cert state data (#13) * feat/gitlab#127 contract owner should be able to set governance contract name (#14) * Feat/issue badge non can account (#9) * issue badge to non CAN account * allow 3rd party pay RAM for all transactions * rename action issuecert to issuebadge * add claimbadge+logissue to ricardian contract * feat/#15 add unit test (#16) * add run binary file * update table name refer from governance design v2.0.0 Co-authored-by: danielAlvess <[email protected]> * Bump lodash from 4.17.15 to 4.17.19 (#24) Bumps [lodash](https://github.com/lodash/lodash) from 4.17.15 to 4.17.19. - [Release notes](https://github.com/lodash/lodash/releases) - [Commits](lodash/lodash@4.17.15...4.17.19) Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: ChimGoKien <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * feat/#25 allow to update encrypted data when revoke certification (#26) * fixed yarn.lock Co-authored-by: danielAlvess <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since
revocationReasonis encrypted along with other privacy info, we should somehow allow to updateencryptedDatadataThe text was updated successfully, but these errors were encountered: