It appears there are some studies that are ongoing regarding ivermectin currently.

There is opposition to using ivermectin even on an experimental, or compassionate use basis. There was similar fierce opposition to hydroxychloroquine even while studies were ongoing. The reason for this is that if there was an efficient treatment for covid, the lockdowns and other means of control under the guise of "protection" from covid could no longer be justified.

I read the documentation, and it appears there might be some missing information.

The second paragraph in the "overview" section starts talking about the "SE" but this term is never defined. It is unclear what this is.

At the end of the first paragraph of the "statechains" section, it says that any collusion between the "SE" and an old owner of a UTXO that results in theft of a UTXO can be trivially proven. This does not explain any consequences of this collusion. If someone were to buy up all the 0.0001 BTC UTXOs one at a time, and sell each UTXO before buying the next one, if they are colluding with the "SE" what would prevent them from being able to have a tx confirmed to an arbitrary address? I don't see anything in the documentation that would.

The "fraud proof" paragraph again says that it can be trivially proven if the "SE" is corrupt, and alludes that the ability to prove a "SE" is corrupt is an incentive to be "honest". Again, the documentation does not explain the actual consequences for the "SE" for being corrupt. The LN protocol for example, has concrete consequences for publishing an old channel state to close the channel -- the other party is able to recover the entire channel balance of both parties. There does not appear to be any financial consequences for a corrupt "SE" that I can see.

I am curious if you are in any way associated with this project.

This is according to Joe Rogan, and may or may not be true.

The opposition to Ivermectin is not about Ivermectin, nor is it about the vaccine. It is about control. The opposition to Ivermectin is about control. Democrats want to mandate (aka force) people into doing something they know they will receive pushback to, and force as many people to do what they don’t want to do as possible. This will lead to Democrats being able to get even more people to do what Democrats want them to do.

I don’t think the day of the week new videos are released is particularly important, as long as it is consistent. You should set this according to your schedule so that you can reliably release videos that day. If your release schedule doesn’t match when viewers are able to watch new videos, viewers will watch new videos later. If you say you will post new videos on Tuesday, and someone can view new videos on Thursday, if they check your channel on Thursday to not find a new video, they might not come back to look for additional videos.

I think this is an escrow address. It was posted as being the address to watch for payments last year. It is certainly not a new address.

If LL said he would find escrow two weeks ago, he should do so.

I don't understand the potential benefit to the end user. If someone doesn't want to spend their own bitcoin, they can simply not broadcast a valid transaction spending their bitcoin. nLockTime is a means to allow a transaction to be prevented from confirming in the event of some kind of dispute between parties conducting business, so the other party can broadcast a conflicting transaction in the interim.

There is no "proper" way to try to bruteforce something.

While this is a bad security practice, many people reuse passwords, or reuse passwords while appending something to the end of a password each time a new one is created. If this is the case, there is a decent change the OP's friend knows her passphrase is one of a dozen or so potential passphrases, but isn't sure which one, and she can check them all in a few minutes.
There are setup costs associated with using a program/script such as btcrecover such as reading the documentation to figure out how to use it. Spending 30 minutes "manually" checking potential passphrases before using a tool to systematically trying to bruteforce the passphase is not going to hurt anyone.

The input from this could be replicated by "just attach a standing miniature fan next to your box and then place a sensor in front of it to measure its turbulence".

When generating private keys of any sort, you should not try to reinvent the wheel. If you are using something as a means to generate entropy in addition to using entropy from a known secure way of generating entropy, at best, you are going to have the same amount of entropy, but you may end up with less entropy.

You either trust your computer to generate a random number or you don't. Using additional input is not going to change this trust. If you don't trust your computer to generate a random number, you should use something that you know will produce a random output, such as a coin toss or a dice roll.

Some people use a passphrase as an additional security measure to prevent theft in the event their hardware wallet is stolen. I think it is fairly common for people to be more lax with their hardware wallets with regards to security, while backups are almost always kept under some kind of lock and key. Some people may also use a passphrase to prevent a $5 wrench attack while spending your coin. It really depends on your security model and assumptions.

If the OP's friend knows their passphrase is one of a dozen or so possibilities, the setup/reading the documentation for something like btcrecover may take longer than using iancoleman's tool.

It is too late now for your friend, however it is a good practice to have backups of everything needed in order to recover your bitcoin. This would include any 25'th word passphrase. If it makes you more comfortable, you can store your passphrase separately from the rest of your seed.

If your friend is able to figure out her passphrase, it would be a good idea to add her passphrase to her backups.

---

As mocacinno said, your friend can change the derivation path to BIP84 on the tool you are using. By default, this will change the path to m/84'/0'/0'/0 -- I am not sure what path ledger uses by default, but if this is not the path that ledger uses, you will have to update the account and internal/external fields accordingly. Otherwise, you will generate different addresses, even if you have the correct passphrase.

Well I do think it would be strange for only email addresses to leak. There is typically more information that leaks when a database is compromised. I would have expected for at least IP addresses and some data about the accounts to leak.

There is a very narrow set of circumstances in which only email addresses would leak from CMC.

Email addresses (and other non-password data) is normally stored in a database. The database itself will usually have permissions restrictions prevent an arbitrary person from accessing the database. The reason this information is stored in a database is so the business, in this case CMC can query this information to complete various tasks, such as emailing their customers.

A password on the other hand is typically stored in a "hashed" format. This means the actual is not actually stored, but rather the result of the password being passed into a hash function is stored. This means that someone querying the database cannot actually get the actual password, but if the correct password is entered into a query, it is trivial to confirm the correct password was entered. The reason passwords are stored this way is because there is no valid business reason for someone to query someone's password. Also, the number of people who can access even the hashed passwords is generally more restricted than other parts of the database.

There have been a lot of hacks of various crypto services over the years. It is not inconceivable to believe that the leaked list is actually a compilation of email addresses used by crypto users.

It is ridiculous to expect to capture every single household that is mining with a single ASIC miner. Someone running a single ASIC miner is expected for all intents and purposes to never find a block. Should the data in the OP also capture the people who are mining by hand?

Those who are solo mining with a small number of ASICs are going to be well within the margin of error I previously explained.

There is no reason why an electric company would complain about heavy electric users as long as they are getting paid.

In China, that is experiencing electricity shortages, and collects extensive data on its people, would be likely to look into why a household is using 10k KwH a month. My guess is someone using 10k KwH per month who is not mining is probably keeping their homes at a ridiculous temperature and or keeping their windows open while running the heat/air conditioning.   

Assets that perform well in stagflation are those that perform well with high inflation that do not rely upon economic growth. Raw commodities should perform well, as should bonds held to maturity that are not at risk of default due to low economic growth.

To the extent that you believe bitcoin will perform well during times of high inflation, it should perform well. Stocks of most companies should perform poorly. Utility stocks should perform better than most other indexes.   

If all that is for sale are email addresses and not passwords (hashes), it is probably safe to assume that passwords were not compromised. Although you should use a unique and distinct password for every account you have.

It is possible that the attacker used some type of vulnerability that will leak information about if a specific email address is associated with an existing account. The attacker could then attempt to use whatever method leaks this information by trying a list of known email addresses known to be associated with bitcoin users against this method.

While there are no financial benefits explicitly paid to non-mining node operators, there are incentives received for running a node.

As you noted, node operators have additional privacy above what non-node operators have. Node operators receive the full value of censorship resistance that bitcoin offers, as SPV servers and other services that facilitate the broadcasting of transactions can trivially censor any transaction they want. You can also be certain that you are aware of any transaction received to an address, as SPV nodes and block explorers can trivially withhold this information.

All of the above give substantial value to node operators. While difficult to quantify and will vary from person to person, the value still very much exists.

This is obviously very bad for Fauci and he should be impeached (if allowed by the law), or otherwise terminated from his position (maybe funding can be withheld from his salary). He should also be criminally investigated for this “research”, and prosecuted to the fullest extent allowed by the law.

With that being said, the dog torture by Fauci has nothing to do with the vaccine. Trump is responsible for operation Warp Speed, which is what funded the vaccine research.

If you are wanting to give the title to your vehicle as collateral for a loan, why don’t you go to a lender that specializes in such kinds of loans? They will likely charge a lot by most lending standards, however they have the expertise needed in order to asses risk and as such can minimize the cost of your loan (if they are willing to give you one).

If you have already tried this, the next question that should be asked is why it would be a good idea for someone here to give you a loan, if lenders who are experts in judging vehicle title collateral is not willing to do so.

I read some papers on the topic, but I don’t think I have a clear understanding of how IT PIR works.

If a particular SQL query accesses a particular record, how would this be hidden from the server hosting the DB? If someone queries a potential address that doesn’t exist in the DB (because it has never received a transaction)(via a where type clause), how would this be hidden from the server?

I bunped your thread. It is now at the top of the board it is posted in.

I have not looked at your altcoin, but my assumption is that it is substantially inferior to bitcoin and most other altcoins. On the off chance that my assumption is wrong, your thread has some exposure so that you can make your case otherwise.

Good luck!