This is still very early draft. Plenty of room for improvements for brevity to conserve space and thus reduce fees for those using this protocol. Also some identifiers like URIs should probably be referenced by their own DID records instead of repeated across records

https://microstrategy.github.io/did-btc-spec/

Reply to this note

Please Login to reply.

Discussion

you like DIDs? Why? What are the trade offs compared to nostr? Did you know you can do FROST/ROAST threshold multi-sig on with nostr? I tried to get nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac to hack on it for design.

nostr:npub1l6uy9chxyn943cmylrmukd3uqdq8h623nt2gxfh4rruhdv64zpvsx6zvtg nostr:npub1t0nyg64g5vwprva52wlcmt7fkdr07v5dr7s35raq9g0xgc0k4xcsedjgqv

https://github.com/m1sterc001guy/roastr

Reading it and posting the repo does not equal endorsement lol

that's why i framed it as a question.

I’m not against hacking on a design, I just don’t understand what it’s supposed to look like. I haven’t looked to see if you responded to my follow-up questions

I really appreciate you. I am colorblind and not good at design stuff. it's hard to explain for me. I have done my best explaining in this issue and note. the others issues cover more technical details of a short path to MVP. it uses React on the front-end but could be anything really. a good UI dev could work wonders. I am happy working toward the backend integration stuff.

https://github.com/EthnTuttle/toast/issues/5

roastr brings a threshold multi-sig option to nostr by leveraging FROST/ROAST. (Fedimint's tech enables this because of the consensus mechanism of Fedimint coupled with FROSTs nonce management requirement.)

you can create a nostr account that requires 2of3 or 3of5 or 1of4 signatures to be valid. This means that a multi-person entity can have a quorum of signers for nostr events.

you can have a nostr account with friends. where you can "vote" on approving a note (or other stuff). Enterprises can have a board "vote" using nostr.

CC: nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8

This could be a direct competitor of Saylor's Orange Juice or w/e it's called. And create a playground for FROST/ROAST to be battle tested without money gone.

i neither like, nor dislike DIDs. Its simply data. From the standpoint of Bitcoin it represents another phase of adoption of a permissionless censorship resistant network. I mainly seek to understand these and hope for storage efficiency

How are identities and their private keys managed? Who owns the keys?

What is the expected cost of creating an identity? Creating 10,000 identities?

a sample transaction on testnet was 254 bytes but this varies based on inputs, outputs, and size of did. For the sampke it was a 32 byte publickey

https://blockstream.info/testnet/tx/5acfba9c13bd92c27e9aa8b8cd75d03730571b2dfcc7f81543e9c15cc1efb961?expand

cost is contingent on sats per byte for blockspace at relevant time.

Is there an example range of where that fee is most likely to fall in?

If I am reading this transaction correctly it cost 500 sats for a 254 characters profile. Does this scale?