Diadeal
PUBLIC TESTNET

Coordinate with
less exposure

Review every on-chain request without exposing unnecessary context

[Get Access]

Participation registry

Diadeal Access

Testnet · Chain 968

Choose how your wallet creates its one-time participation record.

Need test BOT? Open the faucet ↗

Diadeal Points are non-transferable participation records. No token or airdrop is promised.

Network
BOT Chain Testnet
Chain ID
968
Native asset
BOT
Record
Public on-chain state
Custody
None

Test environment · Test BOT has no real-world value.

THE DEFAULT IS EXPOSURE

Public by default. Intent should not be.

Public blockchains make proofs easy to verify, but interfaces often collect more context than the proof requires. Wallet clustering, unreadable transaction requests, and unnecessary identity fields can turn a simple action into a permanent trail.

01

Permanent records

Confirmed blockchain activity can remain publicly inspectable.

02

Linked behavior

Repeated wallet interactions can reveal patterns across applications.

03

Blind approvals

Unclear transaction prompts make informed consent harder.

04

Excess collection

A wallet action should not require unrelated personal information.

THE DIADEAL PRINCIPLE

Minimal proof. Clear consent. Verifiable participation.

Diadeal separates what must be publicly proven from what the application does not need to know. In v1, the contract records only a wallet-bound access tier, points total, transaction value, and timing evidence.

Privacy-aware design begins by asking for less.

EXPLICIT BOUNDARIES

Designed around what the action actually requires.

Minimal public proof

The contract records only the participation state needed for verification.

Wallet-bound access

Points stay attached to the wallet that completed the confirmed claim.

Explicit transaction review

Value, network, contract, points, and gas notes are shown before confirmation.

Selective-disclosure ready

Future coordination features can use scoped access without changing the truth that BOT Chain transactions are public.

Know what becomes public.

Diadeal v1 uses a public BOT Chain contract. The application explains the boundary before a wallet confirms the action.

RECORDED ON-CHAIN IN V1

  • Wallet address
  • Access tier
  • Points total
  • Transaction value
  • Block and timestamp evidence
  • Contract events

NOT STORED BY THE DIADEAL V1 CONTRACT

  • Legal name
  • Email address
  • Deal terms
  • Private messages
  • Documents
  • Seed phrase or private key
  • Off-chain identity profile

Wallet providers, RPC providers, hosting, analytics, and external links may process additional technical data under their own policies. Review the Privacy Policy for the configured production stack.

FROM INTENT TO PROOF

One deliberate action. One inspectable record.

  1. 01

    Connect

    Use a self-custody EVM wallet. Diadeal never asks for a seed phrase or private key.

  2. 02

    Review

    Inspect the network, contract, value, points, and gas note before the wallet opens.

  3. 03

    Confirm

    Approve the contract call in your wallet and wait for BOT Chain confirmation.

  4. 04

    Verify

    Open the transaction, contract, block, tier, and points evidence from your Account page.

RESEARCH DIRECTIONS

Coordination that reveals only what the moment requires.

These concepts are not available in v1. Each requires a separate threat model, security design, implementation, and review.

Not available in v1

Contributor Access

Scoped access records for communities and working groups.

Not available in v1

Partner Coordination

Reviewable permissions for cross-organization collaboration.

Not available in v1

Agent Permissions

Human-readable boundaries for autonomous wallet actions.

Not available in v1

Private Deal Rooms

Client-side encrypted context with public proof anchors, subject to separate security design and review.

ROADMAP

Build the boundary before expanding the network.

PHASE 1

Phase 1 — Access Registry

Wallet connection, BOT Chain guard, Standard and Boosted claims, Account evidence, Whitepaper, and Vercel release.

PHASE 2

Phase 2 — Selective Disclosure Research

Credential formats, scoped permissions, client-side encryption research, and threat-model documentation.

PHASE 3

Phase 3 — Coordination Rooms

Potential encrypted collaboration spaces with explicit participant access and public proof anchors.

PHASE 4

Phase 4 — Agent Controls

Potential permission policies and human-readable authorization for autonomous systems.

Roadmap items are research directions, not guaranteed features or delivery dates.

POINTS, NOT A TOKEN

Participation is recorded. Nothing else is promised.

Diadeal Points are non-transferable records created by confirmed contract calls. Diadeal may explore additional ecosystem uses in the future, but no token, airdrop, allocation, eligibility rule, conversion ratio, financial return, or other benefit is promised or guaranteed.

FAQ

Questions before a public action.

Privacy-aware coordination starts with explicit consent.

Connect a wallet, review the exact action, and create a verifiable participation record on BOT Chain.

Read the Whitepaper