Skip to content
Available on private testnetTestnet: yesMainnet: Not availableSoftware: Core bad4a06ea · protocol pqwerai-v8-testnet/1Updated

Contract Studio

The Studio page is a visual, vertical flowchart for building and deploying smart contracts. Each step turns green when it is valid, so you always know what is left to do.

Two flows

Template flow (tokens and NFTs):

Contract type → Name and symbol → Supply (or Items and metadata) → Features → Owner → Review → Deploy on chain → Verify and track

Custom-code flow:

Code from AI or file → Compile or load artifact → Constructor arguments → Review → Deploy → Verify

Tokens and NFTs from templates

ERC-20 tokens and ERC-721 collections use two OpenZeppelin 5.0.2 templates that are precompiled (pinned solc 0.8.26, evmVersion: london, deterministic, zero warnings). Because they are precompiled, no compiler is needed to deploy them. After deployment the wallet checks that the on-chain runtime code is byte-identical to the shipped artifact, reads back name/symbol/supply/owner, and adds the contract to Tokens.

Working with an AI assistant

Studio is designed to round-trip with an assistant such as Claude or Codex:

  • Copy AI prompt puts clear instructions on the clipboard.
  • Paste from AI reads the assistant's whole answer back. Markdown code fences are stripped, and the content is recognised automatically as a flow ("schema": "pqwerai-flow/1"), Solidity source, a compiled artifact (solc standard JSON, Hardhat, Foundry or Remix) or raw bytecode.
  • Copy flow JSON / Copy Solidity send the current design back to an assistant for review.
  • Flows can also be saved and opened as files.

Compiling pasted Solidity

Pasted Solidity is compiled with standard JSON over stdin. @openzeppelin/contracts 5.0.2 imports resolve from a bundled copy, so the compiler reads no files from your disk and needs no network access. Rules the Studio enforces:

  • Always evmVersion london (a conservative target).
  • PUSH0 in pasted bytecode is flagged.
  • EIP-170 and EIP-3860 size limits are enforced.

The compiler is either the official solc 0.8.26, downloaded on request and accepted only if its SHA-256 matches the pinned value 537fd8d8…eb67 (from binaries.soliditylang.org), or a solc.exe you choose yourself.

Deploy and verify

Every deployment goes through the normal confirmation dialog (all parameters, fee and chain ID) and your password. Custom code is clearly labelled unaudited — you are responsible for what it does. After deploying, the wallet verifies the contract and tracks it.

Seven languages

Through the Studio, PQWERAI supports seven contract languages (Solidity, Yul, Vyper, Huff, Fe, and C++/C# for the WASM VM), each checked against the chain's own EVM and WASM VM. See the Language center.


Sources at 7a33c77104: apps/pqwerai-wallet-windows/README.md

Found a problem? Report a documentation issue · Build testnet-rc1+7a33c77104