Google Pixel is unfortunate the only available hardware that allows third party operating systems to be locked in the bootloader. This means that an attacker with physical access to a turned-off phone cannot just change the operating system.

However, here is the list of required hardware features for full Graphene os support, I'm looking forward to some plebs creating better hardware, but it probably won't be as refined and cheap as google...
https://grapheneos.org/faq#future-devices

And yes, there have been numerous security audits by third parties, with bugs reported and merged to Graphene os. Further, Graphene devs have reported, patched and shipped fixes to upstream dependencies which were merged, so in a sense the upstream maintainers have audited that code.
https://grapheneos.org/faq#audit

In general, I can recommend reading the Graphene os website, there's a lot of interesting info.


Flashing it yourself is super easy, just read the website and click the buttons.
https://grapheneos.org/install/


Keep building bro!


Bullish, this is great progress!


The third in a series of weekly updates detailing progress on bringing MLS protocol DMs and group messaging to Nostr.

This is a long form article, you can read it in https://habla.news/a/naddr1qvzqqqr4gupzq9eemymaerqvwdc25f6ctyuvzx0zt3qld3zp5hf5cmfc2qlrzdh0qqxnzdejxqmnwwpc8qcr2vectx9xjf

This is the third in a series of weekly updates detailing progress on bringing MLS protocol DMs and group messaging to Nostr.

## Previous Updates

- [June 28th 2024](https://habla.news/u/jeffg.fyi/1719562889267)
- [July 6th 2024](https://habla.news/u/jeffg.fyi/1720256910765)

## Progress this week

Short update post this week but I made solid progress updating several OpenMLS dependencies and building a new library that implements all the OpenMLS crypto requirements for Nostr.

### HPKE-RS

I mentioned a PR last week on the `rust-hpke` library, that PR is still waiting on review. However, in the meantime, the OpenMLS library depends on a slightly different hpke library, the `hpke-rs` library.

This library didn't support the secp256k1 curve either so I've [opened a PR](https://github.com/franziskuskiefer/hpke-rs/pull/66) to add support for secp256k1. That PR uses the `RustCrypto` library that is the default in the the `hpke-rs` library. However, because this library is built to allow for swapping out the underlying crypto library (using traits), I was also able to create a new library that uses the `secp256k1` library instead of the `RustCrypto` library. This is the main crypto library that almost all Bitcoin and Nostr apps use so it's important we use that instead of `RustCrypto`.

### OpenMLS Nostr Crypto

The library that I've created ([openmls-nostr-crypto](https://github.com/erskingardner/openmls_nostr_crypto)) does a few things via separate sub-libraries (crates). The entire library tries to do as little as possible; only implementing the one required ciphersuite for all MLS implementations and the `secp256k1` schnorr signatures ciphersuite I've created for Nostr. It's also using the right `secp256k1` library to do it.

**openmls-nostr-crypto:** implementes the crypto traits that the OpenMLS library expects to find for a given provider and removes all the ciphersuites that we don't care about supporting.

**hpke-rs-nostr-crypto:** This implements the crypto traits that the hpke-rs library expects to find. Again removing all the ciphersuites we don't care about supporting.

I've not yet written any tests for these libraries (which needs to be done) but I've gotten some very simple demos working with OpenMLS using this new set of libraries to handle the crypto.

I've been really impressed with the simplicity of the OpenMLS interface as well. While there is A LOT going on under the hood, the public interface that client developers have to use is clean and simple.

## Onward and Upward

Next week I'll continue working on these libraries; adding tests and continuing to build out my small demo app. I've been in touch with the maintainers of the OpenMLS library and I'm hoping to get a review done with them on my PRs and on my new library.

One thing I'll call out here: The review of my library and getting them to review the direction of the project overall will be paid consulting so I'm making sure that I've got as much done as possible before scheduling that time and paying their rates. I'm a strong believer that the right conversation can save you months of wasted time, but I'm also a believer in making sure you're prepared if you're going to drop money on that conversation. 😅


I’ve just dropped my weekly update on the MLS messaging progress. It’s a short one this week but don’t let that fool you, I’m feeling very bullish about the progress. 🤙

Huge thanks to nostr:npub1klkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qulx3vt and nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft who spent multiple hours each with me on calls talking through ideas. 🙏

nostr:naddr1qvzqqqr4gupzq9eemymaerqvwdc25f6ctyuvzx0zt3qld3zp5hf5cmfc2qlrzdh0qqxnzdejxqmnwwpc8qcr2vectx9xjf


Yet another naughty array of pixels.


 nostr:npub167hmfzj38hkumks4wxny89797la0sf7wnwfrw4enlmcl82msp0cs78schc 2.1.0 is now available on the  nostr:npub126ntw5mnermmj0znhjhgdk8lh2af72sm8qfzq48umdlnhaj9kuns3le9ll / #StartOS beta community marketplace: https://marketplace.start9.com/wasabi-webtop?api=community-beta-registry.start9.com&name=Community%20Beta%20Registry

Access your favorite privacy-focused wallet through a web-browser, running 24/7 on StartOS.


Steps how to receive sats ⚡ to custom #BOLT12 address with your own domain via #Phoenix Wallet:

1. Download the latest version of Phoenix Wallet and copy your BOLT12 offer by selecting “Show reusable QR Code”. Starts like this ➡ lno1z..

2. Next, add a TXT record to your domain.
In my case it was Namecheap:
- In the Dashboard, select your domain and click “Manage”
- Go to the “Domain” section and find “Advanced DNS”

3. Phoenix enforcing DNSSEC.
In “Advanced DNS” tab click on DNSSEC toggle to enable it (FYI not all of the registrars support it). Click “Generate DS record”, save the changes.

4. Click “Add new record” and choose type TXT Record.
For the HOST:
<YourName>.user._bitcoin-payment
And for the VALUE:
bitcoin:?lno=<YourBOLT12Code>

✅

This will create the address <YourName>@<yourdomain>.com


Just stumbled across nostr:nprofile1qqs0zuj4s6jq9sr2ajqc69rc53d25rwpd3afcjrfm97r2qek69hcuscpzpmhxue69uhkummnw3ezumt0d5hs3td67d npub, definitely give him a follow, highest quality signal!


#dev #CLN

I've spent the last few workdays completely reworking our onion message code.  This was scattered in various places and I wanted to unify it, and also written several years ago and I'd forgotten how the protocol actually works!

onion messages are *double* encrypted; this is the main source of confusion!  At the high layer, they're a series of nested encrypted calls ("onionmsg_tlv" in the BOLT 4 spec), so each recipient decrypts and hands it on: this is exactly the same as we use for payment information.  But inside that is *another* encrypted blob (onionmsg_tlv.encrypted_recipient_data), which requires a tweak which was handed to you alongside the onion, for you to decrypt (into an "encrypted_data_tlv").  Inside that is all the information about where to send next, any restrictions, and allows you to calculate the *next* tweak to hand on (it can also override the next tweak).

The double encryption is necessary because there are *three* actors here: Alice wants Bob to send her a message, without revealing her identity. So she gives Bob a "blinded path" which goes via Charlie: this path contains Charlie's pubkey (where to start the path), a blinding tweak, and two encrypted blobs for Alice to put into each layer of the onion message.  The first an encrypted blob which Charlie can read, which contains her pubkey so he knows where to send it next.  The second is her own, and contains a secret specific to the purpose of this message, so Bob can't play games trying to use this blinded path for anything else ("hey, are you the same node as this previous payment?") or use a different blinded path for this purpose.  She can also add dummy hops (we don't yet), which she will simply absorb, to obscure the path length from Bob.  You can add padding to make the hops indistinguishable (we don't yet).

Bob puts the actual stuff he wants to send Alice into the final onion call (often including his own blinded reply path!), along with the encrypted blob.

Importantly, even if Bob were sending a message *not through a blinded path* he would use the same double-encrypted format: that's so Charlie can't tell whether a blinded path is being used or not, even though it's slightly less efficient.  Crypto is cheap these days, too.

Now, if Alice gives Bob a blinded path to Charlie and Charlie is Bob's peer, he can simply send the onion and the first blinding tweak to Charlie.  But if Alice needs to send the message via Dave to Charlie, she needs to prepend a step.  That's not quite possible, naively, because blinding tweaks are generated *forwards*, and she needs Charlie to get the right blinding tweak from Dave, and Alice has no way of making that happen.  So inside Dave's encrypted blob, she uses next_blinding_override to tell Dave to hand that blinding override to Charlie instead of the normal one.  I just implemented this for Core Lightning (previously we would simply connect to the first node, which is privacy-compromising and should only be done as a last resort).

These blinded paths have some nice properties: you can't use part of them (you don't know the blinding factor except for the first one, so you can't start in the middle, and you can't replace any data), you need to use all of them.  They can contain timelimits to avoid easy probing, too: a classic measure would be to see if the path fails when a given node is down, but that takes time.  The spec insists all errors within the blinded path are the same, and originate from the entry: this loses some analytical power on failure, but makes probing harder.  The entry point is supposed to add a random delay (we don't yet!).  There may still be implementation differences, but they're hard for Bob to probe (and Alice doesn't need to, as she set up the path).


Excellent pod about many security vulnerabilities in Bitcoins history.

https://podcastindex.org/podcast/4473671?episode=24966944150


Freedom tech relies on users stepping up and contributing wherever they can.

If you're a dev, consider reviewing some open PRs. If you're a writer, publish a blog or post on forums. If you're a teacher, teach others why it's important tech. If you're an uncle Jim, help others to install and set everything up.

And regardless of who you are, consider sending financial support as well. Most contributors to freedom tech would earn insanely more money if they worked in slave tech.

It's your moral obligation to support the people who work on the tools of your liberation.


GrapheneOS really is an exemplary free and open source software project.

Building ontop of a FOSS base, adding numerous security and privacy hardening features, contributing to upstream dependencies with countless vulnerability disclosures and shipping patches to fix upstream bugs.

Thanks to all contributors!


Today we are excited to release "Autoswap", which fully automates liquidity management for your Lightning node using Liquid  🚀

Dive into our guide, walking you through how it works and how to set it up 👇

https://blog.boltz.exchange/p/guide-how-to-use-boltz-clients-autoswap


"🧪 Phoenix now supports BIP-353 LN addresses

To create your address (must have a channel):
- android: Settings > Experimental features
- ios: soon™
- server: ./phoenix-cli getlnaddress

Phoenix (android/ios/server) can all send to both BIP-353 and LNURL addresses"

https://x.com/PhoenixWallet/status/1811442125801705638

Now we just need nostr zaps support for BIP-353..


Yeah, it takes a while until the mosaic of the story gets together, but I think there is fascinating dialog right from the start.


What do you not get?


I'm done with recording chapter 1!

nostr:nprofile1qqswrmfr6c0u6j6d34jh8sydcxwe20eeufv4hkk739auh2h9yejfqpqpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qyvhwumn8ghj7mrfva58gmnfdenhyetvv9ujucm0d5hszythwden5te0dehhxarj9emkjmn99uy07x2f will do the edit, and we'll publish chapter by chapter as soon as it's done.

If you haven't yet read The Lodging of Wayfaring Men, stay tuned, you're in for a treat.

nostr:nevent1qqsg59lgp5gka6q2u4ue0nar39v4jjy5ua9prenwtevv8f9gcjjwargpremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59upzpdlddzcx9hntfgfw28749pwpu8sw6rj39rx6jw43rdq4pd276vhuqvzqqqqqqy22ksdm


The level of attack against freedom tech is escalating, brace yourself.

nostr:nevent1qqsqqqyr9kq6ajn7srdwmkdzqsupanw82l9qeyrpknxz0hkv08l0haspzpmhxue69uhkummnw3ezumt0d5hsygy7xr55qguvm847h33js9md6ngsnqfp99zz72nv8pe8l3n05l4fpgpsgqqqqqqs0hpm5q


Can we increase the max limit of requests, or make it dynamic?


NIP-88
======

Recurring Subscriptions
-----------------------

`draft` `optional`

This NIP defines a way for a pubkey to create recurring subscription payments to another pubkey.

Actors in this flow:
* Recipient: A pubkey that receives recurring payments
* Subscriber: A pubkey that sends recurring payments
* Payment verifier: An optional pubkey recipients can designate to verify payments on their behalf

# Kinds
`kind:37001` - Tier Event -- Optionally published by recipients
`kind:7001` - Subscribe Event -- Published by subscribers
`kind:7002` - Unsubscribe Event -- Published by subscribers
`kind:7003` - Subscription Payment Receipt -- Published by payment-verifier-pubkey

## `kind:37001`: Tier Event
A pubkey that wants to provide others the ability to subscribe to them can create "tiers". These tiers might provide certain benefits to the supporters who subscribe to these.

```js
{
    "kind": 37001,
    "content": "<description of the tier>",
    "tags": [
        [ "title", "..." ],
        [ "image", "..." ],

        // Perks
        [ "perk", "<description>" ],
        [ "perk", "<description>" ],

        // Amount possibilities
        [ "amount", "<amount-in-base-unit>", "currency", "<monthly>" ],
        [ "amount", "<amount-in-base-unit>", "currency", "<quarterly>" ],

        // Zap-splits
        [ "zap", "<recipient-pubkey>", "relay-url", "19" ], // 95%
        [ "zap", "", "relay-url", "1" ], // 5%

        // Relay and payment-verification
        [ "r", "wss://my-subscribers-only-relay.com" ],
        [ "p", "<payment-verifier-pubkey>" ],

        // A unique identifier
        [ "d", "<random-id>" ],
    ]
}
```

`.content`: description of what subscribers can expect.
Tag `title` is an optional title for the tier.
Tag `image` is an optional image for the tier.
Zero or more `perk` tags specify the benefits of the tier; these can be rendered as a list of benefits to the user in addition to the content.
One or more `amount` tags specify the payment required for this tier and its cadence.
    * The first argument should be the stringified amount in cents or msats, and the second argument the currency
    * The third argument SHOULD be one of `daily`, `monthly`, `yearly`
One or more `amount` tags MUST exist.
Zero or more `zap` tags can exist as defined in NIP-57.

A `zap` tag with no pubkey indicates that the client can include any pubkey in the `kind:7001` event (and in the resulting recurring zaps). This way, users can offer a "referral" fee to other clients.

An `r` tag can be included to specify a relay where clients can find special content for this tier.

Zero or more `p` tags can be included to specify a pubkey that is trusted by the tier creator to verify payments on their behalf.

#### Examples
* `[ "amount", "100", "usd", "daily" ]`, $1.00 a day.
* `[ "amount", "1000000", "msats", "daily" ]`, 1000000 millisats a day.

## Subscribe Event

```js
{
    "kind": 7001,
    "content": "<optional-message>",
    "tags": [
        [ "p", "<recipient-pubkey>" ],
        [ "e", "<supporting-tier-event-id>" ],
        [ "event", "<stringied-event-subscribed-to>" ],
        [ "amount", "<amount-in-base-unit>", "<currency>", "<cadence>" ],

        // Zap-splits
        [ "zap", "<recipient-pubkey>", "19" ], // 95%
        [ "zap", "fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52", "1" ], // 5% to client developer where subscription was created
    ]
}
```

When a user wants to subscribe to support a user they create a `kind:7001` event.

* `.content` is an optional message the supporter can write.
* The `p` tag MUST tag the pubkey being supported.
* The `e` tag is optional; it should point to a `kind:37001` support tier event. There MUST be exactly 0 or 1 `e` tag.
* The `event` tag is optional; subscribers can opt to keep the version of the event they subscribed to. There MUST be exactly 0 or 1 `event` tag.
* The `amount` tag specifies what the supporters is committing to pay to the supported pubkey and the cadence. MUST be equal to one of the amounts specified in the
`kind:37001` event if one is tagged. There MUST be exactly 1 `amount` tag.

The `kind:7001` event can be created without an `e` tag so that users can create recurring support events without the pubkey receiving the support having explicitly created a support tier.

### Zap splits
`kind:7001` events can include zap splits as defined in NIP-57. Zap splits MUST be copied by clients as they exist in the `kind:37001` event being subscribed to. When an event has a `zap` tag with no pubkey, clients can discard it, or add the client developer's pubkey, or any other user they wish to receive a share of recurring subscriptions.

## Paying
The supporting user should create a zap `p`-tagging the receiver and e-tagging the `kind:7001`. There MUST be a single `p` and a single `e` tag in the zap request.

```js
{
    "kind": 9734,
    "content": "",
    "tags": [
        [ "p", "<recipient-pubkey>" ],
        [ "e", "<kind-7001-event-id>" ]
    ]
}
```

Clients supporting this NIP can check for zaps e-tagging the `kind:7001` event to find the pubkeys that have a valid, paid subscriptions at each different period.

The same `kind:7001` is re-zapped on a regular basis per the cadence specified in the event.

## Stopping a subscription
A user who wants to signal they are no longer subscribed can publish a `kind:7002` event tagging the `kind:7001` they are stopping and `p`-tagging the pubkey they are no longer subscribed to.

```js
{
    "kind": 7002,
    "content": "<optional-message>",
    "tags": [
        [ "p", "<recipient-pubkey>" ],
        [ "e", "<kind-7001-event-id>" ],
    ]
}
```

## Subscription Payment Receipt
When a subscription payment is made and a `payment-verifier-pubkey` is set on the `kind:37001` this pubkey publishes `kind:7003` events tagging the `kind:7001` event that was paid and `p`-tagging the pubkey that received the payment.

```js
{
    "kind": 7003,
    "content": "<optional-message>",
    "tags": [
        [ "p", "<recipient-pubkey>" ],
        [ "P", "<subscriber-pubkey>" ],
        [ "e", "<kind-7001-event-id>" ],
        [ "valid", "<from-timestamp>", "<to-timestamp>" ]
        [ "tier", "kind:37001-d-tag" ]
    ]
}
```

`p` is the pubkey that received the payment.
`P` is the pubkey that made the payment.
`e` is the `kind:7001` event that was paid.
`valid` is the period for which the payment is valid.
`tier` is the d-tag of the `kind:37001` that this subscription is for.

# Appendix 0: Verifying Payment
The following conditions must be met to verify a payment:

* Time between zap receipts should be equal or less than the cadence specified in the `kind:7001` event.
* Amount of the zap receipt should be equal or greater than the amount specified in the `kind:7001` event. For currencies not directly supported by the zap spec, clients should do a best effort conversion to the currency specified in the `kind:7001` event at the time of zap receipt.
* Zap-receipts should include a zap request `e`-tagging the `kind:7001` event. Zap-receipts might not include a signature (for NWC-automated payments where the subscriber is not present to sign the zap request).
* Validations specified in [NIP-57](https://github.com/nostr-protocol/nips/blob/master/57.md).

If `kind:7003` events are published by the payment-verifier-pubkey, clients can use these to verify payments more simply.


Yeah, but the DVM feed stops after a few posts, an endless scroll would be nice.


Is there a way to get the Nostr Band or Primal trending feeds in Amethyst?
nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug


Looking forward to hearing this conversation.

nostr:nevent1qqsfkn4lq3nqfru5r7346ra2em6d0yq3rvgxyplfmkqehj0lh3khvgcppemhxue69uhkummn9ekx7mp0qgsgnc2tuj0dqpea4qak0qnee55m5kkcdncqpd4r6xjv8hz25n7aqtqrqsqqqqqpnfxwfn


Because most surveillance is done by outlaws.

Instead we must build easy and cheap to use  defensive privacy technologies. (which funnily will be outlawed)


Breakfast literally means to break a fast, only dead people can skip breakfast, you just delay it a bit.


That's the plan.


Almost done with recording chapter one!

nostr:nevent1qqsg59lgp5gka6q2u4ue0nar39v4jjy5ua9prenwtevv8f9gcjjwargpremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59upzpdlddzcx9hntfgfw28749pwpu8sw6rj39rx6jw43rdq4pd276vhuqvzqqqqqqy22ksdm


nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spzpmhxue69uhnzdps9enrw73wd9hszynhwden5te0wp6hyurvv4cxzeewv4eszynhwden5te0wfjkccte9enrw73wd9hsxv8qkt is the notes while you were gone DVM down?


*not yet


Wasabi's Buy Anything Button


Yeah, wild adventure.


Good old times
https://www.youtube.com/watch?v=HfHgzPtj90U


Humans can reverse entropy willfully.


Work is recreating the world according to our will.


AML/CFT laws make you less safe. Not more.

In 2022, 78% of European banks experienced a data breach. Yet AML/CFT laws continue to attempt to mandate increasing amounts of data collection, from IP Addresses to social media activities. This data is routinely targeted, exploited, and sold on dark markets.

In honor of gigabrain takes like "We NeEd SuRrVeiLlAnCe To FiGhT CrImE", this Rage Weekly I compiled a list of 40+ recent data breaches involving the leak of personal data – just in case anyone tries to tell you that increased surveillance leads to an increase in security.

Full list 👉 https://www.therage.co/rage-weekly-data-breach-special/


I've been for five years on a no-bank bitcoin standard.
Maybe it's time to do radical value for value next.


True.

It's just that when there's more than 10 there's simply no excuse anymore.


Dolphin llama 3 70b is great


If there are more than 10 bitcoiners in your close vicinity, you ought to start a regular meeting.


"those who give up essential privacy for number go up will get none of them in the long run"

... inspired by the latest episode of nostr:npub14kw5ygpl6fyqagh9cnrytyaqyacg46lzkq42vz7hk8txdk49kzxs04j7y0 feat. nostr:npub1klkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qulx3vt 🔥

#plebchain #deepstr #PrivacyGoUp

https://fountain.fm/episode/ATkyeNluMY2138QbZO5E


Here's a beautiful talk by the author, gives you a glimpse of the spirit of the book.

https://www.youtube.com/watch?v=Sz-vG4FG1tY

nostr:nevent1qqsg59lgp5gka6q2u4ue0nar39v4jjy5ua9prenwtevv8f9gcjjwargpremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59upzpdlddzcx9hntfgfw28749pwpu8sw6rj39rx6jw43rdq4pd276vhuqvzqqqqqqy22ksdm


Not sure if you can build anything fancy for 2k sats though...


So how is Silent Payments going? nostr:npub1art8cs66ffvnqns5zs5qa9fwlctmusj5lj38j94lv0ulw0j54wjqhpm0w5 and me asked Ruben and Josie for an update: https://bitcoinexplainedpodcast.com/@nado/episodes/episode-94-silent-payments-part-2


I'm looking for a few people to help beta test Fountain's new nostr integration - ideally you already use Fountain but not a strict requirement!

Please DM me if you're interested and repost for visibility!

#asknostr


nut cloud


This guy gets it.
Savage sats stacker.


I have copies for sale at my bookshop.

https://thebitcoinshop.uk/product/a-lodging-of-wayfaring-men/


If you think the hunt for this book is difficult, just try finding the follow up book The Breaking Dawn 😉


nostr:nprofile1qqszh6vr6v4f342d287qchrf88mc9w3l3znx63884fwwe754jw5gujqpz4mhxue69uhk2er9dchxummnw3ezumrpdejqzrthwden5te0dehhxtnvdakqzxthwden5te0wfjkccte9eekummjwsh8xmmrd9skctcu0gzyc I could keep tagging you under crys of outrage for a lack of print, but I think you get the point 😂


A Lodging of Wayfaring Men is a novel by Paul Rosenberg that follows freedom-seekers as they create an alternative society on the Internet - a virtual society with no possibility of oversight or control. The story leads readers through a clever plot where principles of economic freedom, individuality, and justice lead to the creation of a free market uncontrolled by governments or tax men.

The novel was instantly named Freedom Book of The Month and became a major influence in the Cyber-underground. It depicts how this virtual society grows so fast that it terrifies governments and their "security." With no possibility of oversight and control, the System fights to co-opt this cyber-society before it undermines and overwhelms the dominance of corruptocrat governing elites.

The free souls in the novel guide readers through a thought-provoking narrative that explores the potential of a free market society built on the foundations of individual liberty and justice.


Cause this is a book no mainstream publisher would ever put to print.

That's why we need freedom printers like nostr:nprofile1qqszh6vr6v4f342d287qchrf88mc9w3l3znx63884fwwe754jw5gujqpz4mhxue69uhk2er9dchxummnw3ezumrpdejqzrthwden5te0dehhxtnvdakqzxthwden5te0wfjkccte9eekummjwsh8xmmrd9skctcu0gzyc


nostr:nprofile1qqszh6vr6v4f342d287qchrf88mc9w3l3znx63884fwwe754jw5gujqpz4mhxue69uhk2er9dchxummnw3ezumrpdejqzrthwden5te0dehhxtnvdakqzxthwden5te0wfjkccte9eekummjwsh8xmmrd9skctcu0gzyc I smell a great opportunity...


I think Bitcoin brings about something that was not really possible before - Anonymous monetary gifting.

In normal gifting, the receiver generally feels a reciprocal burden. The need/desire to even the score. Whether that's explicit or implicit, that burden cannot be escaped because the receiver knows who gifted him the value (the author talks about this). It may be repaid by a future gift or future favour but the sense of obligation is hard to avoid. Reciprocity is hardwired into our behaviors as social creatures.

To be able to give unconditionally while still allowing for the reciprocity to be paid (anonymously or otherwise) is pretty special. Value is subjective & providing value to another can provide value in & of itself. I give for the selfish reason that it feels good to give, I do not do it from some altruistic quality I posses.

Prior to Bitcoin, I'd need to provide a physical location for reciprocal gifts to be placed anonymously. This requires the consumer to donate there & then. They cannot donate 2 days later in bed when they feel a random sense of gratitude & desire to reciprocate. If I don't provide a way to reciprocate, the gift is not enjoyed as much by those who now feel a sense of obligation. I feel this discomfort & it impacts the value I experience from giving because of the perceived burden.

Take the Assange donation of 8 BTC to cover the debt forced onto him by the Aus gov. He cannot know specifically who donated the money. If he feels a sense of obligation around this gift, he can only pay it forward in a general sense. He cannot directly provide value back to the gifter. There are also no conditions tied to the gift & if someone later tries to claim there are, the gift cannot be rescinded (Bitcoin's finality of settlement). Unconditional giving is a beautiful act that was not easily achieved before Bitcoin.

I'm a little disappointed that the author didn't mention Bitcoin in the 468 page paper. I guess we're still early.


That's a beautiful thought.


Ok, I'll do it.


This will be the fourth time I read the book, and it's gotten better with every reread so far, really looking forward to it.


Ok, I'll do it.

Incoming in two weeks!

nostr:nevent1qqsg59lgp5gka6q2u4ue0nar39v4jjy5ua9prenwtevv8f9gcjjwargpremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59upzpdlddzcx9hntfgfw28749pwpu8sw6rj39rx6jw43rdq4pd276vhuqvzqqqqqqy22ksdm


The pdf is...


Abundance, Generosity and the State, by Jörg Guido Hülsmann

This is basically a book about value for value.

https://mises.org/library/book/abundance-generosity-and-state-inquiry-economic-principles


idk, but I guess there's parallelization, similar to gpus.


Yeah, that's a nice solution, it feels extra special when the sats are earned from a post.


Is there a monero mining pool that pays out in bitcoin ecash?


The SHA-256 algorithm processes input data to produce a 256-bit hash value. Here's a step-by-step walkthrough of the algorithm:

1. Padding: The input message is padded to make its length a multiple of 512 bits. This is done by appending a single '1' bit, followed by '0' bits, and then a 64-bit representation of the original message length.

2. Initialization: Eight 32-bit buffers (A to H) are initialized with specific hexadecimal values derived from the first 32 bits of the fractional parts of the square roots of the first 8 prime numbers.

3. Message schedule: The padded message is divided into 512-bit blocks. Each block is further divided into 16 32-bit words. These words are expanded into 64 32-bit words using a specific formula.

4. Compression function: This is the core of the algorithm, consisting of 64 rounds of operations. In each round:
The current state (A to H) is mixed with the message schedule word and a constant K[i].
Bitwise operations (AND, XOR, rotations) are performed.
The state is updated for the next round.

5. Final addition: After processing all blocks, the final values of A to H are added to their initial values.
Output: The final state of the eight 32-bit words (A to H) is concatenated to produce the 256-bit hash value.

This process ensures that any change in the input, no matter how small, results in a completely different hash value, making SHA-256 useful for integrity verification and digital signatures.


Maybe even mine a shitcoin and instantly dump it for ecash sats?


That would always require additional user input...


Great point, though that personalization could come early on in the UX journey still, it's just that the first screen is instantly useful, instead of yet another account creation flow.


All good points.

My point is that we shouldn't have to degrade the onboarding UX of a single client to fight the global spam problem.

These are two separate problems and should be addressed with dedicated tools, a solution is more usable, robust and automated relay management tools.


This might not even be a problem that needs to be solved client side.

Relays already have their own spam protection mechanisms.


So what?
That has always been a case, spammers will likely use custom scripts that optimize the attack.


How many sats could a modern phone mine within an hour or so?

Obviously not much, but is it at least > 3 sats?

If yes, this might be a good opportunity to have a "faucet" in any app, the mining pool could payout ecash, and the user gets started with at least some sats to start zapping.


Iris did this almost perfect, the user only had to type in a username and be done with it.

Shoutout to nostr:nprofile1qqsy2ga7trfetvd3j65m3jptqw9k39wtq2mg85xz2w542p5dhg06e5qpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxrhwden5te0dehhxarj9enx6apwwa5h5tnzd9az7qgwwaehxw309ahx7uewd3hkctczcs834

It could be even better with simply ignoring the user name at first, or potentially adding a randomly generated nym by default in the kind 0.


nostr:nprofile1qqsr7acdvhf6we9fch94qwhpy0nza36e3tgrtkpku25ppuu80f69kfqpzdmhxw309akx7cmpd35x7um58g6rsd3eqyxhwumn8ghj7mn0wvhxcmmvqyg8wumn8ghj7mn0wd68ytnhd9hx2px56dk I was quite frustrated with having to setup a dummy nsecbunker account, when I just quickly wanted to have a throwaway account for this specific nest.


Tip for nostr apps:

Nostr has a super power, generating an "account" is as simple as generating a private key.

The first time user experience can therefore be **fully automated**!

This is a MASSIVE UX win, we take the initials user journey from 5 clicks for username, password, email etc, and we reduce it to 0 (!!!!) clicks.

User lands on the website, and EVERYTHING JUST WORKS. Initially with a "guest account", but later the user can either add metadata to this new key, log in with an existing nsec or nsecbunker, or add a new nsecbunker setup with another provider.

We can therefore delay the nuances and complexities of account generation to an arbitrary point later in the user journey.


nostr:npub1hqaz3dlyuhfqhktqchawke39l92jj9nt30dsgh2zvd9z7dv3j3gqpkt56s and I couldn’t be more appreciative of nostr:npub1klkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qulx3vt's devotion to the Pleb culture and eloquent way of educating listeners, including myself.

nostr:npub14kw5ygpl6fyqagh9cnrytyaqyacg46lzkq42vz7hk8txdk49kzxs04j7y0 Episode 68 was a glorious success and we encourage you all to listen in via Fountain App and support V4V.

Thank you #Plebchain who listened live via Nostr Nests.

For those that missed the live, enjoy!
https://fountain.fm/episode/ATkyeNluMY2138QbZO5E


No doubt this would be a primitive form of money and society, but I would guess that humans figured out how to store especially honey and tallow for a prolonged time, much sooner than we figured out the nuances of metallurgy


FOSS uncensored models are getting larger and better.
https://huggingface.co/cognitivecomputations/dolphin-vision-72b/tree/main


Impressed by nostr:nprofile1qqspwwwexlwgcrrnwz4zwkze8rq3ncjug8mvgsd96dxx6wzs8ccndmcpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qtxwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx2tmwwp6kyvt6w46kz6nyxa6nxumc8pu82wfj09shvwt2wau8qu3cxvukxuesdd3nxufkws6nvanyx46njufsxvehsmtgwd4nvcejw43n7cnjdaskgcmpwd6r6arjw4jszxrhwden5te0dehhxarj9enx6apwwa5h5tnzd9az77vr4lw progress on secure private messages on nostr.

Bullish


The second in a series of weekly updates detailing progress on bringing MLS protocol DMs and group messaging to Nostr.

This is a long form article, you can read it in https://habla.news/a/naddr1qvzqqqr4gupzq9eemymaerqvwdc25f6ctyuvzx0zt3qld3zp5hf5cmfc2qlrzdh0qqxnzdejxqer2d3exycrwd342u5qhf

This is the second in a series of weekly updates detailing progress on bringing MLS protocol DMs and group messaging to Nostr.

## Previous Updates

- [June 28th 2024](nostr:naddr1qvzqqqr4gupzq9eemymaerqvwdc25f6ctyuvzx0zt3qld3zp5hf5cmfc2qlrzdh0qqxnzde38y6nvv3c8qunyd3hakfln0)

## Progress this week

This week was mostly spent on the topic of how to properly publish prekey bundles and what would be needed in the bundle itself to make it workable. I've included an early version of the spec below for prekeys, and would love thoughts on it. Treat this as an alpha version, very subject to change.

The other thing I spent time on was making changes to the OpenMLS library to add support for our custom ciphersuite. One issue that I've run into is that the IETF standard for HPKE doesn't include the secp256k1 curve. Because of this, the library being used in the OpenMLS library doesn't implement the necessary methods using our curve. Thankfully, there is another library with [an open PR](https://github.com/rozbb/rust-hpke/pull/59) (shout out to nostr:npub1yevrvtp3xl42sq06usztudhleq8pdfsugw5frgaqg6lvfdewfx9q6zqrkl for that!) that would fix this. Additionally, there's an [expired proposal](https://www.ietf.org/archive/id/draft-wahby-cfrg-hpke-kem-secp256k1-01.html) to add secp256k1 to the HPKE spec itself. I've bumped both of these and will continue to follow up. Even without the formal addition to the spec, if we have a working library, I can add that to the OpenMLS library.

## Spec Draft for Prekeys

### Initial keying material (Prekey Event)

Each user that wishes to be reachable via MLS-based messaging MUST first publish a prekey event. Prekeys are used to authenticate and add members to groups (one-to-one DMs or groups with more than two participants) in an asynchronous way. The prekey event is a simple replaceable event and contains all the information needed to add a user to a group.

Prekeys SHOULD be used only once. Resuse of prekeys can lead to replay attacks.

In most cases, clients that implement this NIP will manage the creation and rotation of the prekey event. It's recommended that clients do so interactively with user consent in order to avoid overwriting prekeys created by other clients.

#### Derived vs Ephemeral Prekeys

Since prekeys are generated on a single device/client pair, the private key of the prekey must be either stored or generated in a way that can be deterministically recovered.

The recommended approach is to use derived keys, generated in the manner described in [NIP-06](https://github.com/nostr-protocol/nips/blob/master/06.md). In this way, the user can respond to a new group request from any device/client pair, not just from the same device/client pair that created the initial prekey event. If using derived keys;

* Clients MUST use `104` as the `account` level value and `0` at the `change` level value (e.g. `m/44'/1237'/104'/0/0`).
* Keys are then generated using public derivation by incrementing the `address_index` level value.
* Clients MUST include the full derivation path corresponding to the key used in the `content` field on the prekey event.
* The `content` field MUST be encrypted using standard [NIP-44](https://github.com/nostr-protocol/nips/blob/master/44.md) encryption (encrypted to themselves).

However, for added security (and consequently a more restrictive user experience), clients can chose to generate an ephemeral key and store the private key locally. This means that users will only be able to respond to new group requests from the same device/client pair and won't be able to respond at all if the prekey's private key is lost. Ephemeral keys can also be used with minimal degredation of UX if you're using a remote signer that can manage these keys.

If using an ephemeral key;

* The `content` field on the prekey event MUST be filled in with `EPHEMERAL` and then encrypted using standard [NIP-44](https://github.com/nostr-protocol/nips/blob/master/44.md) encryption (encrypted to themselves). This ensures that anyone looking at prekey events cannot tell whether it's a derived or an ephemeral prekey.

#### Example Prekey Event

```json
  {
    "id": <id>,
    "kind": 10443,
    "created_at": <unix timestamp in seconds>,
    "pubkey": <main identity pubkey>,
    "content": <encrypted derivation path | EPHEMERAL>,
    "tags": [
        ["mls_protocol_version", "1.0"],
        ["ciphersuite", "MLS_256_DHKEMK256_CHACHA20POLY1305_SHA256_K256"],
        ["pubkey", <prekey pubkey>],
        ["prekey_sig", <signature generated from hex encoded pubkey of the prekey>],
        ["r", "wss://nos.lol"],
        ["r", "wss://relay.primal.net"]
    ],
    "sig": <signed with main identity key>
}
```

#### Tags
* The `mls_protocol_version` tag identifies the MLS protocol version being used. For now, this MUST be `1.0`
* The `ciphersuite` tag identifies the ciphersuite supported. For now on Nostr, we're using a custom ciphersuite, `MLS_256_DHKEMK256_CHACHA20POLY1305_SHA256_K256`. [Read more about ciphersuites in MLS](https://www.rfc-editor.org/rfc/rfc9420.html#name-mls-cipher-suites).
* `pubkey` is the derived or ephemeral prekey pubkey.
* The `prekey_sig` tag value is a Schnorr signature (over the secp256k1 curve) of the SHA-256 hashed value of the prekey's pubkey, signed with the prekey's private key.

```js
const privKey = schnorr.utils.randomPrivateKey();
const pubKey = schnorr.getPublicKey(privKey);

const prekeySig = bytesToHex(
  schnorr.sign(bytesToHex(sha256(pubKey)), privKey)
);

const prekeyTag = ["prekey_sig", prekeySig];
```

Finally, clients SHOULD include `r` tags to identify each of the relays that they will attempt to publish this prekey event to. This allows for more complete replacement of prekey events at a later date.

### Replacing Prekey Events

Clients MUST replace the prekey event on all the listed relays any time they successfully process a group welcome event. If the prekey was a derived prekey, clients SHOULD increment the derivation path by 1 for the next key.

## Onward and Upward

This next week I'll continue to work on getting the right curves and code added to the OpenMLS library and start work on a simple demo app. The focus is on better understanding what we need from the control and message events and how we can make those as simple as possible for Nostr clients and relays while also preserving as much privacy as possible.


MLS over Nostr progress update for 28 June 2024

This is a long form article, you can read it in https://habla.news/a/naddr1qvzqqqr4gupzq9eemymaerqvwdc25f6ctyuvzx0zt3qld3zp5hf5cmfc2qlrzdh0qqxnzde38y6nvv3c8qunyd3hakfln0

This is the first in a series of weekly updates I'm publishing on my process around secure messaging. Since it's the first, let's start with a bit of historical context.

## How this started

On April 29th I published [a PR](https://github.com/nostr-protocol/nips/pull/1206) on the NIPs repo detailing how we could achieve "Double Ratchet" DMs on Nostr. There was also a [video](https://share.cleanshot.com/nMKk6cn0) and [demo app](https://drdm-demo.vercel.app/) that went along with the PR. The basic premise was to use an adapted version of the Signal protocol. This would result in DMs that were truly private and confidential, even in the case where you leaked your main private key (your nsec).

I got a lot of great feedback from folks on that PR. Interestingly, nearly all of it focused on two points, both of which I'd deliberately scoped out. Group messaging and multi-device/client support. While I knew these were important, and I'd figured out how these might be accomplished, I'd scoped them out to try and keep the footprint of the spec as small as possible But, the more I talked to people, the more it became clear that this was one problem to be solved and given the complexity, it'd be better to do it in one shot.

At the same time, I'd seen that Messaging Layer Security (MLS) had recently made a lot of progress on becoming an internet standard with their RFC proposal and, goaded on by Vitor, decided to take a closer look.

## Enter MLS

[Messaging Layer Security](https://www.rfc-editor.org/rfc/rfc9420.html) (MLS) is a new protocal that is basically a modern extension of the Signal protocol that makes group messaging way more efficient (log vs linear) and was built to be used in centralized or federated environments. I'd heard other Nostr devs talk about it in the past but it was always overlooked as being too complicated or too early.

After spending a couple weeks reading hundreds of pages of RFC docs and reading through a few implementations of the MLS spec, I believe it's the best solution for secure direct and group messaging in Nostr. It also has the added benefit that we can upgrade the underlying crypto primitives over time in a sane way.

The MLS protocol specifies "a key establishment protocol that provides efficient asynchronous group key establishment with forward secrecy (FS) and post-compromise security (PCS) for groups in size ranging from two to thousands."

The spec I'm working on will detail the ways that we implement this protocol into the Nostr environment (namely, how do we use our crypto primitives, use events as control mechanisms, and use relays for storage, while obfuscating metadata).

## Goals

It's important to be clear about what we're aiming for here. Engineering is all about tradeoffs, always.

- Private and Confidential DMs and Group messages
   - **Private** means that an observer cannot tell that Alice and Bob are talking to one another, or that Alice is part of a specific group. This necessarily requires protecting metadata.
   - **Confidential** means that the contents of conversations can only be viewed by the intended recipients.
- Forward secrecy and Post-compromise security (PCS) in the case of any key material being leaked, whether that's your main Nostr identity key (your nsec) or any of the keys used in the MLS ratchet trees.
   - **Forward secrecy** means that encrypted content in the past remains encrypted even if key material is leaked.
   - **Post compromise security** means that leaking key material doesn't allow an attacker to continue to read messages indefinitely into the future.
- Scales well for large groups. MLS provides this from a computational standpoint, but we need to make sure this works in a scalable way when multiple relays are involved.
- Allows for the use of multiple device/clients in a single conversation/group. Importantly, we're _not_ aiming to enable a device/client to be able to reconstruct the full history of a conversation at any point.

## Progress this week

Ok, finally, what what I been up to?

### Reading
I've spent most of the last few weeks reading the [MLS spec](https://www.rfc-editor.org/rfc/rfc9420.html) and [architectural doc](https://www.ietf.org/archive/id/draft-ietf-mls-architecture-13.html) (multiple times), learning some Rust, and beefing up my knowledge of cryptography (which was, if I'm being generous, paltry before starting this project).

### Ciphersuites

Nostr is built around the same crypto primitives that Bitcoin is, namely Schnorr signatures over the secp256k1 curve and SHA-256 hashes. This curve isn't currently supported officially in the MLS spec. I've been in touch with the MLS working group to better understand the process of adding a new ciphersuite to the set of ciphersuites in the MLS spec. The outcome here is that we're going to start out using our custom ciphersuite that isn't part of the formal spec. The only drawback being that Nostr's MLS implementation won't be immediately interoperable with other MLS implementations. We can always add it later via the formal channels if we want.

### MLS Implementations

Given the complexity of the MLS spec itself (the RFC is 132 pages long), having a well vetted, well tested implementation is going to be key to adoption in the Nostr ecosystem. [OpenMLS](https://github.com/openmls/openmls) is an implementation created by several of the RFC authors and written in Rust with bindings for nearly all the major languages we would want to support.

I've been in touch with the maintainers to talk about adding support to their library for our new ciphersuite and to better understand the bindings that are there. Some (WASM) are very barebones and still need a lot of work. They are generally open to the idea of working with me on adding the missing pieces we'd need.

### Double Ratchet NIP 2.0

I've also started to write up the new version of the NIP that will detail how all of this will work when plugged into Nostr. It's not yet ready to share but it's getting closer.

### Onward & Upward

Hopefully that's a helpful recap. I'll keep doing these weekly and welcome any questions, feedback, or support. In particular, if you're keen on working on this with me, please reach out. More eyes and more brains can only make this better. 🤙


Bitcoin journalism is fucked.

I started The Rage because I'm tired of investors and advertisers telling me what to do for below minimum wage compensation.

What we need are publications willing to let journalists investigate the crap out of the companies, representatives and people enabling the building of surveillance tech behind the scenes.

What we get are publications selling out to corporations, startups and politicians writing public relations puff pieces to keep their returns on track. The point of journalism is to hold power to account, not to become its bedfellow.

There is no lack of talented, experienced, investigative journalists covering bitcoin. The problem is that they write what the powers that be don't want you to hear – so many are out of a job, dabbling away at the next press release for mainstream media, or doing below-minimum wage contract work to pay the bills.

I'm incredibly overwhelmed by all the positive feedback we've been getting for The Rage. In just 8 weeks we've scooped major publications and drove discussions around AML, Samourai and Tornado Cash together with your help. We've even made enough to cover operations with almost 400$ raised, thanks to all the zappers out there.

But here's the thing. I didn't come here to write a good piece every once in a while leaving stories untold left and right because I can't afford to focus on investigations full time. I came here to fuck up the financial surveillance complex. That's why The Rage now needs your help.

We're trying to raise 0.25BTC so we can contract the best investigative journalists in the Bitcoin space to tell the stories that major publications can't afford to print.

If you value your financial freedom, please consider donating via our Geyser fund. We cannot do this without your help.

https://geyser.fund/project/therage

https://m.primal.net/IpWO.png


3x speed is your friend.


List of books recommended in that book:

Asimov, Isaac. Asimov on Astronomy. Anchor Press, 1975.

Barker, Joel. Paradigms. Harper Business, 1993.

Cook, Paul M. “The Business of Innovation.” Harvard Business Review, March-April, 1990.

Kilpatrick, Andrew. Of Permanent Value. McGraw-Hill, 2001.

Klein, Gary. Sources of Power. MIT Press, 1999.

Lightman, Alan. Einstein’s Dreams. Warner Books, 1993.

Negroponte, Nicholas. Being Digital. Alfred A. Knopf, 1995.

Ogilvy, David. Confessions of an Advertising Man. Atheneum, 1963.

Ogilvy, David. Ogilvy on Advertising. Vintage Books, 1985.

Paulos, John Allen. Innumeracy: Mathematical Illiteracy and Its Consequences. Vintage Books, 1990.

Pound, Ezra, ABC of Reading. New Directions, 1934.

Rappaport, Andrew S., and Shmuel Halevi, “The Computerless Computer Company.” Harvard Business Review, July-August, 1991.

Schultz, Howard, with Dori Jones Yang. Pour Your Heart Into It. Hyperion, 1997.

Singular, Stephen. Power to Burn. Birch Lane Press, 1996.

Slywotzky, Adrian. Value Migration. Harvard Business School Press, 1996.

Slywotzky, Adrian, and David J. Morrison with Bob Andelman. The Profit Zone. Times Business, 1997.

Slywotzky, Adrian, and David J. Morrison with Ted Moser, Kevin Mundt, and James Quella. Profit Patterns. Times Business, 1999.

Slywotzky, Adrian, and David J. Morrison with Karl Weber. How Digital Is Your Business? Crown Business, 2000.

Sun Tzu. The Art of War. Translated by Samuel B. Griffith. Oxford University Press, 1963.

Updegraff, Robert R. The Power of the Obvious: Based on the Business Classic Obvious Adams. Executive Press, 1972.

Walton, Sam, with John Huey. Sam Walton: Made in America. Bantam Books, 1993.

“What’s in a Name?” The Economist, January 6, 1996.

Young, James Webb. A Technique for Producing Ideas. NTC Business Books, 1994.


nut stash for your self custody sats?

Gotta stash some nuts from the sack.


The 7 profit models from the book the Art of Profitability:

Customer Solution Profit: Creating tailored solutions for specific customer needs.

Pyramid Profit: Offering products at different price tiers to capture various market segments.

Multi-Component Profit: Selling the same product through different channels at varying price points.

Switchboard Profit: Acting as a broker between buyers and sellers.

Time Profit: Capitalizing on being first to market or innovative.

Blockbuster Profit: Focusing on creating high-impact, successful products.

Profit-Multiplier Model: Leveraging one skill or asset to generate multiple revenue streams.


H.O.R.N.E.T Storage Nostr Relay Launch🐝

Live Demo of Panel 📟
https://hornetstorage.net/

Nostr Relay & Panel in Alpha 💾
https://github.com/HORNET-Storage/hornet-storage
https://github.com/HORNET-Storage/hornet-storage-panel

Toggleable Storage Support 🎛
- Unchunked files as Blossom Blobs🌸
- Chunked files as Scionic Merkle Trees🎄

https://v.nostr.build/BRQ0D.mp4


It's quite likely that non-perishable food like tallow and honey were the earliest forms of naturally emerging commodity money.

These goods are readily available, can last for decades before rotting, are easily divisible,  verifiable and fungible.

As with any money, it's likely that humans tried their best to inflate the supply. In the case of tallow, this might have lead to mass extinction of some large mammels.

Thus the discovery of metallic money might have saved uncountable animal lives.


If I do it, it'll be MIT licensed, and available as a free podcast, similar to cryptoeconomics.
https://podcastindex.org/podcast/4363136


Nice, enjoy it


A Lodging of Wayfaring Men is a novel by Paul Rosenberg that follows freedom-seekers as they create an alternative society on the Internet - a virtual society with no possibility of oversight or control. The story leads readers through a clever plot where principles of economic freedom, individuality, and justice lead to the creation of a free market uncontrolled by governments or tax men.

The novel was instantly named Freedom Book of The Month and became a major influence in the Cyber-underground. It depicts how this virtual society grows so fast that it terrifies governments and their "security." With no possibility of oversight and control, the System fights to co-opt this cyber-society before it undermines and overwhelms the dominance of corruptocrat governing elites.

The free souls in the novel guide readers through a thought-provoking narrative that explores the potential of a free market society built on the foundations of individual liberty and justice.


Interview with the wonderful author

https://www.youtube.com/watch?v=qS0IX2O_oPU


Thinking about doing an audiobook for the lodging of wayfaring men.

Zap if you'd like to hear it.


Someone's gotta do the job


I'm so proud of my friends.

Keep building, you got this.


😢 sorry

https://www.youtube.com/watch?v=Mgt2rxbzz6k


Absolutely phenomenal talk by nostr:nprofile1qqsglcljg053zgvpsyrcwh23hjj08l84gdph42t329gweqpkxkynn3gpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcva6atu

https://www.youtube.com/watch?v=s_8KhEBy4WA


"The regime pretends to respect human rights.
It pretends to percecute noone.
It pretends to fear nothing.
It pretends to pretend nothing."

~ Václav Havel


Zusammenfassung der letzten 5 Jahre meiner FOSS Karriere
https://youtu.be/Mgt2rxbzz6k?si=YQxhFbIjjMLAqsT4


Rent a car, with polish company license plate, pay with bitcoin.

Beautiful

https://shopinbit.com/Premium-Services/Long-term-Car-Rental/


It's v2.3.1 on android


TIL you need to sign up for a hugging face account and provide contact details in order to download a model.


The Q&A is hilarious
https://www.youtube.com/watch?v=bd9Uftz1hfE


Fortune favors the bold.

I'd be in favor of bolt12 only wallets, it's a pain, but it's the visionary path forward, it worked well for Wasabi with segwit only in v1.0


Yes, correct.

Unfortunately the wake-up part requires goople play framework.

I find it great that there's a shoutout to GrapheneOS is the Phoenix UI!


transform anger into compassionate action


Privacy tip:

Go to settings > payment options, and enable random payer key, this ensures that the receiver cannot link multiple payments to the same sender.

nostr:nevent1qqsd39hafhu3vgl85wd23x3uypjn0rd7gc3cgjtwfnnfx282ucl06fgppemhxue69uhkummn9ekx7mp0qgst0mtgkp3du662ztj3l4fgts0purksu5fgek5n4vgmg9gt2hkn9lqrqsqqqqqpcrsxqr


https://bolt12.org/ is a great initiative, very cool to have such beatufiul landing pages for protocol updates.


Phoenix shipped bolt12, the future is bright

https://github.com/ACINQ/phoenix/releases/tag/android-v2.3.1


Nopara's videos about the rejuvenation olympics are very interesting.

https://www.youtube.com/watch?v=fEq9_vKD74M


False ideas are the contrast through which truth emerges.


Exactly, exponentially increase the cost of attack, and decrease the cost of defense.


Join nostr:npub1tvqc82mv8cezhax5r34n4muc2c4pgjz8kaye2smj032nngg52clq0rkrq4  and me for episode 68 of @Plebchain Radio this Friday, July 5th, at 2pm pm ET (UTC -4)

Our guest this week is nostr:npub1klkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qulx3vt , who joins us to talk about all things privacy, Wasabi, nostr, and steak

You don’t want to miss this one.

Set your blockclocks!

https://nostrnests.com/


Working on abolishing the abolition of private property.


Paul is a wordsmith, his prose is inspiring.


Looks pretty good as long as the writing isn't tacky

Description
This novel was a major influence, first in the Cyber-underground and then in the larger world. A Lodging of Wayfaring Men is the story of ethical people who create an alternative society on the Internet – a virtual society, with no possibility of oversight or control. It grows so fast that governments and “leaders” are terrified, and fight to destroy it before it undermines the power of the ruling elite.


We gotta make slavery obsolete.


I love the reaction of Bitcoiners who read A Lodging of Wayfaring Men for the first time.

It's a book made for us.


Nope.


The Graphene file manager only shows files younger than 3 months or so, how can I find older files?
nostr:nprofile1qqsvzkj6vkvxu745zdx7uw4c2f2d5hzafvzw0z60zmyzsdce9564rpgpz9mhxue69uhkummnw3ezuamfdejj7mtxgrd


What you wish for (2023), great movie


Signed metadata is powerful


Concept of Orange Summer - how to free your life with Bitcoin. From nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyrt6w3mtzff6ryp0wetgtllr6dgl3shz43eg7e26adflfjdzlxnh6dnhmjw

https://youtu.be/OdetWF6Y2Qk?si=mvPyPE569lXV9RBO


🎉 A new mint implementation appears 🎉

Chamberlain – A Cashu Mint with Integrated LDK Lightning Node (Rust, based on CDK)
https://github.com/sovereign-app/chamberlain


nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s is a beast and we're proud to support him for the long term. Godspeed, Will! ⚡
https://opensats.org/blog/jb55-receives-lts-grant


Nice, enjoy the rabbit hole!


At last my phone is private and no more sharing my personal data with Big Tech and third part advertising resellers. Good bye iOS, hello #Grapheneos!

It’s only been 24hrs with my new Pixel 8 which is running GOS, and I would recommend to everyone else to follow suit.

nostr:npub1klkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qulx3vt thank you for this beautiful discovery. 💜

https://m.primal.net/IykP.jpg


Amazing, wen alpha sir?


Block 849436
https://image.nostr.build/9506c365b98db84c59f421c06ce10642f57f09b8f7edd3b692966b9971c6369a.jpg


“I’m a Bitcoin Core contributor.”

“Oh, so you’re a developer?”

“No, I run a node and I share my feelings with them.”


Cross platform?


Does it keep some historical record of old files?

If one device deletes a file, is it irrecoverable for all others?


Feels like a lot of underlying assumptions are being challanged recently.

Relying on dns seems flawed now...

So much to build.

Keep it up


PSA: The functionality of multiple Fedimint federations is significantly degraded due to severe DNS issues.

It seems to be the case that some federation guardians have an XYZ domain that the DNS registrar has taken over. Freedom One and Bitcoin Principals appear to have one guardian offline due to this.

Unfortunately, despite the server and keys for these guardians being intact, there is no way for the DNS of a guardian to be swapped out after the fact. We became aware of this issue last week and then became aware that multiple federations are experiencing this: https://github.com/fedimint/fedimint/issues/5482/

Given the critical state of these federations, with one guardian out of four being permanently offline, it's essential that if you have funds in these federations, you should withdraw them immediately. Unfortunately, we're unaware of other public federations, so you must withdraw to another lightning or on-chain wallet.

From our experiences, intermittent/connectivity issues can occur with guardians, and this may result in errors if not all three remaining guardians are consistently online. No other guardian of these federations has XYZ or other domains like it. So, if you're having issues, please try again later.

Unfortunately, not much can be done on the Mutiny side, so we're removing the federation setup flow in the UI as a first step. Sorry for the inconvenience.


Awesome, thanks!
Is there some third party service for hosting a device in the swarm?


The dam of tyranny is cracking


Gotta love this guy, great voice!

https://youtu.be/PhmOF2ucUUo?si=aI_7yMqy5J8P1qDX


Fediral Reserve


Peppermint


Fun names for ecash mints, go!


Is there yet a cross platform file sharing app based on pear?
Something that shares a folder in the OS with all connected devices.
nostr:nprofile1qqstnem9g6aqv3tw6vqaneftcj06frns56lj9q470gdww228vysz8hqpz4mhxue69uhk2er9dchxummnw3ezumrpdejqzrthwden5te0dehhxtnvdakqz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcjgxv3n


Excellent talk by Rahim about the future of investment under a sound monetary standard.

https://www.youtube.com/watch?v=D9t28MaQR_Y


This is actually a super hard problem to solve. The customer is offline, that's why he needs to pay for wifi, but which payment methods work while the sender is offline.

ECash is so beautiful with offline payments.


ok, work-in-progress NIP for interoperable cashu wallets up on wikifreedia 👇

https://wikifreedia.xyz/nip-cashu-wallet/f7z.io

TL;DR: a standardized way for nostr clients to access your cashu wallet(s)

* you login into any nostr app and your balance is right there, you don't need to do anything
* you can create multiple wallets
* you can add optional passphrases if you would prefer a client to have to ask you for the passphrase before it's able to spend

nostr:nevent1qvzqqqqqqypzp75cf0tahv5z7plpdeaws7ex52nmnwgtwfr2g3m37r844evqrr6jqyt8wumn8ghj7ur4wfcxcetjv4kxz7fwvdhk6tcprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsqgzlpxrjx6f4g5vaczcppmx7j6ujw9pn2pxcdxg3nvrp26mnuv83lgqjd042


👀
https://github.com/f321x/ecash-escrow-nostr-concept


nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z would be nice to have a "only unmetered wifi" setting for bandwidth savings.


Paul is a wordsmith


Bullish

nostr:nevent1qqsx64nhx9aytmxr8fq7zah39j7f7wmljr4cjcd4pn432xzgpqsqq8gppemhxue69uhkummn9ekx7mp0qgs0wzz3uacckly3qpq06m73xfskmuzhhxsh47vy3zpu0tw878hfzzgrqsqqqqqprnzfrr


People ask for my opinion on token protocols  & ecash designs a lot.

So we designed and wrote out how we think this set of problems should be solved.

We also made public some research we have been in stealth with for months here as well.

Learn about Atomicity, PKARR, Paykit, Rumble, Offset and more:

https://github.com/synonymdev/atomicity/


Boggles my mind how courageous and smart Bitcoiner kids are...


Because #Privacy Really Matters!
nostr:npub1klkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qulx3vt at #BTCPrague 2024

https://m.primal.net/IjHb.jpg


#Bitcoin privacy panel at nostr:npub167n5w6cj2wseqtmk26zllc7n28uv9c4vw28k2kht206vnghe5a7stgzu3r.

"To be honest, privacy for my generation is near impossible with the current tools" Lykke Dale

"The past generation of devs failed you. We will build better tools with privacy defaults" nostr:npub1klkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qulx3vt

🔥
 https://image.nostr.build/251d8484b41e1aa13a18d0af96f1e1511c2482aaebb65d488356ff3f4c6df487.jpg


This one will blow your mind.
nostr:nevent1qqsxcngsk3xgkh05vgtstdzuxvgsh7hayk63v9j00awcrxy25m8a8jspzpmhxue69uhkummnw3ezumt0d5hsygqs7lrlwuka3yehejxmvpqukcfm9eng379aryhft9efxavl26pa4ypsgqqqqqqsdvkwg6


Upcoming documentary about the FED by the Mises Institute.

https://www.youtube.com/watch?v=IAGYj4fOZjE


Frost for nostr key rotation


Bone broth.


What would happen if you stopped smiling for 6 months? 😂

I tried it.
See what happened here: https://youtu.be/J-x3S4Jp7Z4
https://m.primal.net/IcDi.mov


https://cdn.satlantis.io/1717939325764-vexl.jpeg Apps to use in Prague: Vexl.

Czechs are quite privacy-conscious, so it's only natural that one of the most ambitious p2p KYC-free apps emerged here. Vexl is a phone app giving its users a simple way to discover peers for buying & selling bitcoin locally, in a private manner.

Vexl works through a social graph based on imported phone contacts, is end-to-end encrypted, has no escrow, takes no cut of the trades. It is an open source public good.

Vexl is simply the best way to buy & sell some bitcoin in Prague, with privacy (cash-for-sats recommended to maintain the highest level of privacy).

Check it out at vexl.it


We’re going to announce a new Trezor on BTC Prague 🔥

https://content.trezor.io/new-products-2024


Wow, even with the original cover, that's a rare find these days.


I met an OG bitcoiner a few weeks ago that used to sell copies of the book on Silk Road.

He recently realised he had some copies left that had been sitting in his loft for years.

He wanted to sell them to bitcoiners, so I’m listing them on my website for a bargain price of £60 (copies are going for £294 on Amazon right now)

https://thebitcoinshop.uk/product/a-lodging-of-wayfaring-men/


4279 issues on the Wasabi Wallet repo


#WasabiWallet release v2.0.8.1 Soteria is out https://github.com/WalletWasabi/WalletWasabi/releases/tag/v2.0.8.1

Highlights:

💸 Set maximum coinjoin mining fee rate
🔒 Set maximum coinjoin coordination service fee
👀 Verify coinjoin mining fee matches requested rate

With new independent Wasabi coordinators appearing every day, we are adding extra level of control to users.


It's funny cause it's true.

But what about V3 announcements?
nostr:nevent1qqsg9c4adlfsen47z59lpes0jj4lpxxjyvtn70la0z2962y4rusqk8sppemhxue69uhkummn9ekx7mp0qgsfuv8fgq3cek0ta0rr9qtkm4x3pxqjz22y9u4xcwrj0lrxlfl2jzsrqsqqqqqpurxla8


Meat secured.

nostr:nevent1qqsf6pplq0ulahnufwxk2hk9ayueven20jzwujxelkmuhpfhnxl8e2spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg9ha45tqck7dd9p9egl6559c8s7pmgw2y5vm2f6kyd5z594tmfjlspsgqqqqqqspm4pkw


I usually blastr everything


How come nostr:npub1dvmathygc89axtt4kufld4xz7amxyah4rjfn0tuaxtydw9wvrwfsp2mq7w shows me posts that I already liked or zaped?
nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft


It's such a useful feature.


I come bearing gifts.

Introducing DotNut - a C# library implementing the Cashu protocol

https://github.com/Kukks/DotNut

The best part about this is the naming opportunities honestly. 😂


Working on #WasabiWallet v3.0


Bitcoin Privacy with Max & Max
—  nostr:npub1klkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qulx3vt &  nostr:npub1797h37mc98f6363m5nysxd0t2swuz7nxq4z83saw77em3czld6xqvuar68

#BTCPrague 2024 VIP Stage Fireside Chat

https://m.primal.net/Iaib.png


BTCPay Server 1.13.2 is out! 🎉🎉🎉

🆕BoltCard plugin ⚡ - Create, top-up and check boltcard balance of all from your BTCPay! (A single point of sale device can now not only accept, but also issue and top up BoltCards. BTCPay is now becoming end-to-end solution for #bitcoin economies.
🧑💼 Refund reports
🪲Bug fixes
And a lot of other improvements.

This release sets a great foundation for the 2.0.0 and is only a small glimpse into what's coming next!

Onwards🚀

https://m.primal.net/IZmL.jpg


Announcing Super Testnet Workshops! A series of monthly workshops (first one on June 25) where you can learn bitcoin programming. We start this month with a workshop on Bitcoin Script. Buy a ticket for only $20 or purchase a prerecorded version for only $5 https://www.youtube.com/watch?v=aRi9_4bgkek


These keys are owned by Turbolay https://x.com/Turbolay


Woop woop


Overpaid 8x at 7.5 sats/vbyte 😢


🔀 FreeSabi  🔀

This account will publish liquidity status of free WabiSabi coordinators advertised on Nostr.
You can connect to those coordinators by entering their advertised URI in Wallet Wasabi under Settings -> Bitcoin -> Coordinator URI
Remember to download Wasabi only from official sources: https://wasabiwallet.io/ or https://github.com/WalletWasabi/WalletWasabi/releases

To run your own coordinator and help bitcoiners regain their privacy, visit https://docs.btcpayserver.org/Wabisabi/.
Bootstrapping a coordinator directly from Wasabi Wallet will be improved as the software is undergoing a transition towards FOSS.

Disclaimer: This account will list all free coordinators without any distinction nor control.
A mention isn't an endorsement. It is the responsibility of the coordinators and their users to ensure that they are compliant with AML laws applying in their jurisdiction.


Blast from to the past
a Wasabi 1.0 coinjoin from 2018

https://mempool.space/tx/f250e997dc1a2d68861e03689d1709973e1964a62f929ba5727fe8607dafb676


nostr:npub1u4rl3zlfa2efxslhypf4v6r8va5e0c9smxyr5676pxkyk0chn33s0teswa, a nice bot reporting the liquidity status of free #WasabiWallet coordinators advertised on #Nostr, by nostr:npub145xcuuk0k9nq0u8skxrnvuur5v4ek8uqmeq6g094lf3skqdqeckq6262ee.


nostr:npub1h8nk2346qezka5cpm8jjh3yl5j88pf4ly2ptu7s6uu55wcfqy0wq36rpev has some automated setup for his shows.


Maybe this will be changed with the next hardfork...


The Bigger Bubble now has a geyser fund now, give them some love!

nostr:npub1692hhrw8g22az067up2dz4x6v9caaa24ehxsth9lmy0s2w70q6es3cul54


Nobody should trust #GitHub. We have witnessed many times how repositories are closed. Let's give #Nostr a change and start moving #WasabiWallet things gradually https://gitworkshop.dev/r/naddr1qqx9wctnv93xj4mpd3kx2aqpz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzp83sa9qz8rxea04uvv5pwmw56yyczgffgshj5mpcwfluvma8a2g2qvzqqqrhnydmcq5v


It's good to have you back!


anyhow, giving nostr a try


There are two forms of Sybil protection in Joinmarket, because of the taker-maker asymmetry. Both forms use utxo ownership. The takers have to produce what we call a "PoDLE", a commitment to a proof of discrete logarithm equivalence - in English, they publish a hash and have to reveal the utxo behind that hash to makers that agree to join with them, revealing the utxo behind it. The attack this dissuades: constantly spamming request to find out maker utxos. If someone can see all the makers' utxos they can deanon coinjoins, so it's a "snooping" attack. With PoDLE you are quite heavily rate limited in how many coinjoin requests you can make.

See the first two articles on my blog (P(o)ODLE and Racing against Snoopers) for more on that. https://reyify.com/blog/racing-against-snoopers-in-joinmarket-0.2

The makers have to publish a fidelity bond, as others have noted. See docs/ subdirectory in joinmarket-clientserver for some explanation and links to further explanation.

Fidelity bonds directly dissuade Sybilling and are much weightier, in general (the size of the utxo involved tends to be large), but note that in neither case are utxos spent, they are just held (for PoDLE) or timelocked (for FB). And FB UTXOs are actually published, which is a bad thing; I've recently spent a lot of time looking for efficient utxo set proofs, partly motivated by that.

(Although it's a bad thing, those utxos can be completely separate from utxos used in coinjoins, so it's not *that* bad.)


Removing and adding doesn't fix it.

Yes, with Amber.


The UI is unchanged from first start, kind count is null


I added citrine to my local and private relay, created a draft, but I don't see any connections or subscriptions in citrine.

nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5


The last transaction coordinated by zkSNACKs.

https://mempool.space/tx/0dc6180a7f6ab204cba382065c06c04f6fdd58846437af2d078b4f48eba25d95


Very good!


It isn't planned currently as a technical threat would be able to figure that out, or would be able to tell if it is a decoy through other means. It's a big reason we don't have a hidden profile feature at all (e.g. FFS would leave signs). The feature would only work best against someone with no knowledge on what GrapheneOS is. Cellebrite and XRY and other industry actors mentioning us in their internal documents or product material would suggest they study our work and read our posts.

Another example is Owner is still required to be authenticated first and there's tons of ways to see if an authenticated profile os the Owner or not.

We believe features involved in tricking someone could lead to someone trusting that feature and underestimating how skilled the person they're trying to trick, which could endanger them or bring even more trouble. While you could also trick someone with our Duress PIN that's not the objective, the device owner should trigger it when the time is right.


New Wasabi Wallet release v2.0.8

https://github.com/WalletWasabi/WalletWasabi/releases/tag/v2.0.8

📌 Exclude UTXOs from autocoinjoin
🌎 Coordinator selection in GUI
❄ Tor bridges
💥 Tails & Whonix OS support
💾 Install Linux udev rules for hardware wallets


Bitcoin Optech newsletter #305 is here:

- describes a proposed light client protocol for silent payments
- summarizes two new proposed descriptors for taproot
- links to a discussion about whether opcodes with overlapping features should be added in a soft fork
- summarizes popular Q&A from Stack Exchange
- Optech Newsletter #305 Recap on Twitter Spaces
https://bitcoinops.org/en/newsletters/2024/05/31/

Setor Blagogee posted to Delving Bitcoin to describe a draft specification for a protocol to help lightweight clients receive silent payments (SPs)...
https://bitcoinops.org/en/newsletters/2024/05/31/#light-client-protocol-for-silent-payments

Oghenovo Usiwoma posted to Delving Bitcoin about two new proposed descriptors for constructing taproot spend conditions...
https://bitcoinops.org/en/newsletters/2024/05/31/#raw-taproot-descriptors

Pierre Rochard asks if proposed soft forks that can provide much of the same features at a similar cost should be considered mutually exclusive, or whether it would make sense to activate multiple proposals and let developers use whichever alternative they prefer...
https://bitcoinops.org/en/newsletters/2024/05/31/#should-overlapping-soft-fork-proposals-be-considered-mutually-exclusive

Selected Q&A from Bitcoin Stack Exchange:

- What’s the smallest possible coinbase tx / block size?
- Understanding Script’s number encoding, CScriptNum
- Is there a way to make an address public but hide how many BTC it contains?
- Testing increased feerates in regtest
- Why is my P2P_V2 peer connected over a v1 connection?
- Does a P2PKH tx send to the hash of the uncompressed or compressed key?
- What are different ways to broadcast a block to the Bitcoin network?
https://bitcoinops.org/en/newsletters/2024/05/31/#selected-qa-from-bitcoin-stack-exchange

Bitcoin Optech will host an audio recap discussion of this newsletter with special guests Oghenovo Usiwoma and Pierre Rochard on Twitter Spaces Tuesday at 14:30 UTC. Join us to discuss or ask questions!
https://twitter.com/i/spaces/1eaKbgnYgOBGX


Announcing: Harbor, an ecash desktop wallet for better bitcoin privacy.

https://blog.mutinywallet.com/harbor/

Privacy for the common person is a value worth fighting for. When we see a lack of freedom tools, we must build them into existence. They don't appear on their own.

Much has been said about privacy at the Bitcoin protocol level. For now, we build it on higher layers where we can be more nimble.

Ecash is a tool available today that combines with Bitcoin to bring new levels of common privacy. Cashu and Fedimint are two existing implementations we're interested in.

https://m.primal.net/ISqH.png

Harbor Privacy: All communication runs over Tor. Mutiny is not in the middle of any connections or transactions. Funds in the wallet get a Privacy Score to show how the mints provide privacy over time. More to come on this in the future.

https://m.primal.net/ISqJ.png

Harbor Multi-mint: Instead of relying on a single mint with your funds, spread the risk over dozens or more. Harbor manages this for you, showing you a single balance while connecting with mints for you. A mint can go offline with minimal impact on you.

https://m.primal.net/ISqK.png

Harbor Automation: Running as a desktop app unlocks ability to do long running processes in the background. Move money in and out of mints on your preferred schedule to maximize your desired level of privacy. Harbor makes suggestions, but you are in control.

Move money in and out of Harbor using Lightning or on-chain. We love Bitcoin, and we love privacy. We hope Harbor gives everyday people more privacy and peace of mind.


🕯

https://m.primal.net/ITul.png


btw, for example the coldcard hardware wallet has a "brick me pin" which actually makes that hardware unusable.


Another interesting feature would be a pin that unlocks to a hidden user account with some generic applications installed.


After using the duress password, is it possible to reinstall Graphene and make a new setup, or is the hardware bricked?


This is excellent, thanks!


#GrapheneOS version 2024053100 released. Duress Password is finally here.

- add support for setting a duress password and PIN for quickly wiping all hardware keystore keys including keys used as part of deriving the key encryption keys for disk encryption to make all OS data unrecoverable followed by wiping eSIMs and then shutting down

- disable unused adoptable storage support since it would complicate duress password support (support can be added if we ever support a device able to use it)

- increase default max password length to 128 to improve support for strong diceware passphrases, which will become more practical for people who don't want biometric-only secondary unlock with our upcoming 2-factor fingerprint unlock feature

- disable camera lockscreen shortcut functionality when camera access while locked is disabled to avoid the possibility of misconfiguration by adding the camera lockscreen shortcut and then forgetting to remove it when disabling camera access

- kernel (5.15): update to latest GKI LTS branch revision including update to 5.15.153

- kernel (6.1): update to latest GKI LTS branch revision

- Vanadium: update to version 125.0.6422.147.0

- GmsCompatConfig: update to version 115

-make SystemUI tests compatible with GrapheneOS changes

https://grapheneos.org/releases#2024053100


My write up on how #cashu #ecash like shares might he used for a #mining pool.

https://delvingbitcoin.org/t/ecash-tides-using-cashu-and-stratum-v2/870/20

#Ecash TIDES using #Cashu and #StratumV2

Recommended reading/References:

- Cashu ecash protocol
- ecash Proof of Liabilities
- Ocean TIDES
- Stratum v2 Spec (Sv2)

Goals:

- Auditability
- Small payouts
- Privacy

Using the Blind Diffie-Hellmann key exchange (BDHKE) from Cashu as a Sv2 Protocol Extension, a pool can provide auditable, small scale, private pool rewards in the form of eHash.

A hash provider (HP) connects to a pool and begins job negotiation. This aspect remains largely unchanged from current paradigms. However, the HP will also request the active block_keyset. This is a list of pubkeys as defined in NUT02, but the value amounts for the individual keys correspond to difficulty targets for various miners which is used as a share weight in the TIDES rewards. The unit for these keysets is left up to specific implementations. A block_keyset is rotated once the pool finds a block or when the network difficulty adjustment occurs.

When the HP finds a valid share, in addition to standard share data, the HP will generate a secret and send a blinded message (B_) to the pool. The inputs for this blinded message could be done at an individual ASIC level or as part of a farm proxy implementation, with the latter seemingly ideal for larger farms. This blinded message (eShare) would be included in Sv2 channel messaging as a protocol extension. This signals to the pool that there is a valid share and requests a signature using the appropriate key from the active block_keyset. The same blinded message could be reused multiple times as long as special consideration is given on the pool/mint side for tallying these submissions. Reuse of blinded messages may be necessary during implementation if computing these blinded messages is too costly for a given HP, otherwise a new blinded message should suffice and lower complexity.

When the pool receives an eShare, it first validates the share itself, as usual. Once validated, the pool signs the blinded message, completing the DHKE and providing the blinded signature (C_) back to the HP. This share + blinded signature are then added to the time ordered TIDES defined share_log. The HP retains the blinded message data inputs (x) and the unblinded signature (C) as defined in the Cashu protocol NUT00 1.

This share process continues until a new difficulty adjustment occurs, after which a new keyset is issued with appropriate difficulty targets, OR a block is found by the pool. A keyset rotation after a difficulty adjustment accounts for new share target difficulties. A keyset may be reusable across difficulty adjustments as a % delta from network difficulty.

When a block is found by the pool, a full list of shares and associated blinded signatures is published by the pool. This signals to the HP that the eHash shares are available for redemption. Now the pool references the share_log using the share_log_window (defined in TIDES) for what eHash is eligible for redemption. As HP’s redeem their eHash, the eHash is recorded alongside the public record of shares and blinded signatures as defined in the ecash Proof of Liabilities 5.

Redemption of eHash can be any of the available Cashu or ecash mechanisms appropriate for the HP.

Other thoughts:

Cashu supports spending conditions, such as P2PK (NUT10 1 and NUT11)
the blinded message secret uses hash_to_curve(x) computation which could be offloaded to an ASIC, maybe.
Since this is an ecash usage, Fedimint is also a viable option but has not been considered in depth.

P.S. I look forward to feedback and considerations I may have missed. This post was an effort to solidify my idea into something more concrete and shareable. A vocal (and probably less comprehensive/coherent) monologue of this idea can be found here. I hope to create a diagram to help illustrate this proposal.


There are currently **five** Wasabi coordinators:

```bash
echo '["REQ", "coordinators", {"kinds":[15750]} ]' \
    | websocat -n wss://relay.primal.net \
    | jq 'select(.[2].tags[] | .[0] == "network" and .[1] == "mainnet") | {content: .[2].content, endpoint: (.[2].tags[] | select(.[0] == "endpoint") | .[1])}'
```

https://image.nostr.build/365fdc5a7db36548c071ea100017a77661ab8d40c1ea4ec02b376bebf4d84653.jpg


Yes, and I don't know.


Coinjoins won't work by default, but wallet generation, synchronization, and single user transactions work just as gretlat as before.


zkSNACKs will shutdown its coinjoin coordinator in two days.


I guess it would be wise to explicitly mention an arbitration court as judge, but maybe that should be added by each project, and not in the vanilla license.


https://image.nostr.build/e51419e8fcedf3e6432a3366be5f70863a0d74d50f500777653fcc3e1211d13a.png

https://github.com/AnarchistLicense/OpenAnarchistLicense


Would be cool to see a new OS, of course it's a huge task, but so is a 60FPS eink...


dev/hack/day by HRF

'Cypherpunk and Privacy Socratic Discussion' led by  nostr:npub1klkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qulx3vt,  nostr:npub1s6z7hmmx2vud66f3utxd70qem8cwtggx0jgc7gh8pqwz2k8cltuqrdwk4c &  nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg will dive deep— through a thoughtful, open-ended dialogue — into the principles and challenges of maintaining privacy and freedom in the digital age.

https://m.primal.net/IRYK.png


If you like the Mandibles, you'll love A Lodging of Wayfaring Men.

It's also a tale of dollar collapse, but with a cypherpunk as fuck author who understands how to survive in such a situation.


Shutdown.


zkSNACKs has donated hundreds of Bitcoin to the development of Wasabi Wallet.

Now that zkSNACKs is leaving, someone else has to pick up the slack.

If you enjoy the use of Wasabi, please consider hiring a developer.


To have a chance of surviving in an increasingly hostile environment, #WasabiWallet must evolve. And to do that, it must leave behind comfort and embrace stress and uncertainty. It must focus on the development of the wallet under conditions of resource scarcity, far from the warmth of a sponsoring company's arms.

The #WalletWasabi git repository has been transferred from the zkSNACKs organization to a new organization called WalletWasabi.

https://github.com/WalletWasabi/WalletWasabi


soon


Would be nice to refactor labels, but lots of other things to do


The Wasabi Wallet source code repository has been transferred to github.com/WalletWasabi/WalletWasabi

Wasabi has now left the nest of zkSNACKs


You broke the first rule in the first PR, speaking of leading by example...


lol, nobody follows rule #1 in the repo...


Bitcoin is more than just a digital currency; it's a movement towards a more open, transparent, and equitable financial system. Whether you're looking to invest, transact, or simply learn, there's never been a better time to get started with Bitcoin.

Bisq 2 is open-source software featuring a trading protocol called Bisq Easy, designed to help newcomers easily navigate the process of buying their first Bitcoin.
Welcome aboard!

Get started with Bisq 2 here https://github.com/bisq-network/bisq2/releases/tag/v2.0.4

#dex #decentralized #bitcoin #btc #bisq2 #p2p #stacksats #nokyc
https://m.primal.net/IPHW.jpg


wild

Somewhat reminds me of nostr:npub1nmr6w7qk0ta36vxysv77jv3d5rqghfc6d8sez8240rf3gja4vsmsd2yha8 alphaama


The actual abstract:

Privacy is a vital necessity that fosters meaningful relationships by creating an environment where individuals can express themselves freely without fear of judgment or repercussions. Its denial strips individuals of dignity, esteem, and respect, creating an atmosphere of mistrust that inhibits personal growth and hinders the positive development of individuals and society. Cypherpunks advocate for privacy as the default standard, only to be infringed upon when compelling arguments justify it in specific circumstances.


Yeah, and curiously this started happening right as I fell down the Bitcoin rabbit hole, everything is getting cheaper and cheaper!


QubesOS users unaffected.


Bitcoin Optech newsletter #304 is here:

- summarizes analysis of upgrading LN channels w/o closing/reopening them
- discusses challenges ensuring pool miners are paid appropriately
- links to discussion about using PSBTs for silent payments
- announces proposed miniscript BIP
- summarizes a proposal for frequent rebalancing of an LN channel to simulate a futures contract
- summarizes changes to services/client software
- adds a pooled mining topic
- Newsletter #304 Recap
https://bitcoinops.org/en/newsletters/2024/05/24/

Carla Kirk-Cohen posted to Delving Bitcoin a summary and analysis of existing proposals for upgrading existing LN channels to support new features. She examines a variety of different cases and compares three previously proposed ideas for upgrading channels...
https://bitcoinops.org/en/newsletters/2024/05/24/#upgrading-existing-ln-channels

Ethan Tuttle posted to Delving Bitcoin to suggest that mining pools could reward miners with ecash tokens proportionate to the number of shares they mined...
https://bitcoinops.org/en/newsletters/2024/05/24/#challenges-in-rewarding-pool-miners

Josie Baker started a discussion on Delving Bitcoin about PSBT extensions for silent payments (SPs), citing a draft specification by Andrew Toth...
https://bitcoinops.org/en/newsletters/2024/05/24/#discussion-about-psbts-for-silent-payments

Ava Chow posted to the Bitcoin-Dev mailing list a draft BIP for miniscript...
https://bitcoinops.org/en/newsletters/2024/05/24/#proposed-miniscript-bip

Tony Klausing posted to Delving Bitcoin a proposal, with working code, for stable channels...
https://bitcoinops.org/en/newsletters/2024/05/24/#channel-value-pegging

Changes to services and client software:

- Silent payment resources
- Cake Wallet adds silent payments
- Coordinator-less coinjoin PoC
- OCEAN adds BOLT12 support
- Coinbase adds Lightning support
- Bitcoin escrow tooling announced
- Block’s call for mining community feedback
- Sentrum wallet tracker released
- Stack Wallet adds FROST support
- Transaction broadcast tool announced
https://bitcoinops.org/en/newsletters/2024/05/24/#changes-to-services-and-client-software

Pooled mining occurs when two or more independent miners collaborate on finding proof of work for new blocks, with them fairly dividing the rewards of any blocks they find...
https://bitcoinops.org/en/topics/pooled-mining/

Bitcoin Optech will host an audio recap discussion of this newsletter with special guests Andrew Toth, Antoine Poinsot, and Tony Klausing on Twitter Spaces Monday at 14:30 UTC. Join us to discuss or ask questions!
https://x.com/i/spaces/1nAKEaAkVzVKL


Check the above link, there is a full list of requirements in the FAQ


nostr:npub1a00wj229auzjswlq4s77y4u8eqdx5k9ppatgl8rtv8va65f6mwksum9q3h are you going to use GrapheneOS? I would love hardened hardware that's not from Google...
https://grapheneos.org/faq#future-devices


Entrepreneurs are the historians of the future.


Is there a cashu cover traffic bot?

Make ecash self transfers at random time intervals to increase the anonset of users of that mint.


Jimmy Morrison made this awesome movie about the 2008 boom and bust cycle from an Austrian perspective.
https://www.youtube.com/watch?v=IbyMtVk89o8

Now he's almost finalized the two part sequel about the following ludicrous policies and their consequences.
https://youtu.be/GczCMJPbxw4?si=9Rc59tsiNEzwkG2O

Check it out at https://letusdisagree.com/


If you’re looking for a great way to start your week, leave your preconceived notions at the door and educate yourself about what Anarchy really means with nostr:npub1klkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qulx3vt

https://fountain.fm/episode/GZ1sR5PKLEYphktZ20rp
#Titcoin


Loved listening to this… ESPECIALLY the way to think about the cantilon effect

it’s not just that the 1% closest to the money creation steal off us BUT we in turn are stealing off the generations that follow us

We are unwittingly stealing from others in our society and our future generations

This is the unwitting fiat mindset… just by using fiat you are the problem

Thankyou nostr:npub1cj8znuztfqkvq89pl8hceph0svvvqk0qay6nydgk9uyq7fhpfsgsqwrz4u and nostr:npub1klkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qulx3vt  💪🧡

https://fountain.fm/episode/GZ1sR5PKLEYphktZ20rp


“Even if you might not consciously be aware of how you're hurting yourself in the act of using fiat, once you stop doing it, you realize quite quickly of how devastating this actually was.” — nostr:npub1klkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qulx3vt on nostr:npub10qrssqjsydd38j8mv7h27dq0ynpns3djgu88mhr7cr2qcqrgyezspkxqj8
#Titcoin
https://fountain.fm/episode/GZ1sR5PKLEYphktZ20rp


I'd love to finally have an audiobook for most of these, was contemplating to do it myself already


Good book, but it's strategy, not fiction


This was fun, well done on the edit!


New episode of Nostrovia with nostr:npub1klkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qulx3vt of Wasabi wallet.

nostrovia.org for links.


Yeah, it's pretty wild.


Wasabi is now finally running on Whonix and Tails!

https://github.com/zkSNACKs/WalletWasabi/pull/12991


New Wasabi Wallet release v2.0.7.2, now you can coinjoin from one wallet to another, great for moving your stash to cold storage privately.

https://github.com/zkSNACKs/WalletWasabi/releases/tag/v2.0.7.2


This perfect day is also nice


Basically read anything on anarplex.sirion.io/files

True Names is also excellent


atlas shrugged
a lodging of wayfaring men
alongside night
mandibles


Global & Anonymous #Bitcoin backed loans.

Don’t sell, Borrow!

https://m.primal.net/IEAr.png

Live now! 👀 👇 http://lend.hodlhodl.com


It's so simple and elegant


You can make a payment with one input and two outputs in a large coinjoin, don't use any extra blockspace, but get decent improvement of privacy.


Staunch peer-to-peer maximalist. 🕶

Grafton, Head of Growth at Vexl, is dedicated to enhancing accessibility of #bitcoin without KYC while emphasizing users’ right to privacy. He champions bitcoin's original vision as a truly p2p electronic cash system for everyone.

Ash The Vexl Dog approves the message!

https://m.primal.net/IDsi.png


For me, 2024 is all about helping expand the reach of #Bitcoin tech to as many people as possible.

Recent actions by governments worldwide show that our time to act is limited. While I don't see any chance for Bitcoin to fail, there will be a big struggle over how many people will meaningfully join the network.

Amid rising BTC/USD rate, noise from those preoccupied with their self-centered agendas, and outright scams pushed by bad actors, it's challenging to stay focused and ensure you’re part of Bitcoin's bright future.

https://m.primal.net/IDih.png

What I’ve done over the recent months was all to push forward components that I see as critical for Bitcoin to reach as many people as possible:

- Voucher Plugin: I demoed this with  nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m to show how we can have this tech as part of FOSS stack and streamline onboarding people through a network of merchants. In the second half of 2024, I will release the final version, once all other pieces are in place.

https://m.primal.net/IDim.png

- Bolt Card Functionality:  nostr:npub1zfytz6ktce3av2svlfpl0e79e44tnskxmvlpkcmc7q0xct3qa49swvm60l integrated it directly into  nostr:npub155m2k8ml8sqn8w4dhh689vdv0t2twa8dgvkpnzfggxf4wfughjsq2cdcvg, and we battle-tested it during  nostr:npub1h493d0qgwhu95s82zd9sxrt3ckn3ttgvaf04z02neckadxw5fkvqte4cwz. The final release is coming soon for all who want to create their own Bolt Card Banks.

- Point of Sale: The work that  nostr:npub1za04drthlvxtwsq0phwc4mgh8rxhjafjkv2w7pf6ze5afka8gvaquadur3,  nostr:npub1y24gz5gwucl79vtv4ctwpysl0r5m4xyzu2rgulnr44ks3t5mt92q4nz2ad,  nostr:npub14j7wc366rf8efqvnnm8m68pazy04kkj8fgu6uqumh3eqlhfst0kqrngtpf,  nostr:npub1qm72nur0wn8cdgt0unp0amzssuqxg03tzpd4r87e856nxtz344fs6g74md did along with other BTCPay contributors over the last year on this front has been amazing. And then  nostr:npub13ljnkd633c7maxatymv3y2fqq8vt3qk7j3tt0vytv90eztwgha9qmfcfhw plugin along with Bitcoinize device creates a perfect setup. I’ll continue to support and participate in POS deployments because refining this technology is crucial, so it’s the best possible for circular economies that want to deploy it.

- Payroll Plugin: I'm dedicated to solo development and evangelism whenever possible - I derive a lot of motivation from now seeing how many Bitcoin companies use this plugin to streamline their monthly payouts and save time.

https://m.primal.net/IDik.png

- Evangelizing: I won’t just promote stuff I develop - with PayJoin/CoinJoin videos I have promoted great work others did; work that now can be critical when centralized coordinators are shutting down.

- Supporting Creators: Those who cover efforts and create content around what FOSS contributors develop will always have my support. That’s what my trip to  nostr:npub1rjtrs7xqdvj3588r9njrexh2n750j7jdwx9qs543nutmdsj6ljaqpfmp8a with  nostr:npub1rj7eh0eu3skwcyr5adpcjwxft9z4yjdspjryq6gynqw2j49f9a3quqjpw2 was all about.

https://m.primal.net/IDij.png

- Nostr: Any additional time I have will be devoted to Nostr until #Nostriga. I've invested considerable time in the past year and a half helping organize events around the protocol I see as the one that will bring freedom of communication to masses. I hope you've enjoyed them.

https://m.primal.net/IDii.png

So, if you ever see me, Uncle, doing something and wonder what is behind it - see this post.

Number go up, but also number of Bitcoiners go up. That’s what it’s all about for me.

And any help and support you send to ensure we succeed in this mission will be appreciated.

✊🗽


When people finally start reading anarplex
https://media4.giphy.com/media/10rsLtGrOcCR0s/giphy.gif?cid=6c09b952illb17hjl5y7s9sryd91c7g5i4lp7prttoq01ojj&ep=v1_internal_gif_by_id&rid=giphy.gif&ct=g


This is a highlight created in https://highlighter.com

At some point, working within a system becomes cowardly and immoral; for us, that point has arrived.


Good morning. A reminder that you don’t need to write code to contribute to the #Bitcoin (or Nostr) ecosystem:

“You can be extremely useful to basically any project out there simply by doing what you are marginally best at. The thing that you're really, really good at, much better than anything else that you do, just keep on doing that for whatever project you're interested in. And you're probably going to make a quite valuable and meaningful impact.” — nostr:npub1klkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qulx3vt on nostr:npub10qrssqjsydd38j8mv7h27dq0ynpns3djgu88mhr7cr2qcqrgyezspkxqj8
#Titcoin
https://v.nostr.build/xE8el.mp4


A High-Level Technical Overview of Fully Homomorphic Encryption
https://www.jeremykun.com/2024/05/04/fhe-overview/


Did you know?

You can create an offer to Buy/Sell Bitcoin on Bisq v2.0.3, stipulating the utilization of the Lightning Network ⚡with your prospective trade partner. Simply express your preference for LN ⚡using the custom payment method during the offer creation wizard.

This can be tried out until the Lightning Network ⚡ trading protocol is fully implemented.

#dex #decentralized #bitcoin #btc #lightningnetwork #bisq2

https://m.primal.net/IDef.png

Download Bisq v2.0.3 here to get started: https://github.com/bisq-network/bisq2/releases/tag/v2.0.3


That's pretty cool.

Downsides seem to be that there is no denial of service protection across rounds, the same utxo can disrupt many rounds. A centralized coordinator banns a utxo for numerous rounds.

Also blockspace efficiency is not great, a single equal denomination means users need to do a lot of rounds and create / spend many coins. I don't know how this can be fixed though, maybe some ring signature credential that commits to a homomorphic value commitment, something like Wabisabi kvac but with federeted authorship.


How we deploy the Wasabi coordinator:

nix build github:zksnacks/walletwasabi/


Now you can share your Public Spreadsheets!

https://sheetstr.amethyst.social/?author=460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c&id=Amethyst%20Feature%20Request%20Counts


Guys, the Google Drive Relay is real.

https://nosdrive.app/

https://media.gleasonator.com/1e5993e0a62d25ce9a44fcddb83f0ae85ef069614b19c3bafc0a6a7442926107.png


My latest invention is Emessbee 🐝: Unstoppable Coinjoins with No Coordinator

https://stacker.news/items/529905


The assumption about time preference is that it must always be positive. In other words, we assume that people prefer things sooner rather than later, this is why the natural rate of interest cannot be negative.

(sorry about being pedantic about terminology, but that's what Praxeology is all about)


Yeah, that was the inspiration, but it's too long...
I love how simple MIT is