Extract Stakeholder CLI and Deploy Actions#1056
Conversation
Codecov Report
@@ Coverage Diff @@
## sekanjabin #1056 +/- ##
=============================================
+ Coverage 81.55% 83.46% +1.9%
=============================================
Files 70 71 +1
Lines 9527 9707 +180
=============================================
+ Hits 7770 8102 +332
+ Misses 1757 1605 -152
Continue to review full report at Codecov.
|
ffdb6f6 to
e2a3ec9
Compare
4eca13d to
b1572a7
Compare
72e6633 to
83d7993
Compare
…n to/from UrsulaConfiguration; Attempting to fix reward collection CLI integration tests.
…inflation rewards to specified account or funding account. Touch up reward collection assertions.
|
Just a placeholder. I want to review this but it will have to be tonight, before I leave. In any case, I've been using this as the base of #1111, so if you don't hear about me after today 23:59 CEST, it's an implicit approval. |
|
There's a tiny bug when handling the receipts of the deployment of |
There was a problem hiding this comment.
A few things here that I uncovered during a UX audit with a hardware wallet:
1. Instead of --device, let's do --hw-wallet/--no-hw-wallet.
2. Don't prompt for stakes in Nunits, let's do a float.
3. When I specify --device when creating a new stake-holder, it should specify that that stakeholder is a device so I don't need to do --device when I perform a stake init (maybe? I guess it'll be a default, so it's kinda moot.)
4. It prompts for my passphrase despite using a hardware wallet and then tries to use it when I want to publish the stake on the blockchain; thus, preventing me from staking with a hardware wallet.
5. A better explanation of what a "period" is during the stake initialization process would be ideal.
cygnusv
left a comment
There was a problem hiding this comment.
Apart from the suggested changes, I also had a minor problem with the stakeholder JSON config file. At some moment I had 2 of them, one named stakeholder.json and the other stakeholder-0xfoobar.json, and I had to remove the former and change the name of the latter to stakeholder.json to continue working.
cygnusv
left a comment
There was a problem hiding this comment.
I've just successfully staked (yay!) and set a worker.
One issue I've found is that when using option 'c', it's not creating a new account in the end, but staking with the funding account. I'm sure it's just a minor bug when handling the address in nucypher stake init. Also, as a consequence of the above, it's funding the funding account from the funding account :P
|
@cygnusv - Yes I also noticed this. Noted. |
Co-Authored-By: Derek Pierre <derek.pierre@gmail.com>
This PR goes into the Sekanjabin Epic (#1107); Refactors the staking CLI to suit the
StakeHolderand makes improvements to the usability of development deployment.Based on #1064
Fixes #1119
Contributes to fixing #1117
Introduces #1125
Status
Still has failing mixed-configuration tests, possibly related to federated vs. non-federated keyring attachment methods on Ursula. Needs interactive reviews and Issue-opening follow-ups.
Interactive Review in 4 Steps
1- Run Development Blockchain
2 - Deploy Contracts
3 - Create StakeHolder
4 - Initialize Stake