Tom French

Run commands only on a single package if current working directory is within that package

1

### Problem Within a workspace, we currently run all commands under the `DefaultOrAll` strategy no matter where you are within the workspace. This is unexpected coming from rust where if...

### Problem These functions are currently almost identical except for the subdirectory and the snippet which is being written https://github.com/noir-lang/noir/blob/fd291971f2060438c4b529e4cb5b5911a9939418/crates/nargo_cli/build.rs#L42-L44 ### Happy Case We should abstract these functions so that...

https://github.com/itsdevbear/solmate-merkle-drop/blob/bec7c6a78569597f7a846cc0863d638e7cc3b432/src/ERC20MerkleDrop.sol#L12 Here you're writing to a clean slot for each merkle proof so we're spending 20k gas per user compared to 5k per user if you write to a dirty...

Make stream creation atomic

1

This PR consolidates the two transactions to create a stream (sending ZkAsset to contract and initialising stream) into one. Currently blocked as the AZTEC SDK doesn't support signing an approval...

Currently many of the testing files are still using javascript. As these are being completed we should convert them to typescript so that all non-trivial code is in typescript.

- [ ] pull in relevant interfaces + libraries from @aztec/protocol and bump pragma - [ ] update solidity code to use v0.6 constructs

This issue shows an example on how to avoid the 0% coverage issues: https://github.com/sc-forks/solidity-coverage/issues/474

There are several new features/fixes to the contract which need to be deployed

Once Zeit supports multiple deployments from a single repo I should deploy the new landing page and update the FAQ link to point at that.

Make stream creation and sending of ZkAsset atomic

2

Currently to create a stream requires 2 transactions (1 through sdk to send the ZkAsset to the contract, 1 to give the stream parameters). This leads to the possible situation...