-
Notifications
You must be signed in to change notification settings - Fork 16
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
feat: implement signing #380
Conversation
Terraform Feature Environment (dev-380)Terraform Initialization ⚙️
|
f6d3989
to
0423757
Compare
@itegulov do yo want to merge it with the failing test and then fix it? |
@@ -8,23 +8,22 @@ publish = false | |||
aes-gcm = "0.10" | |||
anyhow = { version = "1.0", features = ["backtrace"] } | |||
async-process = "1" | |||
aws-config = "0.54.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why AWS? IS it because Lake Framework is intended to work with it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, needed for Lake Framework configuration
let payload: [u8; 32] = rand::thread_rng().gen(); | ||
let outcome = ctx | ||
.rpc_client | ||
.send_tx( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the protocol feature is yet to be implemented, what is our plan here (for this PR and first testnet release)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are just making a separate unrelated transaction with the response
98eb562
to
de5d7c0
Compare
Terraform Feature Environment Destroy (dev-380)Terraform Initialization ⚙️
|
Apologies that this code is pretty hairy and that PR is touching a million different things, but I had to fix many little bugs to make this actually work.
I tried to serialize the resulting signature into something more conventional for NEAR's ecosystem, but spent 3 hours going through different tags, SEC1 variations and compression without writing anything that works. So I am leaving that for a follow-up PR.