btcbanksy

As an aside, and you could perhaps chalk one up to admiration for this, but I don’t believe he is a spook. In this respect, I would question you before I would question him. Perhaps that says something 🤷‍♂️

2023-09-21 03:16:40 UTC

- reply

I have respected him as authentic. I believe he muted me. I don’t think he is an intellectual, a distinction I might give to you, and he may be out of his league in this respect, but I think he has a genuine curiosity for truth, and the dispensing of bullshit.

2023-07-27 17:50:14 UTC

Underrated, but I literally spend half my time on Twitter blocking ads.

2023-07-24 12:30:13 UTC

Aging nicely #note1fmg…07gu

2023-07-23 14:18:07 UTC

- reply

Works of Love
-SK

2023-07-23 02:17:46 UTC

I love that line… “There is no time in history where those censoring speech were the good guys”

2023-07-19 03:06:09 UTC

Growth for the sake of growth is strictly cancerous; it consumes all for the sake of growth. This is fiat.

2023-07-04 00:30:03 UTC

What is interesting about LLMs is that they are probabilistic, however much they are refined by RLHF, which is not how thoughts/words are put together. There has to be a more efficient path for making logical distinctions.

2023-07-03 03:23:03 UTC

You are training data

2023-06-28 15:41:22 UTC

- reply

aka hosted lightning?

2023-06-26 19:09:05 UTC

- reply

I don’t trust it

2023-05-24 01:35:21 UTC

ARK … from Burak on Telegram:
Here's Alice & Bob payment flow:
Suppose Alice owns 1234 sats and wants to send 500 sats to Bob, where Charlie is the Ark service provider; Alice joins Charlie’s next pool session to pay Bob. This is akin to joining a coinjoin session where Charlie is the blinded coordinator. Unlike coinjoins, however, (1) pool sessions take place in very short periods, (2) the intention is to pay someone in an aggregate transaction, and (3) there is no on-chain footprint except for the pool outputs and inputs that fund the pool outputs, everything else is off-chain commitments that nests in the pooled output.
Alice’s 1234 sats are made of ten coins; a 1000 sats coin, two 100 sats coins, three ten sats coins, and four one sat coins. These coins are off-chain commitments that live in pools from which Alice was previously paid. Alice can unilaterally revert her coins to on-chain by revealing and claiming her nested coins from these pools.
A pool expires after four weeks of its creation. After expiration, a pool becomes solely claimable by the service operator who funded the pool in the first place. This is so that nested coins can only be revealed within the first four weeks of a pool's creation. Users must spend their coins in this timeframe or send coins back to themselves under a new pool to reset the four-week timer.
The pool content may be revealed if the service provider happens to be non-collaborative or non-responsive for a long period. In the optimistic big picture, however, the final result is almost always a pool transaction with few inputs, the pooled output, the connectors output, and change output where the factory content is rarely revealed on-chain. Therefore, coins remain almost always off the chain.
Each coin has a 2-of-2 key path where the coin owner and the factory operator are co-signers. Coins are also given a script-path refund closure secured by a timelock if the service provider is non-collaborative co-signing from the 2-of-2 key path.
After Alice joins Charlie’s factory session, Alice registers for her ten coins (1234 sats) to spend in the pool, each under a unique Tor identity, similar to registering UTXOs in a coinjoin round. Charlie previously provided liquidity for these coins in his pools and is the co-signer of every single one. He can therefore authorize Alice’s coins for registration based on whether they are invalid, banned, or expired. Charlie, of course, doesn’t know who Alice is; he sees ten different Tor identities who want to register their coins. Charlie gives Alice blinded credentials based on her registered ten coins.
Alice rejoins the pool session, this time to register for payout coins. Alice unblinds credentials she previously received from Charlie and registers for Bob’s payout coins plus her change under a unique Tor identity each. To pay Bob 500 sats, she registers for five payout coins, each carrying 100 sats. Each of these five coins is a 2-of-2 multisig between Charlie and Bob. To calculate Bob’s co-signer key for each payout, Alice tweaks Bob’s dedicated well-known public key (i.e., Nostr key) with a unique payment commitment to (1) preserve Bob’s privacy by eliminating address reuse and (2) obtain proof of payment from this payout when Bob claims his coins. Alice sends these payment commitments to Bob out-of-band (i.e., Nostr DM). Alice also registers for a 734 sats change, made of 14 coins; seven 100 sats coins, three 30 sats coins, and four one sat coins. Alice has registered for 19 payout coins in total; 5 coins to pay Bob and 14 coins to pay herself.
Once the registration phase is over, Charlie crafts his pool template by adding Alice’s 19 payout coins mixed with other participants’ coins under the vtxos output. He adds the vtxos output to the overall pool transaction he is crafting. Charlie then adds a set of additional outputs called vtxo connectors to his pool template under a separate transaction output called connectors output. A vtxo connector output is a single-sig P2TR output spendable by Charlie himself, and it carries a dust value (450 sats). Vtxo connectors are added to the pool number of registered spending coin times. Since Alice has registered ten coins to spend, Charlie adds ten coin connector outputs to his pool, mixed with other participants’ vtxo connectors. Alice has 29 total associated outputs in Charlie’s new pool template; 5 payout coins for Bob, 14 change coins for herself, and ten vtxo connectors for her coins to plug in.
Alice and Charlie collaboratively sign off-chain transactions from the 2-of-2 key path of her coins to connect to her vtxo connectors. The first input in this off-chain transaction is the coin itself, and the second is the vtxo connector from the new pool template, plus one output for Charlie to sweep the funds. The coin (first input) is signed using SH_ALL; therefore, the vtxo connector’s (second input) outpoint in the sighash preimage commits to the pool transaction id. To claim this coin in a dispute resolution, the service provider must point to the agreed pool template by spending the corresponding vtxo connector (second input). This provides an atomic payout construction as the payout coins nest in the same pool as the vtxo connectors.

2023-05-22 00:40:52 UTC

Fedi, Ark, Lightning, Spacechains?What necessitates one over the other? Is there a need for all of these? Are there more?

2023-05-21 18:14:46 UTC

- reply

An apparent solution…
#note1x6t…u7c4

2023-05-19 19:27:43 UTC

Is there a script/environment/something to setup and test running multiple lightning nodes on testnet, preferably with core lightning?

2023-04-28 16:44:21 UTC

Spare me your empty likes. #zap

2023-04-13 21:11:28 UTC

- reply

Gotta stay on top of things… #Bitcoin #Nostr

2023-04-13 20:52:35 UTC

Well, I’d imagine Joe Rogan should be looking at having an interview with #[0], no?! Would be a great representative conversation for both Bitcoin and Nostr, right?!

2023-04-11 22:56:10 UTC

- reply

#[1]

2023-04-05 15:58:43 UTC

Is someone working on nostr + btc exchange?

2023-04-02 02:57:01 UTC

- reply

Someone in that position deserves the potential to earn glory, a position unsuitable for most people.

2023-04-01 18:01:08 UTC

Sam Altman is evil, and all chatgpt users are enablers

2023-03-30 02:32:37 UTC

- reply

Been quite the experience going through the whole “ignore” and “laughing” stages to get here. Bring on the W.
#[0]

2023-03-25 20:40:22 UTC

The problem with AI is the data you are choosing to give it; yeah you.

2023-03-20 23:33:09 UTC

Wasn’t hasufl in cahoots with zhusu?

2023-03-20 15:03:57 UTC

Fiat: “Trust us”
Bitcoin: “Don’t trust, verify”

2023-03-20 13:29:21 UTC

Get rid of the option to “🤙”, and force users to “⚡️”. There is no reason to cater to those who do not understand value; force them to learn.

2023-03-16 21:25:33 UTC

The “Banking System” shouldn’t/doesn’t need resilience.

2023-03-14 14:48:41 UTC

Is this not the time of Bitcoin? Is this not the time for Bitcoin to be the very thing it was born to be? Is this not the time for Bitcoin to be the example, the demonstration, and the way?

2023-03-07 04:12:44 UTC

What are your relays doing with your data?

2023-03-05 23:24:51 UTC

- reply

A thought must have something that exists to think the thought. It is psychologically difficult to think "I do not exist". The proper logical flow of argument is that existence is already assumed or presupposed in order for thinking to occur, not that existence is concluded from that thinking.

2023-03-04 16:29:02 UTC

https://youtu.be/Gu0EQM01VU0

2023-03-03 12:51:18 UTC

- reply

Lol, was just thinking how people suck with naming things. I want to build an app called “Live Support”, and figured really, it should just be called that… so direct and informative.

2023-02-23 14:38:20 UTC

#[0] is the Socratic seminar something I need to sign up for, or be a member of Bitcoin Park to attend? Can I just show up?

2023-02-21 00:54:05 UTC

- reply

What ever happened to Libra?

2023-02-18 23:43:56 UTC

- reply

If I’m not mistaken, you have to simply charge the same for both, rather than charge more in the App Store.

2023-02-17 12:29:51 UTC

- reply

IIRC, I probably used my pseudo email at some point 🤷‍♂️

2023-02-17 12:27:15 UTC

- reply

*verifying

2023-02-17 12:26:43 UTC

- reply

I didn’t verify. Verdi’s action is more for balance limits, and I was just testing it out, so I was fine with the small limits.

2023-02-17 12:18:51 UTC

- reply

I had set one up using this guide. Probably some hiccups in the setup, but I managed. Not currently running it though. https://andreneves.xyz/p/how-to-setup-a-paid-nostr-relay

2023-02-16 13:54:19 UTC

Plans for 2023:
- setup self hosted LN node
- setup join market with qubes os
- do something with theblockreward.com

2023-02-15 13:39:39 UTC

- reply

Latest isn’t on App Store?

2023-02-14 14:44:09 UTC

- reply

Right?

2023-02-14 14:43:00 UTC

- reply

JM + nostr? Some integration I don’t know about?

2023-02-09 12:58:49 UTC