Tim Zerrell

Results 13 issues of Tim Zerrell

Prior discussion: > I think there's instructions for how to run the tool, but not good documentation about why it's necessary, what the limitations are, etc. Current plan is to...

documentation

Our Poseidon/Poseidon2 `hash_pair` functionality is intended to work with Digests generated by Poseidon hashing. However, prior to this PR, it does not perform checking to ensure that its input Digests...

Expand our Rust docs with documentation for code that is enabled only when certain features are turned on, or on certain platforms. Look at https://docs.rs/tokio/latest/tokio/ for an example.

documentation

Every example in the `examples` directory should have at least one test, so we know whether changes have broken that example. Currently examples with no tests I could find: *...

On my local machine, I am encountering the following error when trying to build `main`. This doesn't reproduce on all machines, and may involve my environment being in a confused...

bug

With @capossele's updates to the datasheet in https://github.com/risc0/risc0/pull/897 (:tada:!), we should update the website to link to these new figures rather than the older datasheet. I see a few ways...

documentation

This repository is obsolete, and has been replaced by the [`cargo risczero new`](https://crates.io/crates/cargo-risczero) command and the [Rust starter template](https://github.com/risc0/risc0/tree/main/templates/rust-starter) in our main repo. Ensure all associated content (e.g. issues, PRs)...

## User's Objective Any Trusted Setup Ceremony data that we mirror should be linked in our TSC docs with this mirror (in addition to its native home, if any). ##...

documentation

## User's Objective Users confirming the security of our trusted setup ceremony should be able to see relevant audit information. ## User's Obstacle We are still working through getting our...

documentation

This repository has been migrated into https://github.com/risc0/risc0/tree/main/examples. Ensure all associated content (e.g. issues) is appropriately migrated, put up a redirection notice, and archive this repository.