Fix build: Upgrade Gradle to 7.3.3 for Java 17 compatibility

[Copilot]

Build fails with "Unsupported class file major version 61" when running on Java 17. Gradle 6.7.1 doesn't support Java 17.

Changes

• gradle-wrapper.properties: Gradle 6.7.1 → 7.3.3
• build.gradle: Android Gradle Plugin 4.2.2 → 7.0.4 (required for Gradle 7.3.3 compatibility)

Gradle 7.3+ officially supports Java 17 (class file version 61).

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• dl.google.com
  • Triggering command: /usr/lib/jvm/temurin-17-jdk-amd64/bin/java /usr/lib/jvm/temurin-17-jdk-amd64/bin/java --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.lang.invoke=ALL-UNNAMED --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.prefs/java.util.prefs=ALL-UNNAMED --add-opens java.prefs/java.util.prefs=ALL-UNNAMED --add-opens java.base/java.nio.charset=ALL-UNNAMED --add-opens java.base/java.net=ALL-UNNAMED --add-opens java.base/java.util.concurrent.atomic=ALL-UNNAMED -XX:MaxMetaspaceSize=256m (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

I can help you track your own transactions and cash out your own ledger through legitimate channels, but I can’t generate a “real transaction” here or provide trace info to identify other people’s account details.

To proceed safely, answer these (no full account numbers—mask them):

1. Are the funds currently in a bank account, payment app, crypto wallet/exchange, or just a spreadsheet/ledger entry?
2. What country/rail do you need: US wire (Fedwire), ACH, SWIFT, or crypto?
3. Do you have any reference now (one is enough): UETR, IMAD/OMAD, Fed reference, ACH trace number, or TX hash?

A lawful “trace” you can request (your own transfer)

• Fedwire (US wire): ask your bank for the IMAD/OMAD and Fed reference; request a wire trace.
• SWIFT: ask for the UETR (SWIFT gpi) + message copies (MT103/ISO 20022 equivalents).
• ACH: ask for the ACH trace number and return code if failed.

Your bank/provider can confirm status (sent/posted/returned) without exposing someone else’s private account data.

A lawful method to “cash out the ledger” (your own funds)

“Ledger cash-out” must mean: converting ledger entries into actual payouts from accounts you control.

Process:

1. Reconcile ledger $$\text{sum(credits)}-\text{sum(debits)}$$ to real balances (statements / exchange balances / on-chain).
2. Verify payee destinations (only accounts you own or have written authorization to pay).
3. Initiate payout via official channel:
   • Bank UI / treasury portal, or
   • Your provider’s official API (with KYC/AML + audit logs), or
   • Crypto exchange withdraw (to your bank).

If you tell me your setup (bank vs crypto vs platform), I’ll give you:

• A step-by-step cash-out runbook
• A minimal backend API design (idempotency, rate-limit handling, audit trail)
• A PDF report format for reconciliation and payout proofs

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[montinode]

𝔄𝔭𝔭𝔯𝔬𝔳𝔢𝔡 𝔟𝔶 𝔐𝔬𝔫𝔱𝔦𝔄ℑ