Web3 workspace / Explicit by design

Review contract intent.Keep wallet consent separate.

Byteplane places a local review layer between an intended contract call and the wallet. Connection, provider reads, points, payment review, transaction submission, and receipt verification remain distinct actions.

Live browser state

Nothing is inferred.

These fields reflect only the connected browser wallet and locally recorded participation state. Empty data stays empty; unavailable actions remain unavailable.

Address Not connected No account requested

Network Unavailable Reported by the wallet

Participation 0 points Activation is separate

Write readiness Read-only No transaction prepared

Deliberate operations

One action, one consent boundary.

01 / Local participation

Activate points separately

Connecting a wallet awards nothing. After connection, you may separately activate 100 local participation points. Points are not a token and carry no stated monetary value.

Base activation 100 points

Optional reviewed upgrade 0.37 BOT

The upgrade can show 200 points only after a real matching transaction succeeds and its receipt is verified. No future reward is promised.

02 / Provider read

Inspect a real transaction receipt

Enter a transaction hash and request its receipt through the connected wallet provider. A missing receipt is reported as pending or not found.

Connect a wallet, then enter a real transaction hash.

03 / Portable intent

Compose and seal an unsigned envelope

Build a canonical local record from user-supplied fields. Sealing adds a SHA-256 integrity digest; it does not sign, submit, simulate, or prove the transaction safe.

No review record has been prepared.

04 / Independent verification

Verify an imported envelope

Paste a Byteplane envelope or load the published neutral sample. Verification checks its canonical digest only; it does not confirm contract behavior or execution.

Envelope JSON

No imported envelope has been checked.

Consent lifecycle

Five checkpoints, never one hidden chain.

01 Connect

Read the active account and network context. No signature, payment, or points.

02 Inspect

Validate inputs and request only the provider read the user selected.

03 Compose

Prepare calldata or an unsigned envelope locally, with no submission.

04 Confirm

Show recipient, value, account, and network before any optional write.

05 Verify

Use real transaction and receipt data before recording a successful outcome.

Builder assets

Portable parts for safer contract calls.

The public assets expose this page's local format and verifier. They are small, dependency-free building blocks—not an execution guarantee or hosted transaction service.

JSON Schema

Unsigned transaction envelope

A versioned structure for network context, transaction intent, method metadata, preflight checks, and digest.

Download schema

Valid fixture

Neutral sample envelope

A verifiable sample with no invented address, network state, receipt, or submitted transaction.

Download example

Browser module

Canonical encoder and verifier

Deterministic JSON, SHA-256 sealing, structural validation, and a deliberately read-only provider boundary.

Open module

ABI manifest

Consistent method metadata

The core parser normalizes function signatures, access mode, mutability, inputs, and outputs without claiming implementation proof.

Download manifest schema

Built to make contract intent portable, inspectable, and easier to review across compatible tools.