-
Notifications
You must be signed in to change notification settings - Fork 66
Problem (Fix #1621): Can't deposit into other's new staking address #1625
Conversation
14bcca5
to
9b7899a
Compare
Codecov Report
@@ Coverage Diff @@
## master #1625 +/- ##
==========================================
- Coverage 70.31% 68.12% -2.20%
==========================================
Files 168 170 +2
Lines 21548 22247 +699
==========================================
+ Hits 15151 15155 +4
- Misses 6397 7092 +695
|
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.
maybe also bump version numbers in the affected client-* Cargo.toml
let staked_state = self.get_staked_state(name, &to_address, verify_staking)?; | ||
verify_unjailed(&staked_state).map_err(|e| { | ||
Error::new( | ||
ErrorKind::ValidationError, | ||
format!("Failed to validate staking account: {}", e), | ||
) | ||
})?; |
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.
maybe the jailing test could be optionally run (if the state exists?)
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.
Done
40bd70e
to
335ceb6
Compare
Done |
client-rpc is also affected if client-network changed? |
… address Solution: - Remove the restriction from client network ops code - Add check and double confirmation in client-cli
Yes, just bumped the version too, and reflected that in CHANGELOG. |
bors r+ |
Build succeeded: |
Solution: