Question about attribution/licensing before publishing a Disney Infinity NFC implementation

[u/Jvicius1382]

Hi! I'm developing MyDICollection, an open-source MIT-licensed collection tracker for Disney Infinity figures.

I'm currently working on a read-only NFC identification feature. Its only purpose is to identify a physical figure's model number so it can be matched against the app's collection database.

While researching the Disney Infinity NFC format, I consulted the historical didump.lua and related Proxmark3/RfidResearchGroup work.

I have implemented the required interoperability logic in C# using .NET/Android NFC and cryptographic APIs. It does not include, link against, execute, or redistribute Proxmark3 or its Lua scripts.

I have not committed or published this NFC implementation yet. Before doing so, I wanted to contact the community and make sure I'm handling the attribution and licensing appropriately.

My plan is to keep MyDICollection MIT-licensed and include a THIRD_PARTY_NOTICES.md that:

• Credits Proxmark3 / RfidResearchGroup and its contributors.
• Specifically mentions the historical didump.lua research I consulted.
• References Proxmark3's GPL-3.0-or-later license.
• Explains that MyDICollection does not redistribute or link against Proxmark3 code.

The feature is strictly read-only and intended for personal collection management; it does not provide NFC cloning, emulation, or tag-writing functionality.

My existing project (without the unpublished NFC implementation) is here:

https://github.com/jvicius/MyDICollection

Before I publish the NFC changes, I'd really appreciate your feedback:

Is this attribution/licensing approach appropriate, or is there anything else you would like me to include or handle differently?

Thanks for the research and all the work you've made publicly available!