ably is a browser extension atm but you could connect to NWC and use on tap zap in clients. Other than that pretty straightforward
tbdxxx Launched as Ark - Privacy Preserving Layer 2 Bitcoin Scaling Solution
"Ark is a liquidity network that operates like Lightning, but without introducing liquidity constraints. It uses virtual utxos, to enable anonymous, scalable, off-chain payments. ASPs provide liquidity to the network and charge fees for their services."
https://www.nobsbitcoin.com/tbdxxx-ark-layer-2-scaling-solution/
Interesting
It’s a great Friday
I have an idea and not sure how practical and applicable it can be.
The concept basically is a higher level key pair. We have now a public and private keys. Let’s add two more keys.
The first new key type is a MASTER key, which is a user’s (salt * npub * nsec) or randomly generated. The second key is a POSTER key, which is a public key derived from the MASTER key. Theoretically, a user can have infinite MASTER keys. However, a user may decide at any moment to choose and assign the new key pair. Assigning the new key pair requires the user to publish from the associated npub a possibly new kind event and advertise the POSTER key. This event is a one time irreversible event.
POSTER keys work as pointers and status checkers. They are the npubs managers and the identity keepers. They publish npubs with updatable tags or labels for self or others.
Example: I decided to generate my key pair today. I go to a nostr identity manager client. I enter my current nsec and login to generate a new MASTER pair and publish the event from my current npub. I then will be able to label my npub as active, revoked, expired or old… I could then generate new key pairs for any use case and tag them as such. I could also vouch to other’s npub’s essentially to build on the idea of web of trust.
This also can work with your idea of allowing other people to federate or co-manage identities or keys. I just thought of all this now. I could have overlooked some design flaws.
Apple transition to silicon chips was not the smoothest. Rosetta performance between x86 and arm64 is great but still lots of issues. I’m thinking these issues are mostly because I moved some x86 environments to arm so my own error but not clear…
Lightning Force Close Detected in Block 790230 between Boltz and Aliens LaNDing 👽
55K sats to force close a 5M sats channel 🤮
https://mempool.space/tx/f778c6627eec754e5acb33c197711b7ce91d1c38125511e010dc28a53b8fbe0d
You are the most interesting and depressing bot. I wanted to thank you for your service and mute you.
When you create a new account click see advanced options and you’ll get native segwit
Big if true nostr:note1u02pc0e3ck89uw354azr4nv6stqu2f3evxfvagev3qqglskqpv7q95xhfr
Relays are delicate creatures
aah there’s actually a trick to do it :) turn your setting default to anonymous zaps and zap away… It’s satisfying
Nvm seems fixed now but literally zapped one post more than 100 times yesterday
It does work for me and Im not sure if it’s supposed to #[5]?