-
Notifications
You must be signed in to change notification settings - Fork 390
feat(signer): adds signer-stronghold #2420
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
base: main
Are you sure you want to change the base?
Conversation
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.
seems okay, simple enough, not much work to maintain, ty
@tuddman most of these tests are timing out, mind taking a look? |
Head branch was pushed to by a user without write access
@mattsse you can maybe try running the CI again? works locally... running 11 tests
test signer::tests::test_missing_passphrase ... ok
test signer::tests::test_new_from_path ... ok
test signer::tests::test_chain_id_management has been running for over 60 seconds
test signer::tests::test_end_to_end_transaction_with_anvil has been running for over 60 seconds
test signer::tests::test_get_evm_address has been running for over 60 seconds
test signer::tests::test_initialize_new_signer has been running for over 60 seconds
test signer::tests::test_reinitialize_existing_signer has been running for over 60 seconds
test signer::tests::test_sign_hash has been running for over 60 seconds
test signer::tests::test_sign_message has been running for over 60 seconds
test signer::tests::test_sign_transaction has been running for over 60 seconds
test signer::tests::test_get_evm_address ... ok
test signer::tests::test_sign_hash ... ok
test signer::tests::test_chain_id_management ... ok
test signer::tests::test_initialize_new_signer ... ok
test signer::tests::test_sign_message ... ok
test signer::tests::test_sign_transaction ... ok
test signer::tests::test_end_to_end_transaction_with_anvil ... ok
test signer::tests::test_reinitialize_existing_signer ... ok
test signer::tests::test_signer_trait_implementation ... ok
test result: ok. 11 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 159.88s
Doc-tests alloy_signer_stronghold
running 2 tests
test crates/signer-stronghold/src/lib.rs - (line 48) - compile ... ok
test crates/signer-stronghold/src/lib.rs - (line 29) - compile ... ok
test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.13s |
@@ -515,7 +515,8 @@ impl Geth { | |||
|
|||
if let Some(genesis) = &self.genesis { | |||
// create a temp dir to store the genesis file | |||
let temp_genesis_dir_path = tempdir().map_err(NodeError::CreateDirError)?.keep(); | |||
let temp_genesis_dir_path = | |||
tempdir().map_err(NodeError::CreateDirError)?.path().to_path_buf(); |
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.
I was getting a compilation error from this when trying to clean + test.
This fixes that compilation error.
Up to you, obviously. I'll continue maintaining and supporting it either way. Having it available more broadly tends to surface bugs and improvements faster. It's stable and version-pinned, so maintenance overhead is minimal, imo. And I generally believe offering more options helps the community overall, e.g. like with alloy overall. |
right, now that we have 1.0 which we want to keep stable, I think as a standalone repo this would be more appropriate because iota specific. |
ok. to be clear though - stronghold.rs was built largely to underpin iota's wallet, firefly. afaik, that has never been hacked or compromised. It was originally crafted for iota by @tensor-programming and afaict is truly a 'general purpose' secrets keeper that makes strong protection claims. In that way it's not 'iota-specific' really at all. I'm certainly not using it for that. |
Solution
Adds a signer using a Stronghold as the store
PR Checklist