Avatar
Nice and Kind Vic
21b419102da8fc0ba90484aec934bf55b7abcf75eedb39124e8d75e491f41a5e
https://i.nostr.build/Lqsu56YxOCvwc6G5.jpg 💬 cornychat.com - audio spaces 🖼️ nodeyez.com - bitcoin node images Recommends: 🥣 zap.cooking 🎵 tunestr.io 📲 relay.tools 💩 turdsoup.com 🥔 oddbean.com 🔣 listr.lol 🕹️My Nintendo Switch Code SW-7592-4594-7016 About: I do programming, databases, data parsing, reports, visualizations. Bitcoin maxi. Available for hire Corny Chat (https://cornychat.com) operator, running the first open source audio spaces integrated with Nostr with support for zaps, room customizations. Nodeyez developer (https://nodeyez.com) providing sovereign scripts to get more from your node. It can generate images from your node accessible in a website dashboard or slideshow output to an attached display.

Ive yet to see any NFT proponents leverage nostr or embrace it for such even though it could be done with traceable provenance for ownership. There simply isnt demand for what NFTs represent outside of grift tokenomics

I touch on this briefly in the review.

Depends how many people you are following. If you are an "influencer" that follows less than 5 people, it is very smooth. If you're a pleb following hundreds or thousands, it has some jitter at times as content loads. Ive mentioned to nostr:npub1hte85nxymfyez0nlmmxf287nh9cujfuetxhk9vptwcdqg0pn8pxqxasw3d and hes got his team working it and some other related issues in iOS, but promising that an update scheduled for this weekend may resolve it.

Ive spent the past 36 hours thoroughly testing the new Nostr client Nostatum that Tatum and his team has been working on.

Got a full review here, including screenshots and unlock codes

https://shorturl.at/knFZ6

Some highlights covered

- iOS zap functionality is super fast and self custodial

- Customized emoji reactions with layered branding is cool for organizations

- Drag and Drop list ordering

- Calendar Events (some bugs moving vs copying events to separate calendar)

- Podcast player and integrated stream to zap.stream in mobile version (Desktop not yet supported)

Holy shit this is seriously great work.

Love the new integrated Podcast player feature. Now I can listen to Between Two Asics while surfing through Nostr Notes and cross referencing episodes.

Nice touch on drag and dropping notes for categorized list ordering as well. Chef's kiss.

nostr:nevent1qqsfe0cxh3y6mx47pct3s74nm7chvra4wjn75c9eem5q9h4ja3gj24cpzpmhxue69uhkummnw3ezuamfdejsyg967faye3x6fxgnul77ej23l5aew8yj0x2e4a3tq2mkrgzrcvecfspsgqqqqqqs3vx3rz

A few statements to clarify...

The spender of a tweaked public key is the original private key and the tweak. The commitment for the tweak can be revealed without revealing the private key.

Segwit when implemented did have a practical limit on the number of op codes for standard transactions due to script signature limits.

Per BIP342, taproot maximum script size of 10000 bytes does not apply, and thus only bound by block size.

It was October 2022 that the btcd issue caused lnd nodes to fail when Burak broadcast a 998 of 999 taproot transaction.

Ordinal theory for the modern Bitcoin era began sometime in mid 2022, well before the taproot transaction on mainnet, and doesnt require segwit or taproot. It wasn't the first numbering scheme, but will likely be the dominant one henceforth.

The first Inscription, applying ordinal theory, and leveraging Taproot was in December 2022, with the protocol formally launched in January 2023 by Casey Rodarmor.

A change that was made at the time of Segwit that supported Lightning was the fix for the malleability bug. Lightning network needed Segwit to support its smart contracts.

If one's goal was to drive up fees for transactions, there's far more grief attacks that could be performed, such as bitcoin stamps, and creating non spendable outputs. Shitcoiners are incentivized to drive down their creation costs, to allow creating more per sat.

Replying to Avatar mleku

a little tl;dr on taproot, segwit and ordinals

taproot is a type of HD key scheme where you have the parent key and then a "tweak" value.

a simple taproot key can have no tweak, and its derived private key is the hash of the original private key, and the public key is derived from that.

a taproot key with a tweak is where you concatenate the private key with an arbitrary string of bytes, in a similar way as a HD key derivation, but of course it can be anything, even the binary bytes of a compiled ethereum solidity script.

it is not material to bitcoin what you used in the tweak, it does not interpret it.

it is not material to bitcoin that there is any tweak at all, this is all inside the key generation and derivation process.

it took me a while to wrap my head around it, because in the code it seems like all this derivation is important, but it is not.

the receiver must have the private key and the "tweak" values in order to spend the received sats.

the derived private key that generated the address is not normally stored in the algorithms, but it could be.

TAPROOT IS JUST A SCHNORR SIGNATURE BASED KEY.

segwit, on the other hand, the cryptography of it is not so important to how it works as the fact that it allows you to make transactions with extremely large amounts of arbitrary data, after opcodes like OP_RETURN.

until 2021, nobody really seriously exploited this for anything much larger than about 20kb. then someone dumped a transaction using segwit with over 30kb of data in it, some 999 signatures or something, and lightning was broken temporarily because BTCD code had put a limit, that is not specified in the segwit BIP, as a protection against resource exhaustion attacks.

then the light dawned to the shitcoiner community that they could drive up bitcoain fees and clog the chain by publishing huge transactions, so tehy cooked up scamms like Ordinals, to make their justification for making transactions with ginormous amounts of data in them, and the miners of course were ok with this because during the bear markets tx volumes are thinner and the block rewards are thus lower.

shitcoiners and miners are who benefit from segwit.

segwit was not essential for Lightning. it just made it a bit more secure.

at the time, Schnorr signatures were an option that was discussed, but it was rejected.

this was the wrong decision, obviously.

i don't know how bitcoin is going to recover from the spamfest that ordinals created, but please....

it's not taproot that enabled ordinals, it was segwit.

many of these statements are factually incorrect

Replying to Avatar BTC_P2P

nostr:npub1xkere5pd94672h8w8r77uf4ustcazhfujkqgqzcykrdzakm4zl4qeud0en I love your service but why the 6-20 day withdrawal wait? It’s brutal.

fiat settlement risk

I heard in Oz, stuff like this so common they dont even post the warning signs

no longer available at my local 7-11

the first time i saw porn was when id sneak and watch the scrambled cable channel that 5% of the time would make a perceptible image where you could make out a boobie

Those are common in parts of America to warn of the bloodsuckers. If you see flying overhead, RUN! DO NOT LAY STILL AND PRONE!

Watching The Firm and kind of miss the days when web pages would render slowly inline

https://werunbtc.com/thesis.pdf

Still the 🐐 thesis. Blows Softwar out of the water.

awhile back i made a few translations

in this folder

https://github.com/vicariousdrama/howto/tree/main/bitcoin

Just because someone didnt intend malice doesnt make it not malicious.

Zeus is the bad actor in this scenario. Room for changes but I blocked paying zeuspay for this same issue weeks ago. I agree that others could do this, and it exposes a weakness in HTLCs effectively taken hostage in transit.

LND spent the better part of a year (or so) focused on Taro -> Taproot Assets, and shelved bolt12 and hasnt indicated that they'll implement it

Thats what all FOSS development is.

The positive is attribution, which is enough for some.

Its like planting the seed of a tree, nurturing it but knowing youll never live to benefit from its shade.

yes to some degree.

look at snort social and iris merger as an example.

but competition is healthy and devs often dont agree and especially in visual want creative power.

a better solution is more devs and contributions in general. get active on github curating issues, add to existing any personal insights, find and cross reference duplicates, update documentation (text, screenshots, translations).

if people spent 20 minutes a day doing the above (and learning how is doing), wed make far more progress then rehashing in nests and notes.

Approaching long term normal thresholds

one of my all time favorite 3D games of the 90s