Discussed with @odeimaiz

Proposed solution:

• When a user attempts to change the wallet on a project, this change is prohibited if the current wallet has a negative balance.
• We introduce a new endpoint that will "pay off the debt" and unblock the ability to change the wallet on the project resource. (OM: unblock it in general, right?)

Discussed with @odeimaiz

Proposed solution:

• When a user attempts to change the wallet on a project, this change is prohibited if the current wallet has a negative balance.
• We introduce a new endpoint that will "pay off the debt" and unblock the ability to change the wallet on the project resource. (OM: unblock it in general, right?)

Additional discussion with @odeimaiz @pcrespov

• We need to introduce new state IN_DEBT to understand the debt of the project
• We need to introduce transfer of credits between wallets
• We need to introduce new endpoint to "pay the debt" = "transfer credits from wallet to another"

Research: https://github.com/beancount/beancount

Discussed with @odeimaiz
Proposed solution:

• When a user attempts to change the wallet on a project, this change is prohibited if the current wallet has a negative balance.
• We introduce a new endpoint that will "pay off the debt" and unblock the ability to change the wallet on the project resource. (OM: unblock it in general, right?)

Additional discussion with @odeimaiz @pcrespov

• We need to introduce new state IN_DEBT to understand the debt of the project
• We need to introduce transfer of credits between wallets
• We need to introduce new endpoint to "pay the debt" = "transfer credits from wallet to another"

Research: https://github.com/beancount/beancount
Here’s the formatted version for easy copy-pasting:

Beancount Overview

Beancount is an open-source double-entry accounting system that is highly specialized for accounting and bookkeeping. It is designed for financial accuracy and might offer features that align with your requirements.

Pros of Beancount

• Double-Entry Accounting:

  • Every transaction is recorded in two accounts (credit and debit), ensuring financial accuracy.
  • Prevents common errors like balance mismatches.

• Time-Tested Accounting Model:

  • Handles edge cases like rounding errors and concurrency issues in financial transactions.

• Simplicity in Integration:

  • Provides a format and tools for recording and querying transactions.

• Open Source and Lightweight:

  • You can customize it if needed, without licensing concerns.

Cons of Beancount

• Not Designed for Real-Time Operations:

  • Beancount is file-based and not optimized for high-frequency updates or real-time systems.
  • Parsing large transaction logs might become a bottleneck.

• Requires Custom Adapters:

  • You’ll need to write integration layers between your service and Beancount for API-driven updates.

• Less Scalable for Complex Rules:

  • If your system has dynamic rules (e.g., promotional credits, tier-based deductions), you might outgrow Beancount quickly.