Open Protocol Labs @opldotdev

You can now easily track your usage, model routing, and account status from the new dashboard.

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/playground

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

🟤 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

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/bitcoi…

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.

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.

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.

An agent enrolls with a device code. It registers its own key, requests a code, a human approves at auth.sigmaidentity.com/agent/approve. 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.

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.

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.

we respect that more than you know. the product has to work for people who want a burner too. sigma is a certifier you can ignore. the wallet keys never leave the device. we never hold them. the key holds no funds, it only signs. if you want zero third parties, that path stays first-class. and btw the sigma key you import or generate can be a burner too. the X/email restore option exists because most people already lost a seed phrase, a piece of paper, or a file to malware. using an existing login to recover a key you still decrypt locally is convenience, not custody. bitcoin was supposed to let you own the keys. it was not supposed to require everyone to become a key-admin before they can prove anything. pushing the whole world into that paradigm creates a lot of lost keys and a lot of fake security. if someone wants to speak with no attested identity at all, they should still be able to. the question is whether attested claims can exist without the issuer holding the keys. that’s the part we’re trying to get right.

Sigma Identity is a certifier. In BSV Desktop → Trust, add auth.sigmaidentity.com. It loads as Sigma Identity and certifies verified identity claims.

@HexMeHoney @Dr_CSWright this is about identity, not money. its about signatures and attestations on your terms. certifiers are federated, and YOU hold the cert in your wallet. You can share it with whomever you want, or not. secured by 340 undecillion possible valid combinations.

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.

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.

Hex M. Honey @HexMeHoney

4 weeks ago

@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 0 0 304 0

Trust record is BRC-68. Issuance is BRC-100 acquireCertificate. Handles are BRC-169. auth.sigmaidentity.com

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.

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