> ## Documentation Index
> Fetch the complete documentation index at: https://docs.justly.one/llms.txt
> Use this file to discover all available pages before exploring further.

# Frequently Asked Questions

> This page answers common questions about Justly, how it works, and what guarantees it provides.

This page answers common questions about Justly, how it works, and what guarantees it provides.

Everything you need to know about Justly. If you have more questions, join the Justly community on Telegram: [Official links](https://t.me/justlycommunity).

### General

<details>
  <summary>Can you really trust a decision made by anonymous jurors?</summary>

  Justly 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.
</details>

<details>
  <summary>Is Justly a court or a legal arbitrator?</summary>

  No. Justly 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*)
</details>

<details>
  <summary>What kinds of disputes is Justly built for?</summary>

  The current version of Justly is optimized for **adversarial disputes** in digital platforms, where:

  * disputes are frequent,
  * amounts are not large enough for traditional legal processes,
  * and fast resolution matters.

  Examples include marketplaces, freelancer platforms, and fintech or payment conflicts.

  Governance validation and quality evaluation are planned for later versions, not the current implementation.

  (See: *Use Cases*)
</details>

<details>
  <summary>Is Justly only for Stellar?</summary>

  No. Justly is designed to be **chain-agnostic**, although it may prioritize specific ecosystems depending on adoption and integration demand.
</details>

### How Justly Works

<details>
  <summary>What is a Tier?</summary>

  A tier is the **public-facing dispute profile** exposed to platforms and integrators.

  It packages values such as:

  * number of jurors,
  * juror stake levels,
  * and the arbitration fee amounts required for each side of the dispute.

  Higher tiers increase the cost of manipulation by combining:

  * more jurors,
  * higher stakes,
  * and higher total attack cost.

  (See: *What is a Tier*)
</details>

<details>
  <summary>How long does a dispute take?</summary>

  Resolution time depends on:

  * the selected tier,
  * the evidence and voting windows,
  * and actual juror participation.

  Justly is designed to keep dispute resolution **predictable and bounded**, prioritizing liveness and completion.

  (See: *Dispute Lifecycle*)
</details>

<details>
  <summary>What happens after the dispute is resolved?</summary>

  Once the dispute is finalized, the outcome is enforced at the protocol level:

  * the ruling is stored,
  * juror incentives are settled programmatically,
  * and the final state becomes publicly verifiable.

  If the integration uses a callback, Justly may attempt it after finalization. Callback failure does not invalidate the ruling.
</details>

### Jurors

<details>
  <summary>Are jurors anonymous?</summary>

  Jurors are pseudonymous participants from the perspective of the disputing parties.

  This helps preserve neutrality while allowing jurors to participate economically through staking.
</details>

<details>
  <summary>Can parties be jurors in their own dispute?</summary>

  No. Parties cannot serve as jurors in disputes where they have a direct interest.

  This avoids conflicts of interest and preserves neutrality.
</details>

<details>
  <summary>What if jurors don't vote or go inactive?</summary>

  Jurors are expected to participate within defined time windows.

  Non-participation after selection is treated as incoherence and can result in protocol-defined penalties.
</details>

### Security & Incentives

<details>
  <summary>Can someone "whale" attack Justly by staking a lot?</summary>

  Stakes affect:

  * economic exposure,
  * selection economics,
  * and rewards or penalties.

  Large stakes increase financial exposure, but do not create special control over the final ruling.

  (See: *Security Model*)
</details>

<details>
  <summary>Can someone bribe jurors?</summary>

  Bribery is made harder by:

  * randomized assignment,
  * pseudonymity,
  * and incentive alignment.

  Because jurors are not known in advance, targeted bribery becomes harder, and dishonest coordination is economically risky.

  (See: *Security Model*)
</details>

<details>
  <summary>What prevents sybil attacks?</summary>

  Justly mitigates manipulation through:

  * staking requirements,
  * randomized juror assignment,
  * and economic penalties for incoherent participation.

  (See: *Security Model*)
</details>

<details>
  <summary>Can Justly be fully trustless if operational tooling is used?</summary>

  Yes. Operational tooling can help trigger actions or improve UX, but it does not determine rulings.

  The protocol guarantees remain the same:

  * juror voting determines the ruling,
  * state transitions and settlements are enforced by smart contracts,
  * and callback failure does not affect finality.

  (See: *Security Model*)
</details>

### Appeals

<details>
  <summary>Does Justly support appeals?</summary>

  Not in the current implementation.

  Appeals are planned for a later version.
</details>

<details>
  <summary>How are appeals funded?</summary>

  The final funding model for appeals belongs to a later version and is not part of the current implementation.
</details>

### Integrations

<details>
  <summary>Do users need to hold a specific token to use Justly?</summary>

  No. Regular users, such as the claimer and defender, do not need to hold a protocol token.

  Justly is designed to work with standard assets, such as stablecoins, used for dispute funding and juror stakes.
</details>

<details>
  <summary>Do I need the SDK to integrate Justly?</summary>

  Not necessarily. Justly can be integrated through direct contract interaction and integration guidelines.

  The SDK is useful because it can expose tiers and integration flows in a simpler format, but it is not strictly required.

  (See: *Current Implementation*)
</details>

<details>
  <summary>How does an integration receive the ruling?</summary>

  An integrating protocol can consume the ruling in two ways:

  * by reading the final ruling directly,
  * or through an optional callback flow.

  Callback success is not required for finality.
</details>

<details>
  <summary>Who is responsible for compliance when integrating Justly?</summary>

  Compliance depends on the integrating platform, jurisdiction, and transaction type.

  Justly is neutral infrastructure and can be combined with identity, KYC, or AML solutions when required.

  (See: *Legal & Compliance Considerations*)
</details>

### Legal & Responsibility

<details>
  <summary>Who is responsible if a verdict causes economic loss?</summary>

  Justly 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 Justly is appropriate for their use case and risk tolerance.

  (See: *Legal & Compliance Considerations*)
</details>

<details>
  <summary>Are Justly rulings legally binding?</summary>

  Justly outcomes are **programmatically binding** because parties opt into on-chain enforcement.

  They are not court rulings and do not automatically constitute legal judgments unless an integrator explicitly frames them within a legal agreement at the application layer.
</details>