You send a DAC transaction. It finalizes. Days later, you receive funds at that same address. You have just put new funds behind a public key that is already exposed. That is why @dac_chain’s yellow paper recommends a fresh address for every transaction. Here is the sequence. Before broadcast, DAC’s Entropy-Padded Transactions encrypt the signed transaction, hiding the sender’s public key during transmission. After finalization, the entropy used for encryption is revealed. The transaction, including that public key, becomes public. DAC retains ECDSA, the signature scheme also used by Ethereum. A sufficiently capable quantum computer could derive a private key from its exposed public key. An empty, retired address leaves that attacker nothing to spend. An address you keep funding gives the exposed key control over new money. The practical detail matters: generating another address is only part of the habit. The previously spent address must stay empty and out of use. DAC’s recommendation connects transaction protection with what happens afterward. Once a public key becomes visible, future funds should belong to a fresh one.