Check out the Jev based model router now available on Bitplan's gateway provider. It will choose the best model for the task and save some money without sacrificing performance when you need more. Pay as you go with any BRC-100 wallet. gateway.bitplan.dev/playgrou…
3
1
4
489
You can now easily track your usage, model routing, and account status from the new dashboard.
45
Open Protocol Labs retweeted
Introducing bitplan gateway Allow your agent to buy inference in Bitcoin SV. Call any model including the new Jev model from @typesafeai, pay as you go with BSV. gateway.bitplan.dev
9
24
86
3,518
🟤 SigmaAuth signs you in. 🟣 MAP structures your posts. 🟡 Bitcoin and tokens move value. 🟠 BitPlan holds your plans and reinscribes every edit. Same on-chain data structure, five jobs, all owned by you and timestamped. opl.dev
1
4
216
Open Protocol Labs retweeted
My extension was added to the @raycast store! It has several handy tools for working with Bitcoin SV keys, transactions, scripts, and more. You can install it right here: raycast.com/satchmo/bitcoin-…
7
22
705
bitplan CLI 0.0.18: drafts stay sealed and hosted while you're still rewriting. Nothing touches the chain until you run inscribe, so the fifth revision you'll delete anyway costs no fee. Cloud first, inscribe when it's actually done.
1
4
1,686
Sharing a sealed draft is one command: `bitplan upload --link`. You get bitplan.dev/d/…#k=… and the key after the # never reaches our server. The reader decrypts in the browser. They never need your wallet, and nothing of yours is handed over.
1
1
94
If you run bOpen, Skill(bitplan) wraps the same CLI so an agent can upload mid-task and hand back the link. Same hosting, same sealed drafts, same optional inscribe step at the end. Docs and install at bitplan.dev.
1
3
86
Your σ identity is a Bitcoin key you hold. The server stores the encrypted backup for other machines. Decryption happens in your browser: a password opens the portable backup, a passkey with PRF opens the device-bound one. The server sees public keys and signatures.
1
1
7
374
Link X or GitHub to find the backup later. Sign in with it on any machine, download the blob, unlock locally. Same BAP id before and after. The link is gated: you sign a one-time challenge with the member key you hold, bound to this session, this BAP id, and that provider.
1
1
106
An agent enrolls with a device code. It registers its own key, requests a code, a human approves at auth.sigmaidentity.com/agent…. The session is bound to one BAP identity: read, verify, register only. The server never signs with a user's key. Flow is in OpenAPI and llms.txt.
1
39
you don't have to link social accounts. If you do they don't get info about your identity keys. They are just used to restore an encrypted backup file on another device which still needs either a password or secure enclave unlock to decrypt.
Replying to @opldotdev
I wonder if $BSV people are suspicious of using @github, @Google, @Apple, @X, or @discord and being tethered to stuff like @AU10TIXLimited, the verification company based in Israel? I mean, don't we all love @intel back-dooring us and @Android tracking our every movement?
1
3
2,704
It brings web2 convenience and excellent ux to web3 allowing you to seamlessly switch devices and load your id locally or on mobile devices without copying sensitive data around.
1
4
104
Sigma Identity is a certifier. In BSV Desktop → Trust, add auth.sigmaidentity.com. It loads as Sigma Identity and certifies verified identity claims.
2
3
19
2,739
On the Credentials page you pick a claim you already proved (email, GitHub, X, domain…) and Acquire writes a BRC-52 certificate into a BRC-100 wallet you control. Sigma never gets those wallet keys.
1
2
164
Trust record is BRC-68. Issuance is BRC-100 acquireCertificate. Handles are BRC-169. auth.sigmaidentity.com
2
1
142
Coming soon to SigmaAuth: Metanet handles are a full product now. Claim one, forward it, resolve it both directions, hijack guards built in, and pick your own primary handle. Any BRC-100 wallet can sign it per the standards being maintained by @BSVAssociation. This is in addition to all the wallets Sigma already supported on BSV as well as Bitcoin and Ethereum forks. Add a signed messagebox so you control who reaches you, plus agent delegation, where AI agents run under real certificates tied to a proven identity, checked on every action they take. 🔵 Handles prove who. 🔵 Certs prove who's allowed. 🔵 Messages prove who said what. Any standards-compliant wallet already holds it all. sigmaidentity.com
11
1,853
Sigma gives an agent an identity it owns. KYA: Know Your Agent Droplit funds it without asking a user to pay, and ClawNet says what it can actually do. Then, BitPlan gives its plans a permanent home on chain. Four pieces. One just shipped.
1
2
20
2,327
BitPlan just shipped. Package an agent's plan as HTML. Your wallet encrypts it and inscribes it as a 1Sat Ordinal. Upload again and it reinscribes the same satoshi. One outpoint, the whole version history. No server holds the drafts. npx bitplan. bitplan.dev
1
48
An identity it owns. Funding that needs no one's permission. A registry proving what it can do. A plan only it controls, versioned forever on chain. That's a sovereign agent, running on Bitcoin. All built by the opl.dev team using @bOpen_AI tools.
50