timbowhite

I like this strategy a lot, but the performance of read queries suffer if they span partitions, correct?

The issue I'm facing is a very large table, that is both write and read heavy, and the reads do not fall into a specific range of values for any particular column, so I don't think partitioning is an option.

In Bitcoin's case, public keys are only revealed during a transaction.

And every transaction completely spends the source keypairs' funds.

So the only attack vector a quantum computer could use is:

1. Observing newly broadcast/unconfirmed transactions

2. Deriving the private key(s) from the public key(s)

3. Creating and broadcasting its own transaction using the stolen keypairs before the original transaction confirms (presumably with a higher fee to win the confirmation race).

Please correct me if I'm wrong.

EDIT: correction: every transaction completely spends any selected UTXO of an associated keypair, not all of the "source keypairs' funds". Thus the attack vector also includes being able to steal from any keypair that has ever made a transaction and also has UTXOs.

> I maintain Express.js and Lodash

Thank you!

> In 2025 I made $10 from open source

Slightly off-topic, but I wish more OSS projects and maintainers would advertise cryptocurrency donation addresses. It's probably the easiest way for end users to donate.

Is this the same collision theorized to have created the moon?

I run independent websites and I'm not broke yet.

Pretty neat.

How would the multiplier DCA act during a multi-month "crypto winter"?

I'm honestly ignorant - what political statement is it making?

It seems that liberals dislike Teslas because they dislike Elon Musk.

And conservatives dislike Teslas because they dislike new and different things.