Yuki Kishimoto

GitHub: https://github.com/yukibtc
PGP: 86F3 105A DFA8 AB58 7268 DCD7 8D3D CD04 2496 19D1

Public Key

npub1drvpzev3syqt0kjrls50050uzf25gehpz9vgdw08hvex7e0vgfeq0eseet

NIP-05 Address

Profile Code

nprofile1qqsx3kq3vkgczq9hmfplc28h687py42yvms3zkyxh8nmkvn0vhkyyuspp4mhxue69uhkummn9ekx7mqpr9mhxue69uhhyetvv9ujuun909sjuum49a5kucn00qq36amnwvaz7tmjv4kxz7fwdehhxarj9emkjun9v3hx2apwdfcqzxthwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mgpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgswaehxw309ahx7um5wgh8w6twv5898dln

Publishing to

nos.lol

relay.reya.su/inbox

relay.nostr.wirednet.jp

pyramid.fiatjaf.com

relay.primal.net

nostr.wine

Author Public Key

npub1drvpzev3syqt0kjrls50050uzf25gehpz9vgdw08hvex7e0vgfeq0eseet

Show more details

Last Notes

2026-10-17 06:52:22 UTC

A security update is available for anyone using `negentropy` by NostrDevKit.
Please update to v0.4.4 or v0.5.2
https://github.com/nostrdevkit/negentropy/security/advisories/GHSA-jcg8-qg98-373g
Thanks to @nprofile…g58a for finding and fixing the vulnerability.
#nostrdevkit #rustnostr #rust

2026-08-17 16:33:12 UTC

- reply

Probably in case it gets leaked.
Rumor leaked -> no signature
Seal leaked -> randomized timestamp

2026-08-17 11:53:04 UTC

- reply

As per NIP-59, the rumor should use the current timestamp, while the other timestamps should be tweaked: https://github.com/nostr-protocol/nips/blob/2ab507db107d0af2aa9a61327151799a1ad2d491/59.md#other-considerations
But yeah, I can add that option.

2026-07-27 16:07:31 UTC

- reply

I've published the patch, make sure to use universal-time v0.3.1

2026-07-27 15:58:10 UTC

- reply

I've found the issue, I'll publish the patch soon

2026-07-27 10:06:57 UTC

- reply

Yes, in no_std or WASM you have to define a time provider. You can find an example here: https://github.com/shadowylab/universal-time#with-no_std-or-wasm-unknown
The example just set a fake time, in your app you can get the real one using instant or webtime.

2026-07-26 16:39:11 UTC

- reply

It should be fixed here: https://github.com/nostrdevkit/nostr/pull/1400

2026-07-25 21:55:55 UTC

A security update is available for anyone using NIP-44 in the NostrDevKit (formerly rust-nostr) libraries.
Please update to v0.44.5 or, if you’re on the pre-release, to v0.45.0-alpha.5
https://github.com/nostrdevkit/nostr/security/advisories/GHSA-hrqp-8w79-gwgw
#nostrdevkit #rustnostr #rust

2026-07-18 07:23:09 UTC

- reply

Thanks, I'll fix this in the next few days

2026-07-17 12:40:51 UTC

- reply

It supports WASM, are you compiling it from macOS?
https://github.com/nostrdevkit/nostr/tree/master/crates/nostr#wasm32-unknown-unknown

2026-07-16 17:16:57 UTC

- reply

We've removed it (getrandom + wasm_js feature) because in some context was causing issues (wasm32-unknown-unknown used outside JS).
You can solve the issue by adding the getrandom dep in your Cargo.toml, and enable the wasm_js feature. Make sure to do it for the right getrandom version(s), which can be found in the Cargo.lock

2026-07-03 12:37:08 UTC

- reply

I've checked the `libnostr_sdk_ffi.so` libraries used in the KMP package and they seem to be correctly aligned:
```text
LOAD off 0x0000000000000000 vaddr 0x0000000000000000 paddr 0x0000000000000000 align 2**14
LOAD off 0x000000000032f3c0 vaddr 0x00000000003333c0 paddr 0x00000000003333c0 align 2**14
```
Have you tried verifying whether the APK itself is aligned? From my understanding, the ELF files can be correctly aligned but still be packaged incorrectly inside the APK:
```bash
$ANDROID_HOME/build-tools/<version>/zipalign -c -P 16 -v 4 app-release.apk
```

2026-07-03 10:29:46 UTC

- reply

Yeah, it's enabled: https://github.com/rust-nostr/nostr-sdk-ffi/blob/master/.cargo/config.toml#L12

2026-06-27 16:05:28 UTC

- reply

auth-required*

2026-06-27 15:45:32 UTC

- reply

I don't see the “auth-request: ...”. Is the relay including it in the CLOSED msg?

2026-06-27 13:25:07 UTC

- reply

I've pushed a patch in master branch (also in FFI)

2026-06-20 10:41:12 UTC

rust-nostr v0.45.0-alpha.2 is out for testing!
This alpha includes a major API redesign and several improvements.
Still WIP, feedback is welcome before the final release.
#rustnostr #rust-nostr #nostr #rustlang #rust

2026-05-17 07:33:03 UTC

- reply

Some of the APIs were not designed as well as they should have been. We’re redesigning and refining them with v1.0 in mind (no ETA yet)

2026-05-08 10:46:50 UTC

- reply

I just took a quick look, and I think the problem is that the relays being added with NONE capabilites. This means they can't do anything (neither read nor write).
Unless you want to use specific capabilities, you can omit that argument in addRelay, so they will be added with the default capabilities (READ + WRITE).

2026-05-08 09:40:59 UTC

- reply

Have you a small example to reproduce it?

2026-04-27 06:48:52 UTC

- reply

I've already adapted FFI APIs but not released anything yet. There are still a some things to rework before the next release.
I think if you fork the repo, you should be able to run the workflow for building them by yourself:
Fork the repo -> Go to "Actions" -> Select the "Publish" workflow -> Click on "Run workflow" -> Select the commit to use, deselect everything except "Build KMP" (the "Swift package version" can be empty) and DON'T select "Publish" -> Run it and you'll find the AAR in the artifacts (called nostr-sdk-ffi-kmp-aar).
Compilation can be done also locally, but unfortunately requires macos as it needs binaries also for iOS, and I didn't found a way to cross-compile them from Linux.
https://github.com/rust-nostr/nostr-sdk-ffi/commit/72c07c61b460c701dcfc93d51bc83e4a1c5eb689

2026-04-04 06:46:28 UTC

👀
https://github.com/rust-nostr/nostr-scrolls
By @nprofile…rsym

2026-02-20 08:53:27 UTC

- reply

I've published a NIP-17 event with the key in the nostrsdk-debug repo, and now REQ receives that event from auth.nostr1.com
So there were probably no events published for that key on that relay

2026-02-18 10:37:06 UTC

- reply

I've checked this but I can't reproduce the issue. I've tried both the auto-auth implementation and the manual one, and both successfully send the REQ after the AUTH and receive the EOSE.
To debug the messages that the client send, you have to enable the debug level: "RUST_LOG=debug cargo run"
You must enable the "env-filter" feature for the tracing-subscriber dependency, to be able use RUST_LOG

2026-02-17 16:23:24 UTC

- reply

The URL in the AdmitPolicy is to let you know from with relay the AUTH request is coming.
You don't have to add it, it's added by the SDK.

2026-02-14 09:36:25 UTC

- reply

Done at https://github.com/rust-nostr/nostr/commit/07de813024f930803a1dd81942edb50eb8a87ba3

2026-02-13 08:07:11 UTC

- reply

Thanks, I'll check it, but I think that it's due to an unreachable relay that has just been added to the pool.
The disconnected relays are skipped (return error instead of waiting) after the second failed attempt.
To confirm it, can you try to decrease the connection timeout, configurable via the Client Builder? (I've added this feature yesterday in master branch).
Or, have you a small code snippet to reproduce it? And what relays did you used?
Regarding the issues, are perfect here on nostr.
But instead of using the text notes, the NIP34 would be better. Here is the repo: https://gitworkshop.dev/yukikishimoto.com/nostr
For desktop you can use gitplaza, by @nprofile…3hjm
https://codeberg.org/dluvian/gitplaza

2026-02-12 09:28:24 UTC

- reply

Does this happen with the in-memory gossip store, or with the SQLite one? Or both?

2026-02-11 11:48:23 UTC

- reply

Yes, I've starter working on it a couple of days ago. The PR: https://github.com/rust-nostr/nostr/pull/1252
I'm working on making all the libraries runtime-agnostic. Hope to have a PR ready soon.

2026-02-10 07:18:09 UTC

- reply

Ahh, with the AdmitPolicy::admit_auth is possible handle the approve/reject flow while using the SDK impl: https://github.com/rust-nostr/nostr/pull/1218

2026-02-09 14:22:51 UTC

- reply

Out of curiosity, why are you manually handling auth requests? Are there issues with the SDK implementation?

2026-02-09 14:04:31 UTC

- reply

Fixed here: https://github.com/rust-nostr/nostr/commit/9f3764e8bb3e59140ca63878a2ed491176a181ad

2026-02-05 12:23:11 UTC

- reply

@nprofile…fn5u in addition to the SQLite gossip store, also this PR should help: https://github.com/rust-nostr/nostr/pull/1250
If you have the opportunity to test it, let me know if it's faster.

2026-02-05 08:10:19 UTC

- reply

No, clone doesn't affect that, it's fine to use it. Have you tried the SQLite gossip storage, instead of the in-memory one?

2026-02-04 14:24:18 UTC

The new SDK APIs are now available in the master branch, for those interested in trying them out!
https://github.com/rust-nostr/nostr
#nevent1q…jr8l

2026-01-04 11:58:05 UTC

- reply

This time I just merged them 😂, those are @nprofile…rsym 's work

2025-11-13 11:13:03 UTC

- reply

Thanks @nprofile…kqly
@nprofile…nfdg the NIP-09 doc is now available here: https://rust-nostr.org/sdk/nips/09

2025-11-06 11:37:01 UTC

## 🦀 rust-nostr v0.44 is out!
### 🚀 Highlights
- Support for new NIPs
- Enhanced the Relay Builder (now also available in bindings)
- Optimized default gossip implementation
- Added support for custom gossip implementations
- Improved nostr-lmdb performance
- Released Kotlin Multiplatform bindings 🎉
Thanks to all contributors!
### 🔗 Links
https://rust-nostr.org
https://rust-nostr.org/donate
#rustnostr #nostr #rustlang #programming #rust #python #csharp #dotnet #javascript #kotlin #swift #flutter

2025-09-14 16:12:22 UTC

- reply

I've removed it here: https://github.com/rust-nostr/nostr/commit/c2442d87da7ec521006a6954bb472f3aef73383e
At the moment, I think there are other things more important to focus on. We'll see if re-add it in the future, after the beta or release stage.
Otherwise, if someone is interested in building a nostr-sdk extension library, could add it there.

2025-09-04 14:45:49 UTC

👀
https://github.com/rust-nostr/android-signer

2025-08-21 14:44:37 UTC

Nostr SDK bindings for Kotlin Multiplatform are out for testing!
Package: "org.rust-nostr.org:nostr-sdk-kmp:0.44.0-SNAPSHOT"
Support the following targets: Android (x86, armv7, x86_64, aarch64), iOS (aarch64 and x86_64), Linux (GLIBC and MUSL; x86, x86_64, armv7, aarch64 and riscv64), FreeBSD (only x86_64), macos (x86_64 and aarch64) and windows (x86, x86_64 and aarch64).
#rust-nostr #rustnostr #rust #kotlin #kmp #ffi

2025-08-21 06:10:20 UTC

- reply

Thanks, I've released it ad patch (v0.43.1)

2025-08-20 19:36:17 UTC

- reply

Here you can find some docs/examples: https://rust-nostr.org/

2025-08-06 15:23:20 UTC

- reply

It shouldn't be related to the SDK, error 403 means that the server is blocking you

2025-08-01 14:12:19 UTC

- reply

Unfortunately in bindings I can't mark a function as deprecated.
You have to use the NostrParser and then construct the tags. In this way you can extract only the stuff you need from the text

2025-07-28 14:21:33 UTC

## rust-nostr v0.43 is out! 🦀
### Summary
Put relays to sleep when idle, verify that events match subscription filters and optionally ban relays that send mismatched events, add proxy server for using NIP-07 browser signers from native applications, add support for FreeBSD x86_64 for JVM and C# bindings, and many more!
Thanks to all contributors!
### Links
https://rust-nostr.org
https://rust-nostr.org/donate
#rustnostr #nostr #rustlang #programming #rust #python #csharp #dotnet #javascript #kotlin #swift #flutter

2025-07-26 07:12:29 UTC

- reply

#rustnostr #rust-nostr #rust #elixir #erlang
#nevent1q…u9xv

2025-07-26 07:11:19 UTC

Elixir bindings for the nostr library, by @nprofile…fv49
https://github.com/rust-nostr/nostr-elixir

2025-07-22 16:21:20 UTC

- reply

A web page acts as a bridge between the NIP07 extension and the local server. When the user needs to sign something a request is scheduled, which is then taken from the web page and forwarded to the NIP07 extension. When the extension returns the result, the web page forwards the response to the local server.

2025-07-22 16:02:55 UTC

👀
https://github.com/rust-nostr/nostr/pull/994
This allows using NIP-07 signer in native applications. Thanks to @nprofile…rsym for the idea!
#rustnostr #nostr #rustlang #rust

2025-07-11 15:24:51 UTC

- reply

🧡

2025-07-01 12:04:35 UTC

- reply

If you mean with the Kotlin binding, yes. It's possible to implement a custom signer and use it around the code.
Otherwise, if you mean from directly from rust, I've started working on a NIP-55 implementation, but it is not ready yet. I haven't even tested it yet. I hope to have something working for the next releases.
https://github.com/rust-nostr/nostr/tree/nip55

2025-06-27 07:16:54 UTC

- reply

Good catch, thanks! I'll fix it soon

2025-06-26 09:33:02 UTC

- reply

Reduced to 3 at https://github.com/rust-nostr/nostr/commit/b47962f904679e1ab75e7160982dc905ad10f133

2025-06-24 09:22:48 UTC

- reply

It currently take at max the first 5 relays from the NIP65 list (I thought I had lowered it to 3, I'll decrease it soon).
But also taking at max 3, the number of connections may be high. Should I lower it to 2?
We've added support for "sleep when idle" for relays (in master branch). I still have to finalize the support in the SDK. With this, the gossip relays (or even all relays) can connect on-demand and sleep when idle.
Another plan is to add a persistent storage for gossip data, give a rank/score to relays... but I still not found the best way to do this. Ideas are appreciated :)

2025-06-23 16:45:54 UTC

- reply

@nprofile…gwrl, if it helps, here is how I implemented it for the nostr-relay-builder: https://github.com/rust-nostr/nostr/blob/06dd1b6e532a611929278f9374aa4340455f0f54/crates/nostr-relay-builder/src/local/inner.rs#L698

2025-06-10 04:47:56 UTC

- reply

What version are you using? It should be exposed in the last ones:
https://github.com/rust-nostr/nostr-sdk-js/blob/v0.42.1/src/client/mod.rs#L558

2025-06-10 04:43:49 UTC

- reply

Thank you 🧡

2025-06-06 17:36:26 UTC

- reply

Unfortunately yes. I'll try to add support for negentropy in nostr-rs-relay soon.

2025-06-06 15:09:28 UTC

- reply

@nprofile…qxu5

2025-06-06 15:09:17 UTC

Stats obtained from 766072 NIP-65 lists, downloaded from the following relays: Damus, Primal, purplepag and 0xtr. After extracting and deduplicating the data from the lists, the total unique relays are 5735, of which 1341 reachable. Of these, only 219 supports negentropy.
=== Relay Statistics ===
Total known relays: 5735
Reachable relays: 1341/5735 (23.4%)
=== Negentropy Support (NIP77) ===
Total relays: 219/1341 (16.3%)
=== Top 20 implementations ===
1. https://git.sr.ht/~gheartsfield/nostr-rs-relay: 426 (34.8%)
2. git+https://github.com/hoytech/strfry.git: 283 (23.1%)
3. https://github.com/bitvora/haven: 137 (11.2%)
4. https://relay.nostr.band: 52 (4.2%)
5. git+https://github.com/Cameri/nostream.git: 49 (4.0%)
6. https://github.com/bitvora/wot-relay: 35 (2.9%)
7. https://github.com/fiatjaf/khatru: 34 (2.8%)
8. git+https://github.com/cameri/nostream.git: 34 (2.8%)
9. chorus: 12 (1.0%)
10. https://github.com/bitvora/sw2: 9 (0.7%)
11. unknown: 9 (0.7%)
12. https://github.com/rnostr/rnostr: 7 (0.6%)
13. https://github.com/CodyTseng/nostr-relay-tray: 7 (0.6%)
14. NFDB: 6 (0.5%)
15. https://github.com/github-tijlxyz/khatru-pyramid: 6 (0.5%)
16. https://github.com/Spl0itable/nosflare: 6 (0.5%)
17. https://github.com/haorendashu/cfrelay: 6 (0.5%)
18. https://gitlab.com/soapbox-pub/ditto: 6 (0.5%)
19. https://github.com/quentintaranpino/nostrcheck-server: 5 (0.4%)
20. LNbits: 5 (0.4%)
... and 60 more implementations
Source code (experimental): https://github.com/rust-nostr/nostr-stats

2025-06-05 15:53:59 UTC

- reply

Strfry and chorus. I've implemented it also in the nostr-relay-builder.

2025-06-05 15:50:37 UTC

https://deepwiki.com/rust-nostr/nostr

2025-06-01 16:18:57 UTC

- reply

Use `to_vec` to convert them to an array, so you can iterate them.

2025-06-01 16:16:35 UTC

- reply

As it is written pretty much everywhere, the project is in alpha state, so obviously the documentation is not complete. PRs are welcome to improve it.
To parse a public key (hex, bech32 or nostr URI): `PublicKey.parse`.

2025-05-29 11:07:24 UTC

I've reworked the NostrParser at https://github.com/rust-nostr/nostr/pull/899
This improves the performance of ~2x and reduces the final binary size.
I'm merge this soon, if anyone is interested in testing or reviewing the PR, please share a feedback!
#rust-nostr #rustnostr

2025-05-26 15:24:32 UTC

- reply

Release v0.42.1 is out, which includes a couple of bug fixes related to NIP-47.
#rustnostr #rust-nostr #rust #rustlang #python #csharp #dotnet #javascript #typescript #kotlin #swift #flutter
#nevent1q…9xwa

2025-05-20 09:29:22 UTC

## rust-nostr v0.42 is out! 🦀
### Summary
Blossom, NostrMLS, Relay Monitor, NIP-70 support for relay-builder, NIP-46 reworks, some bug fixes and more!
Note for who is interested in NostrMLS: it's not currently available on https://crates.io as it depends on an unreleased version of openmls. However, you can use it directly from git. The bindings will be available in the upcoming releases.
Full changelog: https://rust-nostr.org/changelog
### Bindings specific changes
Added support for event streaming and extended supported OS and architectures.
New supported platforms for Python, C# and JVM bindings:
- Windows x86 and aarch64
- Linux (GLIBC) x86, armv7 and riscv64
- Linux (MUSL) x86, x86_64, armv7, aarch64 and riscv64
Check all supported OS and architectures at https://rust-nostr.org/sdk/install
### Contributors
Thanks to all contributors!
- @nprofile…rsym
- @nprofile…d56q
- @nprofile…qxu5
- @nprofile…ff74
- @nprofile…fknl
### Links
https://rust-nostr.org
https://rust-nostr.org/donate
#rustnostr #nostr #rustlang #programming #rust #python #csharp #dotnet #javascript #kotlin #swift #flutter

2025-05-17 17:55:54 UTC

- reply

Here you can find an example, but it may not be updated to the last version: https://github.com/rust-nostr/nostr-sdk-ffi/blob/ac4d6a8fb8f61b5f3ce3148a99e9f117bcbc0afc/python/examples/bot.py
I'll try add an example in the book soon.

2025-05-17 15:45:35 UTC

- reply

Glad to hear that 🧡
I'll see what I can do. Currently you can know which relay sent the event by monitoring the notifications (RelayPoolNotification).

2025-05-16 07:40:45 UTC

I've just published a pre-release for the python nostr-sdk (version `0.42.0a2`), using the ABI3. I've also extended the support to Linux x86, windows x86 and aarch64.
If anyone is interested in trying it, please share a feedback if something doesn't work.
https://pypi.org/project/nostr-sdk/0.42.0a2/
#rust-nostr #rustnostr #python

2025-05-09 19:13:27 UTC

- reply

Nice idea!

2025-04-30 18:58:52 UTC

- reply

When it'll be ready, I'll expose it in nostr-sdk bindings, or more likely in a dedicated library (depending on the impact on the binaries size).

2025-04-15 10:19:38 UTC

## rust-nostr v0.41 is out! 🦀
### Summary
Added NIP-C0 support and NIP-98 helpers, fixed NIP-32 and NIP-47 implementations, added nostr-keyring crate, extended admission policies for granular control over which relays can connect and which cannot (useful when gossip mode is enabled), enabled POSIX semaphores for LMDB on iOS & macOS to fix issues with App Sandbox, extended arch support for C# and JVM bindings (linux-x86, windows-x86 and windows-arm64) and more!
For those who missed it, from v0.40.0 are available the C# bindings for nostr-sdk: #nevent1q…s3yy
Full changelog: https://rust-nostr.org/changelog
### Contributors
Thanks to all contributors!
* @nprofile…g0ly
* @npub1kue…drjt
### Links
https://rust-nostr.org
https://rust-nostr.org/donate
#rustnostr #nostr #rustlang #programming #rust #python #javascript #kotlin #swift #flutter #csharp #dotnet

2025-04-09 13:58:57 UTC

Nostr.Sdk package for C# is out!
https://www.nuget.org/packages/Nostr.Sdk
Some basic examples are available at https://rust-nostr.org/
#rust-nostr #rustnostr #csharp #dotnet #nostr #devstr #rustlang

2025-04-06 07:17:42 UTC

- reply

According to NIP32, both should be valid

2025-03-30 08:29:36 UTC

- reply

Because I was using SQLite only for persistence. When it was opened, all the data was loaded into RAM, in the DatabaseHelper. It was basically an in-memory database with SQLite as persistence.
Using the NostrDatabase traits, you can implement your own database, and use it in rust-nostr. But if anyone is interested to open a PR to implement a "pure" SQLite backend, I'll merge it.

2025-03-30 08:28:36 UTC

- reply

You can see the REQs using the debug log level

2025-03-22 20:42:42 UTC

- reply

@nprofile…tknc, yeah, you can use nostrdb APIs directly for the zero-copy queries and nostr-sdk for the networking stuff.
You can eventually clone the nostrdb instance and pass it to nostr-sdk just to automatically save the events received from the relays into nostrdb.

2025-03-18 09:42:34 UTC

## rust-nostr v0.40 is out! 🦀
### Summary
Add NIP-38 and NIP-62 support, add nostr parser, to easily parse any text and extract nostr URIs, URLs and more, extend `Tags` capabilities (i.e., add deduplication support), add admission policy, to selectively select which events to allow receiving and which to reject, add Mac Catalyst support for Swift package, many cleanups, refactoring and performance improvements and more!
Full changelog: https://rust-nostr.org/changelog
### Contributors
Thanks to all contributors!
* @npub1aha…45hy
* @nprofile…g0ly
* @npub1zfs…w445
* @npub16ye…g4wn
* magine
### Links
https://rust-nostr.org
https://rust-nostr.org/donate
#rustnostr #nostr #rustlang #programming #rust #python #javascript #kotlin #swift #flutter

2025-03-12 20:21:20 UTC

- reply

Happy Birthday!

2025-03-07 07:44:42 UTC

- reply

You have to build manually the event:
```python
encrypted_content = nip04_encrypt(sk, pk, msg)
builder = EventBuilder(4, encrypted_content).tag(Tag.public_key(pk))
client.send_event_builder(builder)
```

2025-03-04 16:44:39 UTC

- reply

I've started working on it here: https://github.com/rust-nostr/nostr/pull/797
For now I've only implemented the algorithm for NIP117. Soon I'll add also support for persistent session state and integration with the nostr-sdk library.

2025-03-01 10:44:17 UTC

- reply

I'll check it soon!

2025-02-24 15:32:28 UTC

For devs who use rust-nostr bindings and care about app size: use v0.39 or later, older versions are bloated due to a bug in uniffi.
#rustnostr #rust-nostr #kotlin #python #swift #jvm

2025-02-23 09:12:12 UTC

- reply

I've uses both the book and rustlings: https://github.com/rust-lang/rustlings/
There is also the "Rust by example" book: https://doc.rust-lang.org/rust-by-example/
While you read the book, try to make projects from scratch (not just simple ones). At the end, writing code is the best way to learn it.

2025-02-22 08:52:30 UTC

- reply

Yes, it's most likely due to the python version. What python version are you using?

2025-02-13 21:28:46 UTC

- reply

```python
from nostr_sdk import EncryptedSecretKey
encrypted = EncryptedSecretKey.from_bech32("ncryptsec...")
secret_key = encrypted.to_secret_key("<password>")
```

2025-02-08 07:49:43 UTC

- reply

I have never been very active in discussions but working on rust-nostr (at the time called nostr-rs-sdk) since September 2022 🦀
If I remember correctly there were also @nprofile…njvk and @nprofile…nq40

2025-01-31 15:25:31 UTC

- reply

I usually copy the stuff I already exposed in the UniFFI bindings and adapt it to the flutter_rust_bridge.
So, in the case of metadata stuff, I would copy and adapt this: https://github.com/rust-nostr/nostr/blob/d7a8372e28a5dd7e1ce02b725ee0b43c798e332f/bindings/nostr-sdk-ffi/src/protocol/nips/nip01.rs
To adapt it, I follow these docs https://cjycode.com/flutter_rust_bridge/ or I just check the other modules I already adapted. In short: replace the uniffi macros with `frb` and use the `Result` from anyhow. If a new module is added, it must be exported in the `lib/nostr_sdk.dart` file.

2025-01-31 12:16:20 UTC

- reply

Done, I've exposed the NostrDatabase, added some other Client method and released the v0.39 (tagged in the git repo, I can't publish it to pub.dev).

2025-01-31 11:23:52 UTC

- reply

Nice, so I'll expose the database soon

2025-01-31 11:22:47 UTC

- reply

The rust library for flutter compiles to wasm but I don't know how to pack and ship the flutter package for web. For the desktop and mobile platforms I use cargokit but it doesn't work for the web.

2025-01-31 11:15:31 UTC

- reply

For now are available: Keys signer (with both NIP04 and NIP44 support), NIP59, event de/serialization, event building and the SDK Client (NIP42 auto authentication, gossip, event sending, event fetching and subscriptions).
I'll add the other stuff as I find the time. If you need something specific, let me know that I'll expose it.

2025-01-31 10:55:20 UTC

- reply

Nice! Yeah haha

2025-01-31 10:53:02 UTC

- reply

#nevent1q…4ufg

2025-01-31 10:50:08 UTC

## rust-nostr v0.39 is out! 🦀
### Summary
Add NIP96 support, add NIP22 helpers, NIP01 adjustments, add `try_connect` and `wait_for_connection` methods for better connection handling, support for custom WebSocket clients (both in Rust, Python, Kotlin and Swift), new JVM bindings (Linux, macOS and Windows), huge reduction of UniFFI bindings binaries size, many cleanups, refactoring and performance improvements and more!
Full changelog: https://rust-nostr.org/changelog
### Contributors
Thanks to all code contributors!
* @npub1qqq…rfkq
* @npub1zwn…fhrf
* @npub1r3c…fx0c
* @npub1v0l…qj49
* ethicnology
* Gudnessuche
Thank also to @npub1use…k5ks, @npub1a3t…kq4k and spacecowboy!
### Links
https://rust-nostr.org
https://rust-nostr.org/donate
#rustnostr #nostr #rustlang #programming #rust #python #javascript #kotlin #swift #flutter

2025-01-30 10:54:05 UTC

- reply

No, for HTTP requests I'm using reqwest

2025-01-27 14:18:51 UTC

- reply

#rustnostr #nostr #kotlin #jvm
#nevent1q…phku

2025-01-27 14:16:53 UTC

It's now available a pre-release of the nostr-sdk library for Kotlin JVM (linux, macos and windows)!
```kotlin
implementation("org.rust-nostr:nostr-sdk-jvm:0.39.0-alpha.1")
```
https://central.sonatype.com/artifact/org.rust-nostr/nostr-sdk-jvm