A practical guide

A replay attack reuses a previously valid message or transaction in a context where it should not be accepted again. Protocols can limit this risk with values such as nonces, timestamps, sequence numbers, or chain identifiers. The defenses depend on the system.This is a protocol issue; users can also reduce risk by following {account safety practices|security}.account safety practices

What to know

A signed request should be bound to the intended action and context. If that context is missing or reused, a valid message may be applied in an unintended way. Developers need to design and test these checks; users should review the details of signing prompts.Related foundations include {digital signatures|digital-signature}.digital signatures

Using this information

Do not approve an unexpected transaction to solve an unrelated account problem. UIGame users should use the platform’s official help information and avoid sharing passwords, private keys, or recovery phrases.