Avatar
Bigred92
540201a550876dfcac3385e2dceaa385b8f4a747219397005c195c319f991cf3

Yes thank you it must just be something to do with the public contact list in the wallet

I have a question when I send money into #minibits is that auto converted to #ecash or do I have to and if so when I send a zap or any other lightning based transaction does it go to the Mint first and is converted or does it depend on the user having an #ecash wallet

#asknostr

Replying to Avatar Bigred92

Nvm

You just don't get a preview I was confused

Mine doesn't do small ones not a big deal just wondering what I'm doing wrong

:oh-my-god:

So there is supposed to be a vote on the speaker of the house today at noon eastern time and I don't believe Mike Johnson has the votes

#politics #usa #news

"Good morning! Let the new day be a canvas for your dreams. Paint it with kindness, color it with joy, and make every moment count. Here's to a day filled with small victories and big smiles!"

#plebchain #nostr #morning

i thought it came out that both had been done by former army personal and at least one was radicalized

i not sure if it can not saying it cant just admitting ignorance but i would like to see a decentralized internet protocol come out of this experiment so people are not reliant on giant companies or nation states

thats actually great i should have thought of it lol

digital versions of all the documents i need incase the shit hit the fan but somehow the governement survived and a couple of books prob

Replying to Avatar Ghostofbob89

Here you go. I wish I would have found this when I first arrived at #nostr protocol #asknostr. Hope it's help some of you all..⚡️💜💯

const relays = [

'wss://atlas.nostr.land', // paid relay 15000 npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj

'wss://bitcoiner.social', // paid relay 1000 npub1dxs2pygtfxsah77yuncsmu3ttqr274qr5g5zva3c7t5s3jtgy2xszsn4st

'wss://brb.io',

'wss://eden.nostr.land', // paid relay 5000 npub16k7j4mwsqm8hakjl8x5ycrqmhx89lxkfwz2xxxcw75eav7sd8ztqy2rwdn

'wss://expensive-relay.fiatjaf.com',

'wss://freedom-relay.herokuapp.com',

'wss://nos.lol',

'wss://nostr-2.zebedee.cloud',

'wss://nostr-pub.wellorder.net',

'wss://nostr-relay.alekberg.net',

'wss://nostr-relay.freeberty.net',

'wss://nostr-relay.wlvs.space',

'wss://nostr.bitcoiner.social',

'wss://nostr.blocs.fr',

'wss://nostr.coollamer.com',

'wss://nostr.decentony.com', // paid relay 7000 npub1pp9csm9564ewzer3f63284mrd9u2zssmreq42x4rtt390zmkrj2st4fzpm

'wss://nostr.fmt.wiz.biz',

'wss://nostr.gives.africa', // paid relay 10000 npub1g8dcep2exsadx9smhdrgwds06pgfc9yyyww6ftdcgnyukcuzk2csqs5jed

'wss://nostr.inosta.cc', // paid relay 5000 npub1r34nhc6nqswancymk452f2frgn3ypvu77h4njr67n6ppyuls4ehs44gv0h

'wss://nostr.milou.lol', // paid relay 1000 npub1rvg76s0gz535txd9ypg2dfqv0x7a80ar6e096j3v343xdxyrt4ksmkxrck

'wss://nostr.onsats.org',

'wss://nostr.orangepill.dev',

'wss://nostr.plebchain.org', // paid relay 6969 npub1u2tehhr3ye4lv4dc8aen2gkxf6zljdpf356sgfjqfun0wxehvquqgvhuec

'wss://nostr.rocks',

'wss://nostr.sandwich.farm',

'wss://nostr.wine', // paid relay 8888 npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz

'wss://nostr.zebedee.cloud',

'wss://private.red.gb.net', // paid relay 8888 npub1nctdevxxuvth3sx6r0gutv4tmvhwy9syvpkr3gfd5atz67fl97kqyjkuxk

'wss://puravida.nostr.land', // paid relay 10000 npub16k7j4mwsqm8hakjl8x5ycrqmhx89lxkfwz2xxxcw75eav7sd8ztqy2rwdn

'wss://relay.current.fyi',

'wss://relay.damus.io',

'wss://relay.nostr.bg',

'wss://relay.nostr.com.au', // paid relay 6969 npub1qqqqqrre3jxkuyj3s4m59usdyvm0umgm0lpy6cqjtwpt649sdews5q3hw7

'wss://relay.nostr.info',

'wss://relay.nostrati.com', // paid relay 2000 npub1qqqqqqqut3z3jeuxu70c85slaqq4f87unr3vymukmnhsdzjahntsfmctgs

'wss://relay.nostrich.land', // paid relay 2100 npub1vj0wlergmkcs0sz7hfks2ywj555c2s87f40squ4sqcmqpr7897fqn6mfew

'wss://relay.nostriches.org', // paid relay 421 npub1vnmhd287pvxxk5w9mcycf23av24nscwk0da7rrfaa5wq4l8hsehs90ftlv

'wss://relay.orangepill.dev', // paid relay 4500 npub16jzr7npgp2a684pasnkhjf9j2e7hc9n0teefskulqmf42cqmt4uqwszk52

'wss://relay.snort.social',

'wss://relayer.fiatjaf.com',

'wss://rsslay.fiatjaf.com',

]

thank you i will defiantly bookmark this though i don't believe i should add them all my understanding is too many and you will slow down and amethyst at times can be a lil slow compared to primal at least for me

all recovering democrats are welcome just as trump was once one himself just be careful to leave behind the politics that brought the democrat part to where it is now

Bull Bitcoin becomes the first mobile Bitcoin wallet that allows users to send and receive asynchronous Payjoin transactions without needing to run their own server, using BIP77!

I am very excited about this new and bleeding-edge feature, because it has been a long-standing ambition of Bull Bitcoin to become the first Bitcoin exchange to process Bitcoin withdrawals via Payjoin (Pay-to-Endpoint) transactions.

However, it was hard to justify Bull Bitcoin investing time into building this feature since there were no commercially available end-user Bitcoin wallets that were able to receive Payjoin payments.

Indeed, in order to receive Payjoin payments (BIP78), a Bitcoin wallet needed to be connected to a full node server and be online at the moment the payment is made. This means in practice that only merchants, professional service providers and advanced full node users had the capacity to receive Payjoin payments. This is, we believe, one of the major reasons why Payjoin had failed to gain significant traction among Bitcoin users.

For this reason, the Payjoin V2 protocol (BIP77) was conceived and developed by Dan Gould, as part of the Payjoin Dev Kit project, to outsource the receiver's requirement to run his own server to an untrusted third-party server called the Payjoin Directory. In order to prevent the server from spying on users, the information is encrypted and relayed to the Payjoin Directory via an Oblivious HTTP server.

Bull Bitcoin’s Payjoin ambitions had been put on hold since 2020, until there was more adoption of Payjoin receiving capabilities among end-user Bitcoin wallets…

But it turns out that in the meanwhile, Bull Bitcoin developed its own mobile Bitcoin wallet. And it also turns out that the open-source Bitcoin development firm Let There Be Lightning, which we had collaborated with in the past, had itself collaborated with Dan to build a software library for Payjoin that was compatible with and relatively straightforward to integrate into our own wallet software. All that was missing was to put the pieces together into a finished product.

Thanks to the collaborative open source effort of the Payjoin Dev Kit team, Let There Be Lightning team and the Bull Bitcoin team, the Bull Bitcoin wallet has now become the first commercially available end-user mobile wallet on the Google Play store to implement the BIP 77 Payjoin V2 protocol.

Moreover, the Bull Bitcoin wallet has also implemented asynchronous Payjoin payments, which means that a Payjoin transaction can be “paused” until the receiver or the sender come back online. This way, the receiver's mobile phone can be “turned off” when the sender makes the payment. As soon as the recipient’s phone is turned back on, the Payjoin session will resume and the recipient will receive the payment. This is a major breakthrough in the mobile Payjoin user experience.

We would like to thank the Human Rights Foundation for allocating a generous bounty for the development of a Serverless Payjoin protocol and its implementation in a mobile Bitcoin wallet, as well as OpenSats and Spiral for supporting the work of Payjoin Dev Kit, which made this all possible.

Why does this matter?

Payjoin, also known as Pay-to-endpoint, is a protocol which allows the Bitcoin wallet of a payments receiver and the Bitcoin wallet a payments sender to communicate with each other for the purpose of collaborating on creating a Bitcoin transaction.

I first heard about Payjoin (then called Pay-to-endpoint) in 2018 and it completely blew my mind. What I liked most about it was that it was not a protocol change to Bitcoin, but rather it was an application-layer protocol that allows wallets to communicate in order to create smarter and more efficient Bitcoin transactions.

Whereas in a normal Bitcoin payment the transaction is created by the sender, and all the inputs of that transaction belong to the sender, in a Payjoin payment both the sender and the receiver contribute coins as inputs.

In the Bitcoin whitepaper, Satoshi wrote:

"some linking is still unavoidable with multi-input transactions, which necessarily reveal that their inputs were owned by the same owner"

With Payjoin, this assumption is no longer true. With Payjoin, we have fixed one of Bitcoin’s most fundamental privacy problems... without changing the Bitcoin protocol!

In a Payjoin transaction, the output amounts visible on the blockchain does not necessarily reflect the value of the payment that was actually exchanged. In other words, you can’t easily tell how much money one wallet sent to the other. This is great for users that are concerned a malicious third party may be attempting to obtain sensitive information about their finances without their consent. This does not however pose an accounting problem for the Bitcoin wallets involved in that transaction: since both wallets are aware of which coins they used as inputs and outputs, they are independently able to calculate the "actual" value of the payment that was sent even if the payment on the blockchain appears to be a of a different amount.

Payjoin breaks the common input ownership heuristic, an assumption used by hackers and fraudsters to track ownership of addresses on the blockchain. The neat thing about this property of Payjoin is that it benefits everyone on the network, not just the Payjoin users themselves.

It allows the receiver of a payment to opportunistically consolidate his utxos when he is receiving funds, in a way which does not necessarily appear to be a consolidation transaction on the blockchain. Depending on the configuration of a payment transaction, it can also make a regular payment look like a consolidation.

In addition to these benefits, the introduction of collaborative peer-to-peer transaction protocols opens up exciting opportunities for the creation of Lightning Network channels, as well as efficiencies for transaction batching.

How to use Payjoin in the Bull Bitcoin wallet:

It’s so seamless, you may not even realize you are using it!

To receive via Payjoin, simply navigate to the “Receive tab” using the network “Bitcoin” and you will see a Payjoin invoice. When you want to get paid, send this invoice to the payer, or show them the QR code. If the sender’s wallet is compatible with Payjoin, it will be up to the sender to decide whether or not they want to use Payjoin.

To send via Payjoin, simply paste the receiver's Payjoin invoice, or scan the associated QR code, in the Bull Bitcoin wallet. If you decide that you don’t want to pay with Payjoin, simply turn off the Payjoin toggle.

Original post: https://www.bullbitcoin.com/blog/bull-bitcoin-wallet-payjoin

Download the wallet: https://play.google.com/store/apps/details?id=com.bullbitcoin.mobile&hl=en-IN

this is great