[Backend] Four pairs of migrations share identical timestamps, making apply order non-deterministic

[grantfox-oss]

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

Why this matters

migrations/ contains colliding prefixes 1777000000007, 1778000000008, 1786000000016 and 1788000000018. The 1788000000018 pair is the most dangerous: unified-contract-events.js renames loan_events to contract_events while add-loan-events-missing-indexes.js creates indexes on loan_events, so order determines whether the migration succeeds.

Acceptance criteria

• Rename one file in each colliding pair to a unique, strictly-increasing timestamp
• Verify a clean npm run migrate:up on an empty DB applies all migrations in a deterministic, correct order
• Confirm the rename does not break the already-applied set on an existing DB (pgmigrations table names)
• Document the convention to avoid future timestamp collisions

Files to touch

• migrations/1788000000018_unified-contract-events.js
• migrations/1788000000018_add-loan-events-missing-indexes.js
• migrations/1777000000007_unique-loan-status-events.js
• migrations/1786000000016_webhook-max-attempts.js

Out of scope

• Rewriting the migration logic itself
• Squashing historical migrations

[midexol]

Hi, I'd like to work on this.

[Bug-Hunter-X]

I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. Thank you

[umohjosephemmanuel-cyber]

Software Engineer and Full-Stack Developer with experience building and maintaining backend systems using JavaScript, TypeScript, Node.js, Express, and PostgreSQL. Skilled in database migrations, schema management, and ensuring data consistency across complex applications. Passionate about clean architecture, maintainable code, and improving system reliability. Experienced in analyzing existing codebases, resolving migration conflicts, and enforcing development best practices. Familiar with version control, database indexing, and deterministic deployment workflows. Capable of debugging migration issues while preserving compatibility with existing production environments. Strong understanding of backend development, REST APIs, and scalable system design. Enthusiastic about open-source collaboration and contributing meaningful improvements to projects. Committed to writing clear documentation and establishing standards that prevent future issues. Dedicated to building reliable, maintainable, and developer-friendly software systems.

[Banx17]

Hello team, i will love to work on this issue for your team.

[Arome8240]

Hello, I'm a smart contract and full stack developer, open for contributions. contributed to over 20 project on OnlyDust and Drips , with expertise in Solidity, Cairo, JavaScript, TypeScript, and RUST. I am passionate about building secure and scalable blockchain solutions, and I would love the opportunity to contribute my skills toward solving this issue.

[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.

[david87131]

Applying

[davidmaronio]

testing

[MerlinTheWhiz]

Hello, I'm MerlinThewhiz, a software engineer with a strong background in smart contract, and a couple years in my arsenal. Having read the task requirement, I'd love to work on this issue. Please assign.