There may or may not be ethical issues with looking in the Journal records even though it is technically common place these days. Just incase I have wrapped my research into a spoiler tag. If you have any issues with looking in the journal please feel free to pass up this post.
-Void
This is Persephone as viewed from the developer's video, blink and you will miss it @ 36:50
[video=youtube;Vz3nhCykZNw]https://www.youtube.com/watch?v=Vz3nhCykZNw[/video]
Note the following snip it:
Unfortunately Persephone doesn't have a reported moon in game that you can discover with the navbeacon or maps making it a little suspicious that it would be in the video with the devs. So in my attempt to find a way to determine whether or not there was indeed a hidden body I looked at the Nav Beacon scans in the Journal Records (Courtesy of Cmdr Xeno):
Within each record the following data entries exist:
I decided to put these in order by body ID in the logs and see what came out.
I found Body ID's do not provide any conclusive evidence that there is or was ever a moon around Persephone as Persephone has the very last Body ID in the scan. There very well may be a moon around Persephone that isn't hinted at in the scan because it would be labeled as Body ID 47. Either way, no questions answered, only more have been asked.
For Body IDs 6, 8, 14, 23, 29, and 31 cross referenced their location's in order with the actual system map for Sol and determined that these are most likely place holders or relics for Rings and Belts except for Body ID: 21. This falls between Saturn and Uranus. There is nothing in this location in game, meaning it could be anything from a hidden moon of Saturn or another body between Saturn and Uranus.
There are also notable oddities in Pluto and Charon's Parent Values as well where they appear to have been in orbit around a now redacted object that fell under Body ID 31. Judging by the System map for our solar system I believe body ID 31 is actually a place holder for the Keiper belt. Notably both objects are KBOs so it would make sense that some previous system ordered them as KBOs thus being a child of the KB Body. The Null pointer is mildly concerning from a developer standpoint but otherwise appears to have no other implications.
If I uncover more in my Independent Research I will post it here.
[video=youtube;Vz3nhCykZNw]https://www.youtube.com/watch?v=Vz3nhCykZNw[/video]
Note the following snip it:

Unfortunately Persephone doesn't have a reported moon in game that you can discover with the navbeacon or maps making it a little suspicious that it would be in the video with the devs. So in my attempt to find a way to determine whether or not there was indeed a hidden body I looked at the Nav Beacon scans in the Journal Records (Courtesy of Cmdr Xeno):
Within each record the following data entries exist:

I decided to put these in order by body ID in the logs and see what came out.

I found Body ID's do not provide any conclusive evidence that there is or was ever a moon around Persephone as Persephone has the very last Body ID in the scan. There very well may be a moon around Persephone that isn't hinted at in the scan because it would be labeled as Body ID 47. Either way, no questions answered, only more have been asked.
For Body IDs 6, 8, 14, 23, 29, and 31 cross referenced their location's in order with the actual system map for Sol and determined that these are most likely place holders or relics for Rings and Belts except for Body ID: 21. This falls between Saturn and Uranus. There is nothing in this location in game, meaning it could be anything from a hidden moon of Saturn or another body between Saturn and Uranus.

There are also notable oddities in Pluto and Charon's Parent Values as well where they appear to have been in orbit around a now redacted object that fell under Body ID 31. Judging by the System map for our solar system I believe body ID 31 is actually a place holder for the Keiper belt. Notably both objects are KBOs so it would make sense that some previous system ordered them as KBOs thus being a child of the KB Body. The Null pointer is mildly concerning from a developer standpoint but otherwise appears to have no other implications.
If I uncover more in my Independent Research I will post it here.
-Void
Last edited: