tepid basalt
Hi guys, I am trying to implement the custom account example with assembly script and I have a blocker with __check_auth. It gets called when invoking add_limit but it always traps when trying to access the storage to load the owners (futurenet).
The same happens for me with the original rust example. As soon as trying to access storage within __check_auth on futurenet, it traps.
Is this a known issue? Did somebody succeed to invoke add_limit successfully on futurenet?
dusky wolf
are you sure the footprint is correct?
tepid basalt
are you sure the footprint is correct?
You are right, the footprint was not complete. Preflight does not take __check_auth into account. Thanks a lot, that helped me and now it works. I almost went crazy 🙂
dusky wolf
ah, sure
sorry about that, I should have explained
basically preflight currently only supports the recording auth mode that just collects the required signature payloads. since there is no signature for custom account, there is no way to preflight __check_auth
tepid basalt
no problem, i should have thought of it myself.
dusky wolf
we should address this going forward and add a mode where you could provide a dummy signature and exercise all the custom account logic
neat nest
It's unclear to me how a dapp would know to use a fake sig. Only the signer will know a fake sig is required and it's format.
Do we have any up to date sequence diagrams showing the intended flow for simple auth and custom auth, showing the dapp, wallet, and their respective responsibilities? cc @inner socket