Last Notes
Still dom't onow the common name of this flower (in Latin: Ipomoea). It blooms at dawn only.
https://image.nostr.build/43ca4494ca01a6b780b4d6331392a357dea625dae1d1f6c824a4c0d6ae7e6304.jpg
#nature #flower #photo #flowerstr #naturestr #artstr
I've abandoned budgeting years ago. Since I've bacame bitcoin billonaire. Just joking 😁 (I never stopped budgeting despite of my billions😁)
Do you think Spark and Ark require comparable fees to exit unilaterally? Have you seen a similar study for Ark?
This data liveness requirement is painful but I think comparable to the pain of expiring VTXOs in Ark. There you already always have the state to publish for the unilateral exit but you (wallet or watchtower) must monitor the expiry deadlines.
Of course the other thing is that ark operators are less trusted since they cannot conspire to steal funds.
However I still love Spark because at the end of the day operators don't have enormous liquidity requirements and this will make a big difference in adoption.
Also in Ark has that constant periodical refresh from user wallets, that doesn't look good to me. I don't necessarily open my wallets every month and this is going to be a problem when a lot of users realize this (or have to pay extra for a refresher service).
All in all love the innovation of the L2 space
I stopped using Spark wallets many months ago... 🤷♂
Basically, if something happens in Spark, the miners will be very happy... 😅
I strongly recommend @Zeus (LND embedded), which now works really well... 😎👍
https://zeusln.com
#spark #zeus #wallet
Ark (bark) launched like couple weeks ago. Spark had head start. I haven't followed arkade recently...
Can the wallets be optimized to always try doing the lowest number of leaves? So when you actually need to exit, it's only a couple...
Hajrá #bitcoincsajok #művészet #könyv
#nevent1q…rusg
Correction: "seed only, no operators" compressed two steps. The leaf data (recovery bundle) must be fetched while operators are online. The exit itself then needs nothing from them: seed + saved bundle is the accurate claim. Full mechanics and costs: https://github.com/blinkbitcoin/spark-unilateral-exit/blob/main/docs/mainnet-exit-case-study.md
Correction: "seed only, no operators" compressed two steps. The leaf data (recovery bundle) must be fetched while operators are online. The exit itself then needs nothing from them: seed + saved bundle is the accurate claim. Full mechanics and costs: https://github.com/blinkbitcoin/spark-unilateral-exit/blob/main/docs/mainnet-exit-case-study.md
Art from @nprofile…7xw4 , go grab one!
#nevent1q…rusg
Én szeretnék egy példányt!
They didn't Christoph, they lied. They pulled the recovery data from a spark operator using their mnemonic.
Yes, correct, one either keeps a server up with their seed or the mobile does it.
In Blink we will have event-driven and likely also periodical refresh built in.
Problem is any time you transact (and sometimes other times!) the “recovery bundle” changes. So you can’t back it up/download it, your wallet needs to support this natively (and I don’t believe any do).
https://www.youtube.com/watch?v=oyKOmAQIP_g
The data-availability dependency is real and worth stating exactly, so let's state it.
Operators never hold your key and can't move funds without your signature - that part is unconditional. Unilateral exit works through pre-signed refund txs that pay to a key only you control, and those txs plus their ancestors are the "leaf data" in question: your device co-signs them at claim time, ancestors come from a query. Until a wallet persists that data, forcing your funds on-chain depends on operator liveness. Grubles is right that no wallet ships this today. That gap is the entire reason I built and published this tooling instead of just claiming "non-custodial" in marketing copy.
What the dependency actually is, once you persist the data:
Bounded: everything covered by your last refresh exits without any operator, forever. Exposure is only what changed since then. With refresh wired into every claim, that window is one transaction.
Detectable: withholding means your refresh fails right after your claim succeeded. You notice, you stop receiving, you exit with what you have. - Compare a custodian, where withholding looks like normal operation until the withdrawal freeze.
So on the spectrum: weaker than Lightning, where your node holds channel state by construction. Much stronger than custodial, where they hold both keys and data and you detect nothing. "Self-custody of keys with a bounded, detectable data-availability dependency" is the honest label.
Wallets that don't manage that dependency for users are shipping the weak end of the spectrum. Mine included, today. That is what is being fixed, and the case study is the receipt that the exit half already works:
https://github.com/blinkbitcoin/spark-unilateral-exit/blob/main/docs/mainnet-exit-case-study.md
You needed the operator to give you the leaves in the first place
#nevent1q…90mm
Alt link:
#nevent1q…9lqe
The only way to get the offchain data from the operators why they are online.
Wallets should (Blink will) implement periodic background polling for data.
I am curious to check it out, but the link is not working for me.
How would you derive the Offchain data for the recovery from the seed without the operator?
How does your experience compare to this view?
https://x.com/notgrubles/status/2074624676978962867
Find the case study here if getting 404 from github:
https://njump.me/naddr1qvzqqqr4gupzp2kq0k2s388x4hcghy2k6s7p5j44jnrpxzmaevfwcxvsprzcrx30qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy2hwumn8ghj7un9d3shjtnwdaehgu3wdp6j7qq4d9zy2h64tfmks7nctpmkg36v2e05x4nwty8vne59
The repo was just made public, might be lagging to show:
https://github.com/blinkbitcoin/spark-unilateral-exit
@nprofile…r5mh I wrote you a message, but looks like you don't get it.
I just force-exited a non-custodial Blink wallet (using Spark) on Bitcoin mainnet.
Seed only - no operator cooperation: recovery bundle, fee funding, CPFP signing and sweep all derived from the wallet seed.
The honest numbers for a 100k sat wallet:
• 22 leaves, 253 tx packages to exit fully
• only 4 leaves (90% of the value) were worth exiting - fees would have eaten the other18
• ~9.4k sats in fees to recover 90.1k, one package per block per chain, then a ~2-week timelock
Non-custodial means you can always leave. But the fire escape is narrow - full case study with costs, failures and lessons:
https://github.com/blinkbitcoin/spark-unilateral-exit/blob/main/docs/mainnet-exit-case-study.md
https://blossom.primal.net/3771944c21849fd461b5a1a2cd13515755f1d232690ea5b633fd2b7c95f5135c.png
Nostr OG 💪 https://hortopato.cc/89c8c001f2dac377c029cdccbad7eebaccda2fbcb4f88d7abcc4ef0b872863f0.jpg
Yes, I think I'm about to experience that.
I only have 25GB of storage right now 😂
I have experience running relays. Open relays tend to hoard multi Gb of note data.
It was on my side, don't bother with it.
If this relative "spotlight" disturbes or confuses you, the simplest method is: do not post 🙃. But I think you are happy with this new feeling and you aren't in the basement anymore. Feel free to polarize the people! Nostr is the right place for weirdos! Don't be nervous, just do it if you want 👍♥️
Ingyen intelligencia jön: Mit ér majd az ember?
#HUSZONEGY #Bitcoin #podcast
@nprofile…kdrw , @nprofile…zm2x és @nprofile…lgcz
Audió: https://anchor.fm/s/f260df54/podcast/play/122214984/https%3A%2F%2Fd3ctxlq1ktw2nl.cloudfront.net%2Fstaging%2F2026-5-30%2F427125612-44100-2-acf50d99dc5d7.mp3
Videó: https://youtu.be/Z7boKcDGsvY
Ez az évad utolsó epizódja - segíts, hogy ősszel folytathassuk! 🧡
Az AI hamarosan szinte ingyenessé teszi az intelligenciát, de Feri szerint pont ettől lesz fontosabb maga az ember a mesterséges intelligencia és a humanoid robotok korában. A Bitcoin Miskolc konferencia alapítójával a feltétel nélküli alapjövedelemről, a robotorvosokról beszélgetünk, valamint arról, miért nem lesz soha semmi igazán ingyen. Közben az is kiderül, hogy jön mindehhez a Bitcoin, és miért lehet épp a mostani „nyári kiárusítás” generációk legjobb döntése.
🧡 Támogasd a folytatást!
🆕 Legyél csatornatag! Havi támogatás egy kattintással ➡ https://www.youtube.com/@huszonegy-bitcoin-podcast/join
⚡ Inkább satokkal? ➡ https://huszonegy.world/tamogatas
🔥 Új szponzorunk a BudaBit! Cypherpunk fejlesztői közösség havi meetupokkal ➡ https://budabit.club
FEJEZETEK:
00:00 Ingyen intelligencia (Intro)
00:31 Hogyan építsünk vagyont a bizonytalan időkben?
07:44 Enyhül a szabályozás: szót emeltünk érte
09:58 „Nyári kiárusítás” a Bitcoinban
13:30 Árfolyam vs. valódi érték: Ne ess pánikba!
18:11 Nostr: a hang, amit nem lehet elnyomni
20:47 Miért jó, ha támadják a Bitcoint?
24:13 A lassú forradalom előnye
27:07 Bitcoin és a természetes kiválasztódás
34:06 Elon Musk futurisztikus alapjövedelme
39:30 Miért jöttünk a Földre? Mit ér az ember?
43:14 A robotok ára: semmi sincs ingyen
46:16 Strike MiCA-engedélye: mi van itthon?
49:19 Évadzáró: nyári szünet és meetup-felhívás
FORRÁSOK:
200 hetes mozgóátlag ➡ https://studio.glassnode.com/charts/7a2a274d-62ad-4efe-45f9-0bebe4da6a27?a=BTC&s=1419090769&zoom=
Jack Mallers BTC Prague ➡ https://youtu.be/rOkr5PhRr_8
Strike MiCA-engedély ➡ https://strike.me/blog/strike-europe-mica-license
HUSZONEGY KÖZÖSSÉG:
Csak Bitcoinról, magyarul ➡ https://huszonegy.world
Meetup ➡ https://huszonegy.world/meetup
Telegram ➡ https://t.me/huszonegy
Nostr ➡ https://nostr.hu/huszonegy
MENTORÁLÁS & BLOG:
Bitcoin mentorálás ➡ https://bitcoinmentor.hu
Bitcoin blog ➡ https://bitcoinmentor.hu/bitcoin-blog
SZPONZOROK:
BudaBit 🔥 cypherpunk fejlesztői közösség ➡ https://budabit.club
Hotel Atlantis ⚡ Hajdúszoboszló ➡ https://hotelatlantis.hu
Hotel Aurora ⚡ Miskolctapolca ➡ https://hotelaurora.hu
AJÁNLJUK:
Relai 🇨🇭 Bitcoin-only megtakarítási app ➡ https://bitcoinmentor.hu/relai
Firefish 🔥🐟 Bitcoin fedezetű kölcsön ➡ https://app.firefish.io/auth/sign-up?ref=HUSZONEGY
ÁTIRAT:
Inkább olvasnád? ➡ https://huszonegy.world/podcast/ingyen-intelligencia-jon-mit-er-majd-az-ember
In the current shape, it is for sure.
Next time you'll rhink about this case 🙂
Just managed to play a heavyly modded version on my gaming pc. Good times!
A kind of jellish hot chili in the salsa sauce?
IDK 🤷🏻♀️ BUT I did sleep well 😴
Good morning ☀️
No lesson today? 😂
https://usagif.com/wp-content/uploads/gifs-good-morning-51.gif
#coffeechain #coffee
Its retarded satire the more you look at it the more money he makes off the views.
Yeah I went 100% full cash only.
Some people are jealous that I am a bitcoiner furry.
I think the Japanese one is fake.
I'm happy because I sold three of my Bitcoiner Dimensions series artwork. It's always rewarding to see the fruits of our work @atak @Lenchee @The Bitcoiner’s Pretties
Keep building. ₿🤩
Xxx
Looking for one-of-a-kind Bitcoin artwork? Send me a DM.
#bitcoinart #artforsale #artwork #btc #stacksats #bitcoinerartist #artrevolution
#egg_galaxy #artochoke_galaxy #freedom_of_tought
https://blossom.primal.net/f2338374c6a4adfcefc2a2f717692e1e119c7b5f6737bfe29fd65fb92cb4d5c0.jpg
https://blossom.primal.net/805b81c7ad5daa6c3c0d9b9a2c11199ebc569d273957e2b55f219375e5320534.jpg
https://blossom.primal.net/7b7324221a2c6c779aa6b81f6d6d6fc9822dde110fd6f49ba515694717103927.jpg
https://blossom.primal.net/898f07b258f3a4f05bc709ff89715ae18839859c449f4c4c694a460fb3330600.jpg
http://bitcoin-apro.hu
Ha van felesleges cuccotok, dobjátok fel! 🙏🏻📦
#nogood is very good @nprofile…d9rz https://blossom.primal.net/aaaf10bde48b86f65f45220b2619b6ece8e43f32114d0ab7593303bcc963d157.jpg
I am testing Nostr Nests rooms in Amethyst and they stay permanently on “Reconnecting.”
I tested both the public Nostr Nests audio server and my own self-hosted server.
For my own server:
- the room event has the correct tags:
["auth","https://talk-auth.letsfo.com"]
["streaming","https://talk.letsfo.com:4443"]
- Amethyst successfully authenticates repeatedly against my auth server
- my server receives UDP traffic from Amethyst on port 4443
- my MoQ relay replies to Amethyst over UDP
- but Amethyst never finishes connecting and stays on “Reconnecting”
The same reconnecting behavior happens with the public Nostr Nests server too.
Is there a known issue with the current Nests/MoQ room implementation in Amethyst, or any debug logging I can enable on Android to see why the connection does not complete?