DBCETH
DeepBrain Chain / Ethereum
crypto

Been building a creator-token platform on Solana and just got the launch flow where it should be: the creator signs their own launch, not the platform.
How it’s wired with Meteora DBC:
• createPool takes separate payer and poolCreator. payer = our platform wallet (covers rent/gas), poolCreator = the creator’s own wallet (embedded, Turnkey).
• Server partial-signs the two keys it controls (fee payer + the ephemeral mint), the creator adds their signature client-side, then broadcast.
• No transferPoolCreator step, the creator owns the pool from t=0. mint authority gets revoked right after, supply fixed at 1B.
The one thing I wasn’t sure would hold: whether the embedded-wallet signer preserves the server’s partial sigs when the creator adds theirs. It does, tx landed with all three signatures intact, on-chain creator = the creator’s wallet, fee payer = platform.
Two things I’d flag for anyone doing the same:
• Explorers show the fee payer as “creator” in their summary view, the real owner is the poolCreator field on the pool account, read it from the SDK to be sure.
• Watch your config key isn’t silently falling back to a hardcoded default; that’s your fee-claimer.
Anyone else split payer vs poolCreator this way, or did you go a different route for embedded-wallet launches?

Been building a creator-token platform on Solana and just got the launch flow where it should be: the creator signs their own launch, not the platform.
How it’s wired with Meteora DBC:
• createPool takes separate payer and poolCreator. payer = our platform wallet (covers rent/gas), poolCreator = the creator’s own wallet (embedded, Turnkey).
• Server partial-signs the two keys it controls (fee payer + the ephemeral mint), the creator adds their signature client-side, then broadcast.
• No transferPoolCreator step, the creator owns the pool from t=0. mint authority gets revoked right after, supply fixed at 1B.
The one thing I wasn’t sure would hold: whether the embedded-wallet signer preserves the server’s partial sigs when the creator adds theirs. It does, tx landed with all three signatures intact, on-chain creator = the creator’s wallet, fee payer = platform.
Two things I’d flag for anyone doing the same:
• Explorers show the fee payer as “creator” in their summary view, the real owner is the poolCreator field on the pool account, read it from the SDK to be sure.
• Watch your config key isn’t silently falling back to a hardcoded default; that’s your fee-claimer.
Anyone else split payer vs poolCreator this way, or did you go a different route for embedded-wallet launches?