Description

• apply errorprone fixes found in Pantheon
• update dependency versions
• upgrade gradle to 4.10.2

Support Uint16, Uint24, Uint64, Uint256, Uint384 types.

Description

Basic architecture diagram and some text

Description

We need to implement a gRPC endpoint on this client

Acceptance Criteria

• Needs to be generic so that Pantheon can use it too

Description

We have no logging implemented in the BeaconChain. Checkout this document to get an idea of how we would like it implemented:

https://github.com/PegaSysEng/artemis/blob/master/docs/development/logging.md

Acceptance Criteria

• Use this framework: https://logging.apache.org/log4j/2.x/
• replace all print statements with logging

We should investigate bringing in stuff like net.consensys.pantheon.util.uint and net.consensys.pantheon.util.bytes as dependencies rather than copy-pasting the code into beacon chain packages. (If we even need these.)

Description

CI is currently running on openJDK 8. We'd like it to be 11.0.1

• Cleanup Gradle Plugin Management
• Consolidate common dependencies where appropriate. (Such as for junit and mockito)
• Resolve circular dependencies in parent gradle project.

https://github.com/ethereum/eth2.0-specs/blob/master/specs/test-format.md

Use Java8's long unsigned operations to implement a working Unit64 wrapper.

More details here: https://docs.google.com/document/d/1XBJD10WaUxYGaiUIXyJd23QJJulIXdwcx2iM24DCJR8/edit#bookmark=id.u9kous74kuk0

• Division should perform only integer division. Integer types are not expected to handle remainders.
• Add javadoc style method comments for autocompletion niceness.
• Too much code is repeated in the unit tests, this should be refactored.

Not adding a newline and not being called from build.gradle

Implement a container to support a uint384 (48 bytes) for holding the BLS sigs. Currently, it doesn't seem as though any arithmetic operations are necessary, that should be handled by the BLS lib.

If additional operations beyond simple comparison are necessary, an additional issue should be created.

When using openJDK 11.0.1, I get the following errors:

Execution failed for task ':util:compileJava'.
> Cannot specify -processorpath or --processor-path via `CompileOptions.compilerArgs`. Use the `CompileOptions.annotationProcessorPath` property instead.

Implement data structures in BeaconChain specs as POJOs.

just needs to be a skeleton for now

As per the LICENSE file, every source file must have the following boilerplate copyright added:

/*
 * Copyright 2018 ConsenSys AG.
 *
 * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with
 * the License. You may obtain a copy of the License at
 *
 * http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on
 * an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the
 * specific language governing permissions and limitations under the License.
 */

Create a delegate class demonstrating interaction with the VRC contract.

Create ChainStoreService.java:

• stores blocks, attestations, and states
• controls what to keep in memory and what to write to disk

Note: Alway worth looking at what Pantheon did:
https://github.com/PegaSysEng/pantheon/tree/master/services/kvstore/src/main/java/tech/pegasys/pantheon/services/kvstore

Look at Pantheon repo for guiy

Cards can be added to your board to track the progress of issues and pull requests. You can also add note cards, like this one!

Deploy VRC contract to Ropsten. Annotate the address of the deployed contract in the README.md.

Use guava to implement pubsub pattern

• remove unnecessary primitives that were carried over from pantheon
• remove and/or reconfigure Dockerfile to be specific to developing/running the beacon chain
• remove and/or refactor unnecessary utilities from pantheon not relevant for beacon chain/eth2

Protocol Labs guys added support for quic and partial pub/sub support. I need to keep my PR current with their master so they can approve/merge

The ServiceController handles the lifetime of all the services so it needs to be added there

Implement SSZ in accordance with the spec listed here. Additional resources can be found here here

It might be nice to have a way to instantiate the BeaconChain Service class

Description

We want cool build and test badges

The VRC Contract needs to have tests implemented.

• Install Code of Conduct, Contributing etc. #51
• Add copyright notices to all source files #56
• Automate the CLA signing on first commit
• Create our own Gitter channel (or use Pantheon's?) and reference it in the CLA etc.
• Link to Pantheon's coding conventions from the relevant places
• Automate the build process on commit (Spotless check at a minimum)
• Move to PegaSysEng repo?
• Decide on a cool name?

right now the VRC only emits an event when a validator is registered. Need to emit an event when a new Pow block is detected too.

The hashing function under-the-hood for Eth2.0 is BLAKE2b-512. Currently the algorithms supported in the Hash file are Keccak-256, Sha-256, RIPEMD160.

Implement the helper functions defined in the BeaconChain spec.

Look at Pantheon repo for guidance

Add labels for issue management.

E.g.

• bug
• enhancement
• good first issue

Check what Pantheon does. Add labels to existing issues.

Description

We still have relics of our old file structure in our code

Acceptance Criteria

• folders named beaconchain need to be renamed to artemis
• net/consensys renamed to tech/pegasys
• update imports

IMPORTANT: use git mv to perform the folder renaming

Additional Information

BeaconStateTest.java is not recognized by gradle

• Configure gradle file to run tests with 'gradle test'
• Use annotation VisibleForTesting for testing private methods

Description

We need to implement CLI arg processing similar to Pantheon (they use picocli)

Acceptance Criteria

• implement ArtemisCommand class

Currently, some 3rd parties are using licenses not in our accepted licenses list. For now we have temporarily disabled checking licenses, but we need to either get approval from legal or remove these dependencies.

Create the client (probably making use of web3j) to communicate with the VRC.

Bring VRC contract and Truffle into the repository as a root folder.

Description

Getting this warning: An illegal reflective access operation has occurred

Acceptance Criteria

• no warnings

Steps to Reproduce (Bug)

1. ./gradlew clean
2. ./gradlew build

Expected behavior: [What you expect to happen]
There shouldn't be a warning
Actual behavior: [What actually happens]

$ ./gradlew build
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by io.netty.util.internal.ReflectionUtil (file:/Users/jonny/.gradle/caches/modules-2/files-2.1/io.netty/netty-common/4.1.19.Final/b281916c11d3eeec5e839677ec4f2eb9d7586928/netty-common-4.1.19.Final.jar) to constructor java.nio.DirectByteBuffer(long,int)
WARNING: Please consider reporting this to the maintainers of io.netty.util.internal.ReflectionUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

Frequency: [What percentage of the time does it occur?]
100%

Versions (Add all that apply)

• Java version: [java -version]

openjdk 11.0.1 2018-10-16
OpenJDK Runtime Environment 18.9 (build 11.0.1+13)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.1+13, mixed mode)

• OS Name & Version:

Darwin 10.13.6

• Kernel Version: [uname -a]

Darwin jonnys-MBP.attlocal.net 17.7.0 Darwin Kernel Version 17.7.0: Wed Oct 10 23:06:14 PDT 2018; root:xnu-4570.71.13~1/RELEASE_X86_64 x86_64

Additional Information

Implement Bytes3

Extending the Pantheon types seems to be much more complex than using web3j. Web3j numeric types implement the BigInteger type, which has add(), subtract() , multiply(), divide(), remainder(), equality and comparison, as well as other supported math operations. Web3j types seem simpler to understand as well as cleaner than the Pantheon types. I'm not sure whether extending the Pantheon types would be worth the time required to implement them, at least right now, for the sake of reducing our dependencies.

Mirror the relevant files from Pantheon.

E.g.

• CODE-OF-CONDUCT.md
• CODING-CONVENTIONS.md
• CONTRIBUTING.md
• GOVERNANCE.md
• CLA.md

In addition, set up the CLA as a merge pre-requisite.

Make a basic event loop and skeleton classes