|
The issue was that I had protobuf 3.19.6 installed locally (with pip) and protobuf 29.3 installed globally. I removed the local, pip-installed version, and Electrum now works.
|
|
|
|
I built/packaged Electrum 4.5.8, and when I trying running it, I get this: Error: could not find paymentrequest_pb2.py. Create it with 'contrib/generate_payreqpb2.sh' How do I fix this? I tried running generate_payreqpb2.sh , but I don’t know if it created any files or put them in the right place. Can someone please explain this? |
|
|
|
|
Why should an innocent victim (unborn baby) be executed for his or her father's crime?
The guilty rapist should be executed!
|
|
|
|
I wonder if these mini reactors will ever be like, shrunk down and idiot-proof enough for everyday folks to buy one Westinghouse makes a 3 MW eVinci microreactor for space and ground military applications. |
|
|
|
In an email with subject "[URGENT] Bitwage Banking Switch - Change of Service Offered" dated today, BitWage said: Dear Bitwage Community,
The cryptocurrency sector has been facing challenges due to increasing regulatory pressure on the US banking industry, in what many are calling “Operation Chokepoint 2.0”. This pressure has come in the form of SEC Wells Notices, closed-door conversations between regulators and banks, and restricting direct access from crypto-friendly banks to the Federal Reserve. In our commitment to providing you with the highest quality service, we have worked diligently to maintain stable banking relationships amidst this industry crackdown. |
|
|
|
In an email with subject "[URGENT] Bitwage Banking Switch - Change of Service Offered" dated today, BitWage said: Dear Bitwage Community,
The cryptocurrency sector has been facing challenges due to increasing regulatory pressure on the US banking industry, in what many are calling “Operation Chokepoint 2.0”. This pressure has come in the form of SEC Wells Notices, closed-door conversations between regulators and banks, and restricting direct access from crypto-friendly banks to the Federal Reserve. In our commitment to providing you with the highest quality service, we have worked diligently to maintain stable banking relationships amidst this industry crackdown. |
|
|
|
maybe some tech billionaire out there is really building a hidden underground facility There's already the cryptovault (in the Alps, I think it is). |
|
|
|
Listen what this Austrian Economics / Mises Institute author of a book titled Better Money: Gold, Fiat, Or Bitcoin? says here: https://youtu.be/g7vI957pg7U&t=2597I don't see any reason to think that the price of Bitcoin is going to be predictably higher in the future. 🤦♂️ |
|
|
|
Why can't I import a Bitcoin Core private key into an Electrum wallet that supports Lightning? Running importprivkey in the Electrum console, I get: Error: This type of wallet cannot import private keys. Try to create a new wallet with that key. When I create a new Electrum wallet with the private keys, why is Lightning disabled for that wallet? |
|
|
|
Thanks, but those seem to be mostly e-books. I'm looking for hardcopy book stores. |
|
|
|
Now that Purse.io has been sunsetted, I'm wondering what are some online bookstores that accept ₿? |
|
|
|
prelude to centralized Central Bank Digital Currency (CBDC)? PYMNTS | November 3, 2023
The Clearing House has reportedly said that it is not aware of any ongoing issues after a narrow processing error that affected deposits and transfers at some banks.
Bank of America had sent a memo to clients Friday (Nov. 3) saying that some of their deposits may be delayed due to an issue that was affecting multiple financial institutions, Bloomberg reported Friday. Similarly, a spokesperson for JPMorgan Chase & Co. told the media outlet that a system issue had affected ACH debits and credits sent to the bank and other lenders. Other banks that experienced deposit delays due to the processing issue include US Bank, Truist and Wells Fargo, CNN reported Friday. There were also complaints on social media from people who hadn’t been paid because of the problem. The issue affected a single file, and therefore a batch of payments, and was ultimately a narrow processing issue caused by human error, a spokesperson for The Clearing House told Bloomberg. Reached by PYMNTS, a spokesperson for The Clearing House said in an email: “The Clearing House (TCH) experienced an ACH processing issue which impacted less than 1% of the daily ACH volume in the United States. TCH is working with the financial institutions who have customers that have been impacted.” The Federal Reserve said the processing issue happened at EPN, the automated clearing house owned by The Clearing House, and said all of its financial services were operating normally, the Bloomberg report said. “On November 3, 2023, a processing issue at EPN, the private sector ACH operator, resulted in a number of ACH entries having certain data elements obscured (file dated for November 1, 2023, processed on November 2, 2023, with effective dates from November 2-3),” the Federal Reserve said in an alert issued Friday. “This error was contained in a single interoperator file that was distributed by EPN to its participants during the November 2 6:00 p.m. processing window. These entries contain valid Nacha syntax, but obscured account information and recipient information.” The alert added that EPN had informed the Federal Reserve that these items could not be processed by the receiving depository financial institutions because of the obscured data, that EPN instructed its participants to initiate returns and that originating depository financial institutions will need to be ready to initiate new items to complete the payments. In its Friday memo to clients, Bank of America said, per the Bloomberg report: “Your accounts remain secure, and your balance will be updated as soon as the deposit is received.” ( source) |
|
|
|
What politicians (in any country) are accepting ₿ donations? This U.S. congress candidate does: https://aversa.vote/ |
|
|
|
Did you ask for a refund or that was the only way? I didn't suggest they refund me; they did. |
|
|
|
|
Well, they finally refunded me, so perhaps they're not scamsters.
|
|
|
|
Called them again, and they answered right away. They had no record of any transactions from my phone number, when really the last one was mid-year last year. Called again from my alt number and had to wait a bit longer. They said to email the ₿ transaction details to support@coin.cloud and call them back. I did so and called back, and a different agent didn't realize that there was an escalated tech support ticket on my account and put me on hold for an hour while investigating it and didn't seem to understand what a confirmed ₿ transaction is. Had to send an URL to an online blockchain explorer to prove it was a confirmed transaction. Do they even know that the address I sent to was one of theirs? How hard is that to determine? Either these people are incompetent, or they're scammers. I mean how many months is it gonna take them to fix this what one agent called a "bug"? For sure I'm using locally-operated ₿ ATMs from now on. I've had 100% reliability with them. |
|
|
|
|
Has anyone been able to speak to someone at 855-264-2046 anymore? I haven't.
|
|
|
|
|
Show Posts
