Seth

nostr:nprofile1qydhwumn8ghj7mnjv4kxz7fwvvkhxar9d3kxzu3wdejhgtcprpmhxue69uhhqun9d45h2mfwwpexjmtpdshxuet5qqsgafy9ye4j9p2x8vfmlq6equtpcg4m8ks7v545g0d3f7wwueeq5scz9g5a6 trying maple's api proxy with codename goose and I consistently get a 404. I've restarted the proxy and changed api keys many times. is this a skill issue on my part or a known maple proxy issue? haven't faced it with any other configured goose provider

like all of us have been, I’m considering the core/knots debate. I think Adam Back is making reasonable arguments against knots from a legal perspective. if you try to get a tighter leash on what unconfirmed transactions get broadcast, it stands to reason that the legal attack vector grows. also, core obviously doesn’t allow blocks to exceed 4mb, so this doesn’t make it more difficult to run a node. here’s the thing I can’t quite understand, though: if core wants spammers to use op_return, something 4x more expensive than other avenues, what is the economic incentive there? it seems like another avenue that spammers *could take*, with no economic incentive to get them there. tagging nostr:nprofile1qqs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6ccpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshsv577ew here bc he has been instrumental in helping me at least understand core’s position

nostr:nprofile1qqs9mvjd9uym8ey4w5vevlrxqfesm666cm6su27svcwqfvj8ztvhlgspp4mhxue69uhkummn9ekx7mqpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhg3dt22j, your wallet is probably the best UX for normies. however, imho a couple scenarios prove worrisome for all Bitkey users. am I missing something in the following scenarios? scenario 1, spouse as beneficiary: - you die, spouse gets bitcoin ✅ - you both die, bitcoin is lost ❌ scenario 2, family member as beneficiary: - you die, family member gets bitcoin. spouse and children may never get the bitcoin based on family dynamics 👎🏼 - you and your family take a trip together and die, bitcoin is lost forever ❌