Decot Master FAQ

Decot is a privacy-preserving web app that lets multiple parties draft, negotiate, sign, audit, and even NFT-notarise contracts—anchored on the Sui blockchain while your documents stay encrypted off-chain.

Primarily legal, procurement and sales teams that need airtight audit trails but don’t want to expose sensitive terms on a vendor’s servers—plus tech-savvy SMEs modernising contract ops.

No. Decot custom ZK login hides cryptographic complexity behind a familiar sign-in experience. You can use the platform without managing wallet extensions or seed phrases.

Not yet. Core smart-contract modules remain proprietary (with third-party audits); integration SDKs may be released under permissive licences later.

Front-end and API nodes run in EU & US clouds. Encrypted contract files reside on Walrus—a decentralised object-storage network distributed across multiple operators—so a single data-centre outage can’t bring you down.

Use the 3-step onboarding flow: choose login method, complete secure ZK verification, and enter your workspace.

No. Browser wallet extensions are not required for standard onboarding and usage.

Not required for normal use. Decot provisions secure signing identity during onboarding. Advanced enterprise integrations can be reviewed with support.

PDF is recommended for signing. DOCX, ODT, XLSX, PPTX and common image formats are accepted during drafting or as attachments.

Up to 25 MB on Personal/Team and 150 MB on Business/Enterprise by default; larger blobs on request.

It encrypts your document in-browser, stores the ciphertext on Walrus, then mints a Sui “contract object” that points to that file hash.

Yes—owners grant Commenter or Editor rights; each save creates a new hashed version, so you always know who changed what.

Through flexible sequential or parallel steps in the Workflow Builder (e.g. Legal → Finance → CEO → Counter-party).

Status reverts to Rejected; address comments, upload a new encrypted version, and resubmit.

After execution you can mint an ERC-721-style NFT object on Sui containing the final file hash. Only contract-party wallets receive the token—no public exposure.

Yes—if allowed by your governance rules, execute a Terminate transaction; a new immutable state is appended for audit.

AES-256-GCM (256-bit keys) in the browser via WebCrypto; keys are wrapped with SEAL’s threshold encryption and split across multiple Sui validators.

No—encryption keys never touch Decot servers; Walrus ciphertext is undecipherable without them.

Through Decot account recovery using verified identity checks and configured recovery methods.

Every edit/signature requires a wallet signature; even privileged admins can’t silently alter a contract—Sui rejects unsigned transactions.

Yes—independent Move auditors run static analysis and formal verification; reports are shared with Enterprise customers under NDA.

Yes. You can enable TOTP or passkeys for stronger account protection.

Sui’s object model maps one-to-one with contracts, supports parallel execution and keeps gas fees at fractions of a cent.

None. Decot covers on-chain gas and NFT-mint costs for actions performed in the app.

The bytes live off-ledger, but Walrus nodes settle proofs/payments on Sui. Data = off-chain; metadata = on-chain.

Inside each contract object on Sui: SHA-256 hash for the file plus version hashes.

Groth16 circuits compiled with Circom 2 (Plonkish upgrades on the roadmap).

Yes—every action has a TxID; click View on Explorer in the UI.

Not currently. While Decot is in its pilot phase, the way to try it is a scoped pilot (8–12 weeks) or a read-only demo — pricing is contact-based.

A contract counts once it leaves Draft; archiving frees quota.

Uploads pause; upgrade or delete unused files. Enterprise clients can negotiate higher limits.

No—Decot pays the mint fee as part of your subscription.

Not today. Decot is SaaS-only; Enterprise clients may pin Walrus replicas to their own S3 buckets if required.

Owner, Admin, Editor, Commenter, Viewer and API Service (for bots).

Yes—SAML 2.0/OIDC enterprise connectors are available on Business tier and up.

Use the visual Workflow Builder (e.g. “If Total > €100 k → Legal approval required”).

Yes—trigger Key Rotation in SEAL; old keys are tomb-stoned, new ciphertext is re-wrapped for remaining users.

Not yet. API integrations are currently under development and marked as coming soon.

Not yet. Zapier and Make.com support will be announced once the API launch is live.

Salesforce integration is coming soon and not available in the current release.

This integration is coming soon and currently unavailable.

Not currently. GraphQL is planned for a future release.

They meet key “qualified ledger” criteria (Reg. (EU) 2024/1183); formal certification is planned for 2026.

We delete the Walrus blob and tomb-stone its key; the on-chain hash then points to undecipherable data.

Yes—wallet signatures are legal electronic signatures under ESIGN/UETA, and the immutable audit trail proves intent and attribution. For EU eIDAS, Decot also issues Qualified Electronic Signatures (QES) via DigiCert, which validate as trusted in Adobe Acrobat.

Email [email protected] for our Data Processing Addendum.

SOC-2 Type I is underway; Type II is targeted for Q1 2026.

Check Sui Explorer for Pending status. Decot auto-re-broadcasts after 60 s; contact support if pending > 5 min.

Use Decot recovery with your verified email and recovery setup, then contact support if extra verification is required.

Email [email protected] or submit via our HackerOne program—please include reproduction steps.