A shared compute concept
Fund the
hardware.
Share the
revenue.
Buy compute hardware together. Receive tokens for its net revenue. Trade your tokens or redeem your share of the vault.
Explore the proposed modelDashed line: token claims, not a cash transfer.
Concept presentation. No active presale. No real tokens. No investment offer.
01Fund a batch
→02Put it to work
→03Deposit net revenue
→04Redeem a share
The proposed model
One batch.
A clear path
to the vault.
RigShare connects a defined hardware batch to its own tokens and vault. Each batch stays separate from the next.
This is a design to explore, not a service that operates today.
Pool funds for a defined batch
A presale would collect funds for a specific hardware batch. Its scope, budget, and participant rights need definition before any sale.
Buy the hardware. Install it.
The operator would buy and install the batch. Physical equipment needs power, a network connection, maintenance, and an operator.
Define each token's claim
The batch would issue a fixed supply of tokens. Each token represents a defined claim on that batch's net revenue.
Burns reduce the supply. Later presales use separate batches, tokens, and vaults.
Seek better net revenue
A proposed allocation system compares eligible compute work. It seeks higher net revenue, not just the highest advertised rate.
It would switch available hardware between eligible providers when expected net revenue improves and existing jobs permit.
Demand, costs, and hardware compatibility constrain each choice.
Vast.aiSaladAkashExamples only. No confirmed integrations or partnerships.
Pay costs before the deposit
Power, platform fees, maintenance, and operating reserves come out first. Only net revenue enters the batch vault.
These costs never come out of the vault in this model.
Let participants trade their claims
A proposed market would support purchases, sales, long positions, and short positions. A market price can differ from the vault redemption value.
See the market requirementsBurn tokens to redeem a share
A holder destroys tokens to receive their proportional share of the vault. Those tokens no longer carry claims on future revenue.
Only proportional token burns remove money from the vault.
The vault rule
A smaller supply.
The same value per token.
A proportional burn removes the same fraction of the vault and the token supply. The remaining tokens keep the same redemption value.
Payment for a burn
b × V / S
- b
- Tokens you burn
- V
- Vault balance before the burn
- S
- Outstanding supply before the burn
What changes after a burn?
New vault balance: V − b × V / S
New token supply: S − b
While tokens remain:
(V − b × V / S) / (S − b) = V / S
This equality applies when 0 < b < S. A burn of the full supply redeems the full vault and leaves no tokens.
| What happens | Vault balance | Token supply | Value per token |
|---|---|---|---|
| Start with accumulated net revenue | $1,000 | 1,000 | $1.00 |
| Burn 100 tokensThe holder receives $100. | $900 | 900 | $1.00 |
| Deposit $180 of net revenue | $1,080 | 900 | $1.20 |
New net revenue increases the redemption value per token. A proportional burn does not. Costs come out before a deposit; only burns remove vault funds.
The value is in the vault asset. It is not the market price or a promise to recover the original purchase price. The rule does not guarantee a return or remove custody and legal risks.
The proposed market
Two prices.
Different decisions.
The vault redemption value is a calculation. The market price is what a buyer and seller agree. They need not match.
Buy, hold, or sell
A long position means you buy and hold tokens because you expect the market price to rise.
You could sell to another participant, if a buyer exists. Or you could burn tokens for their share of the vault.
A price fall can cause a loss. Neither a buyer nor a market price is guaranteed.
Borrow, sell, and return
A short position means you borrow tokens, sell them, and later buy tokens to return. You expect the market price to fall.
If the price rises, the tokens cost more to repurchase. Losses can be large and can exceed the initial collateral.
Short positions require available tokens to borrow and clear collateral rules.
A few important questions
The details
still matter.
A clear model is a start.
A real launch needs more.
What does a token actually entitle me to?
The concept proposes a defined claim on one hardware batch's net revenue. It does not establish legal ownership of the hardware.
The exact token rights, legal structure, operator duties, and enforcement process need definition before a real launch.
Does a growing vault guarantee a return?
No. New net revenue increases the redemption value in the vault asset. It does not guarantee that hardware earns revenue.
The purchase price may exceed the redemption value. Demand can fall, and costs can rise. The vault asset can also lose value.
Equipment failure can reduce future revenue. It does not subtract existing vault funds under this model.
Can the operator use the vault for repairs?
No, not in this proposed model. Maintenance, other costs, and operating reserves come out before the operator deposits net revenue.
Only proportional burns remove money from the vault. A real launch needs explicit rules for insufficient reserves and unexpected costs.
Are the compute marketplaces connected?
No integrations or partnerships are confirmed. Vast.ai, Salad, and Akash are examples of marketplaces the proposed system could compare.
Each option needs a review of hardware compatibility, provider terms, demand, fees, and job commitments.
Who holds the hardware and the vault assets?
The concept assigns hardware operations to an operator. The custody arrangements for hardware, tokens, and vault assets need definition.
The mathematical rule does not protect against theft, operator failure, custody failure, or legal disputes.
Can I participate now?
No. This page explains a concept. There is no active presale, no real token, and no investment offer.
No hardware availability or launch date is promised.