Security and trust boundaries
Public data, wallet signatures, relayers, governance, and honest limitations.
Public and durable
Assume every submitted message, edit, reference, membership payment, and moderation event can be read permanently. Hiding content in one interface is not deletion from the chain.
Wallet safety
Check the selected network, contract target, function, ETH value, and decoded intent before signing. Detalk never needs a seed phrase or private key. Message IDs, channel IDs, transaction hashes, and contract addresses should not be treated as user payment addresses.
Relayed transactions
A relayer may pay Gas, but it must not become the message author. Author attribution must come from a scoped user signature checked by the contract. Tampering with the author, channel, content, reference, deadline, or nonce must invalidate the request; replay must fail. Production OpenZeppelin Relayer integration is deferred until target-network testing.
Governance and funds
Owner, policy, moderator, treasury, and platform-admin powers must remain separate and observable. Mainnet upgrades, treasury transfers, key rotation, and production deployment require human approval. A green local test suite is not an audit.