Skip to content
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

feat: support signed messages from nano accounts #105

Open
9 of 10 tasks
mistakia opened this issue Mar 13, 2024 · 0 comments
Open
9 of 10 tasks

feat: support signed messages from nano accounts #105

mistakia opened this issue Mar 13, 2024 · 0 comments
Labels
kind/maintenance Work required to avoid breaking changes or harm to project's status quo priority/high High: Likely tackled by core team if no one steps up status/in-progress In progress

Comments

@mistakia
Copy link
Owner

mistakia commented Mar 13, 2024

Tasks

account data

  • alias
  • representative metadata
    • cpu
    • ram
    • disk
    • donation address
    • shutdown notice
    • contact information
@mistakia mistakia added priority/high High: Likely tackled by core team if no one steps up kind/maintenance Work required to avoid breaking changes or harm to project's status quo dif/hard Having worked on the specific codebase is important status/ready Ready to be worked labels Mar 13, 2024
@mistakia mistakia reopened this Apr 9, 2024
@mistakia mistakia added status/in-progress In progress and removed status/ready Ready to be worked dif/hard Having worked on the specific codebase is important labels Apr 10, 2024
ATXMJ pushed a commit to ATXMJ/nano-community that referenced this issue Sep 16, 2024
* feat: add api endpoint for signed message (close mistakia#105)

* chore: add tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/maintenance Work required to avoid breaking changes or harm to project's status quo priority/high High: Likely tackled by core team if no one steps up status/in-progress In progress
Projects
Status: In Progress
Development

No branches or pull requests

1 participant