Nathan Wilcox

Results 83 comments of Nathan Wilcox

Has there been any update on this proposal? I came here hunting for the design, rationale, and specification specific to issuance, so for me and posterity it would be awesome...

For posterity, I've found [Ethereum 2.0 Economic Review by Hoban & Borgers](https://drive.google.com/file/d/1pwt-EdnjhDLc_Mi2ydHus0_Cm14rs1Aq/view) to be really helpful so far in understanding which attacks contribute to security metrics for amount of ETH...

Bump. This feature, along with #116 are two requirements my project needs beyond what this project already provides. It's so close. Nice work! It would be cool to show vertical...

This sounds like an excellent building block for further capacity improvements. Nice work! :-) ### Miner Aggregation Question Question: Is it possible for a miner to perform aggregation over their...

FYI: I prototyped a minimal rust bindings crate, [zcash_lightwallet_proto](https://github.com/nathan-at-least/zcash_lightwallet_proto#readme) to learn what that would look like. In the README I cautioned that this crate is likely to produce better maintained...

As I started working on bringing the `native_cctools` package into the nix framework, I realized I should check for in-flight PRs with clang builds and discovered https://github.com/zcash/zcash/pull/4613 . I glanced...

I should clarify the `nixpkgs clang v8` is not the same pinned revision being worked on in https://github.com/zcash/zcash/pull/4613. Instead it comes from the revision of `nixpkgs` that this PR pins...

Gave a presentation to ECC devs today about this branch. Github says this branch merged, but I haven't tested the build of that clean merge yet, so I recommend blocking...

@rex4539, apologies for missing your comment! Thanks for trying it out. ### Big picture - a rewrite is probably the right next step: First, some big picture updates before digging...

Now that the spec is linkable, I advocate adding a requirement for "consensus-facing PRs" which is that to check that code comments link to the spec for requirements context. Note...