Ludovit Scholtz

just increase the https://github.com/algorand/go-algorand/blob/master/daemon/algod/api/server/v2/handlers.go#L68 MaxTealSourceBytes to 1M instead 200k pls The error is thrown probably here: https://github.com/algorand/go-algorand/blob/1493410add4aaa4a5537037de1d88f166ccc85db/daemon/algod/api/server/v2/test/handlers_test.go#L1541

> You can do it now (without the need for any change in Algorand source code or new opcodes) : In smart contract which originates the inner TXN, add txn...

> I have no control over the smart contracts which call my contract.. as i said we need this composable.. the same way as dex aggregators can call pact and...

> Oh having no control is another context you just updated and added to this subject. yes in that case this solution I mentioned is of no use. So I...

@pbennett The use case is - Biatec Identity verifies person and stores to the box verification class 2 or trading fees multiplier, Biatec dex allows to swap only with verification...

> > @pbennett > > The use case is - Biatec Identity verifies person and stores to the box verification class 2 or trading fees multiplier, Biatec dex allows to...

> People are getting the cheap trading fees that you intended only for user A. can you please describe more in depth how you mean this? i believe if person...

> The only solution here is for you, Biatec, to decide which DEXs can call you, because you trust them, _not_ to implicitly assume that if the original caller is...

> https://medium.com/@solidity101/demystifying-ethereum-understanding-msg-sender-tx-origin-and-external-calls-dbf02d9e947d Btw if you implement this you remove one argument why ethereum is better then algorand.. With ETH you can work with the signer of the app call in...

I believe that the smart contract developers should have right to choose if they want to check the real tx signer.. Its backed by multiple people above. I dont get...