Labels: Stellar Wave, stellar, audit, interop, drips, help-wanted
Tier: M (2–4 days)
Type: audit
Context
Wraith's whole multichain model assumes the SDK can interpret announcements emitted by any chain's contract using the same scanning algorithm. If the event schemas drift — say, Stellar emits a Bytes where EVM emits a fixed-length array, or scheme_id is u32 on one chain and u64 on another — the SDK has to special-case forever.
We need an audit confirming the schemas are actually congruent and document them in one place.
Scope
Audit and produce a single document contracts/ANNOUNCEMENT_SCHEMA.md that:
- For each chain (EVM, Stellar, Solana, CKB), specifies:
- Field name
- On-chain encoded type
- Off-chain logical type (what the SDK sees post-decode)
- Source-of-truth file path
- Surfaces every divergence as a finding with severity (e.g., "Stellar metadata is
Bytes, EVM bytes, Solana Vec<u8>, CKB embedded in lock args — divergent encoding but logically the same; SDK normalizes").
- Recommends a canonical normalized form (the type the SDK exposes via
Announcement).
- Recommends contract-side changes to reduce divergence where harmless.
Comparison framework
Build a table like:
| Field |
EVM |
Stellar |
Solana |
CKB |
Diverges? |
schemeId |
uint256 |
u32 |
u32 |
n/a (script identity) |
Yes |
stealthAddress |
address(20) |
Address |
Pubkey(32) |
blake160(20) |
Yes |
| ... |
|
|
|
|
|
For each divergence, document whether the SDK normalizes correctly today (link to the SDK code).
Acceptance criteria
Why this matters
This is the foundation for adding a 5th chain. If we don't have an explicit cross-chain schema, the SDK becomes an unmaintainable patchwork the first time someone tries to add Sui or Aptos.
Files to start with
contracts/evm/contracts/ERC5564Announcer.sol (canonical reference, ERC-5564)contracts/stellar/stealth-announcer/src/lib.rscontracts/solana/programs/wraith-announcer/src/lib.rscontracts/ckb/contracts/wraith-stealth-lock/src/main.rssdk/src/chains/*/announcements.ts (consumer side)
Labels:
Stellar Wave,stellar,audit,interop,drips,help-wantedTier: M (2–4 days)
Type: audit
Context
Wraith's whole multichain model assumes the SDK can interpret announcements emitted by any chain's contract using the same scanning algorithm. If the event schemas drift — say, Stellar emits a Bytes where EVM emits a fixed-length array, or scheme_id is
u32on one chain andu64on another — the SDK has to special-case forever.We need an audit confirming the schemas are actually congruent and document them in one place.
Scope
Audit and produce a single document
contracts/ANNOUNCEMENT_SCHEMA.mdthat:Bytes, EVMbytes, SolanaVec<u8>, CKB embedded in lock args — divergent encoding but logically the same; SDK normalizes").Announcement).Comparison framework
Build a table like:
schemeIdstealthAddressFor each divergence, document whether the SDK normalizes correctly today (link to the SDK code).
Acceptance criteria
ANNOUNCEMENT_SCHEMA.mdcommitted at repo root with the full table.Why this matters
This is the foundation for adding a 5th chain. If we don't have an explicit cross-chain schema, the SDK becomes an unmaintainable patchwork the first time someone tries to add Sui or Aptos.
Files to start with
contracts/evm/contracts/ERC5564Announcer.sol(canonical reference, ERC-5564)contracts/stellar/stealth-announcer/src/lib.rscontracts/solana/programs/wraith-announcer/src/lib.rscontracts/ckb/contracts/wraith-stealth-lock/src/main.rssdk/src/chains/*/announcements.ts(consumer side)