Create payment payload
POST /api/v1/stealth/create derives stealth destination and announcement data.Scan announcements
POST /api/v1/stealth/scan discovers payments addressed to your keys.Publish announcement
Push announcement objects to the registry so recipients can discover them.
Workflow
POST /api/v1/stealth/create
Request schema
Hex-encoded recipient meta-address.
Optional channel identifier field in DTO. Current create handler does not use this field.
Response schema
Checksummed stealth EVM address.
Stealth Sui address derived from the same key material.
Hex-encoded ephemeral ciphertext.
1-byte view tag for fast filtering.
Announcement object ready for registry publication.
Announcement ID value from in-memory construction.
Hex ephemeral ciphertext.
Announcement view tag.
Unix timestamp set at creation.
Optional channel id.
Optional transaction hash.
Optional amount string.
Optional chain identifier.
POST /api/v1/stealth/scan
Request schema
Viewing secret key in hex.
Spending public key in hex.
Spending secret key in hex.
Optional list of specific view tags to pre-filter announcements.
Optional scan window start (Unix timestamp).
Optional scan window end (Unix timestamp).
Response schema
Array of discovered payments.
Scan execution metrics.
Number of announcements scanned.
Count of matching results returned by the scan path.
Number of discovered payments.
Total scan duration in milliseconds.
Scan throughput (announcements per second).
Example calls
- Create (cURL)
- Scan (cURL)
- JavaScript
Filter precedence in scan handler
Filter precedence in scan handler
Scan selection uses this order:
view_tags filter first, else time range when both from_timestamp and to_timestamp are provided, else full registry scan.Hex prefix handling
Hex prefix handling
Scan key fields accept values with or without a
0x prefix (strip_hex_prefix in handler).Secret material in discoveries
Secret material in discoveries
Discovery output includes
stealth_sk and eth_private_key. Treat response payload as highly sensitive.