The coinjoin coordinator has an opportunity cost of the fees foregone from any utxo that gets banned.


Someone paying $389 to move $1.94.

547,000 sats to move 2730 sats.

Why?

Because this has nothing to do with Bitcoin and doesn't make any sense from the network's perspective.

People who take comfort that behaviour will remain predictable thanks to economically rational decision making need to know it goes both ways when you start taking in external factors.

You have to do it with miners too.

If a miner can make more money in ways that have nothing to do with bitcoin then you can no longer rely on simple assumptions like "miners will do X because if they don't then they will make less than a miner who does"

The simple example I've used many times is compliance.

If you have a choice between expensive legal battles and exclusion informed by government blacklists (i.e censorship) then it's economically rational to do what's economically irrational.

"You left $500 in TX fees on the table! Why?"

"Because our lawyers advised us that this would save us several million dollars."

We have a case-study of this exact scenario with Wasabi Wallet.

So if this is true, what does it have to do with spam? From a miner's perspective, spam is simply a free lunch.

What's the downside?

The issue is we've been standing on shaky ground when it comes to the assumptions we've made about the choices of miners. Myself included.

It turns out there are instances when economic rationality works *against* the interests of the wider network. It's obvious, but apparently we're all surprised that this it the case, or straight up in denial about it.

Spam is that exact scenario. Blocks are far larger than was ever supposed to be possible with the introduction of witness-discounted data. We see block after block at what was meant to be a theoretical maximum of just under 4MB.

There is no room for interpretation. This is simply harmful and the result of a nasty attack.

The entire basis on which the blocksize wars were fought was that encumbering nodes with way more data would lead to centralization. (Along with a host of other issues, like centralization of mining & pools).

The simple solution is that it needs to stop. Blocks cannot be stuffed with arbitrary data placed there by ambivalent miners.

The way this stops is as a natural extension of a bitcoin community that recognizes attacks and responds accordingly.

It means using node software that isn't designed to hurt its users which is already happening with migration away from Core to Knots. The most popular plug-n-play nodes have all begun offering this.

They did not this time last year.

It means miners choosing pools that at least give them the option of not participating in the attack -> currently well under 1% of the hashrate, 6 months ago not even an option. Hard for me to talk about because obviously I'm employed by the pool in question.

It means people who never mined doing it for the first time.

And mostly it means maintaining an understanding of what makes bitcoin bitcoin. That in itself has always been enough to evict crypto scammers to something other than Bitcoin. Those who wanted to turn it into "paypal 2.0" with the same disregard and contempt for nodes that the spam apologists display now forked themselves off to bcash and craigcoin.

The one thing that will *not* solve this problem is high transaction fees. This is an argument made by those who at least understand an attack when they see it, but are in denial about what surviving it actually involves.

Throughout the last few months the conversation has rapidly progressed and the tide has been turning.

I am under no illusions that this is an easy fix, but that is because of the nature of politics and how much larger the ecosystem is now.

But it's also just history repeating itself.

Bitcoin keeps having to fight the same battles again and again. Always in service of importance of being able to run *and use* a node, affordably and trivially, by complete noobs.

To maintain decentralization.

To resist the corrupting of what we have.

Bitcoin is money. Other features cannot come at the expense of that.

OP RETURN wars, bcash, segwit2x, shitcoins, coloredcoins, hostile BIPs, malicious devs....

We've done it a million times before. Every single time the "laser-eyed toxic maxis" win.


The client will likely score those high value outputs as "anonscore 2" or something very low, and thus continue for numerous rounds of coinjoin in the future, until the anonscore is above the target of 50 or so.

It's very difficult to get large amounts private in a single transaction, that's why a multi round ceremony is initiated.

Try analyzing three hops of coinjoin for those high values, and judge your confidence afterwards.


An alternative is a fedimint with multiple warehouse operators of a subset of the holdings, this way if one warehouse is compromised not all funds are lost.


Ataraxia: the kind of inner tranquility that results from knowing you’ve done everything that was in your power to do.


I'd love to see an ecash mint as fiat cash money warehouse.

The ecash token is redeemable in person for fiat cash.

The mint operator does not need access to fiat banking.


Coinjoin worth 890 bitcoin

https://mempool.space/tx/da90d4fcee3d3965d23aef486065d317ce069f7e43751018443b3a4e0901394e#vout=0

nostr:nevent1qqsr4jj60q3mvax8kdgrvxvtydydnf9xtvwcy3djrqnk88nhhle4v4gpr3mhxue69uhkummnw3ezumt4w35ku7thv9kxcet59e3k7mgzyzm7669svt0xkjsju50a22zurc0qa589z2xd4yatzx6p2z64a5e0cqcyqqqqqqgv0kva2


True, shutdown is an option, but at least no financial benefit for the malicious operator.


Coinjoin worth 673 bitcoin

https://mempool.space/tx/0dcd9698297318e84fdf13445c5e7b1b92a94633f96b635dc707b8cdcc6271f2#vout=1


Is a cashu mint run in a secure enclave custodial?


How do you do normally?


We'll probably end up doing some magic with spacing and colors, it should be formatted like this to be easy for both btc and sat denomination:

12 345, 67 890 124 BTC


Checkout coinjoins.org for an overview of each protocol.

tldr, in order of appearance:

Joinmarket: the OG coinjoin coordinator market place, free blockspace but less privacy for makers, instant custom but expensive transactions for takers.

Wasabi 1.0: the first blinded coinjoin coordination model using zero link, a static coordinator who cannot spy on users, but defines the single equal denomination in the round. Arbitrary input values, and per user one non-equal denomination change output. The equal amount slowly decreases with each round, transactions with 50-200 inputs

Samourai: similar to Wasabi 1.0, but the whirlpool coordinator enforces specific denominations on the input side, and does not allow non-equal change output, thus a single user setup transaction has to me made to prepare the denominations. The coordinator chooses which utxos can remix, different rounds with different equal denominations, transactions with always 5 inputs, 5 outputs.

Wasabi 1.1: similar to Wasabi 1.0, but add multiple equal denominations in the same transaction to allow for faster and more blockspace efficient privacy gain.

Chaincase: A Wasabi 1.1 fork for iOS.

Wasabi 2.0: with WabiSabi eCash the coordinator now defines a range of minimum 5000 sats maximum 40000 btc, and clients can register whatever value they want, allowing for more private, efficient and flexible onchain behavior.

Jam: a user friendly web interface to the joinmarket rpc server.

Sparrow: a whirlpool client interface.

BTCPayServer: A WabiSabi client interface with focus on merchants and customizability.

Trezor Suite: A WabiSabi client with the capability to sign coinjoin transactions on a hardware wallet.

Joinstr: Similar to joinmarket, a incentive based bulletin board for non-blinded coordinators.


Glad that Wasabi was easy and useful!

Let me know how we can make it better.


Gm nostriches!!! Finally used Wasabi wallet to managed some funds from an exchange. Should have used earlier, SO straight forward. “Privacy is necessary for an open society in the electronic age. Privacy is not secrecy” Eric Hughes. We should not have to share our financial transactions with everyone or have limits placed on how much we can transact. #bitcoin #grownostr #maintainprivacy https://image.nostr.build/8ec3b0494823101b97f9e5331ab043ddf097c4e3317cd80d9f3e44cc7869fb91.jpg


Blockspace efficiency was never a priority for whirlpool.

If you'd like to save some sats, try WabiSabi, it's been designed with efficiency as priority.

Checkout coinjoins.org/calculator to find out how much you would pay in different scenarios.


October 2019


Fascinating talk by Timothy C May at HCPP17
https://www.youtube.com/watch?v=TdmpAy1hI8g


The paper is here:
https://github.com/scritcash/scrit-whitepaper/blob/master/scrit-whitepaper.pdf


The forgotten art of anonymous digital cash.

A groundbreaking presentation by smuggler at HCPP 2019, introducing the concept of federated ecash mints with SCRIT (secure, confidential, reliable, instanttransactions).

This is the root of the vision that fedimint encoded.

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


We're thrilled to announce the new major release of BTCPay Serve 1.13.0!

🎨Server Branding
🔗Invite users via email/link
👨💼 New employee & manager role
🛒New Pos Keypad Item
👀Admin can view-only stores
🤳🏻 Better Bitcoin QR Support
🏬 3 new inetgrations - NopCommerce, GrandNode, XenForo
🔌 2 new plugins - Breez, Bringin

https://m.primal.net/HpMQ.mp4

🔗Read full release announcement on our blog
https://blog.btcpayserver.org/btcpay-server-1-13-0/

🎨Server Branding
Server owners can now apply custom name to their server. This functionality complements the previously added capability to upload custom logos, allowing for a branded user interface.

Additionally, a new contact input feature allows you to specify an email or an URL. This will be displayed on publicly visible pages of your server and in the sidebar for server’s users, enabling them to easily contact you for support.

https://video.nostr.build/9510dab2c7baf3c1421a08f2c12feab5ac0343ca922ab2ed7f52034738d03949.mp4

🏪 Overview of stores
We've listened to your feedback! Understanding who is using your instance and how is crucial. To further enhance server owner flexibility, we’ve introduced the ability for owners to easily overview the stores created on their server. Currently, admins can access these stores in view-only mode.

👥 Invite new users via email/link
We’ve redefined how users can be onboarded to a server. Inviting users to your BTCPay Server is now much easier. As a server owner, willing to onboard merchants, you can now invite them through email or by sharing a link. Instantly granting them access to their accounts.

In addition to this, we’ve also added approval for new accounts. If you allow user registration on the server, you now have the ability approve new users before they start using your instance.

https://video.nostr.build/5822455f666ad54f165ca19f1c6e975282792e4d768ad9f4f95b3bdc6a7ae1c5.mp4

💁🏻 New store roles: Manager and Employee
This release introduces two new store roles: Manager and Employee. Alongside the existing Owner and Guest roles these roles are designed to streamline the management of user access to your store, making it easier than ever to delegate responsibilities while maintaining tighter access to private data.

https://video.nostr.build/f691282e655ab296bbb0cef26b46f32fd86d51abeb753f209c29e5c8128bc806.mp4

And much more... visit our blog to read all about the new features and bugfixes in 1.13!

https://blog.btcpayserver.org/btcpay-server-1-13-0/


block filters are magic.


ridiculous


No, bone tea is a thing, so there can be non-vegan tea.


At the forefront of monetary computer science.🚀

nostr:npub1klkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qulx3vt contributes to numerous #bitcoin FOSS projects, incl. Wasabi Wallet &
nostr:npub155m2k8ml8sqn8w4dhh689vdv0t2twa8dgvkpnzfggxf4wfughjsq2cdcvg.

He focuses on establishing a second realm where sovereign individuals can pursue their entrepreneurial action.💥

https://image.nostr.build/1f162269c3c3d6a844fb1f407aca480920ef88a7edf206584a86d55495490dec.png


bone tea > vegan tea


This will be dope.
Wasabikas are coming as well!


Nostr exclusive: Join us for the Ecash Hackday V2 in Berlin June 20-21 2k24. This is a small and intimate event for hackers, researchers, and anyone else interested in Chaumian Ecash.

We have participants from GNU Taler, Fedimint, and Cashu. There will be talks, discussions, and a lot of code. Our goal is to bring the dev community closer together, exchange ideas, and work on cool projects during the hackathon.

Register here.

https://ecashhackday.github.io/
 https://image.nostr.build/4ff512fdb913f50068c076df023f2eb1b34d8c94eddf1e2cbeffafb2a66ab43e.jpg


Let's re-invent the future so that our kids might have the internet they deserve. https://image.nostr.build/513ee8ce8a337e9f91a26139f641445fbadb32ca257aae7f617ea5bede1f1a51.jpg https://image.nostr.build/0498bd4b697b5effc4b528f3a5d0098b94aab2aca4a9f130fcc61de5ec177e1d.jpg
https://sovereignengineering.io/
#SovEng #P2P #peer2peer #Bitcoin #nostr


Savage


How about amber login support for nostr nests?
nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5


Anamorphic Image Encryption in Cyberspace

Anamorphic Image Encryption is a new way to share artwork so that viewers can enjoy it but can't steal it, and it relies on the unique properties of cyberspace.

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

>[!NOTE] Definition
>__Anamorphic__ (adj.):
>_Relating to or involving a form of distortion in which an image or object is only recognizable when viewed from a specific angle or through a specific device, creating an optical illusion._

Anamorphic image encryption is a way of representing an image in cyberspace such that it may only be viewed from a specific location, and the viewed image may not be copied with high fidelity.

The below is theoretical and yet to be implemented in cyberspace. Feedback welcome!

## Primitives

The POW action chain serves as a location primitive. If your action chain is valid, your avatar is in a specific location in cyberspace. The validation rules for action chains enable them to serve as a POW-based proof-of-location and a solution to a location "double spend" (being in 2 locations at once).

This location may be reacted to by a nostr bot watching for an action chain to reach a certain coordinate or area. Once reached, the bot can reveal a secret to the avatar (by sending a DM to their pubkey); the secret is necessary to view anamorphic content. This is a gatekeeper primitive.

If we want to make an image available at a specific location, we need to encode it properly.

If you know what a frustum is, skip this paragraph. Imagine a hollow pyramid. You pick it up and point the tip top of the pyramid right at your eyeball (carefully!). The base of the pyramid is parallel to you, away from your face. This shape is a frustum; it is an imaginary space where all of the objects you can see exist within. Our eyes actually see more of a cone, but in computer graphics the frustum is rectangular. Now think about one edge of the pyramid that goes from the tip at your eyeball to the base away from you; this edge is at the very edge of your "vision" or viewport. If you put a lightbulb on this edge and slid it back and forth from tip to the pyramid's base, it would grow and shrink but it would not change position from your perspective.

Kind 1 notes exist in cyberspace as cubes; each cube's location comes from a simhash of its content. The color of this cube is derived from the last 6 digits of the created_at in hex. Using seconds as a hex color means that the full gamut of hex-based colors spans 16777215 seconds (0xffffff) or 194 days or roughly 6.3 months. This serves as a pixel primitive. Cubes can be used as pixels and placed in specific locations in cyberspace by mining a note's content so that the simhash yields the desired location.

To review:
- We have a location primitive -- the action chain enables us to be in a location.
- We have a gatekeeper primitive -- we can be given access to information at a location.
- We have a pixel primitive -- we can create images in space.

## Depiction of an Image

However, we don't simply want to create a flat rectangular canvas in space, because that would be too recognizable and too easy to copy. We need more obfuscation if we are going to achieve anamorphic encryption.

Instead of a flat canvas, we can construct an image where each pixel is a random distance between the front and back of the frustum. Viewed form the frustum's perspective, it doesn't matter how far the pixel is from the viewer as long as the pixel stays on the same ray cast from the viewer's eyeball to the base of the frustum. If the pixels are randomly distributed across the 3D space of the frustum, then the image may only be seen from an angle very near the frustum's perspective.

Typically something gets smaller when it gets further away, but the kind 1 cubes as viewed in ONOSENDAI are scaled such that they actually grow in size as the viewer gets further away from them. This is to give an impression of the density of notes from a far distance and to enable the user to select them from a far distance when this would normally not be possible. So the distance to the pixel does not matter for the purpose of displaying the anamorphic image.

## Obfuscation of the Pixels

The final piece to this puzzle is a cryptographic obfuscation of the pixels that assemble the image.

The artist should downscale their artwork so that it is low-resolution, such as 800x600 or whatever size is desired. Considerable POW is necessary to create an anamorphically encrypted image, so the size is important.

Then, the location in cyberspace and frustum should be chosen. The frustum can be of any size, although it would be advisable to keep it within 1 sector (2^30 Gibsons) in length (tip to base).

The pixels in the downscaled artwork should be divided into batches; this can be done in any order or direction or spatial arrangement. Each batch will be published by a separate public key in order to obfuscate the image further.

Next, ephemeral keypair 0 ($E0$) is generated to publish the first batch of pixels (kind 1 notes).

A kind 1 note is published to represent the top leftmost pixel. The `created_at` is set to a time where the last 6 digits of the time in hex equals the color of the pixel in the downscaled art. The content of the note, when simhashed, must yield a coordinate along the top left edge of the frustum. This is where the POW is required to produce an anamorphic encrypted image because many guesses may be required to obtain a good-enough result. Bear in mind that good-enough is permissible; it's up to the taste of the artist. This tolerance may be useful in adjusting the amount of POW necessary to successfully create each pixel.

A batch of kind 1 notes my be published with ephemeral key 0. When batch 0 of pixels is complete, the following should happen:
- An even prefix length $L$ should be chosen. This determines the number of leading hex digits need to be matched for subsequent public keys. This prefix length should be the same for all subsequent batches.
- A Secret $S$ of 256 random bits should be generated. This secret will also be used for all subsequent batches.

Public key target 1 is derived from $\text{sha256}( S + E0_{pub})$

Public keys are mined until a resulting public key's hex prefix of length $L$ matches Public key target 1's prefix of length $L$.

```
	9884a42bcf930100... < target public key
	988456aa3a87e4fb... < mined public key
	^^^^ 4-length match
```

The matching mined keys will serve as ephemeral keypair 1 ($E1$).

>[!Tip]
> Check out Rana for mining keypairs with specific prefixes: https://github.com/grunch/rana

Now, the next batch of pixels can be published with $E1$ until the batch is complete.

To obtain $E2$ for the third batch, derive your target from $\text{sha256}(S + E1_{pub})$. Mine until you find a public key with a prefix matching your target's prefix of $L$ hex digits long. Publish your third batch under that key. Repeat until your whole image is published.

>[!Tip]
>To further obscure the relationship between the kind 1 notes and the pixels in your image, you can add random e/p tags to give the impression that the notes are actually part of a conversation, or other random tags to give the impression that they are used for something else.

Now, the artist must set up a bot that subscribes to cyberspace actions so that if an avatar enters a defined coordinate area, their pubkey will receive:
- The first public key $E0_{pub}$
- The Secret $S$
- The prefix length $L$
- Relays to query for the pixels
## Viewing the Anamorphically Encrypted Image

When an avatar looks into the void of cyberspace, they will see a lot of note cubes. Even if viewed from the correct location, the notes comprising the pixels of the artwork won't be free from unrelated clutter. Therefore, it's necessary to filter the notes in the interface to only show notes that comprise the image. To construct this filter requires the following steps.

Using the information supplied by the bot in the DM, the avatar can query nostr relays for notes published by $E0$. Then, the avatar may $\text{sha256}(S + E0_{pub})$ to obtain the target. They can get the prefix with target.substring(0, $L$) and then do a partial author query on the obtained prefix to find notes published by public keys matching that prefix.

>[!WARNING]
>Partial queries on pubkeys must be an even number of hex digits. Make sure you choose an even prefix $L$.

This is where it is important to choose a prefix that is long enough to be fairly unique but short enough to not require a lot of extra POW.

Once you query the author prefix and find zero notes, then you have fully reconstructed the image. Until then, the avatar will continue to derive $E1$, $E2$, $E3$, etc. and query the notes they have published.

Now that the notes representing the pixels of the image are obtained, the client must position these notes in cyberspace as per usual, remove notes not matching the filters from view, and then the avatar must be in the correct location and looking toward the frustum.

Now, finally, the avatar may see the image that the artist intended to portray.

## Anamorphic Properties

When viewing the image, there are some things to keep in mind:
- to view the image, one must know which coordinate to travel to and actually go there with POW
- the image is a low-fidelity recreation of the original image, so the full resolution original may not be reconstructed
- the representation of the image via note cubes scattered inside a frustum introduces perspective errors into the viewing if the avatar is not perfectly positioned in line with the center of the frustum. This is actually a feature, not a bug. Because it is difficult to obtain an exact location in cyberspace, the subtle movement of the avatar will gradually obfuscate the depiction of the image as a function of distance from that ideal point. This makes screenshots and screen recordings suboptimal to capture the image as it will almost always contain defects and perspective errors. However, the way perception in our brains works tends to smooth over these imperfections in real-time, especially as we move. Think about looking through a smudged window or phone screen -- often you hardly notice it. Or, think about looking at something beyond a wire mesh or fence while moving. It's easier to see when you are moving even if the image is heavily obscured.
- the method of batching and publishing the pixels across the frustum with ephemeral keys prevents observers from detecting that an image exists at all, and even if detected, from assembling every pixel due to the necessity of knowing the secret to derive all ephemeral keys. The only way that an image could accidentally be detected would be by accidentally visiting the exact place where the frustum focal point is located and looking in the correct direction, which is about as rare as generating a private key someone else owns.

To summarize, the anamorphic image is better interpreted by our brains than by a screenshot, especially as we move around in cyberspace. It is a way of displaying image content that requires a viewer to be in a place, meet a criteria, and severely limits their ability to take the image with them.

## Potential Counters

Now, one way that the image could be copied is by copying the color data from the cubes once the cubes are known from the secrets provided by the gatekeeper. However, unless the cubes are addressed in cyberspace, they hold no pixel position data in themselves. If the note batches are chopped up creatively, it can be reasonably challenging to reassemble the image even if all the data is at hand.

## Conclusion

This is a unique method of obfuscating visual content behind proof-of-work. The image may be seen, but only if enough cyberspace proof-of-work is provided. The image may not easily be copied or stolen, and will look better when experienced in cyberspace than any stolen representation will look because of how our brains interpret visual information.


That's really interesting.

But why would it be higher quality to view in cyberspace? Even with the perspective distortion, I could just make a screen recording while I move around in cyberspace, and reproduce exactly what's seen there.


Be careful where you download your Software packages from, and always verify PGP signatures!

The correct Website is https://wasabiwallet.io
PGP: 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E

nostr:nevent1qqsxg4zslkyndehf82nnefgqjeuzq05k0fd6vlw4jnlla7e74hnfdzcpp4mhxue69uhkummn9ekx7mqzyzm7669svt0xkjsju50a22zurc0qa589z2xd4yatzx6p2z64a5e0cqcyqqqqqqg6eg88m


Oh, they even start the download when you visit the site?


Yes, it's a scam, be careful! +

There are many fake domains with usually malicious Windows installers.

We are not allowed to make advertisements on Google or duckduckgo, but the scammers are, so they always show up as first result.

We've been reporting them for years, but they always come back. It would be helpful if you can report it too please.


It's already in the RPC server.

There's a chance that we get coinjoin to other wallet in the UI this release. (first step to fake hww cj)

A payment in coinjoin to arbitrary address and amount will hopefully be in v2.0.8


I'm even more bullish on Wasabi v2.0.7 than v2.0.6, even though it's been only one third of the development time.

I hope we can get all the juicy features included, release target day is April 15th [plus two weeks]!


Many wallets support pay to many.

But for a transaction of this value, I'd guess Bitcoin Core was used, with some custom rpc magic ontop.


Outputs are super small, just a hash and amount...


Ontop of that, the more inputs, the higher the likely hood of one of them failing to sign, thus disrupting the coinjoin process.

Thats at least the intuition, but in some analysis the failure rate of +350 input rounds is roughly the same as for 250+ inputs, so maybe this isn't even a serious scaling issue.


Yes, it's one of many variables in the backend configuration file.

In general, larger coinjoins is better, but there are at some point diminishing marginal returns of an additional input.

Bitcoin Core has a mempool standarness policy which limits transactions to 100kvB, that's around 600 inputs and 600 outputs. Larger transactions are still valid when they are in a block, but they don't get releayed as unconfirmed transactions by the default node configuration.

[code here: https://github.com/bitcoin/bitcoin/blob/v24.0/src/policy/policy.cpp#L101 ]

The reason is, that building an optimal block template with very large transactions is computationally very expensive, it's faster to do it with more but smaller transactions. And for mining decentralization, the speed of block template construction is insanely important.


nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z I think here is a rendering bug in Amethyst, the note has `v2.0.6` without any spaces, but it gets displayed as `v2.0. 6` with a final space.


nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z I think here is a rendering bug in Amethyst, the not has `v2.0.6` without any spaces, but it gets displayed as `v2.0. 6` with a final space.


Because when we have very many inputs, it makes sense to split the users based on a second criteria. This could be either for input values, or for sats/vbyte fee rate.

Currently we split based on input values, because it results in two transactions with more homogeneouty, the whales coinjoin with whales, and plebs coinjoin with plebs.


262 out of 1045 coinjoin rounds failed, because there were TOO MANY inputs registered.

We destroy a round when more than 400 inputs are registered.


The average output denomination has an anonscore of 8.8

nostr:nevent1qqs2p0wh6qpxc0a3pupcddlxtupzuq448d7sflx5fhuyuwpfmyypqccpr3mhxue69uhkummnw3ezumt4w35ku7thv9kxcet59e3k7mgzyzm7669svt0xkjsju50a22zurc0qa589z2xd4yatzx6p2z64a5e0cqcyqqqqqqgq5kl63


The average Wabisabi coinjoin has 235 inputs.
Nice increase after the v2.0.6 release.


Due to popular demand here is a quick video of using phoenixd with the Alby NWC app.
https://share.cleanshot.com/Cvpv95FP

it shows:
+ running phoenixd and the NWC app
+ configuring the Alby extension
+ sending / receiving
+ one-click zapping on nostr with Alby NWC + phoenixd (works on web and mobile)

You will be able to use it, too.
But it still needs a bit of work.

I can't wait to hear your thoughts and feedback.

We are also slowly onboarding beta-testers to our new release. Signup if you're interested.


And no filming?


Dunno.

It's likely a custodian.
Maybe a casino or exchange.

Probably they're moving to a cashu setup...


Well, in this case, it's humungous on both counts.

395.18 kWU is big.


Just imagine the thrill of signing this transaction.

A lot of tinfoil required.

nostr:nevent1qqswjk3mcfe3psp6z0uvxpf7dv43v62w3egwl52d4szk9epxq80vs8qpr3mhxue69uhkummnw3ezumt4w35ku7thv9kxcet59e3k7mgzyzm7669svt0xkjsju50a22zurc0qa589z2xd4yatzx6p2z64a5e0cqcyqqqqqqgl0rtwv


Just casually moving a humble stack of 35291 bitcoin.

https://mempool.space/tx/1d9c390ec561559512838bebff74e3e1d636678fc08370e6bd48b6bb29138648


Get shit done.


Any social media managers (aka professional shit poster) looking for a job?


Wasabi's RPC can also be exposed as an ephemeral tor onion service.

So you can remotely control a server from your phone, without needing a static IP or domain name.

nostr:nevent1qqs0jmdptcr3mx468g2nl9enc94882ftq2muy75hhqsfxz2yk6vm0hqppamhxue69uhkummnw3ezumt0d5pzpdlddzcx9hntfgfw28749pwpu8sw6rj39rx6jw43rdq4pd276vhuqvzqqqqqqyzdy4vk


Usually, you can use Wasabi on your desktop app.

https://blog.wasabiwallet.io/use-wasabi-rpc-interface/

But the RPC, or Remote Procedure Call, interface allows you to use the wallet programmatically and even find hidden features!

How do you use Wasabi's RPC interface? What is it? You can read our latest blog to find out all about it, including examples of actual commands you can run.


I wish this were a coinjoin...
https://mempool.space/tx/1d9c390ec561559512838bebff74e3e1d636678fc08370e6bd48b6bb29138648


coinjoins so hot right now.


Correct!

A coinjoin is atomic, so either nothing happens, or everyone gets all his money on a new address.

Coinjoin is also non-custodial, meaning you never give up control over your private keys and utxos.

A coinjoin client assumes that the coinjoin coordinator and other participants are malicious, and it has strong defenses against shenanigans.


We're at a point where major central banks are afraid to decrease interest rates and further increase the fiat base money supply, because of Bitcoin as an escape hatch for inflation refugees.


It's fun how bits and bytes can be beautiful.


Yes!

If only one single input out of those 300+ does not sign the transaction, it is not valid according to Bicoin consensus rules, and other nodes will reject the transaction.

This can happen when a user shuts down his computer, or the wifi goes off, or a Tor node is overloaded, or the user is malicious.

The first attempt of signing a coinjoin transaction has only ~25% success rate.

Then the coordinator kicks out the non-signing input, and attempts a second round, which has ~50% likely hood of success.

So it usually doesn't take more than 5 attempts to succeed.


Imagine the likely hood of 300 people agreeing on where to go to dinner.

Now imagine how hard it is to find a large group consensus about making a bitcoin transaction.


Two huge successful coinjoins within 15 minutes 🔥🔥🔥

360 inputs
346 outputs
42 bitcoin
https://mempool.space/tx/620370cfa56101d5eb5df3eb36cc25dc1b80ded0182a56d50a500db67b8086cd

369 inputs
357 outputs
39 bitcoin
https://mempool.space/tx/5dd0bf6b406ea40c6f19f0729be7564e47d189b265583987e162071b2991b474


SEC-02 calling!

Who's ready to jump on board and explore unchartered waters?

The Sovereign Engineering Cohort 02 expedition sets sail from Monday 6 May, to Friday 28 June.

🏴☠ Privateers sign up here: https://sovereignengineering.io/

#soveng #nostr #bitcoin #lightning #foss #freedomtech #Madeira  nostr:npub1s0veng2gvfwr62acrxhnqexq76sj6ldg3a5t935jy8e6w3shr5vsnwrmq5

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


There's a nostr event for coinjoin coordinator announcements, but so far only btcpayserver is fetching these events.

The coordinator can be changed in the Wasabi config file.

Hopefully soon we'll have something like bitcoinmints.com for coordinators.


Exactly!
This is poisoning the assumption, and thus improving the privacy of even non-Wasabi users.


Probably never.


bitcoinmints.com is fantastic.


I'm glad to see more activity and discussion about the gossip model. Glad to see [fiatjaf](nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6) and [Jack](nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m) posting about it, as well as many developers pitching in in the replies. There are difficult problems we need to overcome, and finding notes while remaining decentralized without huge note copying overhead was just the first. While the gossip model (including the outbox model which is just the NIP-65 part) completely eliminates the need to copy notes around to lots of relays, and keeps us decentralized, it brings about it's own set of new problems. No community is ever of the same mind on any issue, and this issue is no different. We have a lot of divergent opinions. This note will be my updated thoughts on these topics.

COPYING TO CENTRAL RELAYS IS A NON-STARTER: The idea that you can configure your client to use a few popular "centralized" relays and everybody will copy notes into those central relays is a non-starter. It destroys the entire raison d'être of nostr. I've heard people say that more decentralization isn't our biggest issue. But decentralization is THE reason nostr exists at all, so we need to make sure we live up to the hype. Otherwise we may as well just all join Bluesky. It has other problems too: the central relays get overloaded, and the notes get copied to too many relays, which is both space-inefficient and network bandwith inefficient.

ISSUE 1: Which notes should I fetch from which relays? This is described pretty well now in NIP-65. But that is only the "outbox" model part. The "gossip model" part is to also work out what relays work for people who don't publish a relay list.

ISSUE 2: Automatic failover. Apparently Peter Todd's definition of decentralized includes a concept of automatic failover, where new resources are brought up and users don't need to do anything. Besides this not being part of any definition of decentralized I have never heard of, we kind of have this. If a user has 5 outboxes, and 3 fail, everything still works. Redundancy is built in. No user intervention needed in most cases, at least in the short term. But we also don't have any notion of administrators who can fix this behind the scenes for the users. Users are sovereign and that means they have total control, but also take on some responsibility. This is obvious when it comes to keypair management, but it goes further. Users have to manage where they post and where they accept incoming notes, and when those relays fail to serve them they have to change providers. Putting the users in charge, and not having administrators, is kinda necessary to be truly decentralized.

ISSUE 3: Connecting to unvetted relays feels unsafe. It might even be the NSA tracking you! First off, this happens with your web browser all the time: you go visit a web page and it instructs your browser to fetch a font from google. If you don't like it, you can use uBlock origin and manage it manually. In the nostr world, if you don't like it, you can use a client that puts you more in control of this. The gossip client for example has options for whether you want to manually approve relay connections and AUTHs, just once or always, and always lets you change your mind later. If you turn those options on, initially it is a giant wall of approval requests... but that situation resolves rather quickly. I've been running with these options on for a long time now, and only about once a week do I have to make a decision for a new relay.

But these features aren't really necessary for the vast majority of users who don't care if a relay knows their IP address. Those users use VPNs or Tor when they want to be anonymous, and don't bother when they don't care (me included).

ISSUE 4: Mobile phone clients may find the gossip model too costly in terms of battery life. Bandwidth is actually not a problem: under the gossip model (if done correctly) events for user P are only downloaded from N relays (default for gossip client is N=2), which in general is FEWER events retrieved than other models which download the same event maybe 8 or more times. Rather, the problem here is the large number of network connections and in particular, the large number of SSL setups and teardowns. If it weren't for SSL, this wouldn't be much of a problem. But setting up and tearing down SSL on 50 simultaneous connections that drop and pop up somewhat frequently is a battery drain.

The solution to this that makes the most sense to me is to have a client proxy. What I mean by that is a piece of software on a server in a data centre. The client proxy would be a headless nostr client that uses the gossip model and acts on behalf of the phone client. The phone client doesn't even have to be a nostr client, but it might as well be a nostr client that just connects to this fixed proxy to read and write all of its events. Now the SSL connection issue is solved. These proxies can serve many clients and have local storage, whereas the phones might not even need local storage. Since very few users will set up such things for themselves, this is a business opportunity for people, and a better business opportunity IMHO than running a paid-for relay. This doesn't decentralize nostr as there can be many of these proxies. It does however require a trust relationship between the phone client and the proxy.

ISSUE 5: Personal relays still need moderation. I wrongly thought for a very long time that personal relays could act as personal OUTBOXes and personal INBOXes without needing moderation. Recently it became clear to me that clients should probably read from other people's INBOXes to find replies to events written by the user of that INBOX (which outbox model clients should be putting into that INBOX). If that is happening, then personal relays will need to serve to the public events that were just put there by the public, thus exposing them to abuse. I'm greatly disappointed to come to this realization and not quite settled about it yet, but I thought I had better make this known.


So Lea was looking for a venue for this year's Cypherpunk meetup. One owner was inquiring about what is cypherpunk and she gave a proper explanation. Turns out the owner was a bit afraid, we want to organize some kind of a punk concert.

Of course we are, so we sent them helpful photos from last year to see what kind of cool people are coming.

Venue TBC, but it looks good, probably will be much more fun than last year.

Get your tickets here:

https://pay.cypherpunk.today/apps/4LEEvtqY8UMnuB7y5wCmjvi2tXy3/crowdfund

 https://image.nostr.build/622aef90548aa44730fd8f41fad7c5aac178371a6cf51903e01a62a2724e5819.jpg

 https://image.nostr.build/f587d3db626bc50365cdd57ec139c2f1ad117dccc408a0b5de4f060bb3145837.jpg


Privacy warnings and suggestions is an awesome feature in Wasabi.

The client runs branch and bound coin selection algorithm to find an input set that's close to your desired payment amount, so that you can send a little more or less sats in a transaction that doesn't create a change output.

That means you don't have non-private coins in your wallet after the payment, and you don't need to do another coinjoin round.

Yet another blockspace savings technology in Wasabi!

https://blog.wasabiwallet.io/only-wasabi-privacy-warnings/


Financial tyranny index by nostr:npub1mftv2j67vayavkks8rqev3u8jjhefe86tf80msstfxvpunk9vmps6prkl3
https://github.com/vexl-it/fti
#cbdc #tyranny #fiatworld https://image.nostr.build/7c2695158652c344ada63224d0486f5bcf1f7d3731a799008a521af7d4c5f11d.jpg


SEC-01: A Pirate Ship Full of Guinea Pigs

A short review of the 1st Sovereign Engineering Cohort

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

Oh my, what a ride. Where do I even begin? A wise man once said that the best
place to begin is at the beginning. So I'll try to do just that.

## SEC-01: The Beginning

I don't even know how it all started anymore, but I know for a fact that it was
Martijn's idea. And the idea was this: let's do something like a Bitcoin Academy
on Madeira!

"Neat," I thought. "Let's do it," André said. "Let's fuck shit up and do a nostr
thing instead," Pablo remarked. "But it must have a pirate theme," was my only
objection. "Deal."

"Deal."

## SEC-01: What's the Big Deal?

I don't think we did anything special. What we're trying to do, and what I think
we managed to do, is to get the right people together at the right time. We knew
from the get-go that we didn't know what we were doing. And we decided that
that's okay.

We decided that that's okay because any explorative adventure is by definition
unknown. And that's what the [Sovereign Engineering Cohort](https://sovereignengineering.io/#sec) was and still
is: an explorative adventure.

So I guess the big deal was that we were knowingly venturing into the unknown.
And 21 people signed up for it. Willingly.

That's a big deal.

## SEC-01: The Crew

Every pirate ship needs a crew. We [started as four](https://sovereignengineering.io/#crew): Martijn, André,
Pablo, and myself.  We invited three more: Paul, Ben, and Tony—our [North Star
team](https://sovereignengineering.io/2023/10/18/welcoming-mutiny-wallet-as-the-1st-sovereign-engineering-north-star.html)
for SEC-01. And then we invited [21 more](https://sovereignengineering.io/2023/11/30/meet-the-1st-cohort.html)
to board the ship.

Our 21 participants were people with vastly different backgrounds, from vastly
different countries, having vastly different ideas about how Bitcoin, Lightning,
and nostr could transform the internet, and the world at large. One thing that
everyone had in common was a deep-seated dissatisfaction with the status quo.
Everyone knew and still knows that large parts of the internet are broken. And
everyone felt that there's something we can do about it to fix it.

We talked a lot about what it means to build it right. Or at least what it means
to build it wrong.

One goal we had in mind was to learn from each other so that we may not repeat
all the mistakes that we made in the past. And I think it started working
immediately.

## SEC-01: The First Week

We started the program with a brief introduction about what we had in mind for
the eight weeks, as well as an introduction of [the
crew](https://sovereignengineering.io/#crew), [the
participants](https://sovereignengineering.io/#participants), and what everyone
was working on.

One thing that we try to focus on is what I will call the loop. The loop is what
I consider the Cornerstone of the Sovereign Engineering Cohort, as it neatly
summarizes the main idea of the program.

![](https://sovereignengineering.io/assets/images/sec-loop.jpg)

The idea is simple: you talk about what you're going to build, you build it, and
you show it to everyone. Rinse and repeat. Every week. For two months.

## SEC-01: Distributed Cognition

I am convinced that the problems that we are facing cannot be solved by
traditional means. More importantly, they cannot be solved by a lone wolf.
"[Given enough eyeballs, all bugs are
shallow.](https://en.wikipedia.org/wiki/Linus%27s_Law)"

So the question becomes: how do we get enough eyeballs looking at the right
thing? And more than that: how do we get them to look at problems from the right
angle, inhabiting the right perspective?

## SEC-01: Walking the Walk

Looking at things it's necessary but not sufficient. If you want to solve deep
problems you have to think about them deeply. So again, the question becomes:
how do we create an environment that facilitates and allows for deep
conversations?

I think the Ancients were onto something when they came together at the
gymnasium to discuss deep problems, have deep conversations, and—pardon the
pun—hash things out. It strikes me as odd that all the paintings of these times
show people not only talking but walking.

![](https://sovereignengineering.io/assets/images/school-of-athens.jpg)

A lot of people who figured out solutions to hard problems in the past enjoyed
an occasional stroll through the park. Not alone, but with company. There's
something about walking and talking that really gets the brain juices flowing.
From [Aristotle](https://en.wikipedia.org/wiki/Peripatetic_school) to
[Einstein](https://www.bbc.com/future/article/20170612-what-you-can-learn-from-einsteins-quirky-habits), the greats all intuitively figured out
that walking facilitates proper talking, and proper talking facilitates proper
thinking. Someone from the cohort remarked, "Left foot right foot; left brain
right brain." I believe it.

So that's what we did. Not only did we talk the talk, but we also walked the
walk. Once a week. Granted, not all of our walks were perfect or magical, but
many of them were. And a lot of stuff got figured out. And once you've got stuff
figured out, it's almost trivial to build it. Figuring it out is the hard part.

## SEC-01: What Came out of It

Some of you might have been fortunate enough to experience the final Demo Day of
SEC-01, held on the last day of [Bitcoin Atlantis][BA]. It took us three hours to show
what came out of it, failing demos and all. There's so much stuff that I had to
put the list in a separate post, aptly titled:

- "[**SEC-01: What Came out of It**](https://sovereignengineering.io/2024/03/19/what-came-out-of-SEC-01.html)"

Vibes were high, the room was packed, and while most of the
presentations kinda sucked, everyone tried their best to paint a picture of what
they have been working on or what problems they cared about most.

And that's what we cared about most: Getting the people together that care, and
providing an environment where they are encouraged to collaborate and discuss
freely.

We strongly believe that the pie is big enough for us all. Now it's not the time
to think about competition. Now is the time to focus on collaboration. We
believe that Bitcoin is a move from zero-sum to positive-sum thinking. We
believe that we should aim at win-win-win: good for you, good for me, good for
us and the environment we’re embedded in.

## SEC-02: What's Ahead

The space that has opened up by Bitcoin, nostr, and other freedom tech is vast.
We have barely scratched the surface.

The goal of the Sovereign Engineering Cohorts is to scratch the surface as
properly as we know how. So we're going to do it again. In May. Same recipe,
same crew, different participants. **The focus will be on P2P markets and
exchange.**

We're not here to make any promises. I want to repeat once more what we've
[mentioned in the
past](https://sovereignengineering.io/2023/10/23/applications-to-SEC-01-closing-soon.html):
*"Men wanted for hazardous journey. ~~Low~~ No wages, bitter cold, long hours of
complete darkness. Safe return doubtful. Honour and recognition in event of
success."*

But it's going to be fun. Maybe.

Sign up, and let's find out:
[https://sovereignengineering.typeform.com/SEC02][TF]

[TF]: https://sovereignengineering.typeform.com/SEC02
[BA]: https://bitcoinatlantis.com/


Yes.


Assume you have a utxo, and want to spend it privately.

If you do only single user transactions, you would need probably 50 transactions, creating 200 coins, and spending 180 of them, that's a lot of blockspace, and you didn't create much ambiguity of where the und money went.

On the other hand, with WabiSabi it might give you sufficient privacy to make 1 single transaction, spending 1 coin and creating 5 coins. That's a lot less blockspace.


I mean, if you only use lightning to open and close channels, but you don't make any off chain channel state updates, then you used more blockspace than otherwise.


Wabisabi is basically the only blockchain scaling improvement recently.

Lightning and ecash is not blockchain tech.


✨💎 Another Cashu Gem

Paid file upload service which can't link uploads to payments (i.e. works without user accounts) concept by  nostr:npub1rach342hnt3wa0qfqk0pey0exs2drcxfc0azs8eurwnee9vu64vs834atg.

"Add an ecash wallet to the backend and use the "X-Cashu" header to send payments with your file uploads!"

https://m.primal.net/Hkpi.mp4


This guide introduces Debifi, a Bitcoin-backed lending platform that advocates for financial independence by enabling users to leverage their Bitcoin holdings without selling them. It highlights Debifi's non-custodial lending approach, utilizing Bitcoin as super collateral in a secure and transparent manner. The borrowing process is explained through a detailed six-step guide, starting with app download and account setup, emphasizing security measures such as PIN and Two-Factor Authentication (2FA), and concluding with loan acquisition through depositing Bitcoin as collateral.

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

**
## How to Get Started with Debifi: A Guide for Borrowers
**

Welcome to Debifi, where the phrase **“Own your money**” takes a new meaning. We're a movement towards financial freedom and independence, leveraging Bitcoin as a super collateral. Our services are designed to let you **"Never sell. Borrow,"** ensuring you can leverage your Bitcoin holdings without parting with your assets.

As the leading platform in non-custodial, Bitcoin-backed lending, we're here to guide you through every step of the borrowing process. Whether you're new to Debifi or looking to deepen your understanding of our services, this guide will provide you with all the information you need to securely and efficiently use our platform.

#### **How Debifi Works: From Escrow Creation to Loan Repayment**

**
###### Escrow Creation
**
Taking out a loan with Debifi means your Bitcoin collateral is securely held in a ¾ multisig escrow, ensuring it remains dedicated solely to securing your loan. This approach provides a transparent and safe lending experience.

###### **Loan Origination and Repayment**

The Debifi App is at the heart of our secure loan origination process, facilitating a seamless signing process. When it's time to repay your loan, the process is direct and transparent, with your Bitcoin collateral returned upon successful repayment.

#### **How to Get Started with Debifi: Your 6-Step Guide to Borrowing**

This step-by-step guide will walk you through the process of setting up your account and initiating your first loan, ensuring a smooth and secure experience.

****Step 1: ***Download the App & Create Your Account***

The first step to unlocking the power of Debifi is to download our app from debifi.com/app, currently only available for Android users. After installation, create an account using your email. This is crucial for establishing a secure foundation for your transactions on Debifi.

*Key Point: Secure your account by setting up a strong PIN code and enabling Two-Factor Authentication (2FA), adding an extra layer of security to your account.*

https://image.nostr.build/006394998437e5c79d842efcf5acab36c5380fec54c7025c3e27da545645155d.png

****Step 2: ***Secure Your Account & Back Up Your Seed Phrase***

Security is our top priority. Following your account creation, you'll be prompted to secure your account with a PIN code and set up 2FA. Next, back up your 12-word seed phrase by writing it down on paper and storing it securely. This phrase is vital for account recovery and maintaining control over your funds.

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

https://image.nostr.build/5d9ce63dee70c899a7e4a9d1207e18f53e1c97635ec2e3ac17504d8303b9e0f9.png

 https://image.nostr.build/4cc1fc9bc64bb092ee653167ecca9a1d0d91774980120341251431198b8385e2.png

****Step 3: ***Link Your Device & Prepare for Web Interaction***

With your account secured, the next step involves linking your device to your account with the 2FA code. This ensures a secure connection between the Debifi mobile app and our web platform, facilitating a seamless interaction with loan offers and account management.

https://image.nostr.build/96b03585b8708a0eb344540d9fec188fc7fd22010a536e9402c18fca473b8459.png

****Step 4: ***Navigate to Our Website & Explore Loan Offers***

Once your device is linked, visit https://debifi.com/ to explore available loan offers. Our platform connects you with institutional-grade liquidity, offering a range of options to suit your needs.

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

****Step 5: ***Initiate the Loan Process***

After selecting a loan offer that meets your requirements, use the Debifi app to initiate the loan process. This involves signing the loan contract securely through the app, providing your public keys, and establishing a multisig escrow for your Bitcoin collateral, enhancing the security of your transaction.

https://image.nostr.build/2d5264cfbf40ed4f7b3d09a020e67117375bf33012e5009a33b978b0db1588a6.png

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

****Step 6: ***Deposit Collateral & Receive Your Funds***

The final step is to deposit your Bitcoin collateral into the designated multisig escrow system. This action finalizes the loan transaction, ensuring your collateral is securely locked away. Upon confirmation of your deposit, the lender will disburse the loan amount to your specified address, completing the transaction and granting you access to the funds you need.

https://image.nostr.build/79cd3fb3a491c573d07d911bc846242342accebd1f80a8b779ac108210324a7a.png

https://image.nostr.build/8ee507d022aeaee1d893b6dc32a7bfb61d82af87c7f62728267fc2e92086e5e1.png

Debifi stands on the principles of security, transparency, and innovation. We are here to provide a unique lending experience. Navigate your financial path with confidence and insight.

Explore what Debifi has to offer. Download the Debifi app and look into our loan options, you're not just taking steps towards financial flexibility; you're also joining a community that values the principle of Bitcoin in shaping a more empowered future.

It’s about more than just loans; it’s about being part of a movement that prioritizes control over your assets and smart financial planning. At Debifi, we're excited to support you as you explore the possibilities of Bitcoin-backed lending.


A new release is now available: 🔄 Tor Browser 13.0.12 includes important security updates to Firefox & removes the Onion-Location option to automatically prioritize .onion sites when known. ⏩❌🧅 Learn more: https://blog.torproject.org/new-release-tor-browser-13012/


Yeah, decentralization is bloody difficult...


Shoot me a DM.


There's a single company as service provider for this feature, so you'd be employed there, with no meaningful liability.


Here's a long podcast about it
https://www.youtube.com/watch?v=WVJAH6tZnx0

Basically, you tell a company what you want, the company buys it as intermediary, and you then buy the good from the company with bicoin directly.

It's a simple chat interface, but with Wasabi's Tor magic as a layer of protection.

It works great for items > 1000$, like computers, cars, flights and hotels etc.


Lots of demand for Wasabi's Buy Anything Button, we need more concierge agents to handle all the requests.

If you're looking for a job to stack more sats, this is it!


It looks Chris Belcher’s Teleport (coinswap) project has been forked and is being developed again. https://github.com/utxo-teleport/teleport-transactions #Bitcoin #privacy


No, you'll use coinjoin to deposit onchain into the ecash mint, and the mint will use coinjoin for private batching of deposit payouts.

Coinjoin is inherently a blockchain privacy and scaling improvement, and thus it will be around for as long as the blockchain is.

Second layers and custodians will handle way more transactions than the blockchain though.


Arbitrary derivative anonymous bearer assets settled for in bitcoin.

I mean, this hole nutty thing is starting to be just very ridiculous...

Cypherpunk future is now.


Finally I can share my evil plan to really stir up the pot.

Thank you HRF!

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

nostr:note1427apc7j7es8s5te9n6us9jt4fnpdze2h7g7xmnnnw9ye309jwds7kdre5


💥 BitcoinMints.com 💥

We just launched the first place to list and review Cashu mints leveraging #nostr as the discoverability and identity layer.

https://BitcoinMints.com

Cashu is an ecash protocol that will enable https://makeprisms.com users to send millions of #bitcoin payments with one click.

BitcoinMints.com is a Nostr client that uses NIP-87 to publish and review mints.

$boost


## The Lurking Wife Quest

The price of Bitcoin went up and everyone got girlfriends! Your girlfriend is a loving partner and a passionate Bitcoiner, but she doesn’t trust you. She verifies.

You are running errands after work and your girlfriend is suspicious you might break her rules while she’s not around: No drinking, no gambling, and no cheating! She knows one of the UTXOs in your wallet and is watching your every move, will your relationship survive the privacy problems of a public blockchain?

https://wasabigame.creativeagent.hu/

nostr:nevent1qqswkeevx99tdhv7f27cz4qk9q00qenyfh4uvehjyr24ljd29wszazgpremhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtmsdac82mrpwgpzpdlddzcx9hntfgfw28749pwpu8sw6rj39rx6jw43rdq4pd276vhuqvzqqqqqqyh2k6za


## The Lurking Wife Quest

The price of Bitcoin went up and everyone got girlfriends! Your girlfriend is a loving partner and a passionate Bitcoiner, but she doesn’t trust you. She verifies.

You are running errands after work and your girlfriend is suspicious you might break her rules while she’s not around: No drinking, no gambling, and no cheating! She knows one of the UTXOs in your wallet and is watching your every move, will your relationship survive the privacy problems of a public blockchain?

nostr:nevent1qqswkeevx99tdhv7f27cz4qk9q00qenyfh4uvehjyr24ljd29wszazgpremhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtmsdac82mrpwgpzpdlddzcx9hntfgfw28749pwpu8sw6rj39rx6jw43rdq4pd276vhuqvzqqqqqqyh2k6za


Lurking Wife Quest

Learn about utxo management and Wasabi's address labeling with this interactive game!

https://wasabigame.creativeagent.hu/


Find out how much sats you pay for mining and coordination for Wabisabi coinjoin!

https://coinjoins.org/calculator


Wallet loading performance improvement from Wasabi Wallet v2.0.5 to v2.0.6!

Faster than faster than fast.

https://video.nostr.build/4a55fbbeb45155d0bb371e68b72ae6f2b82cd1e05832a34060a9d87593bf26c2.mp4


I don't think the schedule is finalized yet...


After a long wait, we’re back and couldn’t be more excited 🥳

Plebstr has transformed into Openvibe, but our goal remains the same: to keep all the things you love about Plebstr while opening up even more ways to connect with people across the entire Open Social Space.
We’ve just released the first beta version to give you a sneak peek of what’s coming.

Just download Openvibe or update your Plebstr app. We’d love to hear what do you think! 🐙
 https://nostrcheck.me/media/0fe0b18b4dbf0e0aa40fcd47209b2a49b3431fc453b460efcf45ca0bd16bd6ac/940e70f1fab96921d828e1d7df77c260a60cd311d7d95ba82da83d5847c22ea9.webp https://nostrcheck.me/media/0fe0b18b4dbf0e0aa40fcd47209b2a49b3431fc453b460efcf45ca0bd16bd6ac/3f347a4b8ce006abe4111c2db78ca5b86c10c9c5441f773c1beb14544675a21a.webp https://nostrcheck.me/media/0fe0b18b4dbf0e0aa40fcd47209b2a49b3431fc453b460efcf45ca0bd16bd6ac/46c9d3f1487f15b9a366e8fe78e66b224029dd671e2e75cfa9353048bd879968.webp


The blyss when your project doesn't require changes to Bitcoin.


The expo ticket has access to two stages, the English second stage, and the Czech Main stage, probably also some workshop space.

The regular ticket gets you access to the big main stage.

The VIP ticket gets you the VIP stage with some few additional talks. But the food there is INSANELY GOOD, seriously, by far the best dining experience at any conference so far.


Looking forward to hanging out!


Socialists want to either murder us or cancel us (digital murder)

And we want socialists to bring us our order of 🥩

We are not the same...


Read Juraj's writings, they're great!

nostr:nevent1qqsqd60mf7x2a4yqgxt6qgnp3c9l5jgvqll22rsd8fzvp5w6nktfzsspp4mhxue69uhkummn9ekx7mqzyrmvf8sm0dcsdvn63qj5k9h7urvrtly2egwm0r32pju68aufcsdvjqcyqqqqqqgejc2az


Security in depth is bloody difficult...


Data cannot be owned.
Information is non-scarce, and thus private property is not necessary.


Guess what? 10 000 amazing people, who value buying and selling Bitcoin with privacy now use Vexl! 🖤

But still a lot more to accomplish. Those are rookie numbers 🫡
https://m.primal.net/HmEW.png


I have to do nothing, Wasabi coinjoins it automatically.


Yes, look at this recent Wasabi coinjoin, they do get quite large and are can be fingerprinted easily.

It's the same with encryption, you know that there is some encrypted message, but you have no clue what's the actual content.

https://mempool.space/tx/4988e9aaf73e9581a0739c9a49dbd737052e211dce00e1c439a1c813d871ea82


There's new rpc commands paymentincoinjoin and coinjoinwalletsweep which makes sending to cold storage A LOT more private.

Hopefully soon this will also be possible in the user interface.


Wasabi is pretty simple to use, and protects your privacy by default, so there's not much explanation needed.

The results speak for itself, look at this coinjoin and try to find out which inputs and outputs belong to the same user:

https://mempool.space/tx/4988e9aaf73e9581a0739c9a49dbd737052e211dce00e1c439a1c813d871ea82

Let me know if you have any questions!


It's not that difficult after all...


Nice!


## Smart Randomness

Skipping coinjoin rounds based on the fee rate

Latest Wasabi Wallet Blog by nostr:npub1pww7030g95nv9ptfpgfu69jpfxj6pm33xxueztsupwekce45wx4sm6en60 exploring the privacy improvements of the latest release!

https://blog.wasabiwallet.io/smart-randomness-skipping-coinjoin-rounds-based-on-fee-rate/


Cypherpunks 🖤 nostr:npub167n5w6cj2wseqtmk26zllc7n28uv9c4vw28k2kht206vnghe5a7stgzu3r

Once again our CEO Lea is joining forces with nostr:npub1m2mvvpjugwdehtaskrcl7ksvdqnnhnjur9v6g9v266nss504q7mqvlr8p9 nostr:npub1klkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qulx3vt & Stick, hosting the coolest side event of BTCPrague!

Mark your calendar: Thu 13th of June, 2024 and secure your spot via
https://pay.cypherpunk.today/apps/4LEEvtqY8UMnuB7y5wCmjvi2tXy3/crowdfund
https://m.primal.net/HmEG.jpg


nostr:npub1m2mvvpjugwdehtaskrcl7ksvdqnnhnjur9v6g9v266nss504q7mqvlr8p9 knows how to tickle the robot just right.

And just to prove the point, here's the other insanely great pieces:
 https://image.nostr.build/ef8c9c55fc6e48d9cee8423fb03d6a33314460d6d1b750b73032998488b0fbfb.jpg
 https://image.nostr.build/ab52acac96e9773cbbdb6ca753ceb3584cf4549ecc32a90845621b2d6f24b1e2.jpg
 https://image.nostr.build/251657bc994c023c95bbef34565010ce3fa3c1fd407dfefbb872d6d5c944ecd7.jpg
 https://image.nostr.build/317ede196b0d745b9c696347c2462864ed5bc919c2639fba1e80ebd753dbc0cb.jpg
 https://image.nostr.build/609efa3a33c48a443f831817649e89ac2f63913c11d9eec7103c8e3585af811d.jpg


"I cleared the space for the younger generation. But no one came..."
  ~ Anonymous cypherpunk, 2024

https://pay.cypherpunk.today/apps/4LEEvtqY8UMnuB7y5wCmjvi2tXy3/crowdfund


# Quo Vadis, Cypherpunk?
 https://nostrcheck.me/media/b7ed68b062de6b4a12e51fd5285c1e1e0ed0e5128cda93ab11b4150b55ed32fc/1f8c9126f0edc3d59ffa4650b551075fd156b81b612ac789ba469fb47dd6c607.webp

### Fellow Cypherpunks attending BTCPrague 2024!

This year, we are doing a second edition of the Cypherpunk Meetup, independently organized official side event of BTCPrague.

You can look forward to a better venue, new guests, great networking and even some surprises!

But let's ask the hard questions first: Quo Vadis, Cypherpunk?

## Manifesto

#### "I cleared the space for the younger generation. But no one came..." - Anonymous cypherpunk, 2024

The founding fathers of the cypherpunk movement had quite wild predictions for the Y2K+: Anonymous communication and ubiquitous encryption should have led to decentralization of power, freed markets and individual liberty. Looking realistically at today's world - a world in which surveillance is totally normalized and we're stuck between being dominated by megacorps and governments - we fucked up big time, even though we created islands of liberty for the few of us that understood what these technologies are for.

Bitcoin is an exemption and an exceptional success of their story, but looking at its current development, we come to argue that we're now vulnerable to failing even there. The crowds are coming again and they don't even know why they need anonymous money. But wait, do we know?

Once “rebels with a cause” turned into “grandmas with ETFs” and “garage economists with a Twitter account”.

Where do we go from here? What can we do? Is this what cypherpunk is now? Are we bitcoiners just because we can, or can we still look for and successfully find a purpose not lost from the founders' vision?

Emptiness of purpose can be easily hijacked. Looking at the past of the movement, experiencing its presence and foreseeing its future we ask ourselves the question:

Is the movement still relevant?

### Date & place

Thu 13th of June

### Venue

TBA soon (Looking for something better than last year)

### Agenda

6PM - doors
7PM - talks start
8PM - networking & beers
9PM - surprise!

### Speakers

Lea from Vexl, Juraj Bednar, Max Hillebrand from Wasabi Wallet, Uncle Rockstar from BTCPay, Calle from Cashu and more! The format will be lightning talks - don't worry, we won't overwhelm you with lenghty speeches.

### Crowdfunding

We are just enthusiasts wanting this event to happen. We are crowdfunding the cost of the room and rental of the technical equipment. If there are any money left over, we will get some drinks.

If you paid the invoice, you are in. There are no automatic e-mail confirmations. If you want the book, make sure to provide a valid e-mail address. If you want to reach out with a question, please first read this whole page, then you can e-mail us.

### Frequently Asked Questions

#### I did not receive confirmation e-mail after paying

Yes, this is OK. There are no automatic e-mail confirmations, if you paid the invoice, you are in.

#### Why is there a higher price if I choose on-chain Bitcoin payment?

Buying tickets with on-chain transactions is expensive - both for you and for us to spend the coins. The additional fee covers mining fees to swap to lightning. If you don't like it, start using Lightning and pay for the ticket in Lightning. It will be cheaper for you since the first transaction. Juraj has made a super quick intro.

#### Is this event only for visitors of BTCPrague?

Nope. Anyone can join.

https://pay.cypherpunk.today/apps/4LEEvtqY8UMnuB7y5wCmjvi2tXy3/crowdfund

nostr:nevent1qqs9upxq354x0sr2ma5lsxr2q0pamwlutef2nchlr3sgvhr5354yr5qppamhxue69uhkummnw3ezumt0d5pzpdlddzcx9hntfgfw28749pwpu8sw6rj39rx6jw43rdq4pd276vhuqvzqqqqqqyk57j9e


Quo Vadis, Cypherpunk?
Join us for the Cypherpunk meetup in Prague on Thursday 13th of June!

Just in case you needed another reason to go to nostr:npub167n5w6cj2wseqtmk26zllc7n28uv9c4vw28k2kht206vnghe5a7stgzu3r...
 https://nostrcheck.me/media/b7ed68b062de6b4a12e51fd5285c1e1e0ed0e5128cda93ab11b4150b55ed32fc/1f8c9126f0edc3d59ffa4650b551075fd156b81b612ac789ba469fb47dd6c607.webp

https://pay.cypherpunk.today/apps/4LEEvtqY8UMnuB7y5wCmjvi2tXy3/crowdfund


I'm just exploring, I don't remember half the details of the activation.

My original questions was more for channel updates and HTLCs. So the channel stays open on both chains, and then you make an update to one of them, do you need to take caution with the other channel?


A foundational large language model, kinda like chatgpt


Grok-1 weights are open source now.

https://x.ai/blog/grok-os


#asknostr


Both cooperative and uncooperative?


So, could you make separate htlcs for the same channel on both chains?


I wonder if Proton keeps the 2fa setup email address, which is required for every account...


If lightning were around back at the bcash hardfork, would the channel state of Bitcoin lightning pre-fork work also for the bcash chain after the fork?

I other words, is there something like replay protection for lightning?


Congrats on getting this out, great progress, thanks!


🚀 Exciting News Alert! 🚀

We're thrilled to announce the long-awaited launch of Bisq 2! 🎉

The latest version of our decentralized exchange platform is now live and available for download. Bisq 2 brings a host of new features, improvements, and enhancements to make your trading experience even better.

Ready to explore what's new?
Use the link provided below to download Bisq 2 today! Don't miss out on the opportunity to trade securely and anonymously on your own terms.

Let's revolutionize the world of decentralized finance together. See you on Bisq 2! 🌐

Read More about Bisq 2 here: https://bisq.wiki/Bisq_2

Download Bisq2 here: https://github.com/bisq-network/bisq2/releases/tag/v2.0.1

#bitcoin #btc #decentralized #nokyc #stacksats #nokyc #bisq #nostr #nigeria #china #india #turkey

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


Proper craftsmen get an instant follow.


Is it finally happening?


Ron Paul on privacy

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


Nobody knows how to make a pencil.

So why would you expect that anyone understands bitcoin?!

https://fee.org/resources/i-pencil/


Well, with this comment you just made a cryptographic signature over the hash of the letter.

I guess that means you're part of the club now.


NEW EPISODE OF NOSTROVIA

 nostr:npub1lunaq893u4hmtpvqxpk8hfmtkqmm7ggutdtnc4hyuux2skr4ttcqr827lj and I discuss the future of nostr and bitcoin, Stuart's project (satellite.earth), nostrocket, the Empire, the biosphere, aliens.

Stuart Bowman and I spent the last two months in Madeira as part of the first Sovereign Engineering Cohort and thought it would be a good idea to record one of our conversations for the podcast.

FOUNTAIN: https://fountain.fm/show/EHr7oroKVhkIAWNTGGRn

APPLE: https://podcasts.apple.com/hk/podcast/nostrovia-the-nostr-podcast/id1678531266?l=en

SPOTIFY: https://open.spotify.com/show/3FKrua9rST5DDKv0WeAqWn

RSS: https://anchor.fm/s/d8e8d5a4/podcast/rss

WEB: https://anchor.fm/nostrovia


Oh, is this a recent translation?


Awesome, thanks and keep up the good work!


How many total vulnerabilities have you now reported upstream?
Great work!


The judge just ruled from the bench.

CRAIG WRIGHT IS NOT SATOSHI NAKAMOTO

Further findings of fraud etc will come in the written judgment.

Welcome to law.


This is the way.


Bull market purchase idea with Wasabi's Buy Anything Button.

[yes, you get a license plate too]

https://www.blissmobil.com/


We’ve got a very ambitious roadmap for ZEUS this year.

If you’re a developer and interested in working with us on contract, we’d love to hear from you. Reach out! There’s a wide array of projects to work on.


Is anyone orangepilling https://nebula.tv/?


Provides a good setting for inspiring dreams!


I'm so insanely happy with the Wasabi contributors. The quality and quantity of their work is just mind-blowing. Such a team is unstoppable.


So what's the percentage of spends in scripts?


You'd know on the input side, and could get a percentage of spends at least.


Ever wondered what the true cost of printing $6 trillion is?

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


Does anyone know what percentage of Bitcoin is locked up with scripts vs pubkeys?
#AskNostr


But the three of us are having a blast!


How about you write moar perfect code faster, and just ship that instead of shit posting?


Sooo, announcing the announcement of an announcement instead?

Don't give me cypherpunk blue balls...


Damn!
And it's even remembered in the recently opened apps.

Thanks for the tip!


General #Android tip which also works in #GrapheneOS: You can split screen apps. I don't see people do it a lot but it's pretty awesome.

Go to your recent apps menu and tap the icon above the screenshot of the app from where it is left off and select "Split screen". The first choice goes at the top, so pick the one you want at the top first!

You can adjust the width of the apps too.
 https://image.nostr.build/839907ca356748f49d57203f14ae924a46d6e39975398eff08f0808a8b6b894d.jpg


I love my friends.

https://github.com/eu-digital-identity-wallet/eu-digital-identity-wallet/issues/1


The tldr, you're not bullish enough.

Enjoy the food!


You're comparing a base money bitcoin to an m3 fiat supply rate.

It's more accurate to compare bitcoin to the base money of fiat, cash and central bank reserves.
 https://nostrcheck.me/media/b7ed68b062de6b4a12e51fd5285c1e1e0ed0e5128cda93ab11b4150b55ed32fc/1a6acbb4712610c056b858e65949564140df4514ec6ebe1118d94c4b9e05c019.webp


Can't see job destruction as a result of AI.

I think a variation of Jenson's paradox applies, where instead of say, AI destroying the virtual assistant's role, or a junior developer role, it would instead make the costs of such services lower, and therefore more in demand.

More expected for existing roles, at lower prices, but a resultingly bigger scope of activity and net employment.


Both are great!


https://github.com/greenart7c3/Citrine

You can use citrine as a cache relay in nostrudel

https://nostrudel.ninja/#/relays/cache

For other clients for now you have to add it to your relay list


I'm not that comfortable with a third party launcher, not even sure if there are FOSS options, and as you say, they're likely not as well maintained as Graphene directly.

Thus an in-house launcher customizer would be much appreciated.


Satoshi and me is a wild piece of writing by nostr:npub1mz704n7dsaw3jcj3kr5le45n97tqughyt5lxe3yv3xy3025hv3dsp5tl8g

https://www.citadel21.com/satoshi-and-me


I don't care who Satoshi is.
I care about what Satoshi is.


idk, but the fact that nostr has all kinds of emoji reactions is really cool.


Like the gold bugs say - I don’t know the worth but I know the weight.


Cantillion fiat effect
Can't be long fiat effect


I don't care how much you value my sats.
I care about my absolute amount of sats.


Memory tagging is on by default, which uses ~3.25% memory

nostr:nevent1qqspgjl5t8ua39hqk7hxjlyw5cmzgdyfewnhswk9qjjkc8p4dq8nkgsppamhxue69uhkummnw3ezumt0d5pzps26tfjesmn6ksf5mm36hpf9fkjut49sfeutfutvs2phrykn25v9qvzqqqqqqymnf83c


Inflation is expropriation of life time.


Yes, I want to put as much as possible on a single home screen, thus the 7x7 grid would be very useful.


Love to see people create and sell stuff at bitcoin conferences.


Yeah, nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z this is an issue...


What if one out of many mints has rugpulled you and is insolvent?


You'd be on the wrong path if nobody is in the way.


That's why I still work on Bitcoin Privacy.


Isn't it 100%
1 Watt = 1 Watt


Fascinating, thanks!


Who doesn't like a surprise party?


Interesting, thanks!

Do you know when a RNG was first introduced?


That's awesome progress, thanks!


NEW NOSTR CLIENT ANNOUNCEMENT:

https://user-images.githubusercontent.com/99223753/223734919-ee5fc4d0-ee89-409c-a7c8-1848310bb92d.png

ONOSENDAI オノセンダイ
a cyberspace client for the one true metaverse: nostr

🌌 https://onosendai.tech 🌌 (hint: in alpha. desktop/android works best right now)

ONOSENDAI visualizes objects on the nostr protocol in an interactive 3D world referred to as 'cyberspace'.

⚡ Semantic Coordinate System (✅)

Each nostr note (kind 1) is assigned a 3D point in cyberspace based on the _meaning_ of its content using a 256-bit simhash. This unbiased algorithm maps all notes to a 3D universe you can explore.

⚡ Proof of Work for Localization of Constructs (wip🛠)

Placing 3D objects in Cyberspace is a self-evident necessity. Kind 10333 notes may be published with content set to a common 3D format to create public 3D visualizations. Proof of work can be utilized to mine the event ID hash which determines the coordinate location. Proof of work is the only way to claim cyberspace real estate.

⚡ Presence (wip🛠)

Ephemeral events could be used to *optionally* share your current position in cyberspace so that other users can visualize your movement and interact with you.

💡 Rationale

Cyberspace (in this context) is an early-internet trope from the 80s. It's an enthusiastic and naive speculation on the future of network-connected computers and how humans might use them. Ultimately, instead of interacting in 3D virtual spaces, humans ended up interacting via documents in web browsers which is much more practical and efficient than 3D visualizations.

Besides the problem of visualizing content, there are several more critical problems with the concept of cyberspace that are rarely (if ever) addressed in fiction:

- Who hosts it?
- Who decides how it looks?
- Who owns the content?
- Who makes the rules?
- Who assigns the space?
- Who controls it?

These questions are answered satisfactorily in the era of bitcoin and nostr:

- Who hosts it? nostr relays
- Who decides how it looks? nostr clients like ONOSENDAI
- Who owns the content? users cryptographically own their content
- Who makes the rules? open source consensus
- Who assigns the space? an impartial algorithm + proof of work
- Who controls it? 🖕NOBODY🖕

In my opinion, it is only in the context of bitcoin and nostr that something like cyberspace could make sense. Without the decentralized properties of nostr and bitcoin, cyberspace is just another 3D game owned by a company. However, when cyberspace is decentralized, enforces property rights, responds to proof of work, and enables instant value transfer, it becomes something entirely different.

Because cyberspace inherits all of these unique properties from nostr and because value transfer can be executed in cyberspace through bitcoin lightning, I argue that it is time for humanity to take another look at this dusty old concept and start exploring it with renewed interest.

I, unlike many metaverse enthusiasts, have a strong moral preference for reality over illusion. The idealized metaverse or cyberspace worlds that Meta and the like want to build are nothing more than a drug used to extract resources from miserable VR-goggled souls. That is the fiat version of cyberspace and it sucks. I am not interested in building clever simulations that seek to replace reality. I want to build tools that enable people to connect and be more productive. I want to open up new channels for communication, innovation, and human flourishing in reality.

Cyberspace is a new way to visualize the new paradigm for digital communication and property. It is wholly based around cryptography and digital ownership. If not for these things, cyberspace would be irrelevant.

A cyberspace built on decentralized protocols and sound money — nostr and bitcoin — has the potential to be something innovative, healthy, and ultimately productive for humanity. Cyberspace can be something where wealth is not extracted but rather generated by work and free markets. Cyberspace could be a new medium of connection built on sound principles that can enable humanity to do new things not previously dreamed of.

If it were not for the profound inventions of bitcoin and nostr, these aspirations would be nothing but ludicrous and delusional. In fact, any metaverse or cyberspace built outside of the context of bitcoin and nostr are delusional at best and Machiavellian at worst. Spoiler: it's the latter in most cases. But we have the opportunity to build something better. We have the winning hand. Let's make it happen.

Thanks for coming to my TED talk. Let's build. Read lots more and contribute at https://github.com/arkin0x/ONOSENDAI

Made with love posthaste,
arkinox

PS - I'd rather have reposts than zaps! Tell your friends! Thank you! 💜

https://user-images.githubusercontent.com/99223753/223145715-31174a68-9bc5-4c06-abb2-5f3a1e1352a6.mp4


Nostr is the discoverability layer

https://github.com/nostr-protocol/nips/pull/1110


Yes!

Lift the degen gambling off the chain!


Atomic multi-moneywarehouse withdrawals.

Holy shit.

This never even crossed my mind.

Reason number 71680 on why bitcoin fixes ecash!


✨ Multinuteral payments – Pay a single Lightning invoice from Ecash balances on multiple Cashu mints.

We use Lightning multi-path payments (MPP) to achieve atomicity.

This has wild implications for UX and privacy and is a significant breakthrough for Cashu.

Most Cashu wallets have multiple small ecash balances across mints to minimize the custodial risk.

Paying a large LN invoice, however, was a pain. Amounts larger than any of your ecash balances required a multi-mint swap first (swap ecash across mints via LN).

Not anymore!

Instead of one big LN payment, wallets could send multiple small ones from a dozen different mints all running their own LN node.

Either all payments succeed, or all fail. The mints don't communicate with each other. Receiver doesn't notice anything.

Imagine the beauty of this.

This eliminates the need for inter-mint coin control almost entirely. Wallets could show the user one unified balance across all mints and handle it all hidden away from the user.

You simply scan an invoice and an orchestra of Ecash mints and Lightning nodes begin their play.

This is yet another cool example of how ecash can significantly improve the safety and security of custodial Lightning wallets.

The deep integration of Cashu with Lightning makes this possible. And we have more ideas.

https://m.primal.net/HiqI.mp4


Yeah, I was wondering if it's actually true...


Very close to having a local llm like mistral embedded in damus notedeck. It will be able to summarize your nostr feed. All local AI. This is so cool.


nostr:npub1c9d95evcdeatgy6dacats5j5mfw96jcyu79579kg9qm3jtf42xzs07sqfm in the latest Graphene update the icon size of the app list is larger, now there's more scrolling required.

Any plans on making the app list and home screen a grid of 7 wide?


Investing your bitcoin into debt and equity with the goal of earning more bitcoin in the future is a sign of LOW time preference.

nostr:nevent1qqsyxdla0nyx8du9uyld6f7u6mxtsdgfqu2aevq3d2s752ee8axx0wspr3mhxue69uhkummnw3ezumt4w35ku7thv9kxcet59e3k7mgzyzm7669svt0xkjsju50a22zurc0qa589z2xd4yatzx6p2z64a5e0cqcyqqqqqqghh48se


Holding bitcoin is a sign of HIGH time preference.


With a tor exit node, other people route their internet traffic through other people's computer, and the last hop is yours. So other people use your IP address to browse the web and use applications. Now when an adversary like your ISP looks at which websites get visited from your IP, they're not sure if it's actually you, or someone else doing the browsing.

Of course there's a risk that some naughty corners of the web get visited that you don't want to associate with.


Running a tor exit node at home gives you great cover traffic when browsing the clear net.


Thanks for keeping us up to date with these indepth writeups!


#GrapheneOS: #Google has awarded bounties of $5000, $3000 and $250 for our 3 vulnerability reports related to physical data extraction attack vectors. Both $5000 and $3000 issues are being exploited in the wild. $250 bounty is for a minor issue we found while doing general USB hardening work.

Most serious issue is the one with a $3000 bounty. We provided proof of in the wild exploitation and a proposal for preventing exploiting the class of vulnerabilities which is being implemented. For the one they're awarding $5000, we weren't sure they'd even consider it a bug.

The most serious issue is likely only getting $3000 because we do not know the specific bug being exploited. It was classified a low quality report, not because we did a bad job but because we don't have that info. We did provide a way to prevent getting data by exploiting it.

Our proposal for preventing getting data by exploiting the main issue should ship as a Pixel firmware update next month and the feature will become one of our baseline hardware requirements. It's already harder to use it with GrapheneOS and we've made major recent improvements.

Our recent improvements:

1) New USB-C port control setting integrated into the USB-C controller driver to disable USB at a hardware level. It will become "Charging-only when locked, except before first unlock" by default" soon. Shipped in 2024022600: https://grapheneos.org/releases#2024022600

2) We reimplemented our auto-reboot feature with a more hardened implemented which can't be bypassed by crashing system processes. This starts a timer when the device is locked which reboots unless it's successfully unlocked first. Shipped in 2024011300: https://grapheneos.org/releases#2024011300

3) We reduced the default auto-reboot timer from 72 hours to 18 hours. This also shipped in 2024011300. 18 hours is enough that users don't encounter it in practice as long as they unlock their phone a couple times per day. Users who need max security can use 10 minutes.

4) We run a full compacting garbage collection in SystemUI and system_server when the device is locked. Android already does this after unlock to clear credentials. Goes well with our kernel zero-on-free since it zeroes the data. Shipped in 2024020500:
 https://grapheneos.org/releases#2024020500.

Our main proposal should ship for the Pixel firmware in April, resulting in the firmware's fastboot mode fully clearing all of the device's regular memory before enabling USB. We could implement the same thing for the OS to make sure there's no data left from an unclean reboot.

Forensic companies keep misrepresenting adding support for extracting data from GrapheneOS via ADB based on a user providing lock method as being something more in their marketing. This is start of our response. We'll be pushing for much bigger changes for Android and Pixels.

We fully intend to make the same proposals to other Android OEMs like Samsung. We're starting with Pixels because they're the devices we use due to their high level of security. We're also going to begin advocating for big changes like encrypted memory and funding PoC attacks.

We've been working on a duress PIN/password feature for a while that's nearly ready to ship. It's taking so long because we had to prevent bypasses impacting existing panic / duress wipe apps and OS features. We also decided to do the USB-C control and auto-reboot features first.

Since 2016, we've planned to support adding a PIN as a 2nd factor for fingerprint unlock. A new contributor has started working on this feature. We'll get it done after duress PIN/password. This will allow using passphrase primary unlock with fingerprint+PIN secondary unlock.


Correct!

It just blows my mind that bitcoin even works without it.


A bitcoin full node does not use a random number generator or encryption.


New BTCTKVR with Erik Voskuil, that's always a must listen.

nostr:npub12qz56plzehejkyp4waaannmnny4y4c30j8q55a3wlk49haslga2snypdx8

https://pca.st/episode/ecb541d9-3c91-4e7a-b171-c01cb30614e3


🟧🟦🟪 DLCVM 🟪🟦🟧

Generalised, Unboundedly Scalable Computation on Bitcoin

https://dlcvm.tiiny.site/


The money was just the beginning.


With WasabiWallet.io it's not difficult at all. Just receive, wait, and spend, knowing that all the privacy is taken care of by default.


coinjoins.org has the history of the tech, and explains every protocol and implementation.


Correct. The Wasabi client assumes that the backend coordinator is malicious and spying. The client uses sophisticated privacy tech like tor, block filters, and wabisabi, to protect the user against any third party. The coordinator does not know how many users there are, which inputs belong to the same user, which inputs belong to which outputs, and which outputs belong to the same user. The coordinator also doesn't learn about the users xpub or IP address, and for each api request the client uses a new tor identity (which is why just a VPN doesn't work).

The only information that the coordinator learns is which individual address is registering to the coinjoin.

And therefore the only thing you have to trust the coordinator with, is uptime, to provide you the service. He can for whatever reason deny any specific address access rights to the coinjoin api.

I think those trust assumptions are fine, as anyone can easily spin up a coordinator.

And the fact that it's a centralized system brings HUGE efficiency improvements. A much larger group of people can successfully coordinate through the central server, and therefore the resulting onchain privacy is substantially larger, while requiring a lot less block space.


Checkout coinjoins.org on how to protect your privacy while not giving away control of your private keys.


What a trip.


It's happening ~ 3 times a year, the second cohort is this may and june.


The sovereign engineering cohort #soveng was a wild adventure.

The officially organized schedule was very chill, just two days per week with a social gathering, demo day and BBQ.

But we didn't come here of an official schedule. We gathered for companionship, conversation, and support.

It would be boring as fuck if we were wrestling with our tasks alone. You can't do it alone. You don't want to do it alone. The feeling of like minded individuals standing shoulder to shoulder against tyranny and towards liberty is ineffable.

That's why each of our projects has advanced substantially during this time, and numerous new projects have been shaped into existence.

Come join us.
We got shit to build.


The amount of progress since the lightning conference is insanely mind-blowing.

We're winning so hard.


I can concur, it was amazing.


The new donation notification is awesome!


Well, you already kinda trust the open timestamp server, so I guess adding mempool.space is fine.


#Amethyst v0.85.0: Edit away

Adds support for post edits, post forks, pull requests, open timestamps, git repositories, issues, patches and replies, wiki pages and some medical data.

New Additions:
- Adds post editing (NIP-37, kind: 1010)
- Adds edit proposals and reviews
- Adds embedded events as NIP-19 uris
- Adds Open Timestamp attestations (NIP03, kind: 1040)
- Adds decentralized Wiki pages (kind 30818)
- Adds NIP-34: Git repositories (kind 30617), patches (kind 1617), issues (kind 1621) and replies (kind 1622).
- Adds rendering support for some FHIR payloads (kind 82).
- Adds early support for Kind1 forks.
- Sets zap splits automatically for quotes and forks
- V4V: Ask for donations in the Notification page
- Adds relay icon rendering from the NIP11 document
- Adds support for the q tag

Bug Fixes:
- Fixes the text's vertical alignment when emoji's are present
- Fixes DM Chatroom edit button
- Fixes the crash when images are not present in the image dialog
- Inserts uploaded URLs where the cursor is and not at the end of the new post.
- Fixes the rendering of Japanese characters, hashtags and custom emojis in the same line.
- Fixes the dissapearance of some Quartz classes when exporting to maven
- Fixing stack overflow with more than 200 zaps in a single note.
- Fixes image preview visualization on a new post
- Adds support for a new report option as Other
- Fixes missing nsec processing when parsing NIP-29 uris
- Fixes caching issue when creating a Bitcoin invoice for the first time
- Fixes UI issues due to the caching of Polls
- Better aligns post header elements
- Fixes bug with NIP-11s with null `kind` arrays
- Fixes quote and repost notes partially disappearing when they contain hidden users or words.
- Fixes content title for the video playback notification

Updated translations:
- Hungarian by nostr:npub1ww8kjxz2akn82qptdpl7glywnchhkx3x04hez3d3rye397turrhssenvtp
- Spanish, Spanish, Mexico, and Spanish, United States by nostr:npub1luhyzgce7qtcs6r6v00ryjxza8av8u4dzh3avg0zks38tjktnmxspxq903
- French by nostr:npub106efcyntxc5qwl3w8krrhyt626m59ya2nk9f40px5s968u5xdwhsjsr8fz
- Swahili by nostr:npub1q6ps7m94jfdastx2tx76sj8sq4nxdhlsgmzns2tr4xt6ydx6grzspm0kxr
- Czech, German, Swedish, and Portuguese by nostr:npub1e2yuky03caw4ke3zy68lg0fz3r4gkt94hx4fjmlelacyljgyk79svn3eef
- Arabic by nostr:npub13qtw3yu0uc9r4yj5x0rhgy8nj5q0uyeq0pavkgt9ly69uuzxgkfqwvx23t
- Dutch by nostr:npub1w4la29u3zv09r6crx5u8yxax0ffxgekzdm2egzjkjckef7xc83fs0ftxcd

Performance Improvements:
- Improves the speed of the text parser
- Reduced memory footprint of navigation buttons
- Faster hex validation
- Increases the speed of the Robohash SVG to byte buffer function
- Adds Benchmark tests for the content parser
- Adds Benchmark tests for the url detector
- Speeds up image compositions
- Improves relay list NIP-11 caching
- Faster Longform tag filters
- Speeds up the loop through the local cache
- Improves the speed of Location services
- Improves the cache of LnInvoices
- Improves cache of cashu tokens
- Reduces memory footprint for parsed posts.

Code Quality Improvements:
- Moves content parsers and media classes to commons.
- Moves emoji parsers to commons
- Moves Wallet Connect code to Quartz
- Moves Relay information code to Quartz
- Removes dependency on Kotlin serialization
- Adds a release draft generator to CI
- Updates Vico, Compose UI Version, Coil and Google Service dependencies
- Refactors the code to manage extra characters after Bech32 Links
- Moves to Android Studio Iguana | 2023.2.1
- Moves gradle to 8.4
- Moves project to version catalogs

Download:
- [Play Edition](https://github.com/vitorpamplona/amethyst/releases/download/v0.85.0/amethyst-googleplay-universal-v0.85.0.apk )
- [FOSS Edition - No translations](https://github.com/vitorpamplona/amethyst/releases/download/v0.85.0/amethyst-fdroid-universal-v0.85.0.apk )


Nice!

Add the most recent block height as well as the open timestamp, then you have a cryptographic proof of time window when the note was created.


Wabisabi coinjoin size grew by 15% with this deployment (it was expected as the minimum input for fresh rounds is 20% higher but blame rounds min didn’t change). Users don’t even really have to wait much more because the inputs are more “packed”.

Also something really interesting is that average AnonSet per output grew ~30%, from 6.5 to 8.5, which is a great gain of time/fees when you have an high AnonScore Target.

The ratio of change also dropped 25%, from 11% of the Satoshi Amount ending up as change to 8% now, which is explained by having more uniformity in the rounds.


Do you want to own the secret package for the president AND donate 100% of the proceedings to open source #bitcoin development via nostr:npub10pensatlcfwktnvjjw2dtem38n6rvw8g6fv73h84cuacxn4c28eqyfn34f ?

Here is all you need to know: https://v.nostr.build/ejV3.mp4


Thanks nostr:npub1klkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qulx3vt for stopping by

Here is the link
https://timechainartifacts.com/bitcoin-atlantis/984-paco.html

https://image.nostr.build/b40c88d6b8cedc60493e8277765089ff980fed5482c1de91a5430078db15fb6c.jpg


Genius real life explanation of coinjoin remixes.

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


Unfortunately not yet, but this is the first step towards that goal, for now it's only receiving and sending single user transactions.


2565 downloads on the first day, an all time high!

nostr:nevent1qqsgscpw4cddughqjvvjw62s8jxw43duzs3c50g8nkj2cyln8sacrucppamhxue69uhkummnw3ezumt0d5pzpdlddzcx9hntfgfw28749pwpu8sw6rj39rx6jw43rdq4pd276vhuqvzqqqqqqy4cmzl9


That's true, hard to do privacy tech on mobile.


Thanks to the devs!


527 pull requests merged in this release.

nostr:nevent1qqsgscpw4cddughqjvvjw62s8jxw43duzs3c50g8nkj2cyln8sacrucpydmhxue69uhhyetvv9ujuum0wejhyetfvahx2mn8d9hx2etjd9hxwtnfdupzpdlddzcx9hntfgfw28749pwpu8sw6rj39rx6jw43rdq4pd276vhuqvzqqqqqqyh9sgzj


Depending what you buy, for a lambo, probably yes.


That's eucalyptus.


With Wasabi's Buy Anything Button.


burn the boats


After LNBank of nostr:npub155m2k8ml8sqn8w4dhh689vdv0t2twa8dgvkpnzfggxf4wfughjsq2cdcvg  was deprecated and you cannot see its interface, you may want to pay out the users. But what was their balance?

Howto: https://gist.github.com/jooray/1569aedb80b18af0e44b1b9b753f485e

Any alternatives? I have some friends that would like a small store, they don't want to run a node, I don't want to run a node. Manual payouts are OK, but I need accounting.

I've seen Blink integration, but I would prefer something less centralized (no problem with holding coins on my node, but third party that relies on SMS and phone numbers and bans people from some countries is weird, although it would probably work for my use-case).


Payments in coinjoin is in the RPC now, that means the privacy of all other users has just been substantially improved, because now any adversary must factor payments into the decomposition attack.

The BTCPayServer plugin does this already, and soon Wasabi UI as well.

nostr:nevent1qqsgscpw4cddughqjvvjw62s8jxw43duzs3c50g8nkj2cyln8sacrucpydmhxue69uhhyetvv9ujuum0wejhyetfvahx2mn8d9hx2etjd9hxwtnfdupzpdlddzcx9hntfgfw28749pwpu8sw6rj39rx6jw43rdq4pd276vhuqvzqqqqqqyh9sgzj