-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Add a new section for operational security best practices. #113
Comments
This issue now has a funding of 0.3 ETH (98.15 USDT) attached to it. To view or claim this funding, click here. |
hey @maurelian did you want me trying to source this still? i see the bounty has expired.. so you now has the option to clawback the funds or to just keep it open (and ill continue looking for someone to help) |
I'd like to claw it back. This task was too open ended. Unfortunately, I can't see how to do that. |
@maurelian no problem. just sent you the clawback link on slack. |
hey @maurelian happy new years :) let me know if you got that clawback link and if you need any help :) |
is this one still available? It says status = active, but expired = 1 month ago (and from comments above it looks closed) |
It's available on a voluntary basis only now. |
The funding of 0.3 ETH (291.99 USD) attached to this issue has been approved & issued .
|
Please disregard the message from Gitcoinbot above.. The bounty was killled, not approved. |
It should probably have a mention about contract audits. |
Also:
|
Current Modus Operandi is to reduce scope and improve the core content. |
ISSUE: There are many security consideration outside of programming and architecture, which are not covered here.
PR REQUEST: A new section should be created (including modifying the [yaml config(https://github.com/ConsenSys/smart-contract-best-practices/blob/master/mkdocs.yml)), which presents the various operational considerations necessary when deploying a contract system.
These include existing issues:
[] #92
[] #85
[] #79
[] #97
As well as:
[] proper cold storage for critical private keys
[] possible recommendations for M and N on a multisig wallet
[] other
The text was updated successfully, but these errors were encountered: