Edited By
Olivia Johnson

A rising concern among developers highlights the risk of Public Derivable Addresses (PDAs) resulting in conflicts. A program generating PDAs based on a monthly seed could fail if an attacker exploits the same seed to create a conflicting PDA. This has raised alarm bells within the crypto community.
The situation arises when different programs use the same seed to create PDAs. An example from a concerned developer shows that generating one PDA monthly with a reference like "2025-04" could lead to a problem if someone else generates one using "2025-05".
Developers chimed in with solutions and opinions:
Unique Identification: One commenter emphasized that "your PDA always has your program ID. Even if someone generates the same PDA, it doesnβt matter unless they control the program."
Entropy Concerns: Another user warned, "Oh hell no are you generating your own awful entropy keys?" highlighting the need for robust methods in creating random seeds.
Predictability Issues: One user pointed out, "This is also predictable, is it not?" suggesting that predictability could be a major weakness in the design.
"Thanks, Iβm new to Solana. I just did a test When two programs generate two PDAs, they will never generate the same address, even if they use the same seed."
This reassurance calmed some fears about duplicate addresses.
π οΈ Seed Management: Ensuring that the seed is unique to each program prevents conflicts.
π Security Measures: Users should adopt better methods in generating entropies to avoid vulnerabilities.
π Community Consensus: Most commenters agree that the built-in safeguards of the system provide sufficient protection against address duplication.
With the unique identification of programs tied to PDAs, many believe the risk is manageable. Nevertheless, developers must remain vigilant. Regular discussions on forums and user boards help refine approaches in safeguarding crypto applications, ensuring a secure environment in an ever-evolving space.