SecureText • Step 0 (ESM)

Use SecureText to post public or private (encrypted messages) to any blockchain wallet, attest to public keys (to enable private communication between wallets), attest to hashes to prove ownership (whoever attests first) or integrity of a file (whoever attests first), and (soon) validate images and video entirely in the browser. All processing like encryption, decryption, file hashing occurs strictly client-side on your device.

Step 1: Connect

Active Wallet: —

Active Address: —

Active Chain: —

Active Balance: —

Step 2: Key (re)Generation

Derive Root & Child Key

Root fingerprint: —

Extra passkey (optional; defaults to 'inbox' when left blank):

PubKey (base64): —

keyId (keccak): —

Register / Revoke Derived Key On-Chain

Use the derived key to attest or revoke it on the SecureText contract. Metadata can be any label; it is hashed to bytes32 if not already a 0x-prefixed value.

Metadata label or bytes32 hash:

Revocation reason:

—

Step 3: Select Destination

Directory Lookup/Destination Address Selection:

Add/Replace/Remove Directory Address Box:

Selected Destination: —

Destination Balance (current chain): —

Attested Keys For Selected Address

View the registered SecureText keys for the currently selected directory entry.

Select an address to load keys.

Key ID	Metadata	Status	Issued	Revoked	Key Data

Attested Files For Selected Address

View file hashes attested by the selected address. Click a hash to prefill the file lookup area.

Select an address to load files.

File Hash	Initial URIs	Attested At	Action

Step 4: View Related Message History

From date: To date:

Min payment (ETH):

Block	Timestamp	Category	From	To	Payment (ETH)	File Hash	Raw Payload (hex)	UTF-8 Attempt	Decrypt Attempt	Tx Hash

Step 5: File Hashing & Attestation (optional)

Hash files locally to prove ownership/integrity and optionally embed the hash in your SecureText message metadata. All hashing stays in-browser; only the 32-byte digest (and optional URI list) is sent on-chain when you attest.

Select file:

Include file hash in constructed message metadata

No file selected.

File metadata label or bytes32 hash (embedded in message only, not stored on-chain):

Hash: 0x0000…

Initial file URI list (optional; comma/space separated): Hash override (optional; hex or Base64 if you already computed it):

Select a file to hash locally for attestation.

No attestation loaded.

Step 6: Encrypt / Decrypt with Derived Keys

Message: Send as plaintext CBOR (no encryption). Anyone can read; only use when you intend to send cleartext.

0 / — bytes

Encrypt message with destination's attested key

Select a destination to load attested keys for encryption.

Step 7: Post Message (Single-Message Router)

Payment (ETH, optional):

—

Step 8: Fee Routing (Owner Controls)

Configure where collected message fees are routed and how much is charged. 2.7% corresponds to 270 basis points. Only the SecureText contract owner can update these values.

Current fee sink: —

Current message fee: — bps (—%)

Fee sink address:

Message fee (% of payment): Message fee (basis points, 100 bps = 1%):

Connect a wallet to manage fees.