search

opentimestamps / python-opentimestamps

Other
87 stars 39 forks source link

Scrypt Op #44

Closed NCGThompson closed 3 years ago

NCGThompson commented 3 years ago

Even if no current OTS implementations support Litecoin (LTC), Scrypt should at least be in the .ots vocabulary.

In order for a proof to be verified with just a trusted block header, the .ots files need to contain a Merkle brach of the blockchain used. Since LTC uses Scrypt as its hash function, the .ots needs to convey the Scrypt hash function if LTC is used.

Development on LTC support by a third party can't start until there is a consensus on how to serialize/deserialize Scrypt.

petertodd commented 3 years ago

On Fri, Mar 12, 2021 at 08:54:45PM -0800, Nic wrote:

Even if no current OTS implementations support Litecoin (LTC), Scrypt should at least be in the .ots vocabulary.

In order for a proof to be verified with just a trusted block header, the .ots files need to contain a Merkle brach of the blockchain used. Since LTC uses Scrypt as its hash function, the .ots needs to convey the Scrypt hash function if LTC is used.

Development on LTC support by a third party can't start until there is a consensus on how to serialize/deserialize Scrypt.

You're mistaken. Litecoin only uses Scrypt for its proof-of-work function. The merkle tree itself uses SHA256, just like Bitcoin.

-- https://petertodd.org @.***

NCGThompson commented 3 years ago

You're mistaken. Litecoin only uses Scrypt for its proof-of-work function. The merkle tree itself uses SHA256, just like Bitcoin.

I stand corrected. Here is some source code that uses SHA256D64.

Scrypt is pretty useless unless we are worried about a presage attack.