> a sleeper contingent of true cypherpunks sticks around

As opposed to nostr:nprofile1qqsza748zkamgmw4he4hm2xhwqpxd5gkwju38wqh3twmtshx8kv8xvgppemhxue69uhkummn9ekx7mp0qyfhwumn8ghj7am0wsh82arcduhx7mn99uq3zamnwvaz7tmwdaehgu3wwa5kuef02eegaw 's previous plan where someone else takes on the business risk of Bitcoin volatility, this time it's someone else being the cypherpunk.

Reply to this note

Please Login to reply.

Discussion

It wasn't "someone else" in the previous plan. If I deploy that plan locally, I'm going to be the one to take on the volatility risk.

Similarly, it's me in this plan, too.

I'll keep my eyes peeled.