How Syndicate works

One defined campaign finances one service and allocates tokens received by its payment contract.

A campaign is an independent contract. It records backer capital, fixes the operator and terms, and receives payments routed by the service. Backer positions are nontransferable. There is no upgrade administrator, discretionary fee switch or administrator sweep.

Funding and activation

At creation, the operator fixes the funding target, deadline, backer share, service URL, terms hash and any Stock Token bond. Contributions cannot exceed the target. The operator may activate only after the target is reached and before the activation deadline, two days after funding closes.

Activation transfers the full launch budget to the operator to spend. It is not a repayable deposit, and activation does not prove that the service is useful. If the target is missed or activation expires, the campaign can be marked failed and each backer can claim their own refund. After activation there is no unilateral capital exit or service-performance dispute resolver.

Read the operator's published terms and compare their exact text with the onchain hash before funding. A matching hash proves text identity, not the truth of a commercial claim.

Receipt accounting

A paid x402 service must use its campaign contract as the payment recipient. Only tokens actually received by that contract can be allocated. The contract cannot inspect HTTP calls, customers or offchain costs. Direct token transfers also count as receipts, so totals alone do not prove customer demand.

The operator receives the remainder and pays operating costs from its budget and receipts. Gross receipts are not net profit. There is no guaranteed receipt period, income, repayment or minimum return.

Optional Stock Token bond

An operator can escrow a supported Stock Token at campaign creation. The raw amount is public; there is no oracle-based dollar valuation.

• If the funding target is missed, the bond returns to the operator.
• If the target is reached but activation is missed, backers may claim the bond pro rata.
• After activation, the bond remains locked for the stated period, then returns to the operator.

Poor service, downtime and low receipts do not automatically slash it. The bond is not principal insurance. Its value and transferability may change, and issuer restrictions or corporate actions may affect it.

Operator responsibilities

The operator must run the service, publish accurate terms, route accepted payments to the campaign receiver, pay hosting and model costs, and maintain a durable payment journal. The operator can spend the released launch budget and may route customers elsewhere. The contract cannot force all business revenue through it.

A production service requires its own hosted endpoint, reviewed facilitator and verified settlement flow. A payment timeout after broadcast must be reconciled before retrying. No external facilitator partnership or service-level guarantee is claimed.

Risks

Contracts are unaudited. Backers can lose the entire funding amount. A service may have no demand, exceed its budget, fail to launch or be mismanaged. Payments may be diverted; offchain hosting, RPC or facilitation may fail. Stock Tokens may decline, be frozen or have transfer restrictions. There is no early exit after activation, guaranteed yield, profit or repayment. Legal obligations may apply to revenue sharing; no regulatory approval is claimed.

Contracts and network

Target network: Robinhood Chain public testnet. Wallet network checks remain active.

Factory: 0x38e99f1d77e8c3474530e8abc77181c4da6a0406

Every campaign is a separate deployment with its own address and numeric terms. Any future project token is separate from campaign contracts.