Guide Noir zero-knowledge app integration on EVM with verifier generation and hashing parity.
npx skills add https://github.com/tawf-labs/zkt-hackathon --skill noir-tawf-labs
Please help me install this Agent Skill. Skill: noir Source: https://github.com/tawf-labs/zkt-hackathon/tree/main/.agents/skills/ethskills/noir Command: npx skills add https://github.com/tawf-labs/zkt-hackathon --skill noir-tawf-labs
It prevents common, costly integration mistakes when building Noir-based zero-knowledge privacy applications for the EVM, especially around proving, verifier generation, hashing choices, and cross-layer compatibility.
bb rather than removed nargo prove/verify.HonkVerifier.sol using bb write_solidity_verifier, including version/pragma and contract size considerations.msg.sender is public.--oracle_hash keccak), and serialization so proofs verify on-chain.Use the noir skill to set up a Noir circuit and generate a compatible Solidity verifier by running nargo compile and nargo execute, then using bb write_vk with --oracle_hash keccak and bb write_solidity_verifier, and finally wiring the deployed verifier address into your app contract.
High-intent search queries and answers about installing and using this skill.
To generate a Solidity verifier for Noir proofs, you must use the Barretenberg `bb write_solidity_verifier` command rather than removed `nargo` commands, ensuring you also configure the correct pragma and contract size considerations for on-chain deployment.
Noir proofs fail EVM verification when cross-layer ABI and input-order parity are broken. You must enforce consistent Poseidon variants, public input ordering, and oracle hash configuration using `--oracle_hash keccak` during proof generation.
To set up the Noir and Barretenberg toolchain, install nargo and bb in the correct sequence, then use `nargo compile` and `nargo execute` followed by `bb write_vk` with `--oracle_hash keccak` to prepare for proof generation.
You need a commitment-nullifier flow for Noir privacy architecture when using Merkle trees and on-chain action execution, which critically requires unlinkability through fresh burner wallets or relayers when `msg.sender` is public.
Noir supports simple private proofs without a full Merkle tree structure for EVM privacy apps, allowing developers to choose between basic private proofs and full commitment-nullifier flows depending on the required unlinkability constraints.
Limitations of using Noir for EVM privacy apps include the critical need to manage unlinkability manually with fresh burner wallets or relayers, and the strict requirement to maintain hash and serialization consistency across EVM and circuit layers.
PaulRBergBuild EVM dApps with Viem and Wagmi for typed contract interactions.
BarisSozenHandle blockchain RPC errors and estimate gas with buffers for multi-chain transactions.
collat-labsCorrect Noir toolchain, circuit, and EVM verifier integration mistakes.
noir-langOptimize ACIR circuit size for Noir programs using nargo and bb.