Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.solidscipt.zoracle.xyz/llms.txt

Use this file to discover all available pages before exploring further.

When you run a deploy command without a --wallet flag, SolidScript uses a local browser bridge to collect your signature. The CLI prepares the full deployment transaction, your browser wallet signs it, and the CLI waits for the on-chain receipt. Your private key never touches the project directory or the terminal session. 
npx solidscript deploy MyToken -n base-sepolia -a 1000000

​
How the flow works

1

Encode the deployment

SolidScript compiles the artifact and ABI-encodes constructor arguments into the creation transaction.
2

Start the local bridge

The CLI starts a single-use server at http://127.0.0.1:7654/ and opens your default browser.
3

Connect the wallet

The page checks window.ethereum and prompts MetaMask, Rabby, or Coinbase Wallet.
4

Switch chains when needed

The page requests wallet_switchEthereumChain, or wallet_addEthereumChain if the network is missing.
5

Send the transaction

The wallet sends eth_sendTransaction. The browser posts the transaction hash back to the CLI.
6

Wait for confirmation

The CLI waits for the receipt, reads contractAddress, prints it, and verifies source when configured.

​
Hot wallets for test environments

Hot-wallet commands still exist for local and CI test environments where you need non-interactive deploys: 
npx solidscript wallet new dev
npx solidscript wallet balance dev -n base-sepolia
npx solidscript deploy Counter -n anvil --wallet dev --no-browser
Use local hot wallets only for development. For real value, prefer the browser-wallet flow so the CLI never sees your private key.