Loading from chain
Hardware production is financed against output rather than equity. Capital is held in escrow and released tranche by tranche, each one gated on production evidence that claim holders approve.
Commitments go into MilestoneEscrow. A founder cannot withdraw undisbursed funds.
Each tranche unlocks only after the founder publishes production evidence.
Claim holders vote to approve or reject. Weight is snapshotted at submission.
Positions trade on the secondary market rather than locking until delivery.
Four stages from a hardware concept to released capital, each one enforced by the contracts rather than by trust.
A founder publishes the product, bill of materials, target raise and manufacturing plan, then defines the escrow milestone schedule.
Capital is committed and custodied in MilestoneEscrow. Tranche amounts are set by the founder up front and must sum exactly to the funding target, so every unit of capital has an assigned release condition.
At each milestone the founder submits production evidence to IPFS. Vote weight is snapshotted at submission, and claim holders approve or reject within the review window. A protocol oracle can escalate a disputed milestone.
An approved milestone releases its tranche to the founder. Claims remain tradeable throughout on the secondary market, so holders are not locked in until delivery.
Record the bill of materials, target unit economics, supplier lead times and the production plan. This becomes the public project record.
Choose a claim price and supply, then split the raise into tranches. Each tranche is bound to a milestone whose evidence claim holders will review.
Once the schedule is set, funding opens. Committed capital goes to MilestoneEscrow, not to the founder, and claims mint to each backer on commit.
At each milestone, publish the production evidence. If claim holders approve within the review window, that tranche releases to you.
Each layer has one job. Records live in the registry, money lives in escrow, claims live in the token, and trading lives in the market.
ProjectRegistry holds the project record, the raise structure and the milestone schedule. It is the source of truth for status.
MilestoneEscrow holds committed capital and releases it one tranche at a time against approved evidence. Founders never take custody of undisbursed funds.
ClaimToken issues ERC-1155 units per project, so a single approval covers a portfolio and transfers stay cheap. Transfers can be frozen during disputes.
SecondaryMarket settles peer-to-peer listings. Sellers escrow their claims into the market, so a listing can never be unfillable.
The differences below are structural: who holds the money, who can exit, and who decides when capital is released. No return is implied or projected.
| Feature / Parameter | ProtoRWA Hardware Claims | Crowdfunding | Venture Equity | Debt / RBF |
|---|---|---|---|---|
| Cap table dilution | None. Claims sit outside the cap table. | None, but no claim on output either. | 20-35% per round. | None, but a fixed repayment obligation. |
| Who holds the capital | MilestoneEscrow until each tranche is approved. | The creator, on campaign close. | The company. | The company, against future receipts. |
| Release control | Claim-holder vote per milestone. | None. No mechanism to withhold funds. | Board and investor governance. | Covenant and payment schedule. |
| Exit before delivery | Secondary market for claims, at any time. | Not possible. | Illiquid until IPO or acquisition. | Secondary loan trading, where available. |
| What backs the position | Escrowed capital plus a claim on produced units. | A promise of a reward. | Company shares. | A contractual repayment claim. |
| Evidence of progress | Founder-submitted artefacts, hash-addressed and holder-reviewed. | Campaign updates, unverified. | Board reporting. | Periodic financial statements. |
Every rule described here is enforced in Solidity. The test suite covers the full lifecycle including rejected milestones, failed quorum, refunds after a cancelled raise, and frozen transfers during a dispute.
Read the FAQ and risk disclosure