| pragma solidity ^0.4.14; | |
| library Pairing { | |
| struct G1Point { | |
| uint X; | |
| uint Y; | |
| } | |
| // Encoding of field elements is: X[0] * z + X[1] | |
| struct G2Point { | |
| uint[2] X; |
Having seen @pirapira's sketch of Bamboo ( https://github.com/pirapira/bamboo/ ), which proposed to add better control about the "smart contract program flow", even across calls, I thought that this should certainly be added to Solidity, and actually, it might even be possible now to a certain degree using inline assembly.
The problem is that with many functions in a contract, it is not always clear which can be called at which stage in the contract's lifetime. Certain smart contracts would be easier to understand if written as follows:
This document will walk you through compiling your own scientific python distribution from source,
without sudo, on a linux machine. The core numpy and scipy libraries will be linked against
Intel MKL for maximum performance.
This procedure has been tested with Rocks Cluster Linux 6.0 (Mamba) and CentOS 6.3.
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.
| // Use Gists to store code you would like to remember later on | |
| console.log(window); // log the "window" object to the console |