No. I did the backup after I created the shortcut onto my homecreen.
No. I don’t think so. I started on my mobile Safari to accept the invite and then created a shortcut on my iPhone Home Screen to make Mutiny easier to get to.
nostr:e1ff3bfdd4e40315959b08b4fcc8245eaa514637e1d4ec2ae166b743341be1af channel was forced closed in Mutiny over 2 days ago and I’m waiting for funds to show up in my on chain balance. I checked the logs today and am seeing:
ERROR [mutiny_core::onchain:73] Failed to broadcast transaction (REDACTED): Reqwest(reqwest::Error { kind: Status(400), url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("mempool.space")), port: None, path: "/api/tx", query: None, fragment: None } })
WARN [mutiny_core::chain:56] Error broadcasting transaction: Failed to broadcast transaction (REDACTED): Reqwest(reqwest::Error { kind: Status(400), url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("mempool.space")), port: None, path: "/api/tx", query: None, fragment: None } })
Total of four occurrences in the logs since the forced close.
What do I need to do to resolve the error? Keep waiting?
Zapple Pay works! Thanks nostr:npub1u8lnhlw5usp3t9vmpz60ejpyt649z33hu82wc2hpv6m5xdqmuxhs46turz
nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx good opsec at the end of Coin Stories pod. “I’m not gonna go that far…”
Also loved that she asked you about iPhones and blue checks.
It’s both funny and entertaining that you’re taking on the role I’d typically expect nostr:npub1guh5grefa7vkay4ps6udxg8lrqxg2kgr3qh9n4gduxut64nfxq0q9y6hjy to take on RHR because he painted himself into a blue corner.
Signed up again two weeks ago because Ben said something about prioritizing Nostr signups over email in a pod… Excited to try it with real sats is all. Will wait.
Already is. Still waiting to test main net.
Great work! Appreciate the walk through video.
He is risen!