LeastAuthority finding

Area: The zcashd alert system

Area: Benchmarks

Area: Build system

Area: Chain synchronization / Initial Block Download

Area: Continuous Integration

Area: zk-SNARK circuits

Area: Founders' Reward

A-consensus-genesis

Area: Starting a Zcash chain from scratch.

Area: Consensus rules

Area: Cryptography

Area: Dependencies

A-documentation

Area: Documentation

A-end-of-service

Area: End of Service halt

Area: Support for bitpay bitcore insight block explorer

Area: The fuzzers and fuzzing infrastructure.

Area: Halo or Halo 2

Area: The zcash_script library.

A-light-clients

Area: Light clients

A-metrics-screen

Area: Metrics screen

A-network-observatory

Area: Observation and monitoring of the Zcash network and chain.

Area: Networking code

Area: Sapling on Halo2

Area: Packaging

Area: Proof-of-Work and mining

A-rpc-interface

Area: RPC interface

Area: The Rust FFI in the librustzcash library.

A-standard-rule

Area: Standard rules

Area: Tests and testing infrastructure

A-wallet-change

Area: Change handling within the wallet

A-wallet-database

Area: Wallet database and serialization

Category: Issues and tasks related to audit findings

Category: This is a bug

Category: PRs that clean code up or issues documenting cleanup.

C-community-contribution

Category: A contribution from the community!

C-feature-request

Category: This is a request for a new feature or functionality.

C-feature-requirements

Close when the feature's requirements are well specified.

C-future-proofing

Category: Changes that minimise the effects of shocks and stresses of future events.

Category: Engineering notes in support of design choices

C-simplification

Category: Changes that simplify the protocol specification or consensus rules.

C-upstream-port

Category: Changes that are ported from the Bitcoin Core codebase.

D-bitcoin-divergence

Design issue: Divergence from Bitcoin (upstream code and/or architecture).

D-decentralization

Design issue: Decentralization

Design issue: Economics

D-forward-secrecy-vs-recoverability

Design issue: Forward secrecy vs recoverability

D-monetary-policy

Design issue: Monetary policy

database corruption

Death By A Thousand Cuts

deprecation wishlist

dev infrastructure

E-good-first-issue

Effort: Suitable for someone new to the codebase.

Call for participation: Help is requested to fix this issue.

elliptic curves

Represents a multi-sprint effort (auto-generated label)

External Encoding

Feature: Clang support

Feature: C++11 usage

F-diversified-addresses

Feature: Diversified addresses

Feature: Docker support

Feature: I2P integration

Feature: Memo field

F-programmability

Feature: Programmability

F-selective-disclosure

Feature: Selective disclosure of shielded transaction details.

Feature: Tor integration

Feature: Transaction fees

Problems and improvements with respect to Denial-of-Service.

I-error-handling

Problems and improvements related to error handling

The zcashd binary fails to start, or crashes shortly after starting.

Problems that we know exist but cannot reproduce while looking at them.

Problems and improvements with respect to performance

Problems and improvements related to privacy.

I-protocol-fragility

Problems and improvements with respect to protocol fragility.

Problems and improvements related to race conditions.

This is a regression relative to a previous bugfix.

Problems and improvements related to security.

internationalisation

interplanetary exploration

The issue is invalid and has been raised in error.

Requires writing Python code.

Requires writing Rust code.

Link the Code and Protocol

M-circuit-change-unnecessary

This can be done without a circuit change (sometimes surprisingly)

M-going-fully-shielded

This advances our objective of deprecating t-addresses and going fully-shielded.

To-be-removed (GitHub has linked:pr filter)

M-potential-loss-of-funds

This issue risks a potential loss of funds for a user.

A network upgrade is required to implement this.

This change would need to be specified in a ZIP.

M-suggested-to-close

We should consider closing this issue or PR.

memory management

network upgrade management

Network Upgrade Wishlist

note selection and shielded tx construction

Network upgrade: Overwinter-specific tasks

Network upgrade: Sapling-specific tasks

NU2-blossom-adjacent

Issues that aren't directly part of the Blossom upgrade, but that we want to complete alongside it.

Network upgrade: Blossom-specific tasks

Network upgrade: Canopy-specific tasks

Target: ARM processors (AArch64 target)

Operating system: FreeBSD

Operating system: Linux

Operating system: macOS

Operating system: Windows

private testnet

Project Alchemy

public relations

redirected to slack/forum

replace_the_seeder

rollback protection

S-blocking-docs

Status: Blocks on documentation

S-blocking-programmability

Status: Blocks on programmability R&D

S-blocking-scalability

Status: Blocks on scalability R&D

Status: Planned work in a sprint

Status: Consider fixing this soon.

Status: Consider fixing this eventually.

S-needs-clearer-scope

Status: Needs clearer scope

S-scratching-an-itch

Status: Something we haven't planned for a sprint but are doing anyway

S-waiting-on-review

Status: Awaiting review from the assignee but also interested parties.

Tekton: Phase 1 build migration

separate_privileges

shielded address reliability

shielded note locking

special to Daira

special to Nathan

special to Taylor

special to Zooko

spring_cleaning

superceded by t-addr deprecation

Something that came up as an unexpected dependency

This is a bad idea

We really shouldn't do this unless we can't figure out a better alternative.

transaction expiry

tx propagation/mining latency

Includes changes that should probably be provided as a PR on Bitcoin Core

Historic: libsnark

Z-NU2-Blossom wishlist

Z-NU3 ZIP drafting

Historic: OpenMP

zkSNARK Multiparty Computation

zkSNARK Parameter Deployment

No labels found. Sorry about that.