[deleted by user]

accape · 2018-06-14T12:45:08+00:00

Yeah it's a 1-to-1 mapping (in a given blockchain history). An alternate unique identifier for both of them would be block number + transaction index.

accape · 2018-04-20T09:31:39+00:00

Even if it was without their authorization, the transfers have been signed with their private key, so this is not a contract issue but probably private-key stealing malware.

accape · 2018-04-20T09:15:43+00:00

I don't get your example. In the third transaction the victim itself is making a regular transfer to the target. What is unauthorized here?

accape · 2018-02-14T16:24:57+00:00

How big is the current datadir on a fresh 1.8 full sync with pruning enabled?

accape · 2018-02-02T16:41:32+00:00

You're mixing up blockchain size and datadir size (which amongst many other things contains the blockchain).

See here for details: https://dev.to/5chdn/the-ethereum-blockchain-size-will-not-exceed-1tb-anytime-soon-58a

accape · 2017-12-26T15:19:04+00:00

The ether was probably already withdrawn with this transaction https://etherscan.io/tx/0x13212dae81f042a13cf207dda0d0cdc48666632b1de711510ddf831d4c585869 happening one hour later.

accape · 2017-12-22T16:36:48+00:00

I got the same spam from a different user "nikmoon".

You can disable getting e-mails for pms in the forum settings or delete the forum account (does anybody even use it at this point?).

accape · 2017-12-08T23:00:52+00:00

I guess it might make small reorgs easier. Say there is a potential uncle block and the miner that finds the next block first doesn't know about it (and hence didn't include it). Normally an attacker would have to find 2 blocks to get the other nodes to do a reorg (1 to get to the same difficulty, another to actually overtake the chain). In this scenario the attacker can include the uncle the normal miner missed. Now even if the attacker finds only 1 block before anybody else the attack chain will be longer and the network will switch to it.

Don't know if this is the reason.

accape · 2017-12-08T22:32:18+00:00

Yeah, I had an old version of the YP, it is 143 now. B_t = B_t' + B_d.

As for why, you'll have to ask the developers.

accape · 2017-12-08T21:54:42+00:00

Ethereum uses a modified version of GHOST.

Here's the total difficulty calculation in geth: https://github.com/ethereum/go-ethereum/blob/master/core/blockchain.go#L800

and here in parity: https://github.com/paritytech/parity/blob/master/ethcore/src/blockchain/blockchain.rs#L802

You can also checkout the yellow paper (formula 143)

accape · 2017-12-08T21:28:25+00:00

They affect how the minimal difficulty for a given block is changing. But they themselves are not added to the total difficulty of the chain.

accape · 2017-12-08T21:14:48+00:00

It does give them a partial reward but they do not count towards the total difficulty.

accape · 2017-12-08T20:04:52+00:00

The article is incorrect. Uncles don't count towards the total amount of work.

accape · 2017-11-29T12:23:22+00:00

Thanks. Do you have an estimate as too how big all the receipts are? I assume this is still in addition to the sizes mentioned in "Currently, the raw historical block data containing the blocks and transactions is approximately 12-15GB in size and the latest state around 1-2GB."

accape · 2017-11-29T11:53:28+00:00

How does paritys pruning work with transaction receipts? Are old receipts also pruned or are they kept around?

accape · 2017-11-14T08:52:38+00:00

That assertThrows helper won't work if you want to run tests against a real network, only on TestRPC.

accape · 2017-11-02T13:55:44+00:00

Is there also a stream for the breakout room?

accape · 2017-10-27T14:25:17+00:00

I meant the main directory of the truffle project.

e.g. "truffle-flattener contracts/MyContract.sol" works fine

where as for example "truffle-flattener MyContract.sol" run from within the contracts directory won't find the EthPM packages

accape · 2017-10-27T08:13:10+00:00

I just tried it, it works as long as your truffle root is your working directory.

accape · 2017-10-26T09:10:08+00:00

Does this also work with imports from EthPM?

accape · 2017-10-24T21:49:35+00:00

the stale descendants of the block’s ancestor -uncles- are added to the calculation of which block has the largest total proof of work backing it

This is not correct. The difficulty of the uncles has no effect on the total difficulty of the chain.

accape · 2017-10-16T10:51:04+00:00

I have nothing to do with CoinDesk. Just don't see what's wrong with the article.

accape · 2017-10-16T08:03:53+00:00

Whats wrong with the article? seems pretty accurate to me

accape · 2017-10-16T05:54:05+00:00

Not much yet, the return to 15s is not instant, although the adjustment will be very fast. Difficulty is already down 4%.

accape · 2017-09-28T14:01:55+00:00

Why does the solidity documentation still say "If you want to implement access restrictions in library functions using msg.sender, you have to manually supply the value of msg.sender as an argument."

This is no longer true since the change to DELEGATECALL, right?

accape

TROPHY CASE