A big wall of text from you, but almost 0 serious content. I am not going to comment your view at the situation.
But, instead of just telling wild stories, what about you come up with an actual PRO argument (for a blocksize blockweight increase) ?
Or an actual argument AGAINST second-layer scaling solutions?

All you said was 'no thats not a con argument, because it doesn't matter for most people'.

If you want a serious discussion, bring up some serious arguments in favor of on-chain scaling (which by the way do not exist).




Actually, every single user.

---

I have already read about BLS, but i am not sure whether it will really be adopted instead of schnorr. Especially regarding the eventual (not well explored) security concerns (yet).

I haven't heard of MAST before. Thats definitely an interesting feature.
Unbelievable how much potential this whole system has (and how much still will be discovered).

But it has to be decrypted when spending. So if the wallet actually does hold the private key (which it should, because if not it is not a proper wallet) it can be reverse engineered or debugged to extract the private key.
This would eliminate your 'encryption'.

IF the private key is known to the wallet, each user can extract it => 'Permissions' to spend are useless, since one user can steal all funds.
If the private key is NOT known to the wallet, it basically is a (weaker form of an) online wallet where the server does handle payment requests (and also holds the private key) => Unsecure.


For me, it seems this system is flawed and does not work. Did i miss something ? Does your software/concept work differently ? Might explain it more detailed ?

In such a scenario there are way better ways.

For example:

(1) You could encrypt your 12 seed (backup) with a strong password only you know. The gov won't realize what it is, they might recognize that it is encrypted (because it looks like random stuff).

(2) You could use steganography (hiding information inside pictures/videos/audios) to hide your (encrypted) 12 word seed. You might simply choose a granny porn to hide your information inside. I bet the gov won't watch all of your videos and search inside them for hidden information.

(3) You could use an 'offline form' of steganography. You might encrypt your seed, print it out (in hex) and place it somewhere, or print your (encrypted) hex seed onto a cup or something else. The gov probably won't take all of your cups with them to type the hex code into a notepad just to realize it is some random stuff (might realize its encrypted).



IMO these 3 ways are better than completely memorizing a 12 word seed.
And if you do have a paper backup anyway, why do you need to memorize the 12 words?

Everywhere i keep reading the wallet is using an open source bitfi algorithm to calculate the private keys.
Did actually anyone find the source code yet? Their github (https://github.com/Bitfi) is empty. 

I am quite interested in whether only the concept of the wallet is pure shit, or whether the algorithm also is just a pseudo-algorithm, just to call it an algorithm.

---

Please, keep away from this wallet.

You shouldn't care about a backdoor, but about the mechanism itself. It is insecure by design.
Your brain will be able to create an entropy of like 10-20 bits. Thats far away from 256 created by an proper algorithm.

It may be worth to note that with bitcoin you are basically sending the money from yourself to the recipient directly.

With banks, you are telling the guys who hold your money to send an amount to another institution which holds the money for the actual recipient.

Even ignoring the decentralised, immutable, and guaranteed aravial of the money, i think that this is worth paying more than via 'traditional banking'. For me, it is worth paying a few cents more to be the one who decides when to send the money, without a group of people who can refuse/freeze/undo my transaction (2.85 € seems to be quite high for the current mempool).


But i guess this is a matter of opinion. I am looking forward to a stable and tested LN release, so all of this problems will be solved once for all.

Thats a horrible idea.
Even if you are going to memorize the 12 words, without a proper backup this is just careless.
There are a lot of things which can happen which lead to a loss of your memory (e.g. car accident, alzheimer, trauma, shock moment, ...).

Your whole cryptos would be gone in this case. A proper backup (better: 2 or 3) is a must have.




There are a lot of ways to generate a random number. In the end thats all you need.
The easiest (and one of the safest) way would probably be to boot a linux distro (offline) and do some stuff (so the internal entropy pool gets filled), then get a 256 bit number from dev/urandom (don't use dev/random!) and convert it manually to a 12 word seed (with the BIP39 word list). You will need to calculate the last bits of the last word (since they are basically a checksum).

For more information take a look at https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki and https://github.com/trezor/python-mnemonic.
 

I am assuming you are talking about the block size?

Well, the most critical point probably is that increasing the block size is just a temporary scaling.
Doubling the block size brings a small benefit (lower fees) for a short period of time (until transactoun amount doubled).
But the price for this 'scaling' is, that you are sacrificing the possibility of decentralisation. If the block size would increase heavily, smaller nodes wouldn't be able to verify a block fast enough until another one has been mined.
This would lead to a (heavy form of) centralisation where only big data centre could allow to run full nodes. This would then require average user to trust some public nodes, without the possibility of fast and efficient validation.
Additionally, it is hard to perform proper testing on bigger blocks (e.g. 8mb or 16mb).

I recall there was a shitcoin fork which increased the block size, without even proper testing on how hardware/software/network reacts and with blocks being only filled to 0-10%.
Noone knows whether this network will still be fully functional when blocks start getting full, or which new attack vectors are being created out of this.


Segwit effictively already doubled (its at 2.3x at the moment, i think) the amount of transactions which fit into a block.

The next steps toward scaling in terms of transactions/block are
(1) the lightning network (which will allow to make an 'infinite' amount of transactions without paying the on-chain fee, as long your channel is open and filled) and
(2) schnorr signatures, which heavily reduce the size of transactions using multiple inputs (which most of the tx's are). They allow you to combine multiple signatures into one (and therefore saving space in the blockchain).

Ledgers wallet (software) checks whether the firmware on your nano s is geniuine each time you connect and open it.
There is no need for a 'tamper-proof' seal. The best tamper-proof seal is not a small sticker on the package, but a proper genuine check of the firmware.




Note, that samourai is NOT more secure than any other mobile wallet (or desktop wallet).
Each desktop-/mobile- wallet has its vulnerabilities (not purely due to the wallet itself, but more because of the environment (e.g. OS, ..)).

Especially because quite a lot mobile manufacturer do skip android security updates (while displaying the latest patch has been installed), there are always vulnerabilities which can lead to a compromised mobile phone.
This does NOT directly mean that any mobile wallet on your android is compromised, but the possibility for a highly-techy person to gain access to your mobile phone does exist.

One option would be to learn javascript via free eBooks. Look here (https://github.com/EbookFoundation/free-programming-books/blob/master/free-programming-books.md) for a massive amount of free programming eBooks (just search for 'javascript')

The other (probably more easier option) would be to just use a javascript libary (e.g. bitcoinjs-lib).
Everything is explained very detailed in the readme file.

Jaxx is known to be extremely buggy and vulnerable.
Anyone with access to your PC can dump the private keys (regardless of opening Jaxx, PIN, etc.. ).

Unfortunately there isn't much you can do. The next time use a trusted wallet (e.g. best example of a light-weight one: electrum)




If this means, that you have multiple AV software installed, then this might have caused the lack of security.
NEVER have more than one AV installed. With more than one AV software, they are interference each other, making your whole system way weaker than with just one AV.

Definitely make sure to properly(!) check your system for any malware. The best way would be to completely format your drive and reinstall your OS (do not use cracked (windows)OS, since they ALL(!) contain backdoors).

GetMemPoolEntry (txid) returns the mempool data for the given transaction (Documentation: https://bitcoincore.org/en/doc/0.16.0/rpc/blockchain/getmempoolentry/).

Transactions are not updated. Once the transaction is in your mempool, it will stay there until either (1) it gets confirmed and you receive the block or (2) your node drops it from the mempool (variety of reasons lead to this, e.g. not included into a block for x weeks (standard: 2 weeks)).

The mempool gets updated constantly (adding/removing transactions to it).

GetRawMempool returns all transaction id's of the TX inside your mempool. Note: This is NOT a hash function. It is a simple RPC call (Documentation: https://bitcoincore.org/en/doc/0.16.0/rpc/blockchain/getrawmempool/ ).





I don't really understand your question/concern.
GetMemPoolEntry (txid) does return all necessary information regarding a transaction (txid, size, fee, ...).

What exactly is your concern? Are you trying to query your node with a massive amount of RPC calls ?
Is your concern whether how much RPC calls your node can answer in a given time ?  In this case it depends on your specific setup (hardware, OS, .. ).

Core won't resync/reverify anything upon deletion of the wallet.dat.
There is no reason to do so. If you remove your wallet.dat, core will generate a new one.
Syncing/Verifying is only necessary if (1) blocks are corrupted or (2) the chainstate contains errors. Not upon creating a new wallet file.




This remembers me of a quote from Otto von Bismarck:

I don't see a reason to make mistakes if dozens of people already have made them.
Visiting this forum and asking for an advice is a way better way of learning something than to make mistakes and trying to repair them afterwards.

Unfortunately, neither private keys, seeds, nor addresses (can) start with EE being 26 chars long.
Maybe it is a password for a web wallet (blockchain.info) ?

If its not a password, it is not related to bitcoin in any way.




He might have created a web wallet then. Tell him to seach for 'bitcoin' in his emails.
If he finds something, try to recover the account using the email. If not, i guess there is no trace 

If you have used the correct address, your bitcoins are not lost.
You can enter your address into a blockchain explorer (e.g. blockchain.info) and check whether the transaction went through successfully (1+ Confirmation).

Make sure that you have a backup of your wallet file / seed / private keys. This will ensure that you will always be able to access your coins (with or without armory).

You seem to missunderstand the whole situation.

1) Once you deposit to an exchange, it is no longer your money. It belongs to them. All you get is the 'right' to withdraw them (which might get refused if they get hacked, etc..)
2) They are not trading with your money. They are 'grouping' all of their small deposits from individuals to a few addresses containing the whole balance. It makes it way easier for them to manage it this way.

If you want to hold your money (thats what it is about crypto), then withdraw your coins and store them on an address where (only) YOU have the control over the funds.
On an exchange, it is NOT your money.

Did you do the following?


And did you also enter the derivation path correctly (m/44'/0'/0') (note the single quotation mark) ?




Your HD account can create an (almost) infinite number of private keys.
You just need to know which derivation path + index you need to use to create the private key you are looking for.
The first index is 0 and will then be increased for each private key. So the only thing you need to know is the correct derivation path.

So.. you have basically used 100 lines of python code to parse reddit username in relevant crypto subs and are using the official reddit API to message them now.

How can such a service be more worth than 100$ ?
Even building such a bot would not cost 100$ since it would just take 1 to 2 hours. And you believe your service is worth more than 1k $ ?

There are multiple implementations of software to communicate with the bitcoin network.

The most common one referred to is bitcoin core. The source code can be found here: https://github.com/bitcoin/bitcoin.
There is no 'team' of programmers. It is an open source project. More than 500 people have contributed to build core.

The first implementation was from satoshi himself. It was written in C.

There isn't a real reason to backup the blockchain daily (except maybe if you are offering an online service which requires an intact blockchain to operate normally).
Usually it should be enough if you just backup the chainstate folder. It contains all relevant information (UTXO's, current verification state of the blockchain, .. .) and it is just a few GB big.

You can find it in the data directory of core (usually: C:\Users\YourUserName\Appdata\Roaming\Bitcoin for windows and ~/.bitcoin/ for linux).


Is there a specific reason you need to backup the blockchain daily ?

A 26-char string (with numbers and letters) is too short to be a private key.
It might be an address. He should at least tell you the char(s) it starts with (e.g. 1, 3, K, L, xpriv, .. ).


But based on this fact:


I doubt it is what he is looking for.


You don't receive any 'codes', strings, etc.. when purchasing bitcoins.

The general procedure is the following: You create a wallet -> You buy BTC on an exchange -> You send these BTC to your address (created by yourself).
So, in case he has bought BTC and got an address/private key instead of an actual transaction to his self-generated address, it most probably was a scam.