You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a problem that I am hoping you may be able to support me with.
I took part in the V8 Staking security bounty programme earlier this week, staking TRAC in order to secure some of the staking bounty.
Due to unfortunate circumstances, I will be completely unable to access my ledger until the day of 23rd January (and thus cannot sign before the 16th January to claim the bounty).
Is there any way this could be accommodated? I can provide further details if needed.
Expected behavior
Actual behavior
Steps to reproduce the problem
Specifications
Node version:
Platform:
Node wallet:
Node libp2p identity:
Contact details
Email:
Error logs
Disclaimer
Please be aware that the issue reported on a public repository allows everyone to see your node logs, node details, and contact details. If you have any sensitive information, feel free to share it by sending an email to [email protected].
The text was updated successfully, but these errors were encountered:
Issue description
I have a problem that I am hoping you may be able to support me with.
I took part in the V8 Staking security bounty programme earlier this week, staking TRAC in order to secure some of the staking bounty.
Due to unfortunate circumstances, I will be completely unable to access my ledger until the day of 23rd January (and thus cannot sign before the 16th January to claim the bounty).
Is there any way this could be accommodated? I can provide further details if needed.
Expected behavior
Actual behavior
Steps to reproduce the problem
Specifications
Contact details
Error logs
Disclaimer
Please be aware that the issue reported on a public repository allows everyone to see your node logs, node details, and contact details. If you have any sensitive information, feel free to share it by sending an email to [email protected].
The text was updated successfully, but these errors were encountered: