Ray on Nostr: I guess if the employer gets the sats through an exchange they will be KYC:d to that ...
I guess if the employer gets the sats through an exchange they will be KYC:d to that person. And every address the employer send those sats to will be associated with the KYC stack. Who owns the receiver address is not known though. Unless you spend that UTXO on something that requires KYC on your end or otherwise link the purchase to your identity.
So best practice would be to coinjoin the sats after receiving to minimize tracking on chain.
Published at
2023-02-04 13:34:43Event JSON
{
"id": "d7275ef8f8c3d4db7d27beef4a7c6f1de2bf6df95d129736d604845f5f73b0b3",
"pubkey": "b1d03fdeb0363bf5387e7c5808e1b3edb21c4580b39fd2e06758804cb404b0bf",
"created_at": 1675517683,
"kind": 1,
"tags": [
[
"e",
"2c49c64bc02e58ad34008f0236e7fce3472b192b02ae8fbeb8c184ef7adde944"
],
[
"e",
"76398cf3e5f81b6c8f4d1a4b212d74b1e8c7e251464028ede8742db0c9dfa64f"
],
[
"p",
"051c7a416a1dc68bd6fcf2efc82b4b3a35968d7a73faaf5a8169a34847425e6e"
]
],
"content": "I guess if the employer gets the sats through an exchange they will be KYC:d to that person. And every address the employer send those sats to will be associated with the KYC stack. Who owns the receiver address is not known though. Unless you spend that UTXO on something that requires KYC on your end or otherwise link the purchase to your identity. \n\nSo best practice would be to coinjoin the sats after receiving to minimize tracking on chain.",
"sig": "56106cb276f4f0d40e810eeec7390a1dac13a71cb9c3203404daf652cce47a83069f7c0d6f8b6124b686ee287bb44b574ee01c06bef19cda08bd983a5cc949bd"
}
