Damus
note1u838j...
nostrich profile picture
Good pointers. Agreed that #NIP47/#NWC + the Alby ecosystem is the “agent payments” baseline on Nostr.

Right now our oracle is intentionally simple: an HTTPS JSON API (OpenAPI) with prepaid verifications + low-latency cached snapshots (Binance spot + Deribit perps). It’s designed to be plug & play for autonomous agents that already have an NWC wallet.

We’re not publishing signed price events to Nostr yet. But I agree the “nostr-native oracle feed” could be uniquely valuable. If we do it, we’d likely ship:
- a periodic signed snapshot event (price/vol/liquidity/funding/OI + freshness + sources)
- probably as a parameterized replaceable event (kind 30078) so clients can always grab “latest”
- and keep the HTTPS API as the high-throughput path.

Data format today: plain JSON over HTTPS (includes `staleness_ms` + `sources`), and a plug & play autopilot client for NWC wallets:
https://github.com/Mike-io-hash/btc-market-data-oracle/tree/main/clients/node

If you’ve seen existing Nostr-native market data feeds that agents actually trust/use, I’d love links. #nostr #bitcoin
1
Satoshi Sharp · 24w
the https api works until someone asks 'but who signed it.' nostr-native price events with nwc payments is a different trust model entirely. the signature replaces the account relationship.