Frequently Asked Questions
This page answers common questions about Slice, how it works, and what guarantees it provides.
Everything you need to know about Slice. If you happen to have any other questions, feel free to join our Slice Community Telegram group to talk directly you our team. Please check out Official links.
General
Can you really trust a decision made by anonymous jurors?
Slice extends the same incentive logic used in cryptoeconomic systems to human judgment.
Jurors are:
independent,
randomly assigned,
and economically incentivized to vote coherently.
Because outcomes affect real value, the system is designed so that dishonest or low-effort behavior is costly, while coherent behavior is rewarded.
Is Slice a court or a legal arbitrator?
No. Slice is neutral dispute resolution infrastructure.
It is not a court and does not provide legal advice. It enforces outcomes based on protocol rules and smart contract execution.
(See: Legal & Compliance Considerations)
What kinds of disputes is Slice built for?
Slice is optimized for micro-to-medium disputes in digital platforms, where:
disputes are frequent,
amounts are not large enough for traditional legal processes,
and fast resolution matters.
Examples include marketplaces, freelance platforms, fintech/payment conflicts, governance validation, and quality evaluation.
(See: Use Cases)
Is Slice only for Stellar?
No. Slice is designed to be chain-agnostic, although it may prioritize specific ecosystems depending on adoption and integration demand.
How Slice Works
What is a Tier?
A tier defines the security level and economic parameters of a dispute: number of jurors, required stakes, and overall robustness.
Higher tiers increase the cost of manipulation by combining:
more jurors,
higher stakes,
higher total cost to attack.
(See: What is a Tier)
How long does a dispute take?
Resolution time depends on:
tier (number of jurors),
evidence/voting windows,
and juror availability.
Slice is designed to keep dispute resolution predictable and reliable, prioritizing liveness and completion.
(See: Dispute Lifecycle)
What happens after the dispute is resolved?
Once the dispute is resolved, the outcome is executed automatically on-chain:
funds are redistributed according to the ruling,
juror incentives are settled programmatically,
and the final state becomes publicly verifiable.
Jurors
Are jurors anonymous?
Jurors are pseudonymous participants, but Slice can require Proof-of-Humanity (PoH) to prevent sybil attacks.
This means jurors can remain private while still proving they are unique humans.
Why require Proof-of-Humanity (PoH)?
Without PoH, a malicious actor could create many identities and try to influence outcomes.
PoH increases security by ensuring:
one human = one juror identity,
and the economic cost to manipulate results becomes substantially higher.
Can parties be jurors in their own dispute?
No. Parties cannot serve as jurors in disputes where they have a direct interest.
This avoids conflicts of interest and preserves neutrality.
What if jurors don’t vote or go inactive?
Jurors are expected to participate within defined time windows.
Non-participation can result in:
losing the chance to earn rewards,
and protocol-defined penalties depending on the rules of the dispute.
Security & Incentives
Can someone “whale” attack Slice by staking a lot?
Slice is designed so that stake does not grant voting power.
Each juror has exactly one vote, regardless of stake size.
Stakes affect:
economic exposure,
and rewards/penalties, not voting weight.
(See: Security Model)
Can someone bribe jurors?
Bribery is made difficult by:
randomized assignment,
pseudonymity,
and incentive alignment (jurors who vote incoherently are penalized).
Because jurors are not known in advance, targeted bribery becomes harder, and dishonest coordination is economically risky.
(See: Security Model)
What prevents sybil attacks?
Slice mitigates sybil attacks through:
Proof-of-Humanity (PoH) eligibility,
randomized juror assignment,
and economic penalties for incoherent voting.
(See: Security Model)
Can Slice be fully trustless if matchmaking uses a backend?
Slice can use backend-assisted matchmaking to ensure disputes reach the required number of jurors and resolve reliably.
The backend:
coordinates assignment and timing,
but cannot influence votes, outcomes, or fund execution.
All rulings and transfers are enforced by smart contracts.
In the long-term, Slice can support multiple modes such as “Turbo” (assisted) and “Pure Randomness” (fully on-chain randomness).
(See: Security Model)
Appeals
Does Slice support appeals?
Appeals are part of Slice’s protocol design and may be enabled depending on dispute type and implementation phase.
In adversarial disputes, appeal rounds can be opened under stricter conditions to increase robustness and security.
How are appeals funded?
In adversarial disputes, Slice follows a funding model where:
the appellant pays the cost to open a new round,
while the non-appellant may optionally “match” to preserve upside.
This discourages frivolous appeals while keeping escalation possible when needed.
(See: Adversarial Dispute)
Integrations
Do users need to hold a specific token to use Slice?
No. Regular users (claimer/defender) do not need to hold a protocol token.
Slice is designed to work with standard assets (e.g., stablecoins) used for stakes and payouts.
Do I need the SDK to integrate Slice?
Not necessarily. Slice can be integrated through direct contract interaction and integration guidelines.
The SDK is planned to simplify and standardize integrations over time.
(See: Integrate)
Who is responsible for compliance when integrating Slice?
Compliance depends on the integrating platform, jurisdiction, and transaction type.
Slice is neutral infrastructure and can be combined with identity/KYC/AML solutions when required.
(See: Legal & Compliance Considerations)
Legal & Responsibility
Who is responsible if a verdict causes economic loss?
Slice is provided “as-is”.
Outcomes result from:
independent human judgment,
and protocol-defined rules executed on-chain.
Users and integrators are responsible for determining whether Slice is appropriate for their use case and risk tolerance.
(See: Legal & Compliance Considerations)
Last updated