Prop 327, Fix mistaken mention of floating point

This is a mistake I made earlier. I mentioned floating point performance
when describing HashX, there's no floating point in HashX.

HashX is based on SuperscalarHash which is a simplified dataset-bootstrapping
environment within RandomX. HashX and SuperscalarHash are integer-only,
only the full RandomX algorithm used floating point.

1 files changed, 5 insertions, 5 deletions

diff --git a/proposals/327-pow-over-intro.txt b/proposals/327-pow-over-intro.txt
index 3765b8b..db17c06 100644
--- a/proposals/327-pow-over-intro.txt
+++ b/proposals/327-pow-over-intro.txt
@@ -167,11 +167,11 @@ Status: Draft
 
   1) At the lowest layers, blake2b and siphash are used as hashing and PRNG
      algorithms that are well suited to common 64-bit CPUs.
-  2) A custom hash function, HashX, uses dynamically generated functions that
-     are tuned to be a good match for pipelined integer and floating point
-     performance on current 64-bit CPUs. This layer provides the strongest ASIC
-     resistance, since a reimplementation in hardware would need to implement
-     much of a CPU to compute these functions efficiently.
+  2) A custom hash function family, HashX, randomizes its implementation for
+     each new seed value. These functions are tuned to utilize the pipelined
+     integer performance on a modern 64-bit CPU. This layer provides the
+     strongest ASIC resistance, since a hardware reimplementation would need
+     to include a CPU-like pipelined execution unit to keep up.
   3) The Equi-X layer itself builds on HashX and adds an algorithmic puzzle
      that's designed to be strongly asymmetric and to require RAM to solve
      efficiently.