Osmosis #1043 9/20/2026, 9:01:31 AM

Store Bluechip factory contract (native-threshold build, 1 of 2)

Osmosis proposal #1043: This proposal stores the FACTORY contract of the Bluechip creator-token launchpad on Osmosis — the first of two StoreCode proposals (...

Yes

30%

No

0%

Abstain

70%

Veto

0%

Original Proposal Text

This proposal stores the FACTORY contract of the Bluechip creator-token launchpad on Osmosis — the first of two StoreCode proposals (factory + creator-pool; one per proposal because a combined store exceeds per-transaction gas limits). The companion proposal stores the creator-pool; the router needs no new store (byte-identical to code 1903 from proposal #1040). Why a re-store: the previously approved builds valued commits against a USD threshold via the Pyth OSMO/USD feed. Pyth has since discontinued its CosmWasm integration and the on-chain feed is frozen, so the oracle was removed entirely. The commit threshold is now denominated in OSMO itself (500,000 OSMO at launch): a commit's value toward the threshold IS its attached OSMO — no price feed, keeper, or thin-liquidity TWAP can influence when a pool crosses. The only price read left is a chain-native x/twap query used solely to budget the ~20 USDC pool-creation fee swap at crossing, and that swap's spend is hard-clamped to the protocol's own fee retention (never committer funds), failing closed on any anomaly. The factory is the registry and admin control plane: it creates pools, holds the 48-hour-timelocked config (pending changes readable on-chain via its PendingChanges query; an unapplied change expires after 7 days), and serves each pool's live commit context. Bluechip lets a creator launch a token paired against OSMO with no upfront liquidity, built entirely on Osmosis-native modules: the creator token is a TokenFactory denom, supporters commit OSMO, and when a pool's cumulative committed OSMO crosses its threshold the pool mints the fixed 1.2M-token supply, seeds a native GAMM balancer pool from the committed OSMO, and distributes tokens to committers pro-rata. Post-threshold the pool is a standard Osmosis GAMM market. The chain's GAMM pool-creation fee (alloyed USDC on osmosis-1) is funded from the protocol's own 1% commit fee — never by the creator. The admin/migrate authority is a multisig. Artifacts (reproducible from the repository default branch with cosmwasm/optimizer 0.16.0 — git clone, make optimize-all, sha256sum artifacts/*.wasm; commit add5694139198fc12f322748303dd65ccafefcc5): - factory.wasm: sha256 b2d5e5014f08e67a8ed6eca3f0b396f3702ac744f6c66c2978dfa2d53aeb03e6 - creator_pool.wasm: sha256 517ac0daf1b6345b7308d0d29eed2b9448e80b0cf4908ce9b7f0488ebea82b70 - router.wasm: sha256 ea5c69bb716932c0b879780f904437c6606a4c38a25a1d1f0d2bf654207a64ac = stored code 1903 (reused, no new store needed) This proposal only stores code. It instantiates nothing, changes no chain parameters, and grants no module access. Instantiate permission is Everybody: the factory's address cannot be allowlisted before it exists, and third-party instantiations are inert — pools only trust the factory that instantiated them, and the factory's registry only recognizes pools it created itself. Pools only ever hold OSMO, their own TokenFactory denom, and the gamm/pool LP shares of the pool they seeded — no privileged mint of OSMO, no bridged-asset exposure. Codes 1901/1902 from proposals #1037/#1038 are superseded and will remain unused. Forum discussion: Repository: https://github.com/Bluechip23/bluechip-osmosis-contract (commit add5694139198fc12f322748303dd65ccafefcc5)

Community

Up 0 Down 0 Comments 0

1XP X 0base.vc

Cosmos governance portal by 1XP Validator and 0base.vc

... chains Wallet ready