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

Account is required to exist in order to be used to sign in the TS bindings #1118

Open
kalepail opened this issue Dec 13, 2024 · 0 comments
Open

Account is required to exist in order to be used to sign in the TS bindings #1118

kalepail opened this issue Dec 13, 2024 · 0 comments
Labels
bug

Comments

@kalepail
Copy link
Contributor

Describe the bug
I'm trying to sign a Client.deploy with a publicKey that doesn't exist. This should work. I just want to seed the contract ID consistently with my own Address and salt.

Right now I'm getting an error when the publicKey for this doesn't exist. When signing Soroban ops the account doesn't need to exist. You only need the authorizing account to be live if it's spending XLM on fees or a sequence number.

What version are you on?
13.0.0
@kalepail kalepail added the bug label Dec 13, 2024
@github-project-automation github-project-automation bot moved this to Backlog (Not Ready) in DevX Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
DevX
Status: Backlog (Not Ready)
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kalepail