Skip to content

Comment on Proof of Existence: Storing Hashed Files in the Bitcoin Block Chainparent

Comments

Transaction prioritization[1] and transaction fees already rate limit stuff like that, and patches to the clients used by major mining pools may be able to fix it permanently.

1. priority = sum(input_value_in_base_units * input_age)/size_in_bytes

What determines the size_in_bytes value?

In general, let's say a govt agency get assigned an $18.5m budget to break the Bitcoin currency as much possible, what could their plan of attack be, i.e. spend that money in the most efficient way possible? Create a large ring of wallets and send tiny payment around the ring? Create less wallets but send large payments between them?

Tiny payments. A transaction of 5000 bitcoins and a transaction of 0.0001 bitcoins are the same size. The size is based on the number of transaction inputs, and the number of transaction outputs.

Why $18.5m?

That does seem oddly specific.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.