-
Notifications
You must be signed in to change notification settings - Fork 47
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
Define High Level Client APIs, improvements and account packets #1158
Labels
Milestone
Comments
Related to #1103 |
joshuef
added a commit
to joshuef/safe_network
that referenced
this issue
Jan 30, 2024
fixes maidsafe#1158 + also icnrases benchmark limit to account for extra work done here
joshuef
added a commit
to joshuef/safe_network
that referenced
this issue
Jan 30, 2024
fixes maidsafe#1158 + also icnrases benchmark limit to account for extra work done here
joshuef
added a commit
that referenced
this issue
Jan 30, 2024
fixes #1158 + also icnrases benchmark limit to account for extra work done here
Badly linked commit there 🤦 . This was not addressed by the above. |
joshuef
changed the title
Define High Level Client APIs
Define High Level Client APIs, improvements and account packets
Jan 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Account packet
Files System
We should start fleshing out higher level client APIs to properly handle fiilessytem and small data.
We want to:
Ideally:
Other considerations?
If we make the account packet a key... could we derive some DNS around key finding to enable simple safe ids? (PK hash matching etc...)
The text was updated successfully, but these errors were encountered: