Infrastructure micro-pools. Mining rewards are split by the work each rig actually did, approved by the partners with their multisig, and the chain checks that the books balance before a single wei moves.
The parameters that define the business. Changing them recalculates the payout instantly.
The fund cap is 50%: the contract rejects any setting above it, so a misconfigured reserve can never leave the partners with nothing in a "valid" way.
What each partner contributes. It determines their weight and their power use.
Demo data, editable here. In production it would come from the mining software's API.
Turning a rig off is the case that breaks any spreadsheet: that partner contributes less, but also doesn't pay for the power they didn't use.
How the gross is split, in the order the obligations are served.
| Partner | Contribution | Owed |
|---|---|---|
| 0x9230...7CA5 | 66.66% | 0.001921 |
| 0x937B...07a6 | 33.33% | 0.00096 |
How much USDC each partner ends up with if their share goes through HashKey Exchange. This card only quotes: it sends nothing. Real orders are placed with npm run hashkey from your machine.
The route is read from HashKey Exchange. Without a connection to it, it is not shown.
| Partner | In (HSK) | Gross USDC | Fees | Left in USDC |
|---|---|---|---|---|
| 0x9230...7CA5 | 6666.66666666 | 653.333333 | 1.894766 | 651.438567 |
| 0x937B...07a6 | 3333.33333333 | 326.666666 | 0.947433 | 325.719233 |
What the partners approve with the multisig. It is not a summary of the payout: these are the exact bytes executed on-chain.
With this hash any partner takes the period's raw JSON, recomputes the payout and checks they were paid what they were owed. Nobody has to trust the server that did the math.
Partners approve the payout by signing with their own wallet. None of them can settle alone.
Read from the contract's events via Blockscout. There is no server of our own storing this: if this screen disappeared, the same numbers would still be on-chain.
No data.