[DOC] Best practices for app devs on how to validate recipient address

[frol]

Documentation Type

New Documentation

What needs documentation?

It would be nice to have a guide/best practices reference for the application developers who require users to input recipient account. Invalid account id is often a source of problems and funds lost.

Wallets often try to implement some validation and proactively help users to make sure they don't lose their assets. Yet, currently, each application developer reinvent the wheel. Here is a good strategy (see the full thread attached below):

I would show if account exists onchain as primary check. Then you can also cross it with HAPI or other risk scores. Can check accounts “net worth” across other assets if it’s minuscule also should consider it as new account.

For new accounts (eg doesn’t exist onchain) it’s better to get either explicit confirmation or suggest test transaction

Acceptance Criteria

• The best practice is formulated in an easy to follow manner with examples of the typical NEAR accounts (.near, .tg, .sweat, implicit accounts, 0x accounts)
• The article is placed in a place where it would be easy to discover when the readers needs it the most (during the development of a frontend app)
• The article is cross-linked from all the relevant places throughout the docs
• Reach out to MeteorWallet and HOT Wallet teams for review and collaboration

Resources & References

Priority

🟢 P3 : Nice to Have