vyperlang/vyper

VIP: Add support for Blake2 precompile

Open

#1,651 opened on Oct 24, 2019

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Python (4,710 stars) (849 forks)batch import
VIP: Approvedenhancementhelp wanted

Description

Simple Summary

Add support for blake2 cryptographic hash function

Motivation

Blake2 is a newer but popular hash function that is being used in a variety of circumstances including ZKP due to it's efficiency under pairing operations. Support in Vyper would make it easier to develop applications that use it.

Specification

Support for Blake2 is being added in the upcoming Istanbul hardfork. The specification is in EIP-152, and a reference implementation in a client is here: https://github.com/ethereum/py-evm/blob/master/eth/precompiles/blake2.py

Function signature:

blake2b_f() -> bytes32[2]

Backwards Compatibility

No backwards incompatibilities

Dependencies

No dependencies

Copyright

Copyright and related rights waived via CC0

Contributor guide

Tech stack
python
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Understanding of Vyper compiler internalsFamiliarity with EIP 152Knowledge of Ethereum precompilesPython development experience
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Start by reading the Ethereum EIP 152 specification for the Blake2 precompile. Then examine how other precompiles are implemented in the Vyper compiler (e.g., in the codebase at `vyper/compiler/precompiles.py` or similar). Look at the reference implementation in py evm (linked in the issue) to understand the expected behavior. Finally, design the implementation following the function signature provided and ensure integration with Vyper's ABI and type system.