Avatar
darrell
ff140c396a8f0140db85284c9cc79c6844dfd709b4155c2bd43e0009a737e4be
“I don’t believe we shall ever have a good money again before we take the thing out of the hands of government, that is, we can’t take it violently out of the hands of government, all we can do is by some sly roundabout way introduce something that they can’t stop.” – F.A. Hayek 1984

Finally new login system for LNBits!

No more worrying about getting rekt just because you forgot to bookmark the url!

nostr:note1cpzf9rvqljhgn367vzedhesqhkkjhumanh8mr5vgahnycyf2qgmsexyfp4

green wallet lightning wallet supports splicing out of the box? Wow🤩 nostr:note1sx58yxppt332c36j7qcnxq3tm7rpr29frwaw2rsynty37vxy54xqtj7kww

Replying to Avatar nos

Come work with us on Nos!

Nos is looking to hire an iOS developer.

We are looking for an experienced iOS developer to work on our social media app, Nos.social. This is a full-time position available to anyone who can work core hours of 18:00-22:00 UTC, but we are open to working with contractors as well.

Nos is an open-source application part of the emerging social media commons built on the Nostr protocol. Nos is our attempt to build healthier social media by flipping the traditional power dynamics of social media on their head, giving users ultimate control over their accounts, balancing freedom of speech with freedom of listening.

You’ll be joining a small team distributed around the globe. This role will include collaborating with team members in other timezones and attending weekly planning meetings and daily standups. We’re a team that highly values relationships, humility, and a growth mindset. We resonate strongly with the DWeb principles: https://getdweb.net/principles/

You should have a strong working knowledge of iOS frameworks and be proficient with the Swift programming language. We are looking for someone who is fairly independent and can work with our designer and product lead to take a feature from an idea to a polished product.

Familiarity with the following tools and libraries is ideal:

* SwiftUI* Core Data* Combine* Structured Concurrency (async/await)* git/gitflow* Nostr or other p2p protocols

* Test Driven Development* Slack* Figma

Apply here: https://forms.gle/WMRrVU1zyVRw3FhV7

Hi, I’m interested:) It’s exciting to see Swiftui-navigation and swift-dependencies being used in the app. It’s the only bitcoin/lightning/nostr related SwiftUI app I found so far utilizing pointfree’s libraries. I’m a longtime subscriber of Pointfree and TCA user. Any chance TCA being adopted in nos as well?

Also may I ask why CoreData instead of SwiftData since you’re targeting iOS 17 and above only?

On top of that, it seems all the low level utility tools like secp256k1 and bech32 are also written in Swift, ideally Rust would be a better candidate since Rust/bitcoin ecosystem is much more mature and you can easily export them to Swift using FFI, same applies to nostr-specific tools like rust-nostr, e.g. there’s already SPM package available there.

Primal iOS client will overwrite your existing lightning address if you have one. I understand it’s probably the only way to enable Zaps on Apple platform through forcing users to use its built-in wallet with 30% Apple tax included when you purchase sats for zaps through the app. But for me I have to stop using it now since I want to keep using my existing lightning address.

Bitcoin keeper wallet does not require subscription to create multi-sig wallet anymore, nice!

Japan has the highest inheritance tax in the world. It’s probably the only country in the world that the harder you stack your sats, the wealthier the country’s rulers will become. It effectively disables low time preference strategy to accumulate generational wealth in the country. Maybe it’s time to start learning Spanish.

Tried blockstream green lightning wallet for the first time, it seems it’s using breez SDK under the hood.

It seems snort and iris now uses the same UI, what happened to the old iris web UI 🧐

Hard times create strong men. Strong men create good times. Good times create weak men. And, weak men create hard times.

First non-custodial synthetic stable coin wallet using BDK&LDK.

Here we are: nostr:note1leupqnsfugqqc7yjxhxf84a9ktv3wgddjxfg3uge4wnpq3pwzjaq7vtvzq

Even more exciting: breez/greenlight will also be integrated into LNBits, so finally I will be able to use non-custodial lightning wallet with self-hosted LNBits as frontend without relying on any hosted solution while enjoying not have to maintain my lightning node.

https://github.com/lnbits/lnbits/pull/1897

Looking forward to Alby integration with LNbits

https://github.com/lnbits/lnbits/pull/2086

NHK new documentary featuring Satoshi Nakamoto tonight at 10pm https://www.nhk.jp/p/ts/7PJJ8LNP85/

How Primal trending works

My personal favorite session arrived!!!

When building a permissioned network like Libra on top of permissioned system like fiat money, it failed because the permissioned system doesn’t allow you to build on top of it. Now you choose to build a permissioned network on top of the permissionless network like bitcoin and lightning so no one can stop you from building on top of it, it will still fail because no one will use it.

/// Creates a signed uma pay request.

///

/// # Arguments

/// * `receiver_encryption_pub_key` - the public key of the receiver of the payment. This will be used to encrypt the travel rule information.

/// * `sending_vasp_private_key` - the private key of the VASP that is sending the payment. This will be used to sign the request.

/// * `currency_code` - the currency code of the payment.

/// * `amount` - the amount of the payment in the smallest unit of the specified currency (i.e. cents for USD).

/// * `payer_identifier` - the identifier of the sender. For example, $alice@vasp1.com

/// * `payer_name` - the name of the sender.

/// * `payer_email` - the email of the sender.

/// * `tr_info` - the travel rule information to be encrypted.

/// * `travel_rule_format` - the format of the travel rule information (e.g. IVMS). Null indicates

/// raw json or a custom format. This field is formatted as @

/// (e.g. ivms@101.2023). Version is optional.

/// * `payer_kyc_status` - the KYC status of the sender.

/// * `payer_uxtos` - the list of UTXOs of the sender's channels that might be used to fund the payment.

/// * `payer_node_pubkey` - If known, the public key of the sender's node. If supported by the receiving VASP's compliance provider, this will be used to pre-screen the sender's UTXOs for compliance purposes.

/// * `utxo_callback` - the URL that the receiver will use to fetch the sender's UTXOs.

/// payer_node_pubkey` - If known, the public key of the sender's node. If supported by the receiving VASP's compliance provider, this will be used to pre-screen the sender's UTXOs for compliance purposes.

https://github.com/uma-universal-money-address/uma-rust-sdk/blob/842aa7fe2aa205ea811c7b4f5dbdb032762457e1/src/uma.rs#L373

Here’s my rust implementation about calculating the last checksum word by providing the first 11 or 23 seed phrase words. It was based on a fun experiment I did a while ago by throwing dice to generate seed phrases. The nice thing about rust is I can easily bring it to mobile apps.

https://github.com/aki-mizu/lastword/blob/main/lastword-ffi/src/lastword.rs

Yea, Coincheck was the oldest one. Always good to see new players join the game. For this one the UI looks pretty cool.