Deniz Mert Edincik

I think reputation management for sender can be added, to verify they send correct data, with reasonable speed. ( unless this will be p2p for my own cluster )

I think we can make this non-breaking change: https://github.com/onflow/sdks/pull/18#issuecomment-1735471797

this is tricky; their result can leave view scope. ```cadence var ref = view fun(): auth(Storage) &Account{ return getAuthAccount(0x1) }() ref.storage.save("deniz", to: /storage/x) ```

yeah this is very old issue ( related to cadence json in args )there was a fix in flow-go-sdk to match fcl-js behaviour. ( while encoding arguments, extra new line...

@peterargue here is the place I mentioned: https://github.com/onflow/flow-go-sdk/blob/26fbdaba3bb73f5a1d9ac143656d124654fdd57b/transaction.go#L372-L376 Here is go json encoder part: https://github.com/rsc/xstd/blob/55f693673a79603c776ccb0bf91dd0c985148051/go1.14.9/encoding/json/stream.go#L212-L218 Basically go is adding extra \n when encoding Cadence.Value, fcl-js is not. There was some...

> The thing that concerns me a bit more is how we are going to add build flags in general? I don't think this can be possible with `go install`...

it just says "1 workflow awaiting approval, This workflow requires approval from a maintainer" for me? did you manage to get any secrets?

> My proof-of-concept demonstrates that if a maintainer were to click 'Approve and run' on this PR, the payload in matrix.go would execute, compromising the runner and exfiltrating any available...

If we add `hash()` method to struct we can make a `Signed` struct, then we don't need to worry about mutability. It would be nice to be able to generate...

First of all I love this, this is really huge problem now, you send the transaction, approx 4-5 seconds you get the result with executed status, but then it tools...