NIP-69 Peer-to-peer Order events draft optional Abstract Peer-to-peer (P2P) platforms have seen an upturn in recent years, while having more and more options is positive, in the specific case of p2p, having several options contributes to the liquidity split, meaning sometimes there’s not enough assets available for trading. If we combine all these individual solutions into one big pool of orders, it will make them much more competitive compared to centralized systems, where a single authority controls the liquidity.

NIP-60 Cashu Wallet draft optional This NIP defines the operations of a cashu-based wallet. A cashu wallet is a wallet which information is stored in relays to make it accessible across applications. The purpose of this NIP is: ease-of-use: new users immediately are able to receive funds without creating accounts with other services. interoperability: users’ wallets follows them across applications. This NIP doesn’t deal with users’ receiving money from someone else, it’s just to keep state of the user’s wallet.

NIP-61: Nut Zaps A Nut Zap is a P2PK cashu token where the payment itself is the receipt. High-level flow Alice wants to nutzap 1 sat to Bob because of an event event-id-1 she liked. Alice nutzaps Bob Alice fetches event kind:10019 from Bob to see the mints Bob trusts. She mints a token at that mint (or swaps some tokens she already had in that mint) p2pk-locked to the pubkey Bob has listed in his kind:10019.

NIP-73 External Content IDs draft optional There are certain established global content identifiers such as Book ISBNs , Podcast GUIDs , and Movie ISANs that are useful to reference in nostr events so that clients can query all the events assosiated with these ids. i tags are used for referencing these external content ids, with k tags representing the external content id kind so that clients can query all the events for a specific kind.

NIP-70 Protected Events draft optional When the "-" tag is present, that means the event is “protected”. A protected event is an event that can only be published to relays by its author. This is achieved by relays ensuring that the author is authenticated before publishing their own events or by just rejecting events with ["-"] outright. The default behavior of a relay MUST be to reject any event that contains ["-"].

NIP-55 Android Signer Application draft optional This NIP describes a method for 2-way communication between an Android signer and any Nostr client on Android. The Android signer is an Android Application and the client can be a web client or an Android application. Usage for Android applications The Android signer uses Intents and Content Resolvers to communicate between applications. To be able to use the Android signer in your application you should add this to your AndroidManifest.

NIP-54 Wiki draft optional This NIP defines kind:30818 (an addressable event) for descriptions (or encyclopedia entries) of particular subjects, and it’s expected that multiple people will write articles about the exact same subjects, with either small variations or completely independent content. Articles are identified by lowercase, normalized ascii d tags. Articles { "content": "A wiki is a hypertext publication collaboratively edited and managed by its own audience.", "tags": [ ["d", "wiki"], ["title", "Wiki"], ] } d tag normalization rules Any non-letter character MUST be converted to a -.

NIP-34 git stuff draft optional This NIP defines all the ways code collaboration using and adjacent to git can be done using Nostr. Repository announcements Git repositories are hosted in Git-enabled servers, but their existence can be announced using Nostr events, as well as their willingness to receive patches, bug reports and comments in general. { "kind": 30617, "content": "", "tags": [ ["d", "<repo-id>"], // usually kebab-case short name ["name", "<human-readable project name>"], ["description", "brief human-readable project description>"], ["web", "<url for browsing>", .

Introduction In the ever-evolving landscape of cybersecurity, selecting the right encryption algorithm is crucial for safeguarding sensitive information. Three prominent contenders in the encryption arena are SM1, SM4, and AES (Advanced Encryption Standard). This article aims to provide a comprehensive comparison of these encryption algorithms based on their security, vulnerability, and performance characteristics. What is SM1 SM1 refers to the first encryption algorithm in a series of cryptographic algorithms specified by the Chinese State Cryptography Administration (SCA).

NIP-92 Media Attachments Media attachments (images, videos, and other files) may be added to events by including a URL in the event content, along with a matching imeta tag. imeta (“inline metadata”) tags add information about media URLs in the event’s content. Each imeta tag SHOULD match a URL in the event content. Clients may replace imeta URLs with rich previews. The imeta tag is variadic, and each entry is a space-delimited key/value pair.

NIP-49 Private Key Encryption draft optional This NIP defines a method by which clients can encrypt (and decrypt) a user’s private key with a password. Symmetric Encryption Key derivation PASSWORD = Read from the user. The password should be unicode normalized to NFKC format to ensure that the password can be entered identically on other computers/clients. LOG_N = Let the user or implementer choose one byte representing a power of 2 (e.

NIP-96 HTTP File Storage Integration draft optional Introduction This NIP defines a REST API for HTTP file storage servers intended to be used in conjunction with the nostr network. The API will enable nostr users to upload files and later reference them by url on nostr notes. The spec DOES NOT use regular nostr events through websockets for storing, requesting nor retrieving data because, for simplicity, the server will not have to learn anything about nostr relays.

NIP-64 Chess (Portable Game Notation) draft optional This NIP defines kind:64 notes representing chess games in PGN format, which can be read by humans and is also supported by most chess software. Note Content The .content of these notes is a string representing a PGN-database . Notes { "kind": 64, "content": "1. e4 *", // other fields... } { "kind": 64, "tags": [ ["alt", "Fischer vs. Spassky in Belgrade on 1992-11-04 (F/S Return Match, Round 29)"], // rest of tags.

NIP-44 Encrypted Payloads (Versioned) optional The NIP introduces a new data format for keypair-based encryption. This NIP is versioned to allow multiple algorithm choices to exist simultaneously. This format may be used for many things, but MUST be used in the context of a signed event as described in NIP 01. Note: this format DOES NOT define any kinds related to a new direct messaging standard, only the encryption required to define one.

NIP-71 Video Events draft optional This specification defines video events representing a dedicated post of externally hosted content. These video events are addressable and delete-requestable per NIP-09 . Unlike a kind 1 event with a video attached, Video Events are meant to contain all additional metadata concerning the subject media and to be surfaced in video-specific clients rather than general micro-blogging clients. The thought is for events of this kind to be referenced in a Netflix, YouTube, or TikTok like nostr client where the video itself is at the center of the experience.

NIP-29 Relay-based Groups draft optional This NIP defines a standard for groups that are only writable by a closed set of users. They can be public for reading by external users or not. Groups are identified by a random string of any length that serves as an id. There is no way to create a group, what happens is just that relays (most likely when asked by users) will create rules around some specific ids so these ids can serve as an actual group, henceforth messages sent to that group will be subject to these rules.

Trusted Platform Module (TPM) is a crucial hardware-based security feature that plays a key role in securing computing platforms. TPM comes in different versions, with TPM 1.2 and TPM 2.0 being two significant iterations. In this comparison, we’ll explore the differences between TPM 1.2 and TPM 2.0, focusing on security, performance, and compatibility. TPM Evolution History 1999-2000: Inception The concept of a hardware-based security module for computers was first proposed in the late 1990s.

Introduction to LUKS: Linux Unified Key Setup Overview Linux Unified Key Setup (LUKS) is a widely adopted standard for disk encryption on Linux systems. Introduced in 2004, LUKS provides a robust framework for securing data at rest by encrypting entire block devices. It serves as a disk encryption specification that standardizes key management, allowing users to encrypt partitions or entire storage devices with ease. Key Features LUKS offers several key features that make it a popular choice for implementing disk encryption:

LUKS vs VeraCrypt Introduction The landscape of disk encryption offers various solutions, and two prominent contenders are LUKS (Linux Unified Key Setup) and VeraCrypt. This article aims to provide an in-depth comparison between LUKS and VeraCrypt, considering aspects such as security, performance, and cross-platform support. LUKS vs VeraCrypt Security LUKS (Linux Unified Key Setup) Strengths: Proven Security: LUKS has a well-established reputation for providing robust security on Linux systems. Multiple Key Slots: Supports multiple key slots, allowing users to utilize different passphrases or key files, enhancing security.

A Comparative Analysis of AES Rijndael and Serpent Encryption Algorithms Introduction In the ever-evolving landscape of cybersecurity, encryption plays a pivotal role in safeguarding sensitive information from unauthorized access. Two prominent contenders in the realm of symmetric key encryption algorithms are AES (Advanced Encryption Standard) Rijndael and Serpent. Both algorithms have been recognized for their robust security features, but they differ in their design philosophies, key strengths, and potential vulnerabilities. This article aims to provide a comparative analysis of AES Rijndael and Serpent to help readers make informed decisions about their encryption needs.

AES Rijndael and Twofish Encryption Algorithms Introduction In the realm of symmetric key encryption, AES Rijndael and Twofish are two notable algorithms recognized for their security and versatility. This article aims to provide a comprehensive comparison of these encryption schemes, delving into aspects such as security, performance, and their resilience against quantum attacks. Background AES Rijndael Origin and Standardization: Developed by Vincent Rijmen and Joan Daemen, AES Rijndael became the official encryption standard by NIST in 2001.

SHA-1 vs MD5 Introduction SHA-1 and MD5 are both widely used cryptographic hash functions, each serving various purposes in the field of information security. This article provides a comprehensive comparison of SHA-1 and MD5, focusing on security, performance, and their susceptibility to quantum attacks. Background SHA-1 (Secure Hash Algorithm 1): Origin and Purpose: Developed by the National Security Agency (NSA), SHA-1 is designed to produce a 160-bit hash value. It has been widely used for integrity verification and digital signatures.

SHA-1 vs RIPEMD-160 Introduction SHA-1 and RIPEMD-160 are both cryptographic hash functions widely used for various security applications. This article aims to provide a comprehensive comparison of these hash functions, focusing on security, performance, and their susceptibility to quantum attacks. Background SHA-1 (Secure Hash Algorithm 1) Origin and Purpose: Developed by the National Security Agency (NSA), SHA-1 produces a 160-bit hash value and is widely used for integrity verification and digital signatures.

NIP-84 Highlights draft optional This NIP defines kind:9802, a “highlight” event, to signal content a user finds valuable. Format The .content of these events is the highlighted portion of the text. .content might be empty for highlights of non-text based media (e.g. NIP-94 audio/video). References Events SHOULD tag the source of the highlight, whether nostr-native or not. a or e tags should be used for nostr events and r tags for URLs.

In the realm of Virtual Private Networks (VPNs), OpenVPN and WireGuard stand out as two prominent solutions. Each has its strengths and weaknesses, making them suitable for different use cases. In this article, we will delve into a comparative analysis of OpenVPN and WireGuard, focusing on key aspects such as security, speed, and resource usage. Security OpenVPN OpenVPN is renowned for its robust security features. It employs the OpenSSL library for encryption and supports various cryptographic algorithms.

Introduction In the age of digital transformation, the security of information has never been more critical. With the growing number of cyber threats and the increasing reliance on digital communication, cryptographic algorithms play a pivotal role in safeguarding sensitive data. One such algorithm making waves in the world of cryptography is the Kyber algorithm. Developed as part of the NIST Post-Quantum Cryptography Standardization project, Kyber represents a significant step forward in securing our digital world.

NIP-24 Extra metadata fields and tags draft optional This NIP defines extra optional fields added to events. kind 0 These are extra fields not specified in NIP-01 that may be present in the stringified JSON of metadata events: display_name: an alternative, bigger name with richer characters than name. name should always be set regardless of the presence of display_name in the metadata. website: a web URL related in any way to the event author.

Introduction In today’s digital age, surveys, quizzes, and data collection are integral to various aspects of our personal and professional lives. To streamline these processes, Google Forms and Microsoft Forms have emerged as two powerful tools, each with its own set of features and advantages. In this article, we will compare Google Forms and Microsoft Forms to help you make an informed choice based on your specific needs. 1. User Interface and Accessibility Google Forms:

NIP-75 Zap Goals draft optional This NIP defines an event for creating fundraising goals. Users can contribute funds towards the goal by zapping the goal event. Nostr Event A kind:9041 event is used. The .content contains a human-readable description of the goal. The following tags are defined as REQUIRED. amount - target amount in milisats. relays - a list of relays the zaps to this goal will be sent to and tallied from.

What is Authenticated Encryption Authenticated encryption is a cryptographic technique that combines both data encryption and message authentication into a single operation. It ensures not only the confidentiality of data but also its integrity, effectively protecting against unauthorized access and tampering. By incorporating encryption and message authentication codes (MACs) together, authenticated encryption guarantees that not only is the information kept secret from unauthorized parties, but any modifications or alterations to the data can be detected, preventing malicious manipulation.