Skip to content
Snippets Groups Projects
  1. Jun 06, 2022
    • Abhishek Ranjan's avatar
      chore(prot): enable checktx priority for synthetic txns [AC-1547] · 7c5943b0
      Abhishek Ranjan authored and Dennis B's avatar Dennis B committed
      Closes AC-1547. Enable checktx priority for synthetic txns
      
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [ ] The merge request title is in the format `<change type>(<change scope>): <short description> [<task id>]`
        - For example, `feat(cli): add QR code generation [AC-123]`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [ ] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [ ] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [ ] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [ ] CI is passing
      - [ ] Merge conflicts are resolved
      - [ ] All discussions are resolved
      
      Related to AC-1547
      7c5943b0
  2. Jun 02, 2022
    • Ethan Reesor's avatar
      feat(prot): enforce TLD for identities [AC-1489] · acdf4f14
      Ethan Reesor authored
      Closes AC-1489. Force ADIs to have a .acme TLD.
      
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [x] The merge request title is in the format `<change type>(<change scope>): <short description> [<task id>]`
        - For example, `feat(cli): add QR code generation [AC-123]`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [x] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [x] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [x] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [ ] CI is passing
      - [ ] Merge conflicts are resolved
      - [ ] All discussions are resolved
      
      Related to AC-1489
      acdf4f14
    • Ethan Reesor's avatar
      fix(prot): check synth txn keys [AC-1484] · 9d334bd3
      Ethan Reesor authored
      Closes AC-1484. Verify that the key used to sign a synthetic transaction actually belongs to an operator.
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [x] The merge request title is in the format `<change type>(<change scope>): <short description> [<task id>]`
        - For example, `feat(cli): add QR code generation [AC-123]`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [x] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [x] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [x] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [ ] CI is passing
      - [ ] Merge conflicts are resolved
      - [ ] All discussions are resolved
      
      Related to AC-1484
      9d334bd3
  3. May 25, 2022
    • Sander Postma's avatar
      feat(prot): create dn/subnets account [AC-1398] · 596c8939
      Sander Postma authored and Ethan Reesor's avatar Ethan Reesor committed
      Closes AC-1398. *Dn account subnets*
      
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [x] The merge request title is in the format `<change type>(<change scope>): <short description> [<task id>]`
        - For example, `feat(cli): add QR code generation [AC-123]`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [x] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [x] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [x] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [ ] CI is passing
      - [ ] Merge conflicts are resolved
      - [ ] All discussions are resolved
      
      Related to AC-1398
      596c8939
    • Ethan Reesor's avatar
      test: add test data for merkle hashes [AC-1551] · cdb61db3
      Ethan Reesor authored
      Closes AC-1551. Add a file with hard coded test cases for calculating Merkle hashes so that ecosystem devs can validate their implementations.
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [x] The merge request title is in the format `<change type>(<change scope>): <short description> [<task id>]`
        - For example, `feat(cli): add QR code generation [AC-123]`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [x] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [x] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [x] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [x] CI is passing
      - [x] Merge conflicts are resolved
      - [x] All discussions are resolved
      
      Related to AC-1551
      cdb61db3
  4. May 20, 2022
    • Ethan Reesor's avatar
      chore(prot): rename owner to delegate [AC-1522] · 8794c5fd
      Ethan Reesor authored
      Closes AC-1522. Rename the `owner` field of a key page entry to `delegate`.
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [x] The merge request title is in the format `<change type>(<change scope>): <short description> [<task id>]`
        - For example, `feat(cli): add QR code generation [AC-123]`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [x] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [x] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [x] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [ ] CI is passing
      - [ ] Merge conflicts are resolved
      - [ ] All discussions are resolved
      
      Related to AC-1522
      8794c5fd
    • Ethan Reesor's avatar
      feat(prot): guarantee synthetic transaction delivery [AC-816] · 09f9d819
      Ethan Reesor authored
      Closes AC-816. Guarantee delivery of synthetic transactions.
      
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [x] The merge request title is in the format `<change type>(<change scope>): <short description> [<task id>]`
        - For example, `feat(cli): add QR code generation [AC-123]`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [x] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [x] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [x] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [ ] CI is passing
      - [ ] Merge conflicts are resolved
      - [ ] All discussions are resolved
      
      Related to AC-816
      09f9d819
  5. May 18, 2022
    • Ethan Reesor's avatar
      chore(prot): eliminate data chain [AC-1473] · 331e480e
      Ethan Reesor authored
      Closes AC-1473. Eliminate the data chain in order to make Accumulate match Paul's architecture.
      
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [x] The merge request title is in the format `<change type>(<change scope>): <short description> [<task id>]`
        - For example, `feat(cli): add QR code generation [AC-123]`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [x] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [x] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [x] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [x] CI is passing
      - [ ] Merge conflicts are resolved
      - [x] All discussions are resolved
      
      Related to AC-1473
      331e480e
  6. May 13, 2022
    • Dennis B's avatar
      chore(prot): split anchor transactions/signatures [AC-1463] · 156a7485
      Dennis B authored
      Closes AC-1463. 
      - replaced internal transactions/signatures with system transactions/signatures
      - renamed SyntheticMirror to MirrorSystemRecords and make it a system transaction
      - split SyntheticAnchor into PartitionAnchor and DirectoryAnchor
      - Pulled new transactions out of synthetic_transactions.yml to system_transactions.yml system transactions
      
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [x] The merge request title is in the format `<change type>(<change scope>): <short description> [<task id>]`
        - For example, `feat(cli): add QR code generation [AC-123]`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [x] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [x] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [x] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [ ] CI is passing
      - [x] Merge conflicts are resolved
      - [ ] All discussions are resolved
      
      Related to AC-1463
      156a7485
  7. May 12, 2022
    • Ethan Reesor's avatar
      chore(all): add custom analyzers [AC-1517] · 0f90dbf4
      Ethan Reesor authored
      Closes AC-1517. Add two custom analyzers:
      
      - 'noprint' catches print statements. We should be using the logger for basically everything, and adding print statements is common for debugging. Debugging print statements should not be merged.
      - 'rangevarref' catches cases where the body of a for-loop captures a reference to a value-type range variable. The analyzer doesn't know how to determine if a value escapes the stack, so it plays it safe by assuming all values escape. This leads to false positives, but dealing with false positives is much better than having bugs because of false negatives.
      
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [x] The merge request title is in the format `<change type>(<change scope>): <short description> [<task id>]`
        - For example, `feat(cli): add QR code generation [AC-123]`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [x] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [x] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [x] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [x] CI is passing
      - [x] Merge conflicts are resolved
      - [x] All discussions are resolved
      
      Related to AC-1517
      0f90dbf4
  8. May 11, 2022
    • Ethan Reesor's avatar
      chore(prot): refactor signatures · e50e4047
      Ethan Reesor authored
      Closes AC-1407. Refactor signature processing. Remote signatures will not be forwarded until the remote signer is satisfied.
      
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [ ] The merge request title is in the format `<change type>(<change scope>): <short description> [<task id>]`
        - For example, `feat(cli): add QR code generation [AC-123]`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [ ] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [ ] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [ ] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [ ] CI is passing
      - [ ] Merge conflicts are resolved
      - [ ] All discussions are resolved
      
      Related to AC-1407
      e50e4047
  9. May 10, 2022
    • Ethan Reesor's avatar
      feat(prot): require approval from additional authorities [AC-1493] · 5f44a5f6
      Ethan Reesor authored
      Closes AC-1493. When creating an account with additional authorities or adding an authority to an existing account, require a signature from that authority.
      
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [x] The merge request title is in the format `<change type>(<change scope>): <short description> [<task id>]`
        - For example, `feat(cli): add QR code generation [AC-123]`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [x] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [x] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [x] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [x] CI is passing
      - [x] Merge conflicts are resolved
      - [x] All discussions are resolved
      
      Related to AC-1493
      5f44a5f6
  10. May 09, 2022
    • Ethan Reesor's avatar
      fix(cli): improve key handling [AC-1501] · 21b24178
      Ethan Reesor authored
      Closes AC-1501. Improve the CLI's handling of keys to work with non-ED25519 keys.
      
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [x] The merge request title is in the format `<change type>(<change scope>): <short description> [<task id>]`
        - For example, `feat(cli): add QR code generation [AC-123]`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [x] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [x] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [x] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [ ] CI is passing
      - [ ] Merge conflicts are resolved
      - [ ] All discussions are resolved
      
      Related to AC-1501
      21b24178
  11. May 06, 2022
    • Abhishek Ranjan's avatar
      feat(prot): adding factom addresses and balance in genesis [AC-1181] · 659a0aa0
      Abhishek Ranjan authored and Dennis B's avatar Dennis B committed
      Closes AC-1181. adding factom addresses and balance in genesis
      
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [x] The merge request title is in the format `<change type>(<change scope>): <short description> [<task id>]`
        - For example, `feat(cli): add QR code generation [AC-123]`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [x] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [x] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [x] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [x] CI is passing
      - [ ] Merge conflicts are resolved
      - [x] All discussions are resolved
      
      Related to AC-1181
      659a0aa0
  12. May 05, 2022
    • Ethan Reesor's avatar
      feat(prot): state snapshots [AC-1349] · 2ebecdb4
      Ethan Reesor authored
      Closes AC-1349. Add methods to save and restore snapshots of the network state.
      
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [x] The merge request title is in the format `<change type>(<change scope>): <short description> [<task id>]`
        - For example, `feat(cli): add QR code generation [AC-123]`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [x] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [x] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [x] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [ ] CI is passing
      - [ ] Merge conflicts are resolved
      - [ ] All discussions are resolved
      
      Related to AC-1349
      2ebecdb4
  13. May 02, 2022
    • Sander Postma's avatar
      feat(prot): manage credits at the identity/authority of a lite account [AC-1245] · 60e7e5bf
      Sander Postma authored and Ethan Reesor's avatar Ethan Reesor committed
      Closes AC-1245. Move credits, the nonce/timestamp, and the Signer implementation from LiteTokenAccount to LiteIdentity. This allows a lite identity to be used as the signer or the recipient of AddCredits. For backwards compatibility, allow the lite token account to be used as a signer URL.
      
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [x] The merge request title is in the format `<change type>(<change scope>): <short description> [<task id>]`
        - For example, `feat(cli): add QR code generation [AC-123]`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [x] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [x] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [x] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [ ] CI is passing
      - [ ] Merge conflicts are resolved
      - [ ] All discussions are resolved
      
      Related to AC-1245
      60e7e5bf
  14. Apr 25, 2022
    • Ethan Reesor's avatar
      feat(prot): delegated authority [AC-1299] · d5952632
      Ethan Reesor authored and Dennis B's avatar Dennis B committed
      Closes AC-1299. Implement delegated authority.
      
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [x] The merge request title is in the format `<change type>(<change scope>): <short description> [<task id>]`
        - For example, `feat(cli): add QR code generation [AC-123]`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [x] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [x] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [x] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [ ] CI is passing
      - [ ] Merge conflicts are resolved
      - [ ] All discussions are resolved
      
      Related to AC-1299
      d5952632
  15. Apr 21, 2022
    • JATHIN JAGANNATH's avatar
      feat(prot): capture unknown fields [AC-1095] · b4a61248
      JATHIN JAGANNATH authored and Ethan Reesor's avatar Ethan Reesor committed
      Initial Implementation for basic review
      
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [ ] The merge request title is in the format `<change type>(<change scope>): <short description>`
        - For example, `feat(cli): add QR code generation`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [ ] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [ ] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [ ] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [ ] CI is passing
      - [ ] Merge conflicts are resolved
      - [ ] All discussions are resolved
      
      Related to AC-1095
      b4a61248
  16. Apr 18, 2022
    • Ethan Reesor's avatar
      chore(all): improved error handling · 7129df91
      Ethan Reesor authored
      Closes AC-1341. With callsite tracking.
      
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [x] The merge request title is in the format `<change type>(<change scope>): <short description>`
        - For example, `feat(cli): add QR code generation`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [x] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [x] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [x] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [ ] CI is passing
      - [ ] Merge conflicts are resolved
      - [ ] All discussions are resolved
      7129df91
  17. Apr 16, 2022
    • Ethan Reesor's avatar
      chore(core): upgrade tendermint · 29329cbc
      Ethan Reesor authored
      Closes AC-1363. Updates Tendermint from my custom fork of `v0.35.0-rc1` to `v0.35.x`. This fixes a number of bugs, which allows us to use mainline Tendermint instead of my fork. Removing the `replace` directive means we can now `go install gitlab.com/accumulatenetwork/accumulate/cmd/accumulate` (or any other command) without Go failing due to the replace directive.
      
      This is necessary for proper playbook support.
      
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [x] The merge request title is in the format `<change type>(<change scope>): <short description>`
        - For example, `feat(cli): add QR code generation`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [x] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [x] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [x] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [ ] CI is passing
      - [ ] Merge conflicts are resolved
      - [ ] All discussions are resolved
      29329cbc
  18. Apr 09, 2022
    • Ethan Reesor's avatar
      feat(api): multiple transactions per envelope · 6fa75aa1
      Ethan Reesor authored
      Closes AC-1190. Allows multiple transactions to be packed into a single envelope. Removes the old concatenation based batching method. Updates JSON marshalling to accept a single value for any array-valued field.
      
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [x] The merge request title is in the format `<change type>(<change scope>): <short description>`
        - For example, `feat(cli): add QR code generation`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [x] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [x] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [x] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [ ] CI is passing
      - [ ] Merge conflicts are resolved
      - [ ] All discussions are resolved
      6fa75aa1
    • Dennis B's avatar
      test(prot): add test to exercise RCD1-based keys · 6ce0d0b3
      Dennis B authored and Ethan Reesor's avatar Ethan Reesor committed
      Closes AC-1201
      
      - Cleaned up lite accounts in CLI so that they can be corrected tagged as RCD1 type
      - Streamlined the factoid address handling in cli
      - Corrected bug generating lite account address with RCD hash
      - Added test to add credits, faucet, and move tokens from an RCD-based account
      - Added test to exercise the import of factoid addresses
      - Added restore capability to update the tags and fill lite accounts in the wallet
      - Added the ability to first run the restore function to automatically run the restore accounts on a wallet
      
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [x] The merge request title is in the format `<change type>(<change scope>): <short description>`
        - For example, `feat(cli): add QR code generation`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [x] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [x] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [x] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [ ] CI is passing
      - [ ] Merge conflicts are resolved
      - [ ] All discussions are resolved
      6ce0d0b3
  19. Apr 08, 2022
  20. Apr 06, 2022
    • Ethan Reesor's avatar
      test: create a basic simulator · ef8e85b7
      Ethan Reesor authored and Paul Snow's avatar Paul Snow committed
      Closes AC-1321. Creates a basic simulator that allows the block and transaction executors to be tested without involving the ABCI or Tendermint and without concurrency issues due to timeouts.
      ef8e85b7
    • Dennis B's avatar
      chore(prot): add acceptance, rejection, response, and block threshold fields to key page · a41889b0
      Dennis B authored
      Related to AC-1272
      
      - added acceptance, rejection, response, and block threshold fields to key page
      a41889b0
    • Ethan Reesor's avatar
      feat(prot): generalize authority · f7ec7367
      Ethan Reesor authored
      - Closes AC-1302.
      - Generalizes authority:
        - Accounts are governed by authorities
        - An authority has signers
        - A signer has key entries
      - Replaces `AuthDisabled`, `KeyBook`, and `ManagerKeyBook` with `AccountAuth [](URL, Disabled)`
      - Removes the account header
      - Most accounts now have `AccountAuth`
      - Lite token accounts are their own authority
      - Key pages are governed by the authority of the book they belong to - key pages cannot have their own auth rules.
      - Lite identities and lite data accounts are not governed.
      f7ec7367
  21. Apr 05, 2022
    • Ethan Reesor's avatar
      feat(typegen): implement virtual fields · f93e917d
      Ethan Reesor authored
      Closes AC-1303. Implements typegen virtual fields. Converts the hard-coded union discriminator type field into a virtual field. Adds support for defining embedded fields side-by-side with normal fields. Removes `GetType()` and `New<AccountType>()`.
      
      Virtual fields are implemented as getter methods instead of actual fields, but they are still marshalled.
      f93e917d
    • Ethan Reesor's avatar
      feat(prot): support initiating with metadata hash · e299705a
      Ethan Reesor authored
      Closes AC-1300. Allows clients to initiate a transaction with the simple metadata hash of the first signature, instead of a Merkle hash.
      e299705a
  22. Apr 02, 2022
  23. Apr 01, 2022
  24. Mar 28, 2022
  25. Mar 25, 2022
  26. Mar 24, 2022
  27. Mar 23, 2022
    • Dennis B's avatar
      chore(prot): change API to specify acme to spend for obtaining credits · 5097af6e
      Dennis B authored and Ethan Reesor's avatar Ethan Reesor committed
      Related to AC-1085
      - modified add_credits to specify acme to determine the amount of credits to buy
      - modified cli to specify desired credits, max acme to spend, and an optional slippage to bump the acme amount to satisfy the credit purchase
      - updated unit tests and ci tests.
      - removed references to credits as big.Int's within the protocol for increased optimization.
      5097af6e
    • Dennis B's avatar
      chore(prot): track issued tokens instead of reserve · aca50e75
      Dennis B authored and Ethan Reesor's avatar Ethan Reesor committed
      Related to AC-1093
      
      - now tracking tokens issued from the token issuance account rather than tokens remaining in it
      - when a fixed supply limit is specified, it is enforced by the token issuance
      - update human-readable output in cli
      - updated e2e tests
      aca50e75
Loading