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

Introduce provider/signer separation into API #268

Closed
piotr-roslaniec opened this issue Aug 22, 2023 · 1 comment
Closed

Introduce provider/signer separation into API #268

piotr-roslaniec opened this issue Aug 22, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@piotr-roslaniec
Copy link
Contributor

  • Provider vs Signer: Separation between RPC read calls (the "provider") and signing operations (the "signer"), in line with the nucypher codebase (with the BlockchainInterface / Signer separation) and some JS libraries like Viem. This could even allow in the future for non-wallet signing approaches (e.g. signing with keypairs that are not mapped to blockchain accounts).

Originally posted by @cygnusv in #166 (comment)

@piotr-roslaniec piotr-roslaniec added the enhancement New feature or request label Aug 22, 2023
@piotr-roslaniec piotr-roslaniec moved this to On calendar (Implementation, Ops, Market Dev) in v7.0.0 (TACo) Aug 22, 2023
@piotr-roslaniec
Copy link
Contributor Author

Closed by #270

@github-project-automation github-project-automation bot moved this from On calendar (Implementation, Ops, Market Dev) to Completed (Proof-of-Concept) in v7.0.0 (TACo) Sep 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Completed
Development

Successfully merging a pull request may close this issue.

1 participant