and here's 10 sats zap as a reward for your successful trolling ⚡
JDS = Job Declaration Server
TPS = Template Providing Server
both are kinds of Sv2 nodes, or "roles"
in the future people will use Sv2 to sell their souls to the devil with the following business models:
- OFAC-compliant JDS-as-a-service to Pools
- OFAC-compliant TPS-as-a-service to Miners
laser eye til fiat dies
nostr:npub1vy80zvg428jm2f3u9cqxdzgmv7sz0zgdn8pja4qqthe272pjhg3qprd324 and I just delivered the hands-on Stratum V2 workshop during Bitshala Developer Summit in Bangalore, promoted by nostr:npub1m495fdq2e8jleptdq6ruzpmz0esjttln2rjx7dxj9w4zvxs48y3q5pu22l
it was a cohort of ~15 devs from the local indian community 🇮🇳
we had 3 pools and ~12 miners using Sv2 JD to declare their own templates to mine on a custom signet deployed on the VPS of SRI community
the workshop went on for about ~2h was a big success!
everyone was able to find blocks via decentralized Sv2 mining ⛏️
nope, afaik mining-configure has been somewhat ossified into the Stratum V1 protocol
but it's not a widely used message
maybe he'll join when PoW notes becomes common
nevent1qvzqqqqqqypzqxqv29lkfav4k8j5h5kww7xvc2jkkyf7tf93gfk5kzjrjzpszrd3qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy88wumn8ghj7mn0wvhxcmmv9uqzqv92954u0zr0qdqr586f6alxmp0zddrkysk5m3ggm8a3g67k2zmeppsyzq
Mobile GPUs can be leveraged to mine NIP-13 notes via PoCL
just forked lnurl-rs crate by nostr:npub1u8lnhlw5usp3t9vmpz60ejpyt649z33hu82wc2hpv6m5xdqmuxhs46turz
the goal is to build a functional CLI executable on top of the lib
ah e a tag do "location" tava com sintaxe inválida, tive que corrigir pra um array
#JSONsucks
PORRA typo no "created_at"!
mas foi so na hora de transpor o evento, o nonce eh valido ⛏️
{
"kind": 31922,
"id": "000005cfe0bd3f4e5cfb3b3650474a41136b04fb2ef0136b32bb1e4d8f880e84",
"crated_at": 1727922629,
"tags": [
["location", "kitchen"],
["nonce", "13835058055282956758", "21"]
],
"content": "QUERO CAFÉ! ☕",
"pubkey": "21"
}
that's a multidimensional analysis
at a global level, how many shares can your system process at a fixed unit of time?
that's a function of:
1. how much resources are available on your system
2. how many downstreams are being served
3. each downstream's hashrate
- assuming 1 is fixed, more downstreams means each of them must send shares less often
- assuming 2+3 are fixed, more resources means shares can arrive from each downstream more often
so your modeling should start with a single downstream so you can measure your system's max capacity
start with a high difficulty target and gradually decrease the difficulty so you get shares more often, until you find your max capacity
if you get to difficulty 0 without hitting bottlenecks, either add more downstreams or switch to a more powerful one
once you find your max capacity, then for each production downstream, adjust their difficulty targets so your system is operating below this ceiling
“Nostr: a work in progress” by Sjors Provoost. 2025.