100,000 is Muôn in Việtnam . So, 100,000,000 is 1k muôn

1 bitcoin is 1k muôn satoshi 🫡🇻🇳

aisan cultures do orders of 10 in groups of four instead of three.

so western is thousand, million, billion and so on, which are 10^3

east Asian is by 10^4, so the word for 10,000 is mahn in Korean, and 100,000 is 10 mahn and so on.

maybe the reason we have 100,000,000 sartoshis per BTC is because Satoshi was east Asian. 10^8 is much more natural in those cultures.

Ok, let's see if you folks can help. I need to find the npub of two of our translators so that I can create a zap split with them for the next release.

I only have their Crowdin names:

- राजಐயர் (rajs19420616), translates to Hindi

- Maxblake, translates to Polish, but he seems to be a web dev living in London

They must have npubs but those npubs might not be super active.

First to find gets 25,000 SATS each

Not your VPN, not your privacy.

Scatter ecash Sats across the whole internet.

Is there a nostr-based web archive thingy? #asknostr

Sending and receiving ecash sats on Keychat is as simple as sending a picture.

It's the ideal channel for sending ecash sats.

the “ecash as postage stamp for relays” idea seems like a major innovation that applies outside of DMs. have you discussed your plans of this with other clients/relays (e.g. for public posting). how do you think about storage commitments for the value of the stamp?

Keychat and Damus are both applications based on the Nostr protocol. What are the design differences between Keychat, as an application for posting private notes, and Damus, as an application for posting public notes?

In our view, the Nostr protocol has three main innovative points. First, it boldly allows users to use public keys directly as IDs. Second, it has chosen a relay model where relays do not communicate with each other. Third, it is equivalent to having built-in RSS.

For Keychat, it utilizes Nostr’s public keys as identities and the relay model but does not use the built-in RSS. Keychat’s contact list is only saved locally for better privacy.

Keychat has implemented three unique designs.

To address the issue of message encryption security, Keychat employs the Signal protocol to achieve end-to-end encryption.

To tackle metadata privacy issues, Keychat separates the sending and receiving addresses from the ID and continuously updates these addresses.

To ensure that relays can operate sustainably, Keychat uses Bitcoin ecash as postage stamp for messages.

Hal Finney's idea and Bitcoin ecash will be increasingly discussed. nostr:note1h4896wrkwvewrsr3de7tdgj88mmzu5ehxapwjwt9p3z64xhaukqs2ajsyt

There is a type of solution that initially seems hard to conceive, but once disclosed, almost everyone can verify that it's a good solution. These solutions are not particularly complex; they are simply overlooked. This might be what is referred to as insight. We believe that Keychat's use of Bitcoin ecash as postage for messages and the separation of sending and receiving addresses from the ID, with continuous updates, are examples of such insights. They are easily verifiable because they are simple. nostr:note1f6vw6cvnp0mt4s3nwakahffwf3qvh4z49kvt93l9gmqy9jpwd2ksfggmq6

The vast majority of Bitcoiners are not programmers, but they understand the various macro-level designs of Bitcoin. Therefore, we continuously write notes here to help more people understand how a good chat application should be designed. Understanding what constitutes good chat app design does not require you to be a programmer.

This is also a form of "don't trust, verify."

Good money is important, and good communication is also important. nostr:note1fvh6lxjhq07wlxtlrz89n4fh5tlentyvyk5sapknza9u73ylt4hqjg75hv

Keychat will be open-sourced, and we hope to establish a community-recognized Keychat NIP. nostr:note1d09njd8cs995m5zhev6l247uaq9vgrlnvv94vlrz0xa05xcywsvs8afpee

Public key cryptography has been around for nearly 50 years, and we are finally beginning to build the internet using public keys as IDs—not only for social networks, not only for the web, but for the entire internet. nostr:note12fgl8h8jmtjy7rnstm7zyzsl0mfej7663emksc4pygdsv75xqj2swtpuh9

Sorry!

I can't understand why I should pay for messages when I can send messages for free, for example through SimpleX or Briar?

Perhaps you meant that when sending messages with stamps, the relay will have an incentive to work and not interfere with sending encrypted messages? And there might even be special relays?

When we started conceptualizing Keychat, we aimed to design a chat application that surpasses Signal. Our design process was divided into four steps.

First, Keychat addresses issues of user sovereignty. It opts to use Nostr public keys as IDs and Nostr relays for message transmission. Users fully own their IDs, which are not registered on any server. They can choose which relays to use.

Second, Keychat aims to solve the security issue of message encryption by implementing end-to-end encryption that ensures both forward secrecy and backward secrecy. Keychat implements the Signal protocol (X3DH and the Double Ratchet algorithm) on the client side without the need for a coordination server. Existing Nostr relays only need to handle the transmission of encrypted messages.

Third, Keychat tackles the problem of metadata privacy. A major issue with original Nostr DMs is that metadata is not only exposed to relay operators but also to other users. Keychat separates the sending address and receiving addresses from the ID, updating these addresses for almost every message. Thus, each Keychat message is nearly independent.

Lastly, Keychat addresses the issue of user payments and relay charges. Since each message is not linked to an ID, traditional payment models are not feasible. Initially, we thought of having relays issue one-time anonymous access tokens that users could purchase and use for anonymous pay-per-use. Later, we realized that using Bitcoin ecash as postage for messages would be a better solution.

Ultimately, we designed a chat application where users maintain sovereignty, messages are securely encrypted, metadata privacy is preserved, and the economic model is straightforward and reliable. nostr:note1kr8nvdlhz207rq6z300xy6qylf9mmpgjxgfq6925vkez4f3ej3gqh5f0te