When deploying the cap table using forge script, critical information like this is currently not highlighted enough. It degrades developer experience (which is important for collaboration). If only a few people know what to do and where to look, it'll be harder to onboard new devs
forge script script/CapTableFactory.s.sol --fork-url http://*********:8449 --broadcast
[⠒] Compiling...
No files changed, compilation skipped
Script ran successfully.
== Logs ==
Upgrading CapTableFactory with CapTable implementation
Deploying CapTableFactory and CapTable implementation
CapTable implementation deployed at: 0x888afDfCf11E545D5E004B6Fb66008d9787c9579
CapTableFactory deployed at: 0x745258b51eB8CAa675DD041bAFC1f282858BdA57
## Setting up 1 EVM.
==========================
Chain 32586980208
Estimated gas price: 3.2 gwei
Estimated total gas used for script: 11820619
Estimated amount required: 0.0378259808 ETH
==========================
###
Finding wallets for all the necessary addresses...
##
Sending transactions [0 - 4].
I'm considering improving logging throughout the repo.
linear[bot]
commented
9 months ago
When deploying the cap table using forge script, critical information like this is currently not highlighted enough. It degrades developer experience (which is important for collaboration). If only a few people know what to do and where to look, it'll be harder to onboard new devs
I'm considering improving logging throughout the repo.