fjrojasgarcia / ethereumbook Goto Github PK

Upgrade Smart Contracts on Chain

https://vomtom.at/upgrade-smart-contracts-on-chain/

Develop a chapter for Blockchain operating system for decentralized applications

https://github.com/zeppelinos

https://medium.com/@julien.m./what-is-an-ethereum-keystore-file-86c8c5917b97

What are the differences between string, bytes32, byte[], bytes?

etc ...

https://blog.qtum.org/diving-into-the-ethereum-vm-6e8d5d2f3c30

https://gist.github.com/hayeah/bd37a123c02fecffbe629bf98a8391df

Smart contracts Formal verification

https://github.com/fjrojasgarcia/IPFSConsortiumContracts/branches
https://github.com/fjrojasgarcia/IPFSConsortiumProxy
https://press.swarm.city/ipfs-consortium-release-6907f0b55bbf

Hunspell

Solarstorm vs. Reentrancy

https://medium.com/@muneeb/solar-storm-a-serious-security-exploit-with-ethereum-not-just-the-dao-a03d797d98fa

STARKs

Through this issue I intend to highlight the importance that it can have for a developer to know what or who governs the evolution of the Ethereum protocol.

https://vitalik.ca/general/2017/12/17/voting.html

Modifiers can be used to easily change the behaviour of functions, for example to automatically check a condition prior to executing the function. They are inheritable properties of contracts and may be overridden by derived contracts.

You often see _ in modifiers

modifier onlyOwner() {
if (msg.sender != owner) throw;
_
}

From Solidity version 0.4.0+, you now need to add a semicolon after _. See Solidity - Version 0.4.0:

Change _ to _; in modifiers.

The code for the function being modified is inserted where the _ is placed in the modifier.
You can add more than one _s in the modifier code. And the code of the function being modified is inserted in each place where _ is located in the modifier. See modifier checkThree. This may be prevented by later versions of the solc compiler.
The modifiers gets called in the sequence they were defined (checkOne checkTwo checkThree) and at the end of the function, they are called in reverse. The modifiers seem to be applied like a stack. In this example anyway.

https://ethereum.stackexchange.com/questions/5861/are-underscores-in-modifiers-code-or-are-they-just-meant-to-look-cool

http://solidity.readthedocs.io/en/develop/assembly.html

Todo 01 description

https://blog.ethereum.org/2016/12/05/zksnarks-in-a-nutshell/

https://github.com/ethereum/wiki

ethers-ens: https://github.com/ethers-io/ethers-ens

https://ethereum.github.io/yellowpaper/paper.pdf

https://swarm.city
https://github.com/swarmcity

https://vitalik.ca/

This task is only to learn and test Waffle.

zero-knowledge proofs typically require a trusted setup: they must be initialized by some trusted authority because in practice it means that the authority could produce fake “proofs.” These fake proofs could lead to uncontrolled and undetectable inflation.

https://blog.aragon.one/library-driven-development-in-solidity-2bebcaf88736

https://solidity.readthedocs.io/en/v0.4.20/index.html

The "Greedy Heaviest Observed Subtree" (GHOST)

https://github.com/ethereum/wiki/wiki/Design-Rationale#uncle-incentivization

Secure High-Rate Transaction Processing in
Bitcoin

https://eprint.iacr.org/2013/881.pdf

https://media.consensys.net/ethereum-gas-fuel-and-fees-3333e17fe1dc