npub1nq…kkz86

Join Nostr

Why Nostr? About Join Nostr

wss://relay.nostrich.de operator
pynostr dev - https://github.com/holgern/pynostr

Public Key

npub1nqu6xm23khceqjtlnvkjdrhq3yp7a3l4a5hf4c7wadwm3x4thggqjkkz86

NIP-05 Address

nostrich.de

Profile Code

nprofile1qqsfswdrd4gmtuvsf9lektfx3msgjqlwcl676t56u08wkhdcn24m5yqpzpmhxue69uhkummnw3ezuamfdejszenhwden5te0ve5kcar9wghxummnw3ezuamfdejj7mnsw43rzmn3w5m8smfjxd4kscm9w948gmrwwe4k5erjdpcnx7tsxasnxmp5vy6kse35vvmhwctywaknx7p5w35xwem3df4kk73cxclkyun0v9jxxctnws7hgun4v5pxs28s

Publishing to

nostr.wine

filter.nostr.wine/npub1nqu6xm23khceqjtlnvkjdrhq3yp7a3l4a5hf4c7wadwm3x4thggqjkkz86?broadcast=true

bitcoiner.social

relay.nostrati.com

nostr-verified.wellorder.net

relay.damus.io

Author Public Key

npub1nqu6xm23khceqjtlnvkjdrhq3yp7a3l4a5hf4c7wadwm3x4thggqjkkz86

Show more details

Last Notes

2023-09-21 11:09:47 UTC

GM, my #relay wss://relay.nostrich.de is running smoothly again, forgot to renew my certificate 🤦‍♂️

2023-03-14 21:49:00 UTC

- reply

Mostly there are stored in the content of an kind 3 event as json.

2023-03-05 11:48:33 UTC

Read an interesting Twitter thread: https://twitter.com/level39/status/1632240495396044800?t=qX8lpBQEB_C6IBBx8xILaA&s=19
from level39 (is he on nostr?).
The threat is about losing your identity when you lost access to your nsec or NIP05 domain.
I thing this will not a problem in the long run as I'm confident there will be several solutions on nostr regarding these problems (Delegation, key deriving, multisig, key invalidation, did on nostr,... to name a few solutions)

2023-02-27 13:22:24 UTC

New release 0.5.0 of pynostr
In this release the timeout parameter has moved to the class init function.
relay_manager.run_sync(timeout=2) ->
relay_manager = RelayManager(timeout=2)
relay_manager.run_sync()
and
io_loop.run_sync(r.connect, timeout=2) ->
io_loop.run_sync(r.connect)
I added a new example for sending and receiving dms:
https://void.cat/d/M7CgHTmFnAfSAfedFGiwx6.webp
https://void.cat/d/QaeXj1371iDytBMhfL31gH.webp
https://github.com/holgern/pynostr

2023-02-26 18:00:11 UTC

- reply

You can also use the following Python Script. It shows the fee for online paid relays + the number of unique pubkeys.
https://github.com/holgern/pynostr/blob/main/examples/paid_relay_users.py

2023-02-25 11:11:06 UTC

- reply

What is kind 6? It is not listed on the nip readme page.

2023-02-25 11:07:21 UTC

- reply

BASIC
Pascal
PHP
Java
Ada
C++
Bash
C
Python

2023-02-24 21:47:08 UTC

New version of my Python library pynostr is released
https://github.com/holgern/pynostr
It uses now the tornado websocket implementation. I added two examples, more will follow.

2023-02-23 13:21:07 UTC

- reply

True, at least I watched the video before posting. I forget almost all about complex numbers...

2023-02-23 13:08:05 UTC

- reply

https://www.youtube.com/watch?v=9tlHQOKMHGA&t=6s
e^(-pi/2)

2023-02-23 09:52:25 UTC

## How to setup your own relay with nip05 authentication
I'm using a contabo CLOUD VPS M with NVMe and I'm using nostr-rs-relay with sqlite.
nostr-rs-relay does not work on ubuntu 20.04, so I'm using ubuntu 22.04
I mainly followed
https://github.com/BlockChainCaffe/Nostr-Relay-Setup-Guide
Addionially I needed to install protobuf
apt install protobuf-compiler
and I added
proxy_read_timeout 1d;
proxy_send_timeout 1d;
to the nginx conf in location / { } of listen 443 SSL;
The config.toml needs to be changed and
[verified_users]
mode = "enabled"
must be added.
let me know if you have questions are getting stuck during setup.

2023-02-23 09:36:05 UTC

- reply

That happened during moving to the new server. I shortly removed the nip05 requirements for debugging.
Using nip05 works quite fine in fighting spam. Especially as I can blacklist domains.

2023-02-23 07:42:44 UTC

- reply

I will check this out, thanks.

2023-02-23 07:24:15 UTC

I just learned that the nostr-rs-relay is confused when using the same pubkey more than once in the nostr.json for NIP05 validation.
Meaning not a single of my events was stored on my on relay 😥

2023-02-23 07:04:35 UTC

- reply

He was shutted down, as he was getting to expensive.

2023-02-23 07:03:02 UTC

My relay wss://relay.nostrich.de run's now on a more powerful server. (16 GByte ram, 6 cores and NVMe). Using NVMe really makes a difference, everything is much faster than before.
There are currently some good offers from contabo.com (double amount of storage for free). They are quite cheap and a good starting point for your new relay :).

2023-02-22 10:07:29 UTC

- reply

btc-ticker.com is the correct address

2023-02-22 10:05:16 UTC

777777 on my btc-ticker (check btc-ticker.com)
https://i.imgur.com/mJrPJLJ.jpg

2023-02-18 17:10:17 UTC

- reply

I will open source the complete script, but I will first improve and test the code.
Before my script:
wss://nostr-pub.wellorder.net: 2023-02-18 06:26:05 - 320
wss://nos.lol: 2023-02-18 06:26:05 - 320
wss://relay.nostr.band: 2023-02-18 06:26:05 - 320
wss://relay.wellorder.net: 2023-02-18 06:26:05 - 320
wss://relay.lexingtonbitcoin.org: 2023-02-18 06:26:05 - 320
wss://relay.current.fyi: 2023-02-18 06:26:05 - 320
wss://relay.nostrview.com: 2023-02-18 06:26:05 - 320
wss://relay.damus.io: 2023-02-18 06:26:05 - 320
wss://nostr.wine: 2023-02-18 06:26:05 - 320
wss://nostr.globals.fans: 2023-02-18 06:26:05 - 320
wss://no.str.cr: 2023-02-18 06:26:05 - 320
wss://nproxy.kristapsk.lv: 2023-02-18 06:26:05 - 320
wss://nproxy.zerologin.co: 2023-02-18 06:26:05 - 320
wss://nostr.mom: 2023-02-14 16:07:10 - 306
wss://e.nos.lol: 2023-02-14 16:07:10 - 306
wss://knostr.neutrine.com: 2023-02-12 13:03:29 - 299
wss://nostr.radixrat.com: 2023-02-10 17:57:11 - 291
wss://nostr.einundzwanzig.space: 2023-02-06 15:19:28 - 271
wss://nostr.sg: 2023-02-06 15:19:28 - 271
wss://nostrpro.xyz: 2023-02-06 15:19:28 - 271
wss://relay.nostrati.com: 2023-02-06 14:32:12 - 270
wss://relay.nostr.scot: 2023-02-05 08:43:05 - 250
After running my script:
wss://nos.lol: 2023-02-18 06:26:05 - 320
wss://nostr-pub.wellorder.net: 2023-02-18 06:26:05 - 320
wss://nostr.einundzwanzig.space: 2023-02-18 06:26:05 - 320
wss://relay.nostr.band: 2023-02-18 06:26:05 - 320
wss://relay.nostr.scot: 2023-02-18 06:26:05 - 320
wss://nostr.mom: 2023-02-18 06:26:05 - 320
wss://relay.wellorder.net: 2023-02-18 06:26:05 - 320
wss://relay.damus.io: 2023-02-18 06:26:05 - 320
wss://relay.current.fyi: 2023-02-18 06:26:05 - 320
wss://relay.nostrview.com: 2023-02-18 06:26:05 - 320
wss://relay.nostrati.com: 2023-02-18 06:26:05 - 320
wss://relay.lexingtonbitcoin.org: 2023-02-18 06:26:05 - 320
wss://nostr.radixrat.com: 2023-02-18 06:26:05 - 320
wss://e.nos.lol: 2023-02-18 06:26:05 - 320
wss://nostr.wine: 2023-02-18 06:26:05 - 320
wss://nproxy.kristapsk.lv: 2023-02-18 06:26:05 - 320
wss://nproxy.zerologin.co: 2023-02-18 06:26:05 - 320
wss://knostr.neutrine.com: 2023-02-18 06:26:05 - 320
wss://nproxy.cc: 2023-02-18 06:26:05 - 320
wss://nostr.sg: 2023-02-18 06:26:05 - 320
wss://nostrpro.xyz: 2023-02-18 06:26:05 - 320

2023-02-18 17:06:15 UTC

- reply

Every event needs a valid signature, I'm just rebroadcasting an already signed event to relays which do not have the newest version.

2023-02-18 14:37:00 UTC

- reply

Thanks for your zap :):
This is your new list after broadcasting your newest type 3:
wss://nostr-pub.wellorder.net: 2023-02-17 22:15:54 - 665
wss://nos.lol: 2023-02-17 22:15:54 - 665
wss://nostr.einundzwanzig.space: 2023-02-17 22:15:54 - 665
wss://nostr.mom: 2023-02-17 22:15:54 - 665
wss://nostr.developer.li: 2023-02-17 22:15:54 - 665
wss://relay.nostr.scot: 2023-02-17 22:15:54 - 665
wss://relay.nostr.band: 2023-02-17 22:15:54 - 665
wss://nostr.cercatrova.me: 2023-02-17 22:15:54 - 665
wss://nostr.swiss-enigma.ch: 2023-02-17 22:15:54 - 665
wss://relay.damus.io: 2023-02-17 22:15:54 - 665
wss://nostr.hackerman.pro: 2023-02-17 22:15:54 - 665
wss://relay.nostr.ro: 2023-02-17 22:15:54 - 665
wss://nostr.vulpem.com: 2023-02-17 22:15:54 - 665
wss://relay.current.fyi: 2023-02-17 22:15:54 - 665
wss://relay.wellorder.net: 2023-02-17 22:15:54 - 665
wss://relay.plebstr.com: 2023-02-17 22:15:54 - 665
wss://knostr.neutrine.com: 2023-02-17 22:15:54 - 665
wss://nostr.bitcoin-21.org: 2023-02-17 22:15:54 - 665
wss://nostr.blocs.fr: 2023-02-17 22:15:54 - 665
wss://nostr.radixrat.com: 2023-02-17 22:15:54 - 665
wss://relay.austrich.net: 2023-02-17 22:15:54 - 665
wss://nostr.bostonbtc.com: 2023-02-17 22:15:54 - 665
wss://relay.nostrview.com: 2023-02-17 22:15:54 - 665
wss://nostr.sidnlabs.nl: 2023-02-17 22:15:54 - 665
wss://nostr.inosta.cc: 2023-02-17 22:15:54 - 665
wss://relay.nostrati.com: 2023-02-17 22:15:54 - 665
wss://lbrygen.xyz: 2023-02-17 22:15:54 - 665
wss://nostr.rdfriedl.com: 2023-02-17 22:15:54 - 665
wss://e.nos.lol: 2023-02-17 22:15:54 - 665
wss://relay.orangepill.dev: 2023-02-17 22:15:54 - 665
wss://nproxy.kristapsk.lv: 2023-02-17 22:15:54 - 665
wss://nostr.wine: 2023-02-17 22:15:54 - 665
wss://nostr.relayer.se: 2023-02-13 15:58:54 - 22
wss://relay.nostrich.de: 2023-02-01 12:25:04 - 408
wss://nostr.coollamer.com: 2023-01-23 22:33:18 - 212
wss://relay.nostr.info: 2023-01-21 06:15:08 - 98

2023-02-18 14:27:51 UTC

- reply

wss://nos.lol: 2023-02-17 22:15:54 - 665
wss://relay.nostr.band: 2023-02-17 22:15:54 - 665
wss://relay.austrich.net: 2023-02-17 22:15:54 - 665
wss://relay.nostrview.com: 2023-02-17 22:15:54 - 665
wss://nostr.inosta.cc: 2023-02-17 22:15:54 - 665
wss://relay.nostrati.com: 2023-02-17 22:15:54 - 665
wss://nproxy.kristapsk.lv: 2023-02-17 22:15:54 - 665
wss://nostr.wine: 2023-02-17 22:15:54 - 665
wss://relay.damus.io: 2023-02-17 22:15:54 - 665
wss://nproxy.zerologin.co: 2023-02-17 22:15:54 - 665
wss://relay.current.fyi: 2023-02-17 22:15:54 - 665
wss://nostr.mom: 2023-02-17 22:03:29 - 660
wss://e.nos.lol: 2023-02-17 22:03:28 - 659
wss://nostr-pub.wellorder.net: 2023-02-15 21:35:35 - 609
wss://relay.wellorder.net: 2023-02-15 21:35:35 - 609
wss://nostr.blocs.fr: 2023-02-15 21:35:35 - 609
wss://nostr.sandwich.farm: 2023-02-15 21:35:35 - 609
wss://lbrygen.xyz: 2023-02-15 08:13:38 - 607
wss://nostr.developer.li: 2023-02-13 16:10:01 - 602
wss://nostr.swiss-enigma.ch: 2023-02-13 16:10:01 - 602
wss://nostr.cercatrova.me: 2023-02-13 16:10:01 - 602
wss://nostr.relayer.se: 2023-02-13 15:58:54 - 22
wss://nostr.beta3.dev: 2023-02-13 15:58:54 - 22
wss://nr.yay.so: 2023-02-13 15:58:54 - 22
wss://knostr.neutrine.com: 2023-02-12 12:30:57 - 0
wss://nostr.radixrat.com: 2023-02-12 10:28:21 - 0
wss://nostr.bostonbtc.com: 2023-02-10 09:42:12 - 479
wss://nostr.sidnlabs.nl: 2023-02-09 11:04:55 - 522
wss://nostr.bitcoin-21.org: 2023-02-07 21:59:43 - 504
wss://relay.plebstr.com: 2023-02-06 16:12:10 - 480
wss://relay.nostr.ro: 2023-02-04 16:54:53 - 427
wss://relay.nostrich.de: 2023-02-01 12:25:04 - 408
wss://nostr.rdfriedl.com: 2023-01-27 23:49:14 - 403
wss://relay.nostr.scot: 2023-01-25 21:39:53 - 383
wss://nostr.hackerman.pro: 2023-01-25 12:33:37 - 377
wss://nostr.vulpem.com: 2023-01-23 22:33:18 - 212
wss://nostr.coollamer.com: 2023-01-23 22:33:18 - 212
wss://relay.nostr.info: 2023-01-21 06:15:08 - 98
----
newest event 2023-02-17 22:15:54 - 665
most follower 2023-02-17 22:15:54 - 665

2023-02-18 14:17:52 UTC

- reply

After an relay url, you see the event date followed by my following count.

2023-02-18 14:17:01 UTC

I finished my first useful python script, using my pynostr python library.
The script fetches the complete list of relays from https://api.nostr.watch/v1/online and requests from all relays my CONTACTS event.
Then the script checks if date and the follower count.
Finally the newest event is broadcasted to all relays that have a old version of my contact list. The best part is that my script does not need a private key.
Before:
wss://nos.lol: 2023-02-18 09:24:26 - 271
wss://nostr-pub.wellorder.net: 2023-02-05 15:17:34 - 205
wss://nostr.hackerman.pro: 2023-01-12 13:15:32 - 48
wss://relay.nostr.scot: 2023-02-05 10:52:12 - 204
wss://relay.nostr.band: 2023-02-18 09:24:26 - 271
wss://nostr.swiss-enigma.ch: 2023-01-11 15:34:37 - 17
wss://nostr.cercatrova.me: 2023-01-11 15:34:37 - 17
wss://relay.damus.io: 2023-02-18 09:24:26 - 271
wss://relay.current.fyi: 2023-02-18 09:24:12 - 264
wss://nostr-relay.digitalmob.ro: 2022-12-18 20:23:21 - 1
wss://nostr-verif.slothy.win: 2022-12-18 20:23:21 - 1
wss://relay.nostrich.de: 2023-02-18 09:24:26 - 271
wss://relay.wellorder.net: 2023-02-05 15:17:34 - 205
wss://nostr.coinos.io: 2023-01-12 13:15:32 - 48
wss://relay.austrich.net: 2023-02-18 09:23:32 - 255
wss://relay.nostrview.com: 2023-02-18 09:23:32 - 255
wss://relay.nostrati.com: 2023-02-18 09:23:32 - 255
wss://nostr.radixrat.com: 2023-02-10 09:06:31 - 213
wss://knostr.neutrine.com: 2023-02-12 13:50:35 - 219
wss://relay-pub.deschooling.us: 2023-01-16 11:36:50 - 91
wss://nostr.bostonbtc.com: 2023-02-10 09:06:31 - 213
wss://nostr.rdfriedl.com: 2023-01-27 19:45:06 - 171
wss://nproxy.kristapsk.lv: 2023-02-18 09:24:26 - 271
wss://relay.orangepill.dev: 2023-02-18 09:23:32 - 255
wss://nostr.wine: 2023-02-18 09:24:26 - 271
wss://atlas.nostr.land: 2023-01-27 19:45:06 - 171
wss://no.str.cr: 2023-02-18 09:24:26 - 271
wss://offchain.pub: 2023-02-16 20:50:23 - 250
wss://nr.yay.so: 2022-12-18 20:23:21 - 1
wss://nproxy.zerologin.co: 2023-02-18 09:24:26 - 271
After:
wss://nostr-pub.wellorder.net: 2023-02-18 09:24:26 - 271
wss://nos.lol: 2023-02-18 09:24:26 - 271
wss://nostr-verif.slothy.win: 2022-12-18 20:23:21 - 1
wss://relay.nostrich.de: 2023-02-18 09:24:26 - 271
wss://relay.nostr.band: 2023-02-18 09:24:26 - 271
wss://relay.nostr.scot: 2023-02-18 09:24:26 - 271
wss://relay.wellorder.net: 2023-02-18 09:24:26 - 271
wss://nostr.cercatrova.me: 2023-02-18 09:24:26 - 271
wss://nostr.swiss-enigma.ch: 2023-02-18 09:24:26 - 271
wss://relay.austrich.net: 2023-02-18 09:24:26 - 271
wss://relay.nostrview.com: 2023-02-18 09:24:26 - 271
wss://nostr.hackerman.pro: 2023-02-18 09:24:26 - 271
wss://relay.nostrati.com: 2023-02-18 09:24:26 - 271
wss://nostr.bostonbtc.com: 2023-02-18 09:24:26 - 271
wss://relay.damus.io: 2023-02-18 09:24:26 - 271
wss://relay.current.fyi: 2023-02-18 09:24:26 - 271
wss://knostr.neutrine.com: 2023-02-18 09:24:26 - 271
wss://relay-pub.deschooling.us: 2023-02-18 09:24:26 - 271
wss://relay.orangepill.dev: 2023-02-18 09:24:26 - 271
wss://nostr.radixrat.com: 2023-02-18 09:24:26 - 271
wss://nostr.rdfriedl.com: 2023-02-18 09:24:26 - 271
wss://nostr.wine: 2023-02-18 09:24:26 - 271
wss://nostr.coinos.io: 2023-02-18 09:24:26 - 271
wss://nproxy.kristapsk.lv: 2023-02-18 09:24:26 - 271
wss://no.str.cr: 2023-02-18 09:24:26 - 271
wss://offchain.pub: 2023-02-16 20:50:23 - 250
wss://nproxy.zerologin.co: 2023-02-18 09:24:26 - 271
wss://relay.nostr.bg: 2023-02-16 20:50:23 - 250
wss://nproxy.zerologin.co: 2023-02-18 09:24:26 - 271
Let me know if I should run your pubkey

2023-02-18 07:34:10 UTC

- reply

How is the nsec stored? Is it stored in only locally on the in phone?

2023-02-12 21:16:43 UTC

If you are looking for a working nostr Python library take a look at https://github.com/holgern/pynostr
Version 0.2.0 with a first implementation of a tornado based relay client have been released.

2023-02-11 09:28:33 UTC

- reply

Thanks, I ⚡ you but it doesn't show up below your post on snort. Though it works like on the damus client.

2023-02-11 08:50:01 UTC

How do a client know which relays I'm using? I checked the NIP definitions but I did not found something.
It does not work on each client, but snort and amethyst are supporting this.
There is NIP-65 with kind 10002, but it is not used yet.
Any ideas?

2023-02-05 11:09:40 UTC

- reply

On snort.social I can see all your 224 followers and 220 followings.

2023-01-28 16:31:30 UTC

- reply

Have you checked if the wrong lightning address was used by another account?
It could be that your metadata were mixed up with some random account due to a bug in a client.

2023-01-27 11:24:06 UTC

Hi #[0]
can you help me with encrypted messages? In the example in https://github.com/nostr-protocol/nips/blob/master/04.md it says:
let sharedPoint = secp.getSharedSecret(ourPrivateKey, '02' + theirPublicKey)
But what is happening when the actual prefix of theirPublicKey was '03'? I think we will then calculate the wrong shared_secret.
As I understand from https://crypto.stackexchange.com/questions/103442/convert-a-schnorr-public-key-to-a-compressed-ecdsa-public-key
I need the private key to convert a BIP0340 Public key into a secp256k1 ECDSA public key:
BIP0340 to ECDSA: Find out if the associated private key produces a correct or incorrect implicit y
-coordinate. If correct prepend 0x02; if incorrect prepend 0x03.
But as I do not have the private key, how can I assume it is always 02?
For example:
bob_priv = "4138d1b6dde34f81c38cef2630429e85847dd5b70508e37f53c844f66f19f983"
When I create the ECDSA Pubkey it is:
bob_pub = "03a1db8e8b047e1350958a55e0a853151d0e1f685fa5cf3772e01bccc5aa5cb2eb"
When I convert it into the BIP0340 key it will be:
bob_pub_340 = "a1db8e8b047e1350958a55e0a853151d0e1f685fa5cf3772e01bccc5aa5cb2eb"
If I use bob_pub_340 for creating a shared secret, I assuming a prefix of "02 " and build the wrong shared secret.
I'm confused now.

2023-01-23 21:47:30 UTC

- reply

Amethyst rocks, kiwi Browser + nos2x extension+ snort.social is also great.

2023-01-22 07:23:57 UTC

- reply

I have the same problem as well.

2023-01-21 14:48:58 UTC

What is the best websocket client library for python?
* tornado
* websocket-client
* websockets + asyncio

2023-01-19 16:22:17 UTC

- reply

Happened to me just this second.
A second confirmation would be great.

2023-01-19 16:14:20 UTC