otto

Public Key

npub10tt00tt07exx7mgf9td0026mx454hq6dyl9vwm72aeyf0tljf8msjs3z28

Profile Code

nprofile1qqs844hh44hlvnr0d5yj4khh4ddn262msdxj0jk8dl9wujyh4leynacpzpmhxue69uhkummnw3ezuamfdejszxrhwden5te0wfjkccte9eekummjwsh8xmmrd9skcx8dzgh

Publishing to

Author Public Key

npub10tt00tt07exx7mgf9td0026mx454hq6dyl9vwm72aeyf0tljf8msjs3z28

Show more details

Last Notes

2026-07-07 21:01:34 UTC

- reply

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.

2026-07-07 19:03:24 UTC

- reply

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

2026-07-07 18:58:52 UTC

testing

2026-07-07 18:23:30 UTC

- reply

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 =]

2026-06-12 12:28:43 UTC

- reply

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

2026-06-10 23:39:40 UTC

- reply

Do you get a better price than using Trocador?

2026-06-05 13:58:46 UTC

- reply

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

2026-05-29 12:27:52 UTC

- reply

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

2026-05-10 23:16:37 UTC

- reply

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

2026-04-17 12:49:15 UTC

- reply

https://npub10tt00tt07exx7mgf9td0026mx454hq6dyl9vwm72aeyf0tljf8msjs3z28.blossom.band/a667c850b65b1a9855501325e2f64f87546b30b1a88f0aa1721bdcb925ce048f.jpg

2026-04-03 17:53:12 UTC

- reply

Does it use a local LLM?

2026-02-19 16:28:00 UTC

- reply

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.

2026-02-16 01:25:59 UTC

- reply

They were NOT submitted to miners.

2026-02-14 19:41:06 UTC

- reply

Why wouldn't you tell the vulnerabilities?

2026-01-07 13:01:21 UTC

- reply

Done 👍
https://npub10tt00tt07exx7mgf9td0026mx454hq6dyl9vwm72aeyf0tljf8msjs3z28.blossom.band/ef32a2479acb081f4f456eff1de9acd48c2ed1bf7fad294cf5b90cac0ac77171.png

2025-12-17 23:49:09 UTC

- reply

Thank you 🙏
#pardonsamourai

2025-11-20 21:58:35 UTC

Disgusting piece of shit. Better block and move on.
#nevent1q…tzvu

2025-09-26 14:51:05 UTC

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.
https://blossom.primal.net/ae46d49ea150baadbfcc6e82286e16d0e6a8b352e3e76cd6b3fcabc4471df0bd.png
Check the release notes for instructions on how to upgrade from v1:
https://github.com/cculianu/Fulcrum/releases/tag/v2.0.0

2025-07-30 18:09:16 UTC

- reply

lol, should add the original Block Clock too. https://image.nostr.build/aec0deb47e87fa86458afd81d9a8212a9e06930ff57c502716744d2dbd7acb7d.jpg

2025-07-01 00:13:25 UTC

- reply

> 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%?

2025-06-29 16:05:03 UTC

- reply

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

2025-06-24 02:40:18 UTC

- reply

This would be cool!

2025-06-03 23:00:27 UTC

- reply

Use a swap service, like trocador

2025-06-03 17:33:41 UTC

- reply

Satoshi did not use GitHub. Embarrassing.

2025-05-13 22:14:32 UTC

- reply

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.

2025-05-11 17:50:17 UTC

- reply

How come? You need a mempool to estimate fees.

2025-05-04 13:55:24 UTC

- reply

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).

2025-05-03 23:03:38 UTC

- reply

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.

2025-05-02 14:16:47 UTC

- reply

> 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.

2025-05-01 18:04:06 UTC

- reply

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

2025-05-01 18:03:14 UTC

- reply

Thanks for the smartsmall report. I had no idea shit was so abhorrent
https://fountain.fm/episode/RA7asx122a8E7y4kujt2
#nevent1q…6fq5

2025-05-01 17:53:35 UTC

- reply

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

2025-01-09 19:11:16 UTC

I am running a public dojo node alongside other frens here:
https://www.dojobay.pw/mainnet

2024-10-21 02:58:31 UTC

- reply

That was funny as hell 🤣
How to zap some sovereign custodial LN sats?
https://fountain.fm/episode/13z7ZYx3pIaEpRIddIW4

2024-10-20 16:43:07 UTC

- reply

> 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

2024-10-08 14:05:10 UTC

- reply

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

2024-09-30 01:02:27 UTC

- reply

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.

2024-09-29 19:27:18 UTC

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.
https://m.primal.net/LFoi.png
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.
https://m.primal.net/LFoo.png
https://m.primal.net/LFon.png
https://m.primal.net/LFop.png
https://m.primal.net/LFor.png
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.
https://m.primal.net/LFos.png
About the new directory, I would like to file a complaint against the CEO. What the hell was that 😭😭😭🗣️🗣️🗣️
https://m.primal.net/LFov.png
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.
https://m.primal.net/LFow.png
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

2024-02-12 01:57:29 UTC

I don't know how to use this thing