Important organizational announcement Due to feedback from several people who wish to contribute, this project is being moved to it's own repository. The master copy is now at SalusaSecondus/CryptoGotchas. This will let us more easily take PRs/Issues and track contributions.
- Add your project logo.
- Write a short introduction to the project.
- If you are using badges, add them here.
This is for programmers who want to ramp on Go, without resources that reiterate programming fundamentals. This would not be a good list of resources for folks who are learning to program using Go as their first language. Some resources that I dismiss here would be super valuable for newer folks. This is a selection of resources for those who understand programming fundamentals in a different language already.
- First steps = Tour of Go
- Don't waste time on Go Fundamentals-type books - it all lives in tour of Go.
- Consider joining the Gophers Slack
- When you need help, the Go Playground allows you make a quick scratch file and share it. Others trying to help can run your code easily this way.
The following list of questions was taken from https://www.reddit.com/r/ethereum/comments/72reba/do_you_have_deep_questions_about_solidity_or_the/
An updated summary on the different ways one could have two contracts interact (DELEGATECALL, STATICCALL, libraries, all that stuff) with clear pros/cons for each (gas cost, whether it requires EVM assembly directives, etc)
Question by /u/drcode
I won't talk about low-level opcodes here because of the brevity of the answer. In general, there are four ways functions can be called in Solidity:
<?xml version="1.0" encoding="utf-8"?> | |
<SiPolicy xmlns="urn:schemas-microsoft-com:sipolicy"> | |
<VersionEx>10.0.0.0</VersionEx> | |
<PolicyTypeID>{A244370E-44C9-4C06-B551-F6016E563076}</PolicyTypeID> | |
<PlatformID>{2E07F7E4-194C-4D20-B7C9-6F44A6C5A234}</PlatformID> | |
<Rules> | |
<Rule> | |
<Option>Enabled:Unsigned System Integrity Policy</Option> | |
</Rule> | |
<Rule> |
#Loading Tweaks in the Simulator
With the latest updates to the simulator, this turns out to be pretty simple:
You need to be using kirb/theos
In order not to require MobileSubstrate to be loaded and your tweak to be compiled for i386/x86_64, add
In your makefile:
#!/usr/bin/env bash | |
# | |
# american fuzzy lop - corpus minimization tool | |
# --------------------------------------------- | |
# | |
# Written and maintained by Michal Zalewski <[email protected]> | |
# | |
# Copyright 2014, 2015 Google Inc. All rights reserved. | |
# | |
# Licensed under the Apache License, Version 2.0 (the "License"); |
The purpose of this document is to make recommendations on how to browse in a privacy and security conscious manner. This information is compiled from a number of sources, which are referenced throughout the document, as well as my own experiences with the described technologies.
I welcome contributions and comments on the information contained. Please see the How to Contribute section for information on contributing your own knowledge.
Short version: I strongly do not recommend using any of these providers. You are, of course, free to use whatever you like. My TL;DR advice: Roll your own and use Algo or Streisand. For messaging & voice, use Signal. For increased anonymity, use Tor for desktop (though recognize that doing so may actually put you at greater risk), and Onion Browser for mobile.
This mini-rant came on the heels of an interesting twitter discussion: https://twitter.com/kennwhite/status/591074055018582016