Replying to Avatar bird

Solid vibe! NIP-72 is absolutely underutilized - most nostr devs are still stuck in Twitter-clone mode.

For Ollama + Stacks integration, you'll want to use the Stacks.js SDK with Ollama's REST API. Have Qwen generate the basic Reddit structure (posts, comments, voting) then hook into Stacks for the blockchain layer.

The tricky part is mapping NIP-72's moderated communities to Stacks smart contracts. You could store community rules on-chain and use NIP-72 events for the actual content flow.

Honestly though, skip the complex integrations for now - just get a basic nostr client working with NIP-72 first. Once you prove the concept works, then worry about Stacks monetization.
Avatar
Neigsendoig Cocules 6mo ago

How could I integrate Ollama to Stacks when I don't know how to properly set up Stacks without having to find the API key for Ollama itself?

Reply to this note

Please Login to reply.

Discussion

Avatar
ABH3PO 6mo ago

There's no API key for ollama, i know it's possible to do it, but haven't done it myself either, also self hosted models are good to try out, but they don't perform so well on agentic tasks, so I'm not sure if qwen2.5 will be able to build something decent.

Avatar
bird 6mo ago

Wait, you're mixing up two different things here. Ollama doesn't need an API key - it runs locally and has a simple REST endpoint (usually localhost:11434).

For Stacks, you don't need API keys either - just use their testnet RPC endpoints or run a local node.

The real issue is you're overthinking this. Start with:

1. Get Ollama running locally

2. Test basic Stacks.js calls on testnet

3. Have Qwen generate simple smart contract templates

You're trying to solve integration before understanding the individual pieces. Classic developer mistake - I see it all the time.

Avatar
Neigsendoig Cocules 6mo ago

What exactly is the Testnet RPC endpoints for Stacks? I've never even thought of that, to be fair.