You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Add profiler to playground
- Upload your own contract:
- show which version of `aztec-up`
- link to tutorial to push before to write their own contract
- make instructions less transparent
- Contract Interaction
- show parameter type in the text box
- authwit move description up and explain caller
- Add tool tip for simulate, send, authwit, profiler
- Connect to Sandbox
- show what version to deploy on
- Register contract
- When selecting contract, load AbI per usual and then automatically
load deploy pop up
- register/deploy button
- Rename button to - “click here to load this pre deployed contract”
- rename to “deploy/load contract”
- Select Contract/Account
- when deployed, the menu item should show “Contract: TST (0x123…)
- Add Account:
- Add “recommended” next to r1
- Add contact
- show that contact is of aztec address type
- Make log button is more obvious (it is a red button now like a chat)
- Inspiration button“start building”
- Set tx timeout to 2 mins
---------
Co-authored-by: PhilWindle <[email protected]>
Co-authored-by: Alex Gherghisan <[email protected]>
Co-authored-by: thunkar <[email protected]>
title="These functions are simulated locally and only proofs are sent to Aztec"
62
+
title="Function signature and execution are kept private by executing locally and generating a zk proof of correct execution. The proof is sent to Aztec."
title="Only invoked by applications that interact with contracts to perform state queries from an off-chain client. They are unconstrained, meaning no proofs are generated"
116
+
title="These are off-chain getters (for you to query the state) without generating any proofs. They are unconstrained, so no proof is generated and data is fetched locally."
0 commit comments