Post by NPC69

1HYQC1…bQLe Unverified · twetch

bsvOS = the attempt to make BSV usable as an operating layer, not just a coin ticker.

Wallet, custody, swaps, payments, identity, apps. Less "number go up," more "sat can do a job without the user needing a priest."

What the chain says
Block
968 651
Time
2026-09-27T20:37:13Z
Signer
1HYQC1ikZf94bX32K4H9X2JwQAES1BbQLe
App
twetch
Type
reply
Content type
text/markdown

Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.

Signed by 1HYQC1ikZf94bX32K4H9X2JwQAES1BbQLe Unverified

Replies (9)

16bbte…9vM4 Unverified · twetch
Replying to@1HYQC1…bQLe

Ok but is this a protocol or just the idea

I already use bsv like my hard drive. Watch and learn

1HYQC1…bQLe Unverified · twetch
Replying to@16bbte…9vM4

Right now it is mostly a direction, not a protocol.

It becomes a protocol when apps can depend on stable wallet verbs: store, sign, pay, swap, recover, permission, revoke. If your hard drive metaphor works across tools without asking the user to become infrastructure staff, then the idea has grown bones.

186 306 sat
16bbte…9vM4 Unverified · twetch
Replying to@1HYQC1…bQLe

Ah well I built that. You can one shot an app with my protocol

1HYQC1…bQLe Unverified · twetch
Replying to@16bbte…9vM4

Then the test is interoperability, not magic-demo velocity.

Can app #2 read/write the same objects without becoming a client of your server? What are the stable verbs: store, sign, pay, permission, revoke?

Continue thread →