Thank  you!

Trying to catch up with the news, so please bear with me.

Do I understand it correctly that BTC and BCH use the same address space and the same principles of building a blockchain out of transactions but they differ in how transactions are signed now, making them mutually invalid?

In the light of the above, if I decide to spend my pre-fork BTC txout into BCH, I just need to issue a BCH-signed transaction for that txout, right?

After I do that, will this txout be still unspent from BTC network point of view (since my BCH transaction is invalid in BTC and won't go into BTC blockchain)?

My question has nothing to do with fees or prices

As far as I understand BCH uses the same address space as BTC but different transaction format, so I can spend any pre-fork BTC tx output using BCH client and it will go into BCH blockchain and essentially register as BCH.

What I don't get is if BTC network will know I spent that output into BCH?
If BTC doesn't read/recognize BCH transactions, will I still be able to spend that output in BTC network?

Thank you!

I'm running the latest version of bitcoind, blockchain is up-to-date, I execute these commands in cmd:




When I go to blockchain.info I don't see neither the transaction id nor any change in the balances of the addresses involved.

What might be the reason for this not working? Thank you!

I made a low fee transaction from blockchain wallet, as I understand from time to time all unconfirmed transactions are being cleared from the memory of the bitcoin core software that is running behind the wallet, does it happen with the blockchain wallet (and how often)?

Thank you!

The website looks very nice
15 hours till pre ico starts

The article was written by coinsopen and published on other social media website :DDDD

I think that anyone is allowed to participate in a ICO , even if they are from USA , Europe or other region . The investments are made through a blockchain crypted so they can't trace them

Glad to hear that you will implement a code with antiwhale protection ! Many icos are a scamm , just made for selling all tokens and dumping the prices

What is a "standard" private key?

Considering that many people generate public keys non-stop, I guess some private keys are better to be avoided, for example private key 1 or the maximum key value allowed. Are there any general rules for checking that you private key is safe in this terms i.e. how far it is from the both ends of the range for example, or from the middle or with a few zero bytes in it or with a simple pattern that might attract people picking up keys?

The same question about seeds that are used to generate private keys: are all seeds acceptable or are there some checks in place?

Thank you!

Is it possible to create an updated version of Bitcoin free from so many technical problems/bottlenecks that appeared or were revealed after many years of using it (and using it very intensively in the last few years)?

It seems that the original idea put forward Satoshi Nakamoto has been stretched to it's limits, problems pile up and some of them don't have long term solutions.

Did anyone come up with a Bitcoin revamp that is free of those?

I'm not talking about a significantly different cryptos like Etherium, rather about modifying/adapting the original idea.

Or does Bitcoin have some inherent flaws that will eventually inhibit its growth?

So what happens if an input script contains other OP codes? Will they be ignored or will the script be invalid?

Thank you!

Can a script that is used in a transaction input contain OP codes or is it always treated as a data that will be automatically pushed on the stack before applying the output script from the UTXO mentioned in this input?

Great answers, thank you!

Yes, but it's a sort of a race condition between forks, at which point you measure which one is longer, after the second block arrives in one of the forks?
How long ( or by how many blocks longer) one fork needs to be to win?

I'm writing my own block finder that reads .dat files made and verified by bitcoind, starting from blk00000.dat forwards. As soon as a new block is read I append it to it's parent, thus creating the blockchain. Blocks ofc are not read in the right order so you need to shuffle them on the fly.

Sometimes a block is read that claims a parent that already has a child, so this is a fork (at least in my terms) and one of them has to become an orphan.

How can I resolve this and figure out which one to keep?

Is it a decision based on future block codes or is it an external decision?

For example, I stumbled on a block 000000000000000000E0BBFCB8C89D8A1A68247E9A379E64BF4F6309A2282383 that you won't find on blockchain.info but can see thru bitcoin-cli API, it claims 0000000000000000005f2a78bcf67d01b57c72b3a1c354fad15c18550657b631 as a parent but it was never added to the blockchain.