From d3469a91f2ad82fa0aca8677e6f6fb83c97b66fb Mon Sep 17 00:00:00 2001
From: Louis <contact@boul2gom.com>
Date: Tue, 7 Apr 2026 16:28:01 +0200
Subject: [PATCH] Refactor: Use Encryptable concern in CoinbaseItem (#1339)

Remove the duplicated encryption_ready? method in favor of the Encryptable concern which provides the exact same functionality.
---
 app/models/coinbase_item.rb | 10 +---------
 1 file changed, 1 insertion(+), 9 deletions(-)

diff --git a/app/models/coinbase_item.rb b/app/models/coinbase_item.rb
index 6641958e6..0adf2fe11 100644
--- a/app/models/coinbase_item.rb
+++ b/app/models/coinbase_item.rb
@@ -1,17 +1,9 @@
 class CoinbaseItem < ApplicationRecord
   include Syncable, Provided, Unlinking
+  include Encryptable
 
   enum :status, { good: "good", requires_update: "requires_update" }, default: :good
 
-  # Helper to detect if ActiveRecord Encryption is configured for this app
-  def self.encryption_ready?
-    creds_ready = Rails.application.credentials.active_record_encryption.present?
-    env_ready = ENV["ACTIVE_RECORD_ENCRYPTION_PRIMARY_KEY"].present? &&
-                ENV["ACTIVE_RECORD_ENCRYPTION_DETERMINISTIC_KEY"].present? &&
-                ENV["ACTIVE_RECORD_ENCRYPTION_KEY_DERIVATION_SALT"].present?
-    creds_ready || env_ready
-  end
-
   # Encrypt sensitive credentials if ActiveRecord encryption is configured
   # api_key uses deterministic encryption for querying, api_secret uses standard encryption
   if encryption_ready?