Nostr notes by otto

This is pointless here, it only affects your node. Other knots ...

2026-07-23T23:41:35Z

In reply to nevent1q…h7za
_________________________

This is pointless here, it only affects your node. Other knots users aren't doing it, but repeating Luke's BS that Whirlpool deliberately chose to break op_return limit and that this is bad for privacy.

You can easily remove "knots" from your UA to circumvent this detection and also disable the ban on your node.

Knots by default does not relay Whirlpool and BIP47 transactions, ...

2026-07-23T22:21:29Z

In reply to nevent1q…zj69
_________________________

Knots by default does not relay Whirlpool and BIP47 transactions, two common transaction types of Dojo users.

It seems the only way to post with a sec is using --sec <sec ...

2026-07-07T21:01:34Z

In reply to nevent1q…93tv
_________________________

It seems the only way to post with a sec is using --sec <sec key> or using an env var. I was confused because the examples have `nak event --sec 02 -c 'good morning'`.
I thought that meant the 2nd (or 3rd) sec key, but apparently that '02' is the priv key itself.

I was trying to find a way to use my nsec key instead of a ...

2026-07-07T19:03:24Z

In reply to nevent1q…s38x
_________________________

I was trying to find a way to use my nsec key instead of a generated one.
I was able to post this using --sec <nsec>, but isn't there a way to add it with key or admin commands?

The test: https://iris.to/note1mhdkwyg2s5ypnuwd9qvxjkwq6kcuepzrek7vy2069khuw73z3lvsgnev5w

Nostr event nevent1qqsdmkm8zy9g2zqe78xjsxrft8qdtvwvs3pum0xz98azmt780g3glkgzypaddaaddlmycmmdpy4d4aattv6kjkurf5nu43m0ethy39a07fylwud3rut

2026-07-07T18:58:52Z

testing

How do you use nak? There are many examples on GitHub, though ...

2026-07-07T18:23:30Z

In reply to nevent1q…uj8c
_________________________

How do you use nak? There are many examples on GitHub, though there isn't a single post?

You can use `at` instead of cron too =]

I think you get better rates with Trocador, though not atomic ...

2026-06-12T12:28:43Z

In reply to nevent1q…t5cj
_________________________

I think you get better rates with Trocador, though not atomic AFAICT.

Do you get a better price than using Trocador?

2026-06-10T23:39:40Z

In reply to nevent1q…dnue
_________________________

Do you get a better price than using Trocador?

FWIW, they changed this on Apr 29th: ...

2026-06-05T13:58:46Z

In reply to nevent1q…0phh
_________________________

FWIW, they changed this on Apr 29th: https://github.com/chainwayxyz/clementine/pull/1241

I don't know if that went on mainnet release (not that it was needed, anyway).

Said it on X also: https://x.com/ottosch_/status/2062895674916581480

It seems to me SP could be used for those too.

2026-05-29T12:27:52Z

In reply to nevent1q…kevx
_________________________

It seems to me SP could be used for those too.

This is great, but remember Roman Sterlingov didn't build the ...

2026-05-10T23:16:37Z

In reply to nevent1q…w73c
_________________________

This is great, but remember Roman Sterlingov didn't build the tool; he was a user of Bitcoin Fog!

Nostr event nevent1qqszvtyuxkkxcw9uk7u8nstln83f9tadrvnm7vq29xzk6yc2w5xnn3szypaddaaddlmycmmdpy4d4aattv6kjkurf5nu43m0ethy39a07fylw4mlsfy

2026-04-17T12:49:15Z

In reply to nevent1q…jf5l
_________________________

Does it use a local LLM?

2026-04-03T17:53:12Z

In reply to nevent1q…zjml
_________________________

Does it use a local LLM?

They were relayed through regular nodes running libre relay. I ...

2026-02-19T16:28:00Z

In reply to nevent1q…6y6j
_________________________

They were relayed through regular nodes running libre relay.

I myself had one running and saw many transactions > 80 bytes in my logs.

Made several posts about it with txids so anyone could verify.

They were NOT submitted to miners.

2026-02-16T01:25:59Z

In reply to nevent1q…gzsv
_________________________

They were NOT submitted to miners.

Why wouldn't you tell the vulnerabilities?

2026-02-14T19:41:06Z

In reply to nevent1q…f23h
_________________________

Why wouldn't you tell the vulnerabilities?

Done 👍 ...

2026-01-07T13:01:21Z

In reply to nevent1q…k2d2
_________________________

Done 👍

Thank you 🙏 #pardonsamourai

2025-12-17T23:49:09Z

In reply to nevent1q…qlle
_________________________

Thank you 🙏

#pardonsamourai

Disgusting piece of shit. Better block and move on. ...

2025-11-20T21:58:35Z

Disgusting piece of shit. Better block and move on.

quoting
nevent1q…tzvu
Dear nostr,
For all those posting "free samourai", you are just virtue signaling a dead cause.
They pleaded guilty, is game over !

If they were real freedom fighters will never plead guilty and will "play" the court in other way, not with pussy lawyers.

I suggest to watch the old movie "Interstate 60" and see what am I talking about. here is a scene of how to play the court to defend your position.

Watch the entire movie so you will understand why they used metaphorically a bomb-vest in the movie...

You never plead in a court, guilty or not guilty, never plead.
Pleading means you renounce to all your rights, you are a garbage, a slave and they can do whatever they want with you.

Fulcrum 2.0 has been released! I synced a new DB from scratch, ...

2025-09-26T14:51:05Z

Fulcrum 2.0 has been released!

I synced a new DB from scratch, here's my experience:

It took about 2.5 days to sync the new Fulcrum on a laptop (Ryzen 7 5700U, db_mem 8000 GiB).

The v2 DB is a little larger than v1: 176 GiB against 166 GiB.

To test performance, I repeteadly queried a large BTC address (1HckjUpRGcrrRAtFaaCAUaGjsPx9oYmLaZ) for balance and history and got these results:

v1 get_balance: [335, 416] range, avg 378 ms;
v2 get_balance: [348, 355] range, avg 352 ms;

v1 get_history: [32676, 33723] range, avg 33214 ms;
v2 get_history: [23208, 23947] range, avg 23508 ms;

Hopefully someone will come up with better benchmarks, it was a real PITA to measure time due to netcat/socat keeping the connection alive.

Now, the best part:
I left a script running all day, killing -9 Fulcrum and restarting it for a total of 95 kills. The DB was not corrupted.

Check the release notes for instructions on how to upgrade from v1:
https://github.com/cculianu/Fulcrum/releases/tag/v2.0.0

lol, should add the original Block Clock too. ...

2025-07-30T18:09:16Z

In reply to nevent1q…hm8q
_________________________

lol, should add the original Block Clock too.

> The next step should be to hardcode the 5% coordination fee ...

2025-07-01T00:13:25Z

In reply to nevent1q…chas
_________________________

> The next step should be to hardcode the 5% coordination fee on the client

Why not accept the coordinator's fee, as long as it's <= 5%?

They might not be reading it. As far as we know, they don't ...

2025-06-29T16:05:03Z

In reply to nevent1q…r5sd
_________________________

They might not be reading it. As far as we know, they don't have social media.

This would be cool!

2025-06-24T02:40:18Z

In reply to nevent1q…8whg
_________________________

This would be cool!

Use a swap service, like trocador

2025-06-03T23:00:27Z

In reply to nevent1q…stym
_________________________

Use a swap service, like trocador

Satoshi did not use GitHub. Embarrassing.

2025-06-03T17:33:41Z

In reply to nevent1q…cu50
_________________________

Satoshi did not use GitHub. Embarrassing.

Yeah, sure, you don't really need a mempool... but Bitcoin ...

2025-05-13T22:14:32Z

In reply to nevent1q…3kse
_________________________

Yeah, sure, you don't really need a mempool... but Bitcoin Core also has that option, called `-blocksonly`.

Maybe he means libbitcoin does not require an UTXO set. I remember Eric has stated that a bunch of times.

How come? You need a mempool to estimate fees.

2025-05-11T17:50:17Z

In reply to nevent1q…6hv2
_________________________

How come? You need a mempool to estimate fees.

Yes. 1- Scammer sees you selling; 2- Finds a buyer (victim); 3- ...

2025-05-04T13:55:24Z

In reply to nevent1q…lx5n
_________________________

Yes.

1- Scammer sees you selling;
2- Finds a buyer (victim);
3- Tells victim to send you fiat;
4- You see the payment, send coins to scammer;
5- You and the scammer are happy, the victim isn't and will call the bank, go after you etc;

Step 2 can be unrelated to Bitcoin (ex: scammer could pretend to be selling a phone).

The problem is when you stumble upon some piece of sh*t ...

2025-05-03T23:03:38Z

In reply to nevent1q…yz5n
_________________________

The problem is when you stumble upon some piece of sh*t performing MITM scams. One bad trade ruins dozens or hundreds of good trades.

I made like 10 trades and then met the scammer. Bank charged back the money from my account. I filed a lawsuit, won, but had the bank account terminated and was banned from some services affiliated with that bank.

For Lightning or Monero swapping, gift cards etc, it's great. But without a reputation system, it's too risky to interact with the fiat system.

> Knots quickly fixed this in its 25.1 release 1- Knots did ...

2025-05-02T14:16:47Z

In reply to nevent1q…ugvt
_________________________

> Knots quickly fixed this in its 25.1 release

1- Knots did not fix anything. Everybody running Knots is storing all the data exactly as the people running Core or other implementations.

2- Even if every single node runner were running Knots, if ONE miner decides to take those transactions, the data would still be there.

3- Even if all miners ran Knots, the inscription pattern (called envelope) can trivially be adapted to bypass that filter.

Make sure you listen to the show. That chapter is much larger and ...

2025-05-01T18:04:06Z

In reply to nevent1q…q23n
_________________________

Make sure you listen to the show. That chapter is much larger and couldn't fit a clip.

Thanks for the smartsmall report. I had no idea shit was so ...

2025-05-01T18:03:14Z

Thanks for the smartsmall report. I had no idea shit was so abhorrent

https://fountain.fm/episode/RA7asx122a8E7y4kujt2

quoting
nevent1q…6fq5

I already had the worst opinion about him, but had no idea it was ...

2025-05-01T17:53:35Z

I already had the worst opinion about him, but had no idea it was that bad.

Thanks for sharing this, lads.

https://fountain.fm/clip/gATnYAXBRrhTxrtKTJzm

Thank you, it was great to be part of it. ...

2025-02-28T15:23:18Z

Thank you, it was great to be part of it.

https://fountain.fm/episode/xp1DyyIrSfCMARKW5cfz

quoting
nevent1q…0fgj

I am running a public dojo node alongside other frens here: ...

2025-01-09T19:11:16Z

I am running a public dojo node alongside other frens here:

https://www.dojobay.pw/mainnet

That was funny as hell 🤣 How to zap some sovereign custodial ...

2024-10-21T02:58:31Z

That was funny as hell 🤣
How to zap some sovereign custodial LN sats?

https://fountain.fm/episode/13z7ZYx3pIaEpRIddIW4

> For the record, the whirpool-client code does have Tor ...

2024-10-20T16:43:07Z

In reply to nevent1q…4z99
_________________________

> For the record, the whirpool-client code does have Tor identity management

> However neither the android app nor sparrow manage identities.

Sir, as pointed by Pavel, whirlpool-client is a dependency of the android app:

https://github.com/Archive-Samourai-Wallet/samourai-wallet-android/blob/develop/app/build.gradle#L127

No, any wallet can interact with it. Sparrow was another wallet ...

2024-10-10T00:27:11Z

In reply to nevent1q…fcm0
_________________________

No, any wallet can interact with it. Sparrow was another wallet that used to do it.

Someone has to host the Whirlpool server, though.

Yes, but without Whirlpool, at least for the moment.

2024-10-08T14:05:10Z

In reply to nevent1q…34z2
_________________________

Yes, but without Whirlpool, at least for the moment.

Only way to do that is inspecting the source code of bitcoinj, ...

2024-10-08T14:04:58Z

In reply to nevent1q…8elq
_________________________

Only way to do that is inspecting the source code of bitcoinj, compiling and using it, instead of using the version from JitPack.
Downloading dependencies from popular repositories like JitPack is normal (not saying it's the best practice, but normal).

TBH I did compare that source with an older version I found on noosphere888's GitHub and found the majority of changes were removing old stuff (like BIP70), but cryptography is tricky so I preferred to let that comment out.

Sparrow Wallet is migrating to the new PayNym directory. ...

2024-10-04T01:50:22Z

Sparrow Wallet is migrating to the new PayNym directory.

https://github.com/sparrowwallet/sparrow/commit/e50fe4c68cd0ce0b9a987b4adbc05c09bb942810

quoting
note18ae…3wly
I've finished comparing the released Ashigaru code with
Samourai Wallet.

I did this for my own, personal usage, but it might serve others. Feel free to add your remarks/questions, DYOR and/or wait for more reviews.

TL;DR: I found nothing wrong and plan to use it soon.

I ran a diff between this release and TDevD's commit from Apr 24th. I didn't check the code between the latest SW release and that date since I already trusted SW.

Ashigaru devs (AD) published release notes [1] and there are also the commit messages from SW commit radar [2].

SW had a fork of bitcoinj. I never had it cloned and it's possible the repository is lost :(

The library and source code are downloaded from JitPack. According to their logs [3], it was built in Mar 20th.
Unless AD are wicked and in cahoots with JitPack, it should be safe to me.

=====

From ExtLibJ, which is used for Stonewall, Soroban, BIP47 etc, there are no changes, except for backend URLs.

Comparison was made with noosphere888's repository [4].

=====

Ok, so now on to the actual review.

New features: the wallet pings an onion URL to see if there's a new version, maybe because there's no Play store and they have no social media.

Also there's a new wallet sync view.

Tor and own Dojo are now mandatory.

OXT explorer was removed. Apparently one is available only if the Dojo instance has one.

Soroban (without Joinbot) and Ricochet are back. So is PayNym, under a new directory. The connect fee has been waived.

Whirlpool removed from the GUI and also options to call SW's support.

About the new directory, I would like to file a complaint against the CEO. What the hell was that 😭😭😭🗣️🗣️🗣️

To finish the review, there were many changes due to rebranding, changing URLs, colours and addresses.

=====

The build is reproducible as per the instructions. I used unzip instead of apktool because it's faster and was already installed.

That's it, congratulations and good luck to Ashigaru devs. Now, take some time to visit http://freesamourai.com [5].

#FreeSamourai

Links:
[1] https://ashigaru.rs/news/release-wallet-v1-0-0
[2] https://t.me/SamouraiCommitRadar
[3] https://jitpack.io/io/samourai/code/whirlpool/bitcoinj/007/build.log
[4] https://github.com/noosphere888/ExtLibJ
[5] https://freesamourai.com

How is it black box? About the npub creation, I'm sure you ...

2024-09-30T13:26:42Z

In reply to nevent1q…kq7p
_________________________

How is it black box? About the npub creation, I'm sure you can find when it was created on your own.

No, both the binaries and the sources are available here (append ...

2024-09-30T01:02:27Z

In reply to nevent1q…lwfh
_________________________

No, both the binaries and the sources are available here (append the file name to the URL): https://jitpack.io/io/samourai/code/whirlpool/bitcoinj/bitcoinj-core/007/

It was a relief knowing it was uploaded before the arrest!
It's not ideal, but JitPack is a very popular Maven repository, like google and mavencentral.

I've finished comparing the released Ashigaru code with ...

2024-09-29T19:27:18Z

I've finished comparing the released Ashigaru code with
Samourai Wallet.

I did this for my own, personal usage, but it might serve others. Feel free to add your remarks/questions, DYOR and/or wait for more reviews.

TL;DR: I found nothing wrong and plan to use it soon.

I ran a diff between this release and TDevD's commit from Apr 24th. I didn't check the code between the latest SW release and that date since I already trusted SW.

Ashigaru devs (AD) published release notes [1] and there are also the commit messages from SW commit radar [2].

SW had a fork of bitcoinj. I never had it cloned and it's possible the repository is lost :(

The library and source code are downloaded from JitPack. According to their logs [3], it was built in Mar 20th.
Unless AD are wicked and in cahoots with JitPack, it should be safe to me.

=====

From ExtLibJ, which is used for Stonewall, Soroban, BIP47 etc, there are no changes, except for backend URLs.

Comparison was made with noosphere888's repository [4].

=====

Ok, so now on to the actual review.

New features: the wallet pings an onion URL to see if there's a new version, maybe because there's no Play store and they have no social media.

Also there's a new wallet sync view.

Tor and own Dojo are now mandatory.

OXT explorer was removed. Apparently one is available only if the Dojo instance has one.

Soroban (without Joinbot) and Ricochet are back. So is PayNym, under a new directory. The connect fee has been waived.

Whirlpool removed from the GUI and also options to call SW's support.

About the new directory, I would like to file a complaint against the CEO. What the hell was that 😭😭😭🗣️🗣️🗣️

To finish the review, there were many changes due to rebranding, changing URLs, colours and addresses.

=====

The build is reproducible as per the instructions. I used unzip instead of apktool because it's faster and was already installed.

That's it, congratulations and good luck to Ashigaru devs. Now, take some time to visit http://freesamourai.com [5].

#FreeSamourai

Links:
[1] https://ashigaru.rs/news/release-wallet-v1-0-0
[2] https://t.me/SamouraiCommitRadar
[3] https://jitpack.io/io/samourai/code/whirlpool/bitcoinj/007/build.log
[4] https://github.com/noosphere888/ExtLibJ
[5] https://freesamourai.com

Nostr event nevent1qqs0zfzngp3a0ud9wcykpecvqu9vjtschyq6l8zqk26qpaprrlcerzgzypaddaaddlmycmmdpy4d4aattv6kjkurf5nu43m0ethy39a07fylwfn52y9

2024-02-12T01:57:29Z

I don't know how to use this thing