lighthouse/beacon_chain/spec/Cargo.toml

[package]
name = "spec"
version = "0.1.0"
authors = ["Paul Hauner <paul@paulhauner.com>"]
edition = "2018"

[dependencies]
bls = { path = "../utils/bls"  }
types = { path = "../types" }
Add `ChainSpec` structure. It includes all constants from the [Constants](https://github.com/ethereum/eth2.0-specs/blob/master/specs/core/0_beacon-chain.md#attestation) section in the spec, except for things that are clearly enums. My reasoning is that these enums are not so much "chain specification" and this struct should be reserved for items that "configure" the chain. 2018-12-12 05:08:01 +00:00			`[package]`
			`name = "spec"`
			`version = "0.1.0"`
			`authors = ["Paul Hauner <paul@paulhauner.com>"]`
Add 'edition = "2018"' to every Cargo.toml 2018-12-19 15:38:59 +00:00			`edition = "2018"`
Add `ChainSpec` structure. It includes all constants from the [Constants](https://github.com/ethereum/eth2.0-specs/blob/master/specs/core/0_beacon-chain.md#attestation) section in the spec, except for things that are clearly enums. My reasoning is that these enums are not so much "chain specification" and this struct should be reserved for items that "configure" the chain. 2018-12-12 05:08:01 +00:00
			`[dependencies]`
Add extra params to `ChainSpec` 2018-12-13 05:01:04 +00:00			`bls = { path = "../utils/bls" }`
Add `ChainSpec` structure. It includes all constants from the [Constants](https://github.com/ethereum/eth2.0-specs/blob/master/specs/core/0_beacon-chain.md#attestation) section in the spec, except for things that are clearly enums. My reasoning is that these enums are not so much "chain specification" and this struct should be reserved for items that "configure" the chain. 2018-12-12 05:08:01 +00:00			`types = { path = "../types" }`