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
Pain point: when using cargo-stylus, it is unclear to me when to use the cache manager and how to use it to reduce costs for future calls to the contract
Proposal: when I use cargo stylus deploy, I can see:
$ cargo stylus deploy \
--private-key=<PRIV_KEY>
Compressed WASM size: 3 KB
Deploying program to address 0x123...
Estimated gas: 123456789
Submitting tx...
Confirmed tx 0xabc..., gas used 123456789
Activating program at address 0x456...
Estimated gas: 123456789
Submitting tx...
Confirmed tx 0xdef, gas used 123456789
INFO: Your contract is not part of the cache. To submit a bid to add your deployed contract 0x123... to the cache, please use `cargo stylus cache`
The text was updated successfully, but these errors were encountered:
Pain point: when using cargo-stylus, it is unclear to me when to use the cache manager and how to use it to reduce costs for future calls to the contract
Proposal: when I use cargo stylus deploy, I can see:
The text was updated successfully, but these errors were encountered: