nips
slips
nips | slips | |
---|---|---|
70 | 90 | |
2,096 | 1,448 | |
1.6% | 1.1% | |
9.5 | 9.0 | |
2 days ago | 13 days ago | |
Markdown | ||
- | Creative Commons Attribution Share Alike 4.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nips
-
Why isn't Bluesky a peer-to-peer network?
I'm interested in this too. While I note the [slightly chaotic] plethora of NIPs[0], and many of them look blockchainy, NIP-01 is looks ultra pragmatic and simple, and is the only one that is required to be implemented, AFAIK.
[0] https://github.com/nostr-protocol/nips
-
Today I'm launching Flare, a video sharing site built on Nostr Like YouTube
For you and others following. Common in early nostr apps. The web-extension spec is defined in https://github.com/nostr-protocol/nips/blob/master/07.md. Most apps check for window.nostr, then fail silently when it's missing or blocked. There are also some popular extensions in that list.
-
RSS can be used to distribute all sorts of information
https://github.com/nostr-protocol/nips/blob/master/65.md
The TLDR is that when a Nostr client supports NIP-65, it broadcasts to all known relays (which is continually updated/expanded) the list of relays that User A posts their stuff to.
This means that as long as User B is connected to at least one of those "all known relays", their client now knows what relays User A posts their stuff to, and will specifically fetch things from those relays when it needs to load User A's things.
It's essentially the Nostr take on the Gossip protocol: https://en.wikipedia.org/wiki/Gossip_protocol
-
Ask HN: What is the next great online community?
I think your best bet here is Nostr (Notes and Other Stuff Transmitted by Relays): https://nostr.com https://github.com/nostr-protocol/nostr
Nostr isn't a federated platform like Mastodon or Lemmy, it's more similar to the AT protocol created by Bluesky, whilst being far simpler to understand and write apps using it. The nostr protocol is defined by a series of NIPs (Nostr implementation possibilites https://github.com/nostr-protocol/nips), the most basic of which can be implemented in a client or a relay in 50-100 lines of code in any modern programming language.
Each user runs a client, anyone can write a relay or run any of hundreds of existing implementations, both clients and relays can choose to support a number of NIPs. Users have a public-private keypair, and distribute notes to relays signed with their private key, which are verified by relays. Clients subscribe via websockets to any number of relays (I usually have 20-30), and receive notes from all users on those relays' databases, or filtered by the public keys of the users you're following. Relays for the most part don't communicate with each other. If you're ever blocked or banned from a relay, you'll still be able to have your notes seen as long as you have at least one relay in common with anyone who wants to see them. I run my own as well for extra resiliency.
At the moment there's ~50 standardised NIPs, which add features like likes, zaps (bitcoin tips for notes), user status, post expiration, mentions, search, DMs, and public chats. Nearly all of these are supported by popular clients and relays. While nostr is primarily used for social media at the moment, it's already possible to build upon as a protocol for pretty much any online service.
The total active user count on most public relays I'd estimate is somewhere around 500k to a million, though the nature of the protocol makes it impossible to estimate its true size. The perceived community on most relays before following anyone frankly can get pretty cancerous, mainly due to a lot of clients sorting notes by new by default, so I can only hope to high heaven it'll improve as it grows.
Though like any new non-centralised platform, it's more difficult to get started on for most non-technical users as they have to pick one of hundreds of clients to install, and requires caution to never leak your private key and be very wary of which clients you trust it with.
-
Nostr: A Decentralized Messaging Protocol
There is no "zaps balance". Zaps are just receipts of lightning payments.
The basic idea is that a lightning node will detect when the invoice with a nostr note inside is paid, and then send the receipt to nostr as a nostr note, with the original bolt11 invoice inside with the signature from the user who sent the zap.
It's all describe by NIP-57, a spec I put together to support this:
https://github.com/nostr-protocol/nips/blob/master/57.md
I was working on c-lightning at the time and I thought it would be really cool to replace the "like" button with an instant bitcoin micro-payment. I think it worked out quite well! There are many sites utilizing zaps in all aspects of the protocol, such as a decentralized market for AI job requests (data vending machines), zapgoals and zap fundraisers. All built on this note type. protocol synergy!
- Why even let users set their own passwords?
-
Where does iris upload it's images?
Take a look at NIP-23: Long-form Content https://github.com/nostr-protocol/nips/blob/master/23.md .
- Nostr NIP-05 : Mapping Nostr keys to DNS-based internet identifiers
- Greetings! I'm here to tell you about Nostr, a decentralized and censorship resistant social communication protocol that has recently added protocol level support for Moderated Communities. Developers are actively building this on Nostr and would love your help and support. Let us know what you want
- I happened to learn about Nostr by chance.
slips
-
As XRP Toolkit doesn't support Trezor, is there an alternative way to use SetRegularKey on my Trezor to be able to register for the Evernode Airdrop via Xumm?
The official SLIP-0039 standard itself confirms it is not possible to convert this mnemonic type to BIP-0039. Down in Section 9 "Compatibility with BIP-039":
-
Shamir Secret Sharing
For anybody new or returning to SSS, check out SLIP-0039: https://github.com/satoshilabs/slips/blob/master/slip-0039.m...
One of the big downsides of SSS is that it’s very raw and you have to do a lot of legwork to make it actually useable. It’s rightfully criticized for this and the argument follows the don’t roll your own crypto vein.
SLIP39 solves this by formalizing a protocol for handling SSS splits built atop standards for crypto key serialization (BIP-39). SlIP shards are unique on each generation so parties with the same underlying SSS shard can’t compare mnemonics, they’re mnemonically serialized, and have a checksum and group index metadata which makes a more sane UX possible when combining.
-
Trezor-T XMR Account Recovery (do not use, sample only)
Well every wallet chose to solve this problem independently. Trezor proposed a new standard called SLIP10 to do BIP44 type operations coins that did not use secp256k1. Problem is, there are very few utilities I've found that will do SLIP10 derivations.
-
Seed Conversion Woes
Checkout the SLIPs repo (https://github.com/satoshilabs/slips.git) and modify testvectors.py. We are going to replace the curvenames and last four show_testvectors lines with the following:
-
Reminder: Trezor Shamir Backup is fundamentally secure
They use an open source algorithm which is documented here. Anyone can verify it and the recovery outside of a Trezor hw-wallet is possible if required.
-
Article explaining how Ledger Recover works
It will be using SLIP-39, like Trezor and Electrum, or a Ledger rewrite of it. All the language about shards is straight from the SLIP39 spec.
- Is it possible to have both BTC and XMR keys stored on the same Trezor at the same time?
-
Simple sample script to dump Trezor Coinjoin taproot addresses
This was all done with the SLIP-14 seed using the passphrase coinjoin if you want to follow along.
-
Simple sample script to dump coinjoin taproot addresses
With the introduction of the new Coinjoin feature in the latest release of firmware and software, I had the need to dump some of my taproot derivations. Although blockbook can do this fine using descriptors in place of xpubs for taproot accounts, it fails on Coinjoin accounts. This is likely because SLIP-25 as 6 deep derivations while BIP-86 uses a standard derivation depth of 5.
-
coinjoin funds accessible to other wallets?
The recovery of Coinjoin accounts is described here. Accessing them outside of Trezor Suite will 100% destroy all privacy obtained since Suite is the only keeper of the anonymity set for each UTXO. Using your CJ coins outside of Suite may also erode the privacy of previous transactions using your Suite Private coins as well.
What are some alternatives?
simplex-chat - SimpleX - the first messaging network operating without user identifiers of any kind - 100% private by design! iOS, Android and desktop apps 📱!
bip39 - A web tool for converting BIP39 mnemonic codes
gotosocial - Fast, fun, small ActivityPub server.
shamir39 - Split BIP39 mnemonics using Shamir's Secret Sharing Scheme
nostr-emitter - An end-to-end group encrypted event emitter, built on the Nostr protocol.
python-shamir-mnemonic
nostream - A Nostr Relay written in TypeScript
bips - Bitcoin Improvement Proposals
awesome-nostr - nostr.net - awesome-nostr is a collection of projects and resources built on nostr to help developers and users find new things
slip39 - A web tool for SLIP39 mnemonic shares
smtp-nostr-gateway - SMTP to Nostr NIP-04 Gateway
python-mnemonic - :snake: Mnemonic code for generating deterministic keys, BIP39