teor
teor
**Is your feature request related to a problem? Please describe.** Currently, Zebra binds to the configured `listen_addr`, and also advertises that address to peers for inbound connections. This doesn't work...
## Motivation Some miners use shielded coinbase, but it's pretty rare. ### Specifications > * [Sapling onward] If effectiveVersion ≥ 4 and nSpendsSapling + nOutputsSapling > 0, then: > –...
## Motivation Mainnet nodes must check that their chain contains NU5 before: - risking funds, including mining - displaying transactions to users, including through `lightwalletd` Ticket #5912 fixes this issue...
## Motivation When I use in-browser SSH to a CD VM instance, I get this message: > Please consider adding the IAP-secured Tunnel User IAM role (iap.tunnelInstances.accessViaIAP) to start using...
## Motivation We currently have a separate test file for end of support tests, which makes `cargo` link `zebrad` into two different test binaries. This increases build time and test...
## Motivation Unknown unified receivers are valid according to the spec, but Zebra's RPCs reject them. Unified addresses are designed to be forwards-compatible, so new or experimental receiver types can...
## Motivation We need to store block work in the finalized state database to: 1. efficiently calculate `getnetworksolps` & `getnetworkhashps` responses, and 2. show the full cumulative chain work in...
## Motivation We don't have any block test vectors for NU5 on: * mainnet: https://github.com/ZcashFoundation/zebra/blob/main/zebra-test/src/vectors/block.rs#L542 * testnet: https://github.com/ZcashFoundation/zebra/blob/main/zebra-test/src/vectors/block.rs#L855 This means we're not testing the NU5 consensus rules in some unit...
## Motivation We've had a request to add the `valuePools` field to the `getblock` RPC response, to support a Zcash dashboard: > Not sure if this is the right place...
### What happened? I expected to see this happen: Users will expect to see the full chain work for every chain fork. This is what `zcashd` does. Instead, this happened:...