The launch starts with both of you.

DUOPAD gives two Solana creators a shared room to shape a token, record their proposed split and approve the same version before a launch transaction.

A token idea can start in a conversation: one person brings the artwork, another brings the name, and both decide to build something together. The difficult part comes when that conversation becomes a launch. Which image is final? Did the ticker change? Does the other person agree with the proposed split? What, exactly, did each person approve?

DUOPAD gives those questions a place to be answered. It is a launch room for two people, built around one shared draft and two separate wallet approvals. The aim is concrete: make the plan visible before either person treats it as agreed.

Put the idea on the table

The creator starts with a token name, ticker and optional story. They can upload artwork and enter their co-creator's Solana wallet address. Two percentages sit beside the draft, making the proposed creator and partner shares visible while the idea takes shape.

You can prepare this information before saving a room. Connecting a compatible wallet and signing a message creates the shared record. That save does not launch a token, submit a purchase or move funds. It establishes the draft that the other person will review.

The creator then copies an invitation link. The partner opens the same room and connects the wallet named in the plan. Anyone who receives the link can read the room, but approval is restricted to the two named wallets. Share the link with that visibility in mind.

One version. Two decisions.

An address in a form is not an approval. Each participant reviews the draft and signs their own approval message. DUOPAD records those signatures against the current version of the plan.

That version matters. Suppose the creator changes the artwork after the partner has approved it. The updated draft becomes a new revision and needs fresh approvals from both wallets. An earlier yes does not silently carry over to a different proposal.

The creator edits the room; both participants review and approve it. This keeps responsibility clear while allowing the pair to work toward the same final version. The room also offers an agreement download containing the draft and its recorded signatures, so the participants can retain the record outside the interface.

What the percentages mean

The split is a statement of the two creators' proposed agreement. For example, a 60/40 setting records that plan alongside the token details and approvals. It does not automatically allocate 60% and 40% of the token supply, divide trading fees or transfer funds between the wallets.

DUOPAD's current approval system is also an application-level review process. It is not a multisig vault or a mechanism that gives both wallets joint control over every future transaction. The creator wallet handles the launch transaction. These distinctions are part of understanding the product, not details to discover after signing.

From agreement to launch review

When both named wallets have approved the current revision, the creator can move to launch review. The implementation uses Raydium LaunchLab on Solana mainnet, with no initial token purchase included in the launch configuration.

A launch needs publicly hosted token metadata. The JSON must match the agreed name, ticker and story and include a public image. If artwork was uploaded to the room, the public artwork must match it. This check connects the proposal that both people reviewed to the information used for launch.

Before asking for a transaction signature, DUOPAD prepares the transaction and requests a network simulation. The review displays the estimated creation cost and network fee. Account rent and network fees apply, and the creator's wallet presents the transaction for the final decision.

After submission, a transaction record provides a Solscan link and a way to refresh its confirmation status. A submitted transaction is not automatically a confirmed launch. The status remains visible so the creator can check what the network actually recorded.

What is live

The current build includes persistent shared rooms, artwork uploads, invitation links, wallet-signed approvals, revision tracking and downloadable agreement records. The room and approval workflow has been tested with generated test keys, including rejecting invalid signatures and approvals for an outdated revision.

The mainnet launch integration is implemented, but a funded end-to-end mainnet launch has not been completed as part of that testing. Its availability depends on the connected wallet, valid public metadata, sufficient SOL and a successful network simulation. The animated phone walkthrough illustrates the product steps; it is not evidence of a completed on-chain launch.

Built around the pair

The interface reflects the workflow: two sides of a folding device, two voices beside the screen and one plan brought into view as the page unfolds. Inside the launch room, the same idea becomes practical. Draft the token. Invite the other half. Review the exact version together.

DUOPAD starts with a simple standard for a shared launch: both people should be able to see what they are saying yes to.