Feat/issue badge non can account #9
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
quocle108
commented
Apr 9, 2020
quocle108
commented
- allow 3rd-party(ram.can) pay ram for all action from users/issuers
- issue badge to non-CAN account by issued to ghost account, user can claim certification later once they has CAN account
- Removed offer/claim part which is no longer used
danielvo11
reviewed
Apr 9, 2020
|
@danielalvess Pls verify again |
This was referenced Apr 21, 2020
quocle108
added a commit
that referenced
this pull request
Apr 21, 2020
* 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]>
danielvo11
added a commit
that referenced
this pull request
Apr 23, 2020
* 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]>
danielvo11
added a commit
that referenced
this pull request
Dec 14, 2020
* 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]>
danielvo11
added a commit
that referenced
this pull request
Dec 14, 2020
* 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>
quocle108
added a commit
that referenced
this pull request
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.