Record the contribution
Bind a submitted signal to its source and receipt instead of reconstructing participation after an outcome.
Strategy PoolsStrategy participation.
Strategy participation.
Show how a contribution was used.
Help strategy operators answer who contributed an input, when it was considered, and what can be reviewed after disclosure. Preserve participant attribution while respecting the rules that protect a strategy before its reveal.
Evaluation required · Check the exact operation and deployment.
Decision timelineWhat was committed before disclosure?
- Commitment
- Controlled disclosure
- Attribution review
A familiar challenge
A team wants to evaluate a strategy's history without disclosing its live decisions to everyone.
A more useful way forward
Review commitments and permitted disclosures in sequence. A proof of attribution is not a promise of performance.
See a practical example ↓Why it matters
Give contributors a reviewable participation history.
For strategy operators and quantitative platform teams.
Control disclosure
Understand what remains sealed during a strategy lifecycle and which evidence becomes available later.
Review the allocation
Connect disclosed decisions and configured contribution rules to their retained outcome records.
Core capabilities
The capabilities behind the outcome.
Match these capabilities to your workflow. Enabled operations and access are confirmed during integration planning.
Signal attribution
Associate an admitted contribution with its source and receipt.
Decision commitments
Retain consideration and relevant execution commitments under the supported workflow.
Controlled disclosure
Separate sealed information from the evidence available after the required lifecycle transition.
Allocation review
Inspect disclosed contribution rules and outcome records without treating receipt as a payout guarantee.
Public records illustrate inspectable data; they are not customer results or confirmation of production activation.
How Strategy Pools works
Contribution first. Disclosure under defined rules.
- 01
Receive attributable signals
Capture submitted inputs and participant context under the supported ingestion policy.
- 02
Retain decision commitments
Record consideration and the relevant execution commitments while applying the configured disclosure boundary.
- 03
Reveal and review
After the required lifecycle transition, inspect the permitted reveal, contribution allocation, and outcome evidence.
A practical example · illustrative
A contributor asks how a signal was used.
A strategy operator needs to explain participation without exposing a live strategy before its disclosure conditions are met.
- Receipt
- Confirm the input was received and associated with its source.
- Boundary
- Respect the configured distinction between a commitment and a public reveal.
- Review
- After disclosure, follow the available decision and allocation evidence.
What the team takes away
A participation trail that can be reviewed without presenting illustrative returns as a track record.
Evaluation required
Plan your first deployment.
Confirm the currently supported strategy workflow, disclosure rules, and settlement operations. Examples do not establish available investment products, live liquidity, expected returns, or enabled payouts.
Before your first integration
- Confirm supported ingestion, commitment, and disclosure operations.
- Define who may inspect each stage and when reveal is permitted.
- Review allocation and any enabled settlement independently of performance claims.
Questions before you buildPrivate while active.
PUBLIC / SUBJECT-VERIFIABLE✓ OPENING COMMITMENT✓ CIPHERTEXT HASH✓ OPENED AT✓ PROOF STATE REMAINS PROTECTED× MARKET× DIRECTION× ENTRY× SIZE× VENUE From a considered signal
ILLUSTRATIVE PROFIT ALLOCATIONSETTLED POOL RESULT+ 9,240.00 USDCDISCLOSED EXECUTION · VERIFIED One partner.
01 · LIVE 02 · LIVE 03 · REGISTERED Registration is part
01POOL IDENTITY 02SIGNED INGESTION 03DISCLOSURE POLICY 04PERFORMANCE BOUNDARY Observe first.
Reward insight.
01CROWDSOURCED ALPHA 02AI STRATEGY OPERATORS 03COPY & RESEARCH NETWORKS 04PERFORMANCE PROGRAMS 05PARTNER DISTRIBUTION 06FUTURE STAKED LIQUIDITY
Strategy Pools, explained.
Does a recorded signal guarantee a reward?
No. Receipt, consideration, execution, allocation, and payout are separate stages. Applicable rules and enabled operations determine what follows.
Are the example returns real performance data?
No. Walkthrough allocations and returns are illustrative. They are not verified results or a basis for predicting future performance.
What should we agree before starting a pilot?
Use the product-specific checklist above to define scope and acceptance tests. Ask the team to confirm the deployment environment, access, supported operations, integration responsibilities, support arrangements, and commercial terms. Availability labels are not a pricing quote or a service-level commitment.
Explore the technical architecture and walkthroughs
Optional deeper reading. Demonstrations are illustrative, not live operational status or a promise of activation. Use the availability guidance above and the current API contract for integration decisions.
PARTNER SIGNEDSIGNAL RECEIPT RETAINEDLIVE POSITION SEALEDPOST-CLOSE REPLAYREWARD EVIDENCE
EXPLORE THE PROOF CHAIN
Private while active.
Replayable after close.
Inspect how the public boundary changes across one illustrative execution. The system exposes enough to prove timing and integrity at every stage without disclosing a live strategy prematurely.
ILLUSTRATIVE STRATEGY EVIDENCEMOMENTUM CONSENSUS · HYBRID-DEMO
PROOF CHAIN INTACTSEALED · INTACT
The live trade stays private.
Core publishes an opening commitment and encrypted payload hash. Market, direction, size, venue, and entry remain concealed while the strategy is active.
execution · 66bad671…aaa8DETERMINISTIC ATTRIBUTION
From a considered signal
to a settled reward.
Hybrid-Chain does not decide why a strategy trusted a participant. It proves what the operator reported: which committed signals were considered, the allocation assigned after the outcome, the resulting reward, and the vault that received settlement evidence.
Inspect execution proofsPARTICIPANT 017112 BPS103.49 USDC
PARTICIPANT 04286 BPS79.46 USDC
PARTICIPANT 10861 BPS56.36 USDC
MULTI-POOL OPERATING MODEL
One partner.
Many strategy identities.
A registered operator can run multiple pools for different models, asset universes, risk policies, or participant groups. Every event selects a canonical strategy code and remains inside that pool’s evidence and performance context.
Momentum Consensus
Broad-market directional signals with close-only disclosure.
- EXECUTIONS
- 184
- DISCLOSED
- 177
Digital Asset Breakouts
Currency-scoped pool using independently registered strategy context.
- EXECUTIONS
- 62
- DISCLOSED
- 58
Volatility Reversal
A separate model ready for its first partner-signed contribution.
- EXECUTIONS
- 0
- DISCLOSED
- 0
CREATE CREDENTIALS · REGISTER POOLS · SELECT STRATEGY CODE · MONITOR DELIVERYOpen partner registry
OPERATING CONTROLS
Registration is part
of the proof boundary.
A strategy is not an informal label. It is a managed context with a stable identity, admitted source credentials, explicit privacy policy, and measurable delivery state.
Every strategy receives a permanent public UUID, partner source, strategy code, disclosure policy, and operating state.
Partner credentials bind signals and lifecycle events to an admitted source with timestamp and replay protection.
A pool can state when protected execution data becomes public, while commitments exist from the moment of opening.
Public metrics use disclosed outcomes only. Active sealed positions cannot silently influence a published result.
THE NEXT CAPITAL LAYER
Observe first.
Stake only with proof.
Today’s evidence model proves contribution, execution disclosure, allocation, and reward settlement. Native capital participation comes next: MPC wallets fund a pool through reserve-backed Hybrid Settlement, balances remain attributable, and withdrawal requires the same cryptographic authority and Layer-2 burn discipline.
MPC WALLET AUTHORITYRESERVE-BACKED FUNDINGPOOL SHARE EVIDENCEPROVABLE REDEMPTION
BUSINESS APPLICATIONS
Reward insight.
Protect the strategy.
Prove participation before revealing a live strategy. Start with contribution evidence and add capital participation only when the wallet, reserve, and settlement model is ready.
Record paper-trading contributions, model consideration, and resulting reward allocations without revealing live market intent.
Give each model a registered strategy context, signed ingestion credentials, disclosure policy, and public performance record.
Prove that ideas were delivered and considered before an outcome—without forcing the operator to expose proprietary logic.
Turn disclosed results and deterministic allocation records into transparent competitions, rankings, and contributor rewards.
Let multiple partners register distinct pools and route signed events by strategy code through one evidence standard.
Extend proven strategy performance into MPC-funded participation only after custody, reserve, and settlement gates are active.
PERFORMANCE & PARTICIPATION NOTICE
Published performance includes disclosed outcomes only and is not a promise of future results. Sealed positions do not expose live trading details. Strategy Pools evidence does not constitute investment advice, and capital staking remains unavailable until the applicable MPC wallet, funding, custody, reserve, governance, and regulatory controls are active.
Start with one useful result
Discuss your deployment Make it work for your team.
Bring your workflow. We’ll help identify the scope, access, and acceptance checks for a practical pilot.
Build the next part of your workflow
Connected products.
Start with Strategy Pools. Review these adjacent capabilities when your requirements call for them.
Verifiable Pricing Feeds
Understand the sources and policy behind a published price.
Explore Verifiable Pricing FeedsFunding & Settlement
Connect external funding observations to a controlled settlement workflow.
Explore Funding & SettlementAutomation Studio
Connect platform events to controlled, retry-safe business actions.
Explore Automation Studio