myutzy / pic-witness Goto Github PK

A document called avoiding_common_attacks.md that explains what measures you took to ensure that your contracts are not susceptible to common attacks. (Module 9 Lesson 3)

https://www.kingoftheether.com/contract-safety-checklist.html

Follow Solidity comment spec: https://solidity.readthedocs.io/en/v0.4.24/layout-of-source-files.html?highlight=comments#comments

User Interface Requirements

• Run the app on a dev server locally for testing/grading
• You should be able to visit a URL and interact with the application
• App recognizes current account
• Sign transactions using MetaMask / uPort
• Contract state is updated
• Update reflected in UI

Test Requirements

• Write 5 tests for each contract you wrote
• Solidity or JavaScript
• Explain why you wrote those tests
• Tests run with truffle test

Design Pattern Requirements

• Implement emergency stop
• What other design patterns have you used / not used?
• Why did you choose the patterns that you did?
• Why not others?

Security Tools / Common Attacks

• Explain what measures you’ve taken to ensure that your contracts are not susceptible to common attacks

Use a library

• Implement a library or an EthPM package in your project

Stretch requirements (for bonus points, not required):

• Deploy your application onto the Rinkeby test network. Include a document called deployed_addresses.txt that describes where your contracts live on the test net.
• Integrate with an additional service, maybe even one we did not cover in this class
  • IPFS
  • uPort
  • Ethereum Name Service
  • Oracle

Users should be able to add descriptions to pictures.

A document called design_pattern_desicions.md that explains why you chose to use the design patterns that you did.

• At least 5 tests per contract
• Write a sentence or two explaining what the tests are covering, and explain why you wrote those tests