Everything that runs BWICK on-chain is open. This section is the actual source of every deployed contract, file by file, with a plain-English overview of each so you can see exactly what happens when you launch a token, swap, bridge, or vote.
These pages are generated directly from the contract source in contracts/ and regenerated whenever a contract changes, so what you read here is what is deployed, not a summary that can drift.

​
The contracts

Launchpad

Permissionless token launches on a bonding curve that graduates to the AMM.

AMM

Constant-product pools, swaps, and liquidity for graduated tokens.

Oracle

The on-chain BWICK/USD price feed.

Config Registry

The single on-chain pointer every app resolves addresses from.

Vesting

Time-locked token release schedules.

Name Service

The .bwick name registry.

Proposals

On-chain community proposals and multi-option voting.

​
How to read a contract

Each contract follows the standard CosmWasm layout, so once you know the four files you can read any of them:
FileWhat it is
msg.rsThe interface: every message you can send and every response you get back. Start here.
state.rsThe storage: the structs and keys that persist between calls.
contract.rsThe logic: the instantiate / execute / query entry points and their handlers.
error.rsThe typed errors and what triggers them.
CW20 (the fungible-token standard the launchpad mints) is the audited cw20-base library, not custom code, so it is not reproduced here.