Bitcoin Forum
February 19, 2019, 11:48:47 AM *
News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 [6] 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 ... 551 »
101  Bitcoin / Bitcoin Technical Support / Re: How to go from testnet to livenet on: November 10, 2018, 03:27:45 AM
Your questions is pretty vague. What part of "going from testnet to livenet" do you need help with? Connecting to nodes? Conecting to bitcoind? Addresses? etc.
102  Alternate cryptocurrencies / Altcoin Discussion / Re: How to revert made fake coin exploit code's bug? on: November 03, 2018, 12:50:53 PM
So litecoin forked coin is safe?
No. Litecoin, and every other coin that was forked from Bitcoin or pulled in new code from Bitcoin are vulnerable, unless they have also pulled in the fix.

And if this happened, what solution can be used to fix?
Pull in the changes from Bitcoin Core. Sync a new node with that software. Once it reaches the invalid block, it will reject it. From there, start mining a fork. Once that has more work than the original blockchain with the invalid block, that will become that coin's blockchain.
103  Bitcoin / Development & Technical Discussion / Re: Does Bitcoin Core in prune mode support mining? on: November 02, 2018, 02:36:58 PM
I have currently set my Core node to -prune=550, but I see that getblocktemplate returns data, so can one mine on the pruned node?
Yes, you can mine.

With only 550 blocks stored, how can/would a pruned node make sure that an input given by user to be signed in a block isn't a double spend? There'd be no way to check that on such a node, right?
(E: Although i think there's probably a mechanism for this, otherwise it wouldn't be able to verify any transactions at all.)
That's not how Bitcoin Core works. Pruned nodes are still full nodes. They have validated every block in the blockchain; they still validate and relay every single valid block and transaction they receive. They are, by definition, full nodes. The difference between pruning and not pruning is whether the node can serve historical blocks to new nodes coming online. Everything else is the same; they can be miners, they will still receive all blocks and transactions, etc. The UTXO data that is necessary for validation is not pulled from the block history, that would be rather slow. Instead, when a block is validated, the UTXOs are copied to a UTXO database and the UTXOs that were spent are removed from that database. Pruning still keeps that database and all of the UTXOs, so validation is still works.
104  Bitcoin / Development & Technical Discussion / Re: scriptPubKey not verified upon locking, but when trying to unlock it on: November 01, 2018, 03:12:49 PM
That is hardly an explanation, we are talking about syntactic correctness here, not semantic.

A scriptPubKey can be preliminarily validated against this kind of mistakes that I described above, I was not expecting it to be run on its own because I know they only make sense concatenated together. However, errors like these can be caught up without actually running the script...
It is up to the transaction creator to ensure that their script is constructed correctly. There are tools available that let you do this. It is not the Bitcoin network's job to be your debugger. Further, any script is syntactically correct, even if it is "wrong". There really is no syntax.
105  Bitcoin / Development & Technical Discussion / Re: scriptPubKey not verified upon locking, but when trying to unlock it on: November 01, 2018, 01:43:51 PM
1) why it worked in the first place, doesn't the scriptPubKey go via the same validation rules as the scriptSig ?
Because the scriptPubKey is only half of a script. It cannot be executed. If it were, it would always fail because a scriptPubKey is just part of a script. Same with the scriptSig; it is just part of a script. On their own, neither can be executed and get a successful result.

2) why would bitcoind even care about the scriptPubKey of the UTXO i'm trying to spend, i thought it was supposed to just first run <scriptSig> then keep the stack and run <scriptPubKey> (which it may already consider valid...?)
The scriptPubKey defines the spending conditions, i.e. what needs to go into the scriptSig. It has to run the scriptPubKey to ensure that the scriptSig is correct.

You can think of the scriptSig being the first half of a script and the scriptPubKey being the second half. On their own, they mean nothing and when executed on their own, they will fail. But concatenate them together, and you get a full script which can be executed. That is conceptually what script validation does. Before script validation, neither the scriptPubKey nor the scriptSig are considered valid.

The scriptPubKey in an output can be anything, it is not and cannot be validated when it is created. There have been multiple instances of people putting random garbage in scriptPubKeys. Those transactions are totally valid and in the blockchain. It is just that the outputs are not spendable because attempting to spend them would result in an invalid script.
106  Bitcoin / Bitcoin Technical Support / Re: raspberry pi errors 0.17.0.1 on: October 31, 2018, 08:36:42 PM
Your databases are corrupt. Start bitcoind with -reindex.
107  Bitcoin / Development & Technical Discussion / Re: Flaws in LN (Lightning Network). on: October 31, 2018, 08:35:19 PM
This thread is devolving into flaming each other. Thus it will be locked.
108  Bitcoin / Development & Technical Discussion / Re: When bitcoind starts up, In where and which function difficulty is calculated? on: October 30, 2018, 01:53:12 PM
Quote
That error is completely unrelated to the difficulty. The getblocktemplate RPC will refuse to return a valid block template if it thinks it is not fully synced. That will happen if the timestamp of the most recent block is not within two hours of the computer's time.

Thank you so much for the reply. I'm a bit confused a little bit here. The most recent block is my genesis block. If I create a new genesis block and do the compiling and starting up process, same thing will happen. That's why I speculated about difficulty.You say there is no problem with the network and I can create transactions properly?
There are other conditions that can trigger this error, it is not just the timestamp. It may be possible that the fact that there is only the genesis block is what is causing the problem. I think it could be that just having the genesis block even if it is up to date will still cause the node to think it is still in InitialBlockDownload. You can just make the error go away by commenting out or removing these 2 lines in src/rpc/mining.cpp.
109  Bitcoin / Bitcoin Technical Support / Re: "Premature end of block data" when using linearize on: October 30, 2018, 12:42:46 AM
./linearize-data.py linearize.cfg
Runs fine and reads all the blocks but seems to try to read the next blk file that does not exist.
I do get a bootstrap.dat file but I also get a "Premature end of block data". I can't tell if this is a normal ending to running the script or not.
That does not seem like the normal end of the script. That error means that it was unable to open the next file of block data which it was expecting. This could be due to a configuration error, or that perhaps the node is not synced to where you believe it to be. However, the resulting bootstrap.dat file should still be valid and usable. It just does not contain as many blocks as you expect it to contain.

How does one confirm that a bootsrtrap.dat is, in fact, accurate or properly done?
By trying to load it into a version of Bitcoin Core that can read the bootstrap.dat file and seeing if it does load it.
110  Bitcoin / Development & Technical Discussion / Re: Please, help with bitcoin core on: October 30, 2018, 12:39:04 AM
Those errors look like permission errors. Make sure that the user that bitcoind is running as has permission to read and execute the file. Note that the user that you are currently using in the shell is not necessarily the same user. Further, if you have to use sudo to do anything to the file, then something is probably wrong, unless bitcoind is being run as root (which you shouldn't be doing).
111  Bitcoin / Development & Technical Discussion / Re: When bitcoind starts up, In where and which function difficulty is calculated? on: October 30, 2018, 12:31:52 AM
So you mean that if I change nBits and consensus.powLimit parameters in chainparams.cpp the whole network should work fine ? but I face a problem when I run two bitcoindd :
Yes.

The two servers start up properly but when i type the command "bicoin-cli getblocktemplate" I get

Code:
error code: -10
error message:
Bitcoin is downloading blocks...
That error is completely unrelated to the difficulty. The getblocktemplate RPC will refuse to return a valid block template if it thinks it is not fully synced. That will happen if the timestamp of the most recent block is not within two hours of the computer's time.
112  Bitcoin / Development & Technical Discussion / Re: How are bitcoin blocks verified? on: October 29, 2018, 04:01:13 AM
By definition, everything in a computer is a string of bytes, even text  Grin



All kidding aside, a block has a serialized byte format. It is not transmitted over the network in JSON. The JSON output that you get from Bitcoin Core is merely something that is human readable. That is not actually how blocks are transmitted over the network.

The block format is just bytes with bytes at certain positions having specific meanings, as defined by the format. You can see the hexadecimal representation of these bytes if you call getblock with verbosity level 0 (i.e. getblock <hash> 0).

A block is not a script. Scripts are part of transactions and are in a specific field for scripts only.
113  Bitcoin / Development & Technical Discussion / Re: When bitcoind starts up, In where and which function difficulty is calculated? on: October 26, 2018, 06:38:37 PM
The difficulty is merely a user facing thing. In reality, it does not calculate the difficulty at all and the difficulty itself is never used anywhere.

The only thing that matters when it comes to the proof of work is that the block hash, when interpreted as a 256 bit little endian integer, is less than or equal to the target value.
114  Bitcoin / Bitcoin Technical Support / Re: Currupted block database detected error on: October 26, 2018, 06:33:13 PM
You are using versions of Bitcoin Core and Litecoin Core that are vulnerable to CVE-2018-17144. Any block that exploits this vulnerability will have the side effect of causing block database corruption when the block is being reorged out of the blockchain. Furthermore, testnet is known to have blocks exploiting this vulnerability, and because you are using vulnerable versions, you are likely running into these invalid blocks which is causing your error.

If you upgrade to the latest versions of Bitcoin Core and Litecoin Core, do you still see the same problem?
115  Bitcoin / Development & Technical Discussion / Re: What would the math be behind these claims? on: October 24, 2018, 01:39:13 PM
Even vanitygen can only do 500k/s with point addition(though we do include sha256 and ripemd160 hashing).
Vanitygen is pretty slow and does not used optimized key generation code. If you use an optimized library like libsecip256k1 (which is used in BItcoin Core), it can be much faster.
116  Bitcoin / Bitcoin Technical Support / Re: Negative Balance in RPC Accounts on: October 24, 2018, 01:35:08 PM
This is expected behavior with accounts. This is also one reason why you shouldn't use it.
117  Bitcoin / Bitcoin Technical Support / Re: Please Help! on: October 24, 2018, 04:10:31 AM
Be patient, there isn't anyone here can do about that. Transactions get an additional confirmation for every new block that is found that has the block containing your transaction in its history. As more blocks are found, the number of confirmations for your transaction will increase. There isn't anything that anybody about that, that's up to the miners to continue to produce blocks. There isn't anything special that needs to be done to get more confirmations. The confirmations will come, just be patient for more blocks to be mined.
118  Bitcoin / Development & Technical Discussion / Re: Bitcoin core watchonly address 2 of 2 on: October 23, 2018, 10:53:45 PM
createmultisig does not add the multisig address's redeemScript to your wallet. You need to use addmultisigaddress for that or import it with importmulti.
119  Bitcoin / Development & Technical Discussion / Re: can't get the same publickey for c and nodejs on: October 23, 2018, 03:07:09 PM
for my c code (use secp256k1 directly from bitcoin core)  

 unsigned char ctmp[]={0x79,0x54,0x55,0x9D,0xE4,0x26,0xCB,0x23,0x8C,0x9A,0x8A,0x2E,0x45,0x3C,0x75,0x8C,0xCA,0xD9,0x17,0xE1,0xF4,0x66,0x79,0x2A,0x51,0x66,0xEB,0xED,0x59,0x32,0x0F,0x6F};

     secp256k1_context *vrfy = secp256k1_context_create(SECP256K1_CONTEXT_VERIFY | SECP256K1_CONTEXT_SIGN);
secp256k1_ec_pubkey_create(vrfy, &pubkey, &ctmp)
and print it out get  0xBB,0x19,0xAB,0xD0,0x74,0xD4,0xA2,0xFE,0x21,0xC9,0xFA,0x3E,0x4E,0x8C,0x46,0x81,0xC3,0x75,0x80,0xE2,0xF3,0x1B,0x3E,0x3D,0xE7,0xC6,0xF9,0xDD,0x44,0x47,0xAD,0xC0,0x36,0xC5,0x03,0x7E,0x3D,0x29,0x2B,0x10,0xBC,0x1B,0x11,0x73,0x55,0xF8,0xE4,0x69,0xB9,0xB6,0x4B,0xCD,0xC9,0xD9,0xD1,0x5D,0xE9,0x13,0x20,0x65,0xF2,0x72,0x3C,0xD6
How are you printing this out? If you are just printing the pubkey object without serializing it, then that is obviously wrong.

If you look closely, you'll notice that 0xBB,0x19,0xAB,0xD0,0x74,0xD4,0xA2,0xFE,0x21,0xC9,0xFA,0x3E,0x4E,0x8C,0x46,0x81,0xC3,0x75,0x80,0xE2,0xF3,0x1B,0x3E,0x3D,0xE7,0xC6,0xF9,0xDD,0x44,0x47,0xAD,0xC0 is the first half of the pubkey that you got from node.js, but with the bytes reversed. Further, 0x36,0xC5,0x03,0x7E,0x3D,0x29,0x2B,0x10,0xBC,0x1B,0x11,0x73,0x55,0xF8,0xE4,0x69,0xB9,0xB6,0x4B,0xCD,0xC9,0xD9,0xD1,0x5D,0xE9,0x13,0x20,0x65,0xF2,0x72,0x3C,0xD6 is the second half of the pubkey, again with the bytes reversed. This will happen if you are just inspecting (or printing) the secp pubkey object itself since internal byte order is not the same as the byte order when actually serialized.
120  Bitcoin / Development & Technical Discussion / Re: Please, help with bitcoin core on: October 23, 2018, 03:04:08 PM
But getnewaddress creates address based on one account. And I need separation between two wallets(accounts)-30% to hot wallet, 70% to cold.
An address is not a program, it can't forward anything automagically. You will need to have something that waits for transactions to that address and creates the forwarding transaction for you. You can do this by using -walletnotify.
Pages: « 1 2 3 4 5 [6] 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 ... 551 »
Bitcointalk.org is not available or authorized for sale. Do not believe any fake listings.
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!