nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0
There is another mantra: Can we do better?
I was refering to this, for the uninformed:
Other peoples money spent on somebody else
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
I just want to point out that the IRS will make believe that every satoshi going out of your wallet, is a capital gain, and every satoshi that is received, is income, effectively causing the value transmitted to be worth only ~50% of what was sent after they come after you.
KYC is a bitch. Be careful out there.
Because they are both interpreted languages
Create an alt now while your nsec is uncompromised. Post indicated that this is your alt. This is proof you can use in the future.
Bitcoin doesn't use encryption
If a bad guy has your password, you can lose access to your account
If a bad guy has your nsec, you always still have access to your account (but they do too)
There is no second trip
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
Holy fucking shit!
How deep down the rabbit hole do you want to go?
That's because you are using the wrong science. Fiat science clearly shows the correlation.
I hate to say this but who couldn't see this coming? đ
The hyperinflation in the Weimar Republic during the early 1920s and the onset of World War II are connected through a series of political, economic, and social factors that contributed to the rise of extremist movements in Germany, particularly the Nazi Party.
1. **Economic Instability**: After World War I, Germany faced severe economic challenges, including the burden of reparations imposed by the Treaty of Versailles. The hyperinflation that peaked in 1923 devastated the German economy, wiping out savings and leading to widespread poverty and unemployment. This economic instability created a fertile ground for political extremism.
2. **Social Discontent**: The hyperinflation caused significant social unrest and discontent among the German populace. Many people felt betrayed by their government and the Treaty of Versailles, which they believed had humiliated Germany. This discontent was exploited by radical political groups, including the Nazis, who promised to restore national pride and economic stability.
3. **Rise of the Nazi Party**: The economic turmoil and social unrest allowed the Nazi Party, led by Adolf Hitler, to gain support by promoting nationalist and anti-Semitic rhetoric. They capitalized on the public's desire for a strong leader who could restore Germany's former glory and address the economic crisis. The Nazis promised to reverse the effects of the Treaty of Versailles and rebuild the economy.
4. **Political Instability**: The Weimar Republic was marked by political fragmentation and instability, with numerous parties vying for power. The economic crisis weakened the democratic institutions, making it easier for the Nazis to gain influence and eventually seize power in 1933.
5. **Militarization and Expansionism**: Once in power, the Nazis pursued aggressive militarization and expansionist policies, which ultimately led to the outbreak of World War II. The desire to reclaim lost territories and assert Germany's dominance in Europe was fueled by the nationalistic sentiments that had been exacerbated by the economic hardships of the Weimar period.
In summary, the hyperinflation in the Weimar Republic contributed to economic and social instability, which facilitated the rise of the Nazi Party and set the stage for the aggressive policies that led to World War II.
Put all your creepy apps in a separate Android profile. They they can all snitch on each other.
