Added functions that generate dummy signatures #464
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We want to unblock people when our service isn't working and take some pressure off keeping the damn thing up. This PR hard codes in a private key with a value of 0 and a nonce with a value of 1 and does accurate key derivation on it. Provided you fetch the dummy root key, client code should behave consistently. The only small difference is I don't include episilon or a changing nonce meaning that signatures with an identical predecessor, derivation and payload will be identical. This currently doesn't build on WASM and I suspect my moving around of dependencies will have bloated the size of the contract.
Terraform Feature Environment (dev-464)Terraform Initialization ⚙️
|
|
The build on my M1 fails as well. It's happening because of the On x86 Ubuntu it works, but the test is failing with This is because One more related issue/NEP: near/NEPs#443 |
|
hmm, I'm not sure what you guys are seeing, but this is compiling and the tests are running locally for me For reference, I'm running both of these: cargo build -p mpc-contract --target wasm32-unknown-unknown --release
cargo test --package mpc-contract --lib -- test --nocaptureEDIT: ahh I see, you made the kdf a test dep which is why the node code isn't picking it up |
The dependencies you added are a part of dev-dependencies, so that won't bloat the contract size at all |
|
hmm, looks like the contract can't be deployed. I'll get back to this if I find some time, but feel free for anyone to try and solve it |
|
@ChaoticTempest I was able to deploy it, but I'm getting |
|
@ChaoticTempest I've tried to refactor the contract, but faced other compilation issues. It's in We can simplify it to a single |
|
Looks like we do not need this logic anymore. |
Terraform Feature Environment Destroy (dev-464)Terraform Initialization ⚙️
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We want to unblock people when our service isn't working and take some pressure off keeping the damn thing up.
This PR hard codes in a private key with a value of 0 and a nonce with a value of 1 and does accurate key derivation on it. Provided you fetch the dummy root key, client code should behave consistently. The only small difference is I don't include episilon or a changing nonce meaning that signatures with an identical predecessor, derivation and payload will be identical.
This currently doesn't build on WASM and I suspect my moving around of dependencies will have bloated the size of the contract.