feat(docs): add transaction profiler docs #9932
Conversation
saleel
changed the title
Docs PreviewHey there! 👋 You can check your preview at https://6736ede7171fe516edd8a7ec--aztec-docs-dev.netlify.app |
docs/docs/guides/developer_guides/smart_contracts/profiling_transactions.md
Outdated
Show resolved
Hide resolved
docs/docs/guides/developer_guides/smart_contracts/profiling_transactions.md
Show resolved
Hide resolved
saleel
force-pushed
the
saleel/tx-profiler-docs
branch
from
86302dd
to
557aede
Compare
saleel
force-pushed
the
saleel/tx-profiler-docs
branch
from
557aede
to
5f2d770
Compare
There was a problem hiding this comment.
I am trying this command
aztec-wallet deploy token_contract@Token --args accounts:owner Test TST 18 -f owner -a token
on the master version of the sandbox and am seeing this error.
throw new Error('Invalid contract artifact argument provided. To use this option, command should be called from a nargo workspace');
based on aztec-wallet deploy -h , the package@contract syntax can only be used from inside a nargo workspace, so will this only work if people run the command with this syntax from inside the monorepo.
Token deployment works when I run it in the monorepo after I compile the token contract. This is a lot to ask readers to go through, any ideas on how we can make this faster/easier?
Otherwise it works great! 🙌
| aztec-wallet create-account -a user | ||
|
|
||
| # Deploy a token contract and mint 100 tokens to the user | ||
| aztec-wallet deploy token_contract@Token --args accounts:owner Test TST 18 -f owner -a token |
There was a problem hiding this comment.
Should we add a note that readers need to clone the monorepo and compile the token contract with aztec-nargo compile --package token_contract in noir-projects/noir-contracts?
There was a problem hiding this comment.
Oh, right. I have added this note.
This is a lot to ask readers to go through, any ideas on how we can make this faster/easier?
In practice, devs would be trying this with their own contracts in their nargo workspace. This mostly serves as an example right?
But if they want to follow along and use the same steps then they would need to clone the monorepo and deploy the token contract. I think it is ok given that considering its not a mandatory step for anyone to profile their contract.
Solves AztecProtocol/dev-rel#443