Escrow and Settlement Policy
1. PURPOSE AND LEGAL CHARACTERIZATION
---------------------------------------
1.1 Limited Operational Custody. Plucasa operates a platform-controlled
escrow mechanism for the sole purpose of conditional transactional
settlement between Users. Digital Assets are temporarily held in a
Platform-controlled Escrow Wallet strictly to facilitate outcome-based
conditional release or refund.
1.2 No Fiduciary Relationship. Nothing in this Policy creates: (a) a
trust relationship; (b) a fiduciary obligation; (c) a banking
relationship; (d) a deposit-taking arrangement; (e) a payment service
account; (f) an investment custody mandate; or (g) any form of
safeguarded client asset regime.
1.3 No Beneficial Ownership Transfer to Plucasa. Digital Assets
transferred to escrow remain subject to conditional settlement rights
defined by Platform rules. Plucasa’s control of the Escrow Wallet is
administrative and operational only.
--------------------------------
2. SUPPORTED NETWORK AND ASSET
--------------------------------
2.1 The Platform exclusively supports Ethereum (ETH) on the Arbitrum One
network.
2.2 Transfers sent on any unsupported network, bridge, layer, or token
standard are not recognized and may be permanently unrecoverable.
2.3 Users bear sole responsibility for: (a) verifying the destination
address; (b) verifying network selection; (c) ensuring sufficient gas;
(d) confirming transaction broadcast integrity.
2.4 Blockchain transactions are irreversible once confirmed.
------------------------------------
3. ESCROW WALLET CONTROL FRAMEWORK
------------------------------------
3.1 Escrow Wallet Structure. Escrowed Digital Assets are held in one or
more blockchain addresses controlled by Plucasa or authorized operators.
3.2 Operational Purpose Limitation. Escrowed assets are held exclusively
for: (a) conditional settlement; (b) dispute resolution; (c) fraud
investigation; (d) compliance review; (e) technical correction
procedures.
3.3 Prohibited Use of Escrowed Assets. Escrowed Digital Assets shall not
be: (a) lent; (b) staked; (c) rehypothecated; (d) pledged; (e) invested;
(f) commingled for speculative gain; (g) used for proprietary trading.
3.4 No Interest. No interest, yield, staking reward, or return accrues
to Users during escrow holding.
-----------------------------------
4. CREATION OF ESCROW TRANSACTION
-----------------------------------
4.1 An Escrow Transaction is deemed created only when: (a) Buyer
confirms purchase via Platform interface; (b) ETH is transmitted to the
designated Escrow Wallet; (c) Required blockchain confirmation threshold
is met; (d) Internal risk validation procedures are satisfied.
4.2 Prior to confirmation, no settlement obligation arises.
4.3 Plucasa may refuse recognition of escrow funding where: (a)
suspicious patterns are detected; (b) sanctions risk is present; (c)
transaction anomalies arise; (d) technical inconsistencies occur.
-------------------------------
5. CONDITIONAL HOLDING PERIOD
-------------------------------
5.1 Escrowed Digital Assets remain locked until one of the following
occurs: (a) automatic release; (b) voluntary refund; (c) administrative
determination; (d) compliance hold; (e) technical investigation.
5.2 Holding duration is operationally determined and may extend beyond
displayed windows where necessary to preserve Platform integrity.
-------------------------
6. AUTOMATIC SETTLEMENT
-------------------------
6.1 If no dispute is initiated within the Platform-defined Dispute
Window, escrow may automatically release to the Predictor.
6.2 Automatic settlement is subject to: (a) fraud detection systems; (b)
sanctions screening; (c) anomaly detection protocols; (d) manual
override authority.
6.3 Settlement execution is performed via blockchain transaction
initiated by Platform-controlled infrastructure.
--------------------
7. DISPUTE PROCESS
--------------------
7.1 Buyer Dispute Initiation. Buyers may initiate disputes strictly
within the displayed Dispute Window.
7.2 Upon Dispute Initiation: (a) escrow locks; (b) automatic release
pauses; (c) Predictor receives electronic notice.
7.3 Predictor Response. Predictor may issue voluntary refund within
response window.
7.4 Administrative Review Trigger. Failure to refund within response
window triggers mandatory administrative review.
---------------------------------
8. ADMINISTRATIVE DETERMINATION
---------------------------------
8.1 Review Scope. Review is strictly limited to objective comparison
between: (a) Prediction’s stated criteria at time of purchase; and (b)
Official event outcome from recognized sources.
8.2 Binary Outcome. Administrator shall determine either: (a) Release to
Predictor; or (b) Refund to Buyer.
8.3 Finality. Administrative determinations are final and binding within
the Platform, subject only to correction of manifest clerical or
technical error.
8.4 No Judicial Standard. Administrative review is contractual and not
equivalent to judicial arbitration or regulatory adjudication.
-------------------------------
9. DISPUTE ADMINISTRATION FEE
-------------------------------
9.1 Where administrative adjudication occurs, the unsuccessful party
incurs a €10 administrative processing fee.
9.2 The fee reflects dispute handling cost and does not constitute a
penalty or wagering consideration.
9.3 The fee may be deducted from escrow, applied against balances, or
recorded as payable liability.
-------------------------------------------
10. FRAUD, INTEGRITY AND COMPLIANCE HOLDS
-------------------------------------------
10.1 Plucasa may freeze, delay, or refuse settlement where reasonably
necessary to: (a) investigate suspected fraud; (b) enforce Platform
rules; (c) conduct AML/CTF review; (d) comply with sanctions screening;
(e) respond to legal process; (f) mitigate systemic or operational risk.
10.2 Holds may extend beyond displayed timelines.
10.3 Plucasa may request additional documentation.
10.4 Plucasa is not liable for losses arising from good-faith compliance
holds.
----------------------------------
11. FAILED OR DELAYED SETTLEMENT
----------------------------------
11.1 Settlement transactions may fail due to: (a) network congestion;
(b) gas insufficiency; (c) infrastructure malfunction; (d) blockchain
reorganization; (e) third-party infrastructure outage.
11.2 Plucasa may reattempt settlement or apply corrective measures.
11.3 No guarantee is made regarding settlement timing.
---------------------
12. IRREVERSIBILITY
---------------------
12.1 Completed blockchain settlements cannot be reversed except pursuant
to binding legal order.
12.2 Users waive claims relating to irreversible blockchain mechanics.
---------------------------------------
13. SECURITY AND RISK ACKNOWLEDGEMENT
---------------------------------------
13.1 Plucasa implements commercially reasonable safeguards.
13.2 No custody system is immune from compromise.
13.3 Users accept residual custody risk inherent in blockchain systems.
----------------------------
14. INSOLVENCY POSITIONING
----------------------------
14.1 Escrowed assets are held solely for transactional settlement
purposes.
14.2 This Policy does not create statutory client asset segregation.
14.3 Users acknowledge digital asset treatment in insolvency may depend
on applicable law.
-----------------------------
15. LIMITATION OF LIABILITY
-----------------------------
15.1 To the maximum extent permitted by law, Plucasa shall not be liable
for indirect, incidental, consequential, or punitive damages relating to
escrow or settlement.
15.2 Aggregate liability per Escrow Transaction shall not exceed the
Platform Fee paid for that transaction.
----------------------
16. POLICY AMENDMENT
----------------------
16.1 Plucasa may amend this Policy at any time.
16.2 Continued use of the Platform constitutes acceptance of amendments.
CONTACT legal@plucasa.com support@plucasa.com