Free software.Paid devs.

Every launch here names an open-source project and sets aside at least 50% of its creator fee for it. Launch your own, and all of it is yours.

The share waits in a vault until the repository's owner signs in with GitHub and names a wallet, which can withdraw after 3 days of public notice. The launchpad's owner can name one only to settle a dispute or a lost account, with the same notice. Claiming is optional; opting out of new launches needs no wallet.

How verification works

GitHub says who owns the repository; the vault holds the share until that owner names a wallet. Five steps, all public.

  1. Find your repository

    A launch names its project by its GitHub repository, kept by GitHub's numeric id: a rename or a transfer keeps it, and a squatter on the old name gets nothing. The project's page lists its launches and what each chain holds for it.

  2. Sign in with GitHub as its owner

    Only the owner counts. Write access isn't ownership, so an admin or a maintainer can't claim, opt out or authorize anything.

    • Can: The account that owns a personal repository
    • Can: An active owner of the organisation that owns it
    • Can't: Repository admins and maintainers
    • Can't: Collaborators and anyone else with write access

    We ask GitHub for read:org only when an organisation owns the repository, check the answer, record it on the project's page and revoke GitHub's token. A sign-in can act for 30 minutes and changes nothing by itself.

  3. Choose what to do

    Each one is recorded in public on the project's page.

    • Claim the share

      Name the wallet the vault pays and sign with it. This starts the notice below.

    • Authorize one launch

      One per project reads Developer-authorized. Cleared if the repository changes owner.

    • Opt out

      No new launch can name the repository. No wallet needed; you can opt back in.

  4. The public notice

    The wallet you name signs, our registrar countersigns (good for an hour), and the wallet sends the proposal to the vault. Then it waits where anyone can see it.

    A proposal waits 3 days in public, then anyone can execute it for 7 days.

    During the notice, the project's current payout address can cancel a proposal our registrar signed; the owner Safe can cancel any. After it, anyone (our keeper included) can make it take effect within 7 days, or it lapses.

  5. Withdraw, whenever you like

    The vault pays only the project's payout address. That wallet withdraws what is held, asset by asset, as new shares keep arriving. From the project's page it can move the payout address or decline the share; a declined share stays held.

Keep the software free. Give the work a way to earn.

A launch earns the creator fee you set on every buy and sell, on top of the trade fee that goes to REA.fund's treasury. Launch your own verified repository and all of it is yours; launch someone else's and at least 50% is held for them until they claim it through GitHub.

What it earns depends on trading volume, not the token's price. A launch paired with a Robinhood Stock Token earns in that Stock Token, which Robinhood can pause, freeze or burn.

Creator fee
You choose, 1% to 10%, for the token's life
The project's share of it
50%, 75% or 100%, fixed at launch
Yours
The rest, collected from Profile any time
Trade fee
1%, all to the treasury
Launch fee
0.0005 ETH, to the treasury

Three steps

From a working build to a launch people can back.

  1. Show the build

    Name the project and its GitHub repository, and add a screenshot of it at work. Say what works today in the token's description.

  2. Create the token

    Choose a name, a ticker and a picture you have the right to use. Set your creator fee and the project's share of it, check the terms, and launch.

  3. Bring people in

    Share the launch, show your progress, and give people something new to try each time you ship.

What a launch's badge says

Every launch that names a project wears one, so it's plain whose launch it is.

Community-led
Launched by someone in the community. The project's developers haven't claimed their share; it's held for them.
Claim pending
A payout address for the project is in its public three-day notice; it takes effect after that unless it is cancelled.
Developer verified
The project's owner verified through GitHub and receives this launch's project share. They don't run or endorse it.
Developer-authorized
The project's owner verified through GitHub and authorized this launch.
By the developer
Launched by the wallet the project's owner verified through GitHub.
Developer declined
The project's owner turned the share down. What this launch earns for the project stays held.

Projects launched here

Show us what you're building.

A rough first version is a beginning. Tell people what it does today and give them a reason to follow the next release.