Propose a question

What the form is#

Propose a question at /app/propose is for a question the current templates cannot express. It takes:

• a question of 12 to 240 characters;
• a topic from the fixed list of 17 categories, with three topic-specific details;
• a future final resolution deadline, entered in UTC;
• an https URL for the source a resolver would use;
• resolution rules of 80 to 3,500 characters and exception rules of 20 to 1,000 characters. Include the outcomes, observation window, source finality and unavailable results.

Elections ask for the jurisdiction and electoral authority, office/district/round, and candidates or parties with a certification criterion. Esports asks for the game/tournament/match, teams/start time, and match/map/series format. Each category has its own source and exception guidance.

Choose Review proposal to inspect the exact combined rules before signing. The details, deadline, exceptions and rules are stored together in the existing resolution-rules field, limited to 6,000 characters. You can return to editing without losing the draft.

Submitting asks your wallet for a signature, not a transaction. There is no gas. The server verifies the signature against your wallet address and stores the proposal with the status proposed.

What it is not#

The form's own confirmation says it: "Proposal submitted for review. No trading market has been created."

• It does not create a market, an event, a series or a template.
• It does not send anything to the chain.
• It does not enter a workflow. The stored record has one status and there is no code that moves it to another.
• It is not private. Your proposal text and your wallet address are stored together and are publicly readable through the administration read endpoint; the form says so before you sign.

Creating a market is a separate act, done from an approved template by anyone the template allows, and it does not reference a proposal. See Create from a template. A new template needs governance and a fourteen-day public notice. See Template permissions and notice periods.

The on-chain market request#

Separately from the form, the registry contract carries a market request petition: anyone can put the hash of a proposed question for the curated calendar template on chain, a seven-day notice starts, and accounts with locked RINO can back or oppose it in public with the same weights and caps as a token-listing petition. A curator who acts on such a request creates a market whose subject anyone can check against what was asked for. Backing is a signal that cannot bind. See Token-listing petitions.

Duplicate questions#

The form rejects an existing proposal with the same title, source URL and rules. Changing the author or category does not create a new question; differences in title capitalization and text whitespace are ignored. This is a text comparison, not a guarantee that differently worded questions are distinct.

The factory separately rejects a market with the same template, canonical parameters and cutoff. Proposals are not yet linked to that on-chain identity, so equivalence with already deployed markets still needs review.