Karol Ochman-Milarski

Uhm, so for me the issue persists on `AURA Version 3.2.7`. Is this fix included?

Why is `DatumHash`/`TxId`/`PubKeyHash` 28 bytes? For example [`DatumHash`](https://playground.plutus.iohkdev.io/doc/haddock/plutus-ledger-api/html/Plutus-V1-Ledger-Scripts.html#t:DatumHash) is described as: ```-- | Script runtime representation of a @Digest SHA256@.``` Why are these not 32 bytes? also what are the...

#### `DatumHash`, `RedeemerHash`, `ValidatorHash`, `MintingPolicyHash`, `StakeValidatorHash` For types `Datum`, `Redeemer`, `Validator`, `StakeValidator`, `MintingPolicy` from [plutus-ledger-api/Plutus.V1.Ledger.Scripts](https://playground.plutus.iohkdev.io/doc/haddock/plutus-ledger-api/html/Plutus-V1-Ledger-Scripts.html) there are functions in [plutus-ledger/Ledger.Scripts](https://playground.plutus.iohkdev.io/doc/haddock/plutus-ledger/html/Ledger-Scripts.html) calculating matching hashes. - `DatumHash`, `RedeemerHash` boil down to [hashScriptData](https://input-output-hk.github.io/cardano-node/cardano-api/Cardano-Api-ScriptData.html#g:2)...

As of now the hash types used are defined in [cardano-ledger/StandardCrypto](https://github.com/input-output-hk/cardano-ledger/blob/b076a648dd7b20e85c20fa6f0446bfa3d47b261b/libs/cardano-ledger-core/src/Cardano/Ledger/Crypto.hs#L39), where data hashes correspond to `HASH` (therefore are be 32 byte) and script hashes correspond to `ADDRHASH` (therefore 28...

I think it's impossible to stay consistent with decoding of "simple" values (like ints), due to protobuf3 semantic. I'm just today confronted with weird choices of protobuf3, so correct me...

if this interface is different or has changed could you please point me to some relevant piece of doc/code?

For my `npm run build` command to succeed while building the default derivation I need to provide `which` executable. I think I should override `buildInputs`, like in the example above.

Found that you guys (iog i mean) have hit this problem yourself, exactly that problem: https://github.com/IntersectMBO/plutus/blob/b97e8be50470065f37948f62dcaa7d67f71b9a39/nix/agda-project.nix#L14 Which is good because i have a fix. But also a second time that...

#11 might be useful, might not

I remember this issue since forever. Can we add a simple flag filtering outputs for just one system? As simple partial workaround, like: ```bash $ nix flake show --system=x86_64-linux ├───checks...