Tag Info

At the core, there are no ETC and ETH account addresses. Private keys are equally valid on both chains. But, a contract can be deployed on one chain or the other uniquely and so contract addresses can be chain specific and aren't generated from a private key. It really depends on whether the exchange is using a contract to manage its wallets or private key ...

Update Apr 12 2017
There are only 3 more days to withdraw your refunds from the WhitehatWithdraw contract.
There are still 1,651,062.7506 ETC (USD 4,292,763.15) remaining in the withdrawal contract.
87% of accounts have NOT withdrawn their refunds.
Check this spreadsheet to confirm that you have withdrawn all your refunds.
Following is a chart of the ...

Update Jun 02 2017
From WARNING: Do NOT Use SafeConditionalHFTransfer! Or Use It Correctly:
The SafeConditionalHFTransfer saved a lot of ethers being moved incorrectly on the wrong chain after The DAO hard fork. So far there has been 20549 txns + 16022 internalTxns passing through the SafeConditionalHFTransfer at ...

Send Ether to your contract (ethertransfer) from the external account (a term for user controlled accounts). To be able to make it, you need to have a payable function in your contract (which might be the fallback function
https://solidity.readthedocs.io/en/latest/contracts.html#fallback-function). Payable function is the function with the payable modifier (...

I'm using the same unmodified script from How many ethers have been drained through the recursive call attacks on The DAO? to calculate the balance of The DAO and it's child DAOs.
For a finer categorisation of the different child DAOs, see the latest update from How do I get a refund for my The DAO tokens that was split into a child DAO?. There are several ...

ETC has the same network_id = 1 as ETH (see this question for the list of known network ids).
As ETH and ETC nodes use the same wire protocol they can connect to each other and send blocks and transactions. But ETC and ETH have different sets of bootnodes predefined in their clients. This results in two non-overlapping networks.
To distinguish ETH and ETC ...

A general solution is EIP 155 Simple replay attack protection.
Starting with Geth 1.5.3 and Parity 1.4.4, they implement EIP 155 so that your ETH transactions should be safe from a replay attack on ETC. Create another account and move all your ETH to the new address. Don't forget to backup this new account (and don't delete the old account since it has ...

Yes, an account before the DAO-fork will have Ether on both chains: ETH and ETHC.
It's not a double spend in the usual sense, because when you send ETH to Alice, you cannot send the same ETH to Bob. You could send ETH to Alice, and ETHC to Bob, but they are separate blockchains (similar to how you could send BTC to Charlie, except that ETHC account ...

The easy, low-tech way to do this for ETH held in a regular Externally Owned Account is to create two new addresses, one for each chain, and send a transaction on each chain moving your ether to a different address. Once that's done any subsequent replayed transaction will be coming from an address with no ETH in it, and will therefore be invalid.
It's ...

The Baddies joined into the Split Proposal #59 where they were not the curator. From this split, the Baddies created a number of split proposals where the Split Proposal #59.10 was used to split out the attacked funds into a split where the attacker was the curator. The Baddies have now created the Non-Split Proposals #59.10.1 and #59.10.2 where the funds ...

You are mixing 2 layers of abstraction:
the distributed ledger, on which multiple machines do things many times to reach a consensus
the Ethereum Virtual Machine (EVM), which is an expression of the consensus, and which behaves like a single process computer.
So since your program computes in the EVM, it is unaware of the distributed ledger and the many ...

It actually appears that you may have emailed the Ethereum Foundation instead of Poloniex; Hudson Jameson is part of the Ethereum Foundation and not Poloniex.
Log into Poloniex's customer support portal here and provide them with your tx id, as you did above. Let them know what happened.
Poloniex controls the private keys and, therefore, should be able ...

I think it remains good practice to check any contract before running it.
The contract seems to be at: https://github.com/BitySA/whetcwithdraw/blob/master/whetcwithdraw.sol
Is there a way to check that the contract at the address 0x9f5304da62a5408416ea58a17a92611019bd5ce3 is indeed coming from the source above?
In order to verify that the contract ...

On a public blockchain, all the transactions between accounts (externally controlled and smart contract) are public. You can browse each transaction of each block using tools such as EtherScan.
For example, on the picture below, you can see every data for a transaction to a smart contract (write operation) :
Transaction Hash
Block No
Timestamp
From account ...

That the DAO attacker could crash ETC by dumping his 3 million ETH might be an exaggeration. If analyzed using market economics, it acts more like a zero sum game, in that when someone sells, another person buys. The worst that could happen is that the attacker dumps the price which would let a few lucky people buy cheap ETC. As long as there is R&D ...

The Ether will still be in your Ether address.
Yes, you will have both ETC and ETH. If there are any other forks that use the genesis block from the Ethereum presale, you will have all those Ether too.
You may want to "split" your ETC and ETH to different addresses to avoid replay attacks: this leads to a number of options for doing so.

The code itself for Ethereum (non-classic) was modified in such a way that at block 1920000 it moved the ether in all the child DAO's created from The DAO to a withdraw contract. The classic code was not modified. This had the effect of changing the affected accounts' balances on the non-classic fork. Resetting, for example, the balance of the Dark DAO to ...

These are all user-submitted values and also non-Ethash-based algorithms. For the most part, the users submitting 100 MH/s+ hash rates have indicated these are for multi-GPU systems. For example, someone has submitted this:
ASUS 2х7990 1000 1500 win 8.1 pro 16.1 Ethereum 95Mh/s
The HD 7990 is, itself, two GPUs rolled into one. And this user ...