Cursor vs Offset Pagination

Design a paginated REST API endpoint that returns a list of transactions for a Coinbase wallet. The endpoint must support BOTH offset-based and cursor-based pagination and allow the caller to choose which method to use via a query parameter. Your task is to:

1. Explain the performance and consistency trade-offs between offset and cursor pagination.
2. Implement the SQL queries and pseudo-code for each strategy.
3. Return the appropriate metadata in the JSON response so the client can request the next page (total count and page numbers for offset; next_cursor for cursor).
4. Discuss which strategy you would recommend for a public mobile API that serves millions of wallets with high write throughput and why.

Assume the transactions table has columns: id (UUID), wallet_id, amount, currency, created_at (timestamp), and is_deleted (boolean). The primary read pattern is listing the most recent transactions first (ORDER BY created_at DESC, id DESC).