Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Sandbox

Comments on 💥 CHALLENGE: Find a Collision in Leviathan v3.1 (Deterministic)

Post

💥 CHALLENGE: Find a Collision in Leviathan v3.1 (Deterministic)

+0
−2

The Context: I have officially deprecated SHA-2 and SHA-3. This decision stems from a critical security breach I witnessed: a virus that infected my system using forged digital signatures that were somehow validated as authentic by current standards. This proved that the 'trust' in existing hashing algorithms is compromised. Consequently, I have engineered Leviathan v3.1 Turbo to replace them with a system that doesn't just verify, but defends.

The Logic: This algorithm uses a Fractal Carry system and a massive 10,000-digit Prime Constant to ensure that even the slightest bit-flip in the input causes a catastrophic avalanche in the output.

The Task: Simple. Find a Collision. Find two distinct inputs (strings or byte arrays) and such that:

$$Leviathan(M_1) == Leviathan(M_2)$$

Where $M_1 \neq M_2$

The Code: The algorithm is fully DETERMINISTIC. No random salts. Pure math. Get the Source Code Here (OSF)

Why you will fail:

  • The "Displaced Mutation Buffer" prevents linear collisions.
  • The output space is 1024 characters. The Pigeonhole Principle is on my side, not yours.
  • The internal state evolves fractally, meaning depends non-linearly on .

Rules There will be a maximum of 3 winners. The first 3 to succeed will win, and they must present the algorithm or explain how their code works.

Prize: The glory of breaking the first post-NIST hash algorithm.

"Good luck. You'll need more than a supercomputer; you'll need a new dimension."

History

2 comment threads

Challenge should be self-contained (1 comment)
Challenge type and scoring (3 comments)
Challenge type and scoring
trichoplax‭ wrote 8 months ago

The challenge wording suggests that the goal is to find a collision. This would suggest that the first answer will win, and that there is no meaning in having any further answers. However, the challenge is tagged "code-golf", suggesting that there can be multiple answers and the shortest code wins. Is an answer expected to contain code? Is there expected to be more than one answer, with a way of scoring them, or is the maximum meaningful number of answers intended to be 1?

KaoruAK‭ wrote 8 months ago

Basically, the first three people will win. They will have to explain how they made the algorithm, or how they achieved it.

trichoplax‭ wrote 8 months ago

If there isn't a way to score the answers so that they can be sorted into order, it seems arbitrary to restrict to 3 winners. I could understand "first to answer wins" or "everyone who answers wins", although I wouldn't necessarily expect either of those to be on topic here.

Generally each challenge has a way of scoring each answer. There could potentially be a Meta discussion about whether to have other types of challenge that do not have scoring, and what that would mean.