I did my best to explain in the opening post
Please re-read that first post, & look at the source code changes to understand what is going on.
It provides:
1. A mechanism to enable oscam to uniquely identify a feed & retrieve the correct BISS key. Exisitng methods in SoftCam.Key & constant.cw are weak here, as feeds quite often have identical sid/pmt/vpid etc, but different keys. Channel zapping between encrypted feeds is then impossible without editing the key files on-the-go.
2. A template SoftCam.Key entry which includes transponder details & timestamp. If copy/pasted into your SoftCam.key this builds into a log of your feedhunting history.
It does this whilst retaining full compatibilty with the previous methods, so you can ignore it if you so wish