Skip to content
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

Cold Staking: Ability to refuse staking by a hot wallet #22

Closed
thecrypt0hunter opened this issue Nov 20, 2019 · 2 comments
Closed

Cold Staking: Ability to refuse staking by a hot wallet #22

thecrypt0hunter opened this issue Nov 20, 2019 · 2 comments

Comments

@thecrypt0hunter
Copy link
Contributor

thecrypt0hunter commented Nov 20, 2019

A problem with running a hot wallet is that you have no control over who can stake using your wallet i.e., as a hot wallet operator I am unable to refuse to receive stake delegations.

This could be used as a vector for denial of service - if a staking address is leaked or provided as part of a staking pool, it is possible to force the stakers wallet to manage an unreasonable amount of UTXOs, it may impact the staking performance and possibly increase orphans. The cost of such attack is negligible costs (only the fees required in the stake delegations) as the coins always remain in possession of the attacker.

It would also be possible for a user to identify another stakers address simply by examining the blockchain and then delegate staking to that address.

One option would be to allow the staker to whitelist only "approved" addresses. Another consideration would be to add a flag that would purposely allow cold staking rather than normal staking.

@thecrypt0hunter
Copy link
Contributor Author

The feature should have an API interface taking two parameters the whitelist address and a TTL parameter so that the whitelisting would expire after a set amount of time.

@dangershony
Copy link
Member

This was done here
#38

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants