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.

Sign up for GitHub

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

Jump to bottom

Generate "partial accounts" in the sandbox #2458

Closed
Tracked by #2459
rahul-kothari opened this issue Sep 21, 2023 · 1 comment · Fixed by #2491
Closed
Tracked by #2459

Generate "partial accounts" in the sandbox #2458

rahul-kothari opened this issue Sep 21, 2023 · 1 comment · Fixed by #2491
Assignees
@benesjan

Comments

@rahul-kothari
Copy link
Contributor

Example, a public key without the private key, such that devs can experiment with "what happens if you query someone else' private state". Practically speaking, it appears as if we have no private state since the RPC server can decrypt everything currently.

@zac-williamson @catmcgee anything else to add?
@github-project-automation github-project-automation bot moved this to Todo in A3 Sep 21, 2023
@rahul-kothari rahul-kothari mentioned this issue Sep 21, 2023
Closed
@LHerskind LHerskind mentioned this issue Sep 21, 2023
Closed
@rahul-kothari rahul-kothari changed the title Generate "partial addresses" in the sandbox Generate "partial accounts" in the sandbox Sep 22, 2023
@PhilWindle
Copy link
Collaborator

This may already be possible. If not I suspect it's minimal effort. You can already register public keys with the sandbox, we just need to verify the workflow.

@PhilWindle PhilWindle self-assigned this Sep 22, 2023
@benesjan benesjan assigned benesjan and unassigned PhilWindle Sep 25, 2023
@benesjan benesjan moved this from Todo to In Progress in A3 Sep 25, 2023
@benesjan benesjan mentioned this issue Sep 25, 2023
Merged
4 tasks
benesjan added a commit that referenced this issue Sep 25, 2023
@benesjan
test: no private key account state (#2491)
5813fb3 
Fixes #2458 

> Note: Now the Synchronizer throws if we request a sync status for
account which is not registered. I think this is the correct behavior
because when a dev requests this info for unregistered account it would
probably be a mistake even though returning false there is correct
(unregistered account is technically not synchronized).
@github-project-automation github-project-automation bot moved this from In Progress to Done in A3 Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@benesjan benesjan

Labels
None yet
Projects
A3
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

test: no private key account state AztecProtocol/aztec-packages
3 participants
@benesjan @rahul-kothari @PhilWindle