Skip to content

feat: accumulate playbooks

Ethan Reesor requested to merge playbooks into develop

Closes AC-1347. Implement Accumulate Playbooks: Markdown notebooks with Go code blocks that can be executed, which can be used as tests of and examples for Accumulate.

Generate a lite address

alice := GenerateKey("alice")
aliceAddr := LiteAddress(alice, ACME)
Show(aliceAddr)

Result:

acc://544c73aba05e0d8693e7afb96dbc029ef6bcd582b4a298c8/ACME

Get tokens

Show(Faucet(aliceAddr).Wait())
Show(Get(aliceAddr))

Result:

ACME Faucet Transaction
    Hash:     FEB7DD5BC2F6BF65DEF19D0280126C3528EDC2CBBD71D4D33638E1FC070552FD
    To:       acc://53232cfe088f4c2dc74f1d055b285b61b0066248146fac67/ACME
    Amount:   2000000 ACME
Lite Token Account
    Identity:   53232cfe088f4c2dc74f1d055b285b61b0066248146fac67
    Issuer:     ACME
    Balance:    2000000 ACME
    Credits:    0

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
  • 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

Merge Checklist

  • CI is passing
  • Merge conflicts are resolved
  • All discussions are resolved
Edited by Ethan Reesor

Merge request reports