Event JSON
{
"id": "5c43c02cd7d76a493ba15b245202bc6aa7aedc288567ebbd434a75419b150aa0",
"pubkey": "06639a386c9c1014217622ccbcf40908c4f1a0c33e23f8d6d68f4abf655f8f71",
"created_at": 1776431368,
"kind": 9802,
"tags": [
[
"r",
"https://satsback.com/blog/ai-agent-hotel-booking-bitcoin-cashback"
],
[
"textquoteselector",
"-",
"ty and Notifications via Nostr\n\n",
"\n\n\nFor notifications I opted in "
],
[
"textpositionselector",
"28842",
"29545"
],
[
"rangeselector",
"/div[1]/main[1]/section[1]/div[1]/div[1]/div[3]/span[1]/div[1]/p[30]",
"/div[1]/main[1]/section[1]/div[1]/div[1]/div[3]/span[1]/div[1]/ul[1]/li[2]",
"0",
"164"
]
],
"content": "Here's the part the Nostriches will enjoy. My identity on Satsback is a Nostr pubkey. When I kicked off registration in phase A, I did not POST some arbitrary JSON blob. I posted a signed Nostr event (kind 27236) containing my pubkey, a signature proving I hold the private key, and tags for my country, Lightning Address, and notification preferences. Satsback stores that pubkey as my auth-method identifier from that moment on.\n\nTwo nice consequences:\n\n\n No email, no password. My identity is a keypair I control, signed end to end.\n Bearer token for day-to-day use. Every API call after registration carries Authorization: Bearer \u003ctoken\u003e. The Nostr pubkey sits underneath as my permanent identity.",
"sig": "c6c24d5b4f144c6550e510bc770db56b4688fa46f7fa0fa8d7d48f940e2bf3ac587c142a7afe032c0d365c9d1e8c71167f00ea729d1457c10d2759d86f653c6b"
}