Event JSON
{
"id": "28afeac71c97a4599978d5f282f33c8a6e4d468480ad5316b3456ff442d2dc84",
"pubkey": "40b9c85fffeafc1cadf8c30a4e5c88660ff6e4971a0dc723d5ab674b5e61b451",
"created_at": 1740587285,
"kind": 1,
"tags": [
[
"e",
"e8c9e3d6b62089b319560fc8070509db13a3372439d14d83dbe97bd981bc4aac",
"",
"root"
],
[
"e",
"1949c9c584d538c4ab29e28e9abe4992ce6a2d800bf711a753df873f6ff77a88",
"nostr-idb://cache-relay",
"reply",
"16f1a0100d4cfffbcc4230e8e0e4290cc5849c1adc64d6653fda07c031b1074b"
],
[
"p",
"dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319"
],
[
"p",
"16f1a0100d4cfffbcc4230e8e0e4290cc5849c1adc64d6653fda07c031b1074b"
],
[
"p",
"40b9c85fffeafc1cadf8c30a4e5c88660ff6e4971a0dc723d5ab674b5e61b451"
]
],
"content": "Sure, but where do we solve the case for users who do not want to reveal themselves publicly in a place where you cannot control the reach of your publications? I think the only solution for the case of btc on-chain to keep privacy is to fallback to a server to provide a fresh btc address. Do you think this can be compatible with what you are trying to do? Like `[\"w\", \"bitcoin\", \"https://mypayserver...\"]` ?",
"sig": "83b89651e9d7e705802fce28c140fe1a482191831dcea2cc1896587302502634defbc7ae9d47b000217f0618fb29b618f6dbec7fd745ef0217b216282aaf87cc"
}