Questions on: security - страница 1

You simply can't add, insert or install software or any executable stuff into a Trezor. Due to the way the Trezor is set up, it runs fully autonomically. The only thing that goes into the Trezor is transaction details (addresses, amounts, etc)
Simple answer, no. What you're most likely talking about are interesting ways to use script to pay to a m-of-n multisig, for example. Generally, when you get paid in bitcoin, you, as the merchant, get to choose where the customer sends the bitcoin
Transaction malleability has a very small effect on a regular user, at most it can mess up some of your bookkeeping if you store the Transaction Id of a transaction before it is confirmed. Transaction malleability only affects unconfirmed transaction
Bitcoins can be stolen in a variety of ways. In fact, researchers at SecureWorks, a division of Dell, released a paper at the RSA conference and highlighted that there are over 146 different types of malware which have the capability to steal bitcoin
What you are asking is, does Bitcoin have a vulnerability where if a computer system is compromised can the attacker steal money. The Bitcoin network is a decentralized, peer-to-peer network. There is no "master node" that controls a ledger
First, from a cryptography point of view, transactions have to be signed, and the other nodes in the network will be able to detect and reject transactions for which the signature was forged. Second, from an incentive point of view the miner will hav
Is the random library used by the standard client in any way deterministic, or can one count on it being truly random? For example, often random libraries are initialized with seed value of the current time, like in C++: srand(time(NULL)); But if som
This is essentially correct: the protocol leaves it up to the miner to decide which transactions to include in a block. There is no requirement for them to include any transactions at all, other than the "coinbase" transaction which specifies where t
A transaction is a unit of work that you want to treat as "a whole". It has to either happen in full, or not at all. A classical example is transferring money from one bank account to another