https://github.com/securitybrahh/identity
Who we are?
https://github.com/securitybrahh/identity
Last synced: 10 months ago
JSON representation
Who we are?
- Host: GitHub
- URL: https://github.com/securitybrahh/identity
- Owner: securitybrahh
- Created: 2025-03-03T03:50:31.000Z (10 months ago)
- Default Branch: main
- Last Pushed: 2025-03-10T07:13:56.000Z (10 months ago)
- Last Synced: 2025-03-10T07:32:03.820Z (10 months ago)
- Size: 19.5 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# identity
https://soatok.blog/2024/11/21/key-transparency-and-the-right-to-be-forgotten/
[Oblivious passwords aka keys that never leave the device](https://blog.cloudflare.com/opaque-oblivious-passwords/)
Identity emerges from Honesty & Musn't (aka Decency). (on the other hand free speech, is about shoudn't/can't)
[Who we are?](https://letters.empiresec.co/p/what-are-we)
https://docs.polycentric.io/futo-id/
[Thank God For Nostr discusses NIP-77 and Web of Trust](https://fountain.fm/episode/aD6Jp6wGxOOitdqeaBii)
https://github.com/hoytech/strfry/blob/nextneg/docs/negentropy.md

https://github.com/wds4/tapestry-protocol/blob/main/glossary/decentralizedLanguage.md


[W. David Strayhorn, MD PhD | The Pretty Good way to calculate a user's influence within your web of trust](https://habla.news/a/naddr1qqxnzdes8q6rwv3hxs6rjvpeqgs98k45ww24g26dl8yatvefx3qrkaglp2yzu6dm3hv2vcxl822lqtgrqsqqqa28kn8wur)
[conceptGraph](https://github.com/wds4/brainstorm/blob/main/src/redux/features/conceptGraph/slice.js).js [grapevine](https://github.com/wds4/brainstorm/blob/main/src/redux/features/grapevine/slice.js).js
https://github.com/wds4/pretty-good/blob/main/appDescriptions/curatedLists/overview.md
## The great Key Management UX problem
is Web Standard of Passkey with [resident keys - userVerificationRequired](https://developers.yubico.com/WebAuthn/WebAuthn_Developer_Guide/Resident_Keys.html)
TODO ss of resident key stored a series 5.
`The user handle and private key are stored in persistent memory on the authenticator during the registration ceremony. During the authentication ceremony the authenticator returns the user handle, allowing the RP to look up the associated user. This means that the user does not need to enter a username to login.`
bitcoin cold signing {multisig} , mon-mnemonics, metal(gold), paper wallet, and now nsec 🤦 [supperbacked](https://github.com/superbacked/superbacked) by sun knudsen
## Custodians (Banks)
https://blog.casa.io/introducing-casa-vault/
https://armantheparman.com/inheritance/
https://bitcoinlaws.io/federal
Post Liquid - A better porotocol on top of or side of the bitcoin chain, as bitcoin as the underlying asset in the Censensus.
`Who can peg out? Public can not independently peg-out, which means they require from a Federation member to convert L-BTC back to BTC`
Btc fungibility graveyard (taintness) can be solved via joinstr.xyz (need local light node running on mobile)
Also companies need to have privacy if btc is accepted as unit of account, albeit some info can be in black and white (btc) {countries have portals for disclosures, filings etc}
[Lightning Service Provider node's btc rotated through channels to provide most profitability and efficiaeny in routing
](https://www.voltage.cloud/blog/deprecating-flow-2-0---paving-the-way-for-a-superior-solution)
## Formulas
https://freakoverse.github.io/wotonnostr/
iris - https://github.com/mmalmi/nostr-social-graph/blob/master/src/SocialGraph.tsts
https://github.com/stackernews/stacker.news/blob/master/worker/trust.js
https://github.com/coracle-social/coracle/blob/master/src/partials/WotScore.svelte