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

Casper-client [get-transaction should allow returning both transactions and legacy deploys] #168

Open
RBYGLLS opened this issue Jun 7, 2024 · 0 comments
Assignees

Comments

@RBYGLLS
Copy link

RBYGLLS commented Jun 7, 2024

Component: casper-client
Description: Right now casper-client get-transaction receives the Digest corresponding with the transaction as a parameter. The command assumes that the provided Digest belongs to a V1 transaction but get-transaction should allow users to also retrieve old style deploys. This is because the new Transaction is actually a versioning wrapper that can understand both legacy deploys and new style v1 transactions.
The ask is to add a new command line parameter to casper-client get-transaction that allows users to specify if the provided digest Digest resolves to a V1 transaction hash or a legacy Deploy hash. (e.g. casper-client get-transaction -d 0xabc232 retrieves a transactions by TransactionHash::Deploy(DeployHash(0xabc232)) and `casper-client get-transaction -v1 0xabc232 retrieves a transactions by TransactionHash::V1(TransactionV1Hash(0xabc232)) )
Release: 2.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants