[Contracts] RemittanceNFT transfer moves seized/default state to recipient, enabling reputation laundering

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

transfer in remittance_nft/src/lib.rs copies Metadata, ScoreHistory, DefaultCount, and Seized to the destination but a seized borrower can still call transfer (only from.require_auth() and not-paused are required; is_seized is never checked). The seized borrower can offload the NFT, and conversely the score/seized flags are not tied to outstanding loans in loan_manager, so transfer can move credit standing in ways the lending logic does not expect.

Acceptance criteria

• Decide and enforce whether seized or NFTs with active loans may be transferred; block transfer when is_seized or when an active loan references the holder
• Ensure DefaultCount/Seized cannot be shed by transferring to a fresh address
• Add tests for transfer attempts by seized users and by users with active loans
• Document transfer eligibility rules alongside the seize_collateral doc comment

Files to touch

• remittance_nft/src/lib.rs
• loan_manager/src/lib.rs

Out of scope

• Making the NFT non-transferable entirely (unless chosen as the fix)
• Cross-contract active-loan registry redesign

[gloskull]

Hello, I have 4 years of experience delivering solutions for projects like this, covering backend, frontend, and smart contract development. After carefully reviewing your requirements, I have a clear understanding of the task and am confident in my ability to deliver a clean, efficient, and thoroughly tested solution on time. I prioritize code quality, maintainability, and industry best practices throughout the development process.

[iyanumajekodunmi756]

Hi maintainer, I would love to work on this issue. I have studied the details of the issue description and I understood the requirements. I shall deliver with qualitative feedback and promptly.

[grantfox-oss]

🦊 GrantFox — @iyanumajekodunmi756 has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #12)
2. Your PR will be reviewed by the LabsCrypt maintainers

Good luck! Track your progress on GrantFox.