Avatar
Rob
763971ba21b318790c38f533ea5f387adad52089c954b5a2f6bfcdf4c681e853
βœοΈπŸ‡ΏπŸ‡¦

The bittersweet pain of orange-pilling a friend, who then surprised me this week with buying a hardware wallet so they can take ownership of their #Bitcoin - and it's a Ledger.

I know it's a big step in the right direction, maybe I'm being a toxic maxi, but Ledger can get bent after the leak and the whole 'Recover' fiasco. Don't trust them at all anymore.

Replying to Avatar Niel Liesmons

https://void.cat/d/RA5DZHkCMx4vsoUf427rxY.webp

https://void.cat/d/H4hRiCuiGmiHTkzPEyXsjx.webp

Professional apps need professional logo's.

Current Amethyst logo:

- has the wrong colors

- the eye is not part of the compound path

- lacks alignment

- the A is hard to recognize

Redesign I did a while back:

https://w3.do/T29KyB0w

No pressure though nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z πŸ˜‰

#nostrdesign #logo

Your redesign looks more like a shadow puppet πŸ€·πŸ»β€β™‚οΈ

#datechain, more like #baitchain

Well this is disappointing. What was a tentative step forward for mass #bitcoin adoption in South Africa at major retailers has been paved over by our two largest local exchanges. It incentives hodling on exchange, and removed the need for retailers to use native lightning solutions.

https://mybroadband.co.za/news/cryptocurrency/506610-pick-n-pay-gets-easier-bitcoin-payments-with-valr-and-luno.html

According to our best efforts, anytime before June of 2011 πŸ˜‚

So, we OK with the mempool situation? It's pricing out coinjoins. 5 days of 8 sats/vB. Whole of August was 6+. This just going to escalate all the way into the halving hype? There are peeps with transactions waiting since April, clearly a manipulated situation.

#bitcoin

In my opinion the focus should be on getting new users set up with and backing up their 12 words. Once you have that foundation, nostr private keys, non-custodial lightning seed words, etc, all of that can be derived from/based on those 12 words, using standard passphrases or BIP85's, etc. Otherwise you are having to stitch all these things together yourself, and is not natural.

Why are we talking about PoW pubkeys 😭 I'm saying each pubkey (normal pubkeys!) have a PoW difficulty requirement to write events to the relay. Per pubkey. The relay handles its own requirements, and adjusts difficulty according to that pubkeys behaviour.

What would a regular note look like, before and after a migration like this? Can you provide a real example? Curious what it looks like, and confused as to why if you're having to recreate a note as though the new key posted it, why providing a new POW value is not an option at the same time. The pubkey, sig, id, etc all change anyway?

I'm still confused why we're talking about old and new keys? Are we able to migrate notes from one pubkey to another as though the new key posted it? This is my nth pubkey, I would've liked to know πŸ˜‚

I'm assuming you mean spammers will just generate new pubkeys to bypass. New pubkeys should have a higher difficulty target.

Yes, but why would old notes need migrating? The relay, at the time of writing, puts up a difficulty requirement, and the note gets written. Raising the difficulty on that pubkey only applies to future notes, it shouldn't require reposting old content to meet the new difficulty target.