It looks like EagleSong is a brand new hash function that does not have peer reviewed security properties though EagleSong combines ideas from Keccak and BLAKE2. My questions are:
What are the goals for creating a new PoW? Is ASIC resistance a goal or a non-goal? Or Energy efficiency?
Why not use an existing hash function that has published/peer reviewed security properties?
There is a bit of motivation in this medium article. I agree that the RFC should contain some background, or at least it should be clear where motivation and design rationale can be found.
It looks like EagleSong is a brand new hash function that does not have peer reviewed security properties though EagleSong combines ideas from Keccak and BLAKE2. My questions are: