Cardano Updates

Remove redundant idx_transaction_block_hash_tx_index index as the existing idx_transaction_slot_desc_tx_index_desc already provides efficient query performance for block transaction retrieval with proper ordering.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Add complete read path for DRep vote delegations including database entities, repository, and service layer integration. Rename DelegationEntity to PoolDelegationEntity across codebase to distinguish pool delegation from vote delegation. Add GovernanceTransactions test generator for creating DRep registration and delegation test data.

Key changes:
- Add DrepVoteDelegationEntity, DrepVoteDelegationId, and DrepVoteDelegationRepository
- Rename DelegationEntity → PoolDelegationEntity and update all references
- Integrate DRep delegation queries with certIndex filter in LedgerBlockServiceImpl
- Add mapper methods for DRep delegation entity-to-domain conversion
- Add GovernanceTransactions class with DRep registration and delegation transactions
- Update TestTransactionNames enum with DREP_REGISTER and DREP_VOTE_DELEGATION

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Add database entities, repository, and service layer integration to support reading DRep vote delegations from the vote_delegation table. This completes the read path for governance delegation operations, complementing the existing construction endpoints. Filters results to certIndex == 0 as per requirements.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Problem:
- Pre-release builds were failing with "invalid tag" error
- Action expected .env file in root which doesn't exist
- When .env was missing, script exited silently (exit 0) but outputs were unset
- This caused Docker tags to be empty (e.g., "cardano-node:") causing build failures

Solution:
- Changed action to read from .env.docker-compose (which exists and contains all needed variables)
- Changed exit 0 to exit 1 for fail-fast behavior
- Added error messages when variables are not found
- Added debug output showing found values

This fixes the issue introduced in commit b9f1b0467 where versions were separated
for cardano-node, postgres, and mithril in DockerHub, but the action wasn't updated
to read from the correct source file.

Variables now correctly read from .env.docker-compose:
- CARDANO_NODE_VERSION=10.5.1
- PG_VERSION_TAG=REL_14_11
- MITHRIL_VERSION=2537.0

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

transactions are ordered correctly within blocks (0, 1, 2, ...) and in search results.

Changes:
- Added txIndex field to TxnEntity JPA entity
- Updated JOOQ Transaction and TransactionRecord classes to include TX_INDEX field
- Modified TxRepositoryQueryBuilder to select and map tx_index in queries
- Updated search query ordering to use (slot DESC, tx_index DESC)
- Updated block transaction query to order by tx_index ASC

This ensures:
- Transactions within blocks are returned in correct order (0, 1, 2, ...)
- Search results maintain proper chronological and within-slot ordering
- Consistent pagination for /search/transactions API
- Proper ordering for /block and /block/transaction endpoints

Changes:
- Modified Index 6: idx_transaction_slot_desc_tx_index_desc (replaces tx_hash with tx_index)
  - Query pattern: ORDER BY slot DESC, tx_index DESC
  - Provides deterministic pagination for /search/transactions
- Added Index 7: idx_transaction_block_hash_tx_index
  - Composite index on (block_hash, tx_index)
  - Ensures transactions within blocks are ordered correctly (0, 1, 2, ...)
  - Optimizes /block and /block/transaction endpoints

This prepares the database schema for Yaci-Store 2.0.0-beta tx_index column support.
Since 2.0.0 will reindex from genesis, no DROP INDEX or migration files needed.

transactions are ordered correctly within blocks (0, 1, 2, ...) and in search results.

Changes:
- Added txIndex field to TxnEntity JPA entity
- Updated JOOQ Transaction and TransactionRecord classes to include TX_INDEX field
- Modified TxRepositoryQueryBuilder to select and map tx_index in queries
- Updated search query ordering to use (slot DESC, tx_index DESC)
- Updated block transaction query to order by tx_index ASC
- Created database migration V1.0_2501_0 with optimized indexes:
  - idx_transaction_block_hash_tx_index for block transaction ordering
  - idx_transaction_slot_desc_tx_index_desc (PostgreSQL) for search pagination
  - idx_transaction_slot_tx_index (H2) for search pagination
  - Drops old idx_transaction_slot_desc_tx_hash index

This ensures:
- Transactions within blocks are returned in correct order (0, 1, 2, ...)
- Search results maintain proper chronological and within-slot ordering
- Consistent pagination for /search/transactions API
- Proper ordering for /block and /block/transaction endpoints

transactions are ordered correctly within blocks (0, 1, 2, ...) and in search results.

Changes:
- Added txIndex field to TxnEntity JPA entity
- Updated JOOQ Transaction and TransactionRecord classes to include TX_INDEX field
- Modified TxRepositoryQueryBuilder to select and map tx_index in queries
- Updated search query ordering to use (slot DESC, tx_index DESC)
- Updated block transaction query to order by tx_index ASC
- Created database migration V1.0_2501_0 with optimized indexes:
  - idx_transaction_block_hash_tx_index for block transaction ordering
  - idx_transaction_slot_desc_tx_index_desc (PostgreSQL) for search pagination
  - idx_transaction_slot_tx_index (H2) for search pagination
  - Drops old idx_transaction_slot_desc_tx_hash index

This ensures:
- Transactions within blocks are returned in correct order (0, 1, 2, ...)
- Search results maintain proper chronological and within-slot ordering
- Consistent pagination for /search/transactions API
- Proper ordering for /block and /block/transaction endpoints

transactions are ordered correctly within blocks (0, 1, 2, ...) and in search results.

Changes:
- Added txIndex field to TxnEntity JPA entity
- Updated JOOQ Transaction and TransactionRecord classes to include TX_INDEX field
- Modified TxRepositoryQueryBuilder to select and map tx_index in queries
- Updated search query ordering to use (slot DESC, tx_index DESC)
- Updated block transaction query to order by tx_index ASC
- Created database migration V1.0_2501_0 with optimized indexes:
  - idx_transaction_block_hash_tx_index for block transaction ordering
  - idx_transaction_slot_desc_tx_index_desc (PostgreSQL) for search pagination
  - idx_transaction_slot_tx_index (H2) for search pagination
  - Drops old idx_transaction_slot_desc_tx_hash index

This ensures:
- Transactions within blocks are returned in correct order (0, 1, 2, ...)
- Search results maintain proper chronological and within-slot ordering
- Consistent pagination for /search/transactions API
- Proper ordering for /block and /block/transaction endpoints

Regenerated all JOOQ table and record classes to reflect current database schema
with consistent formatting and field ordering.

Changes:
- Updated all JOOQ table classes (Transaction, Block, Address, AddressUtxo, etc.)
- Updated all JOOQ record classes with consistent getter/setter ordering
- Applied consistent code formatting across all generated files

Affected tables:
- Transaction and TransactionRecord
- Block, Address, AddressUtxo
- Delegation, StakeRegistration
- PoolRegistration, PoolRetirement
- Error, InvalidTransaction
- And all other schema tables (48 files total)

Generated from database schema using JOOQ code generator.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Mateusz Czeladka <[email protected]>
Co-authored-by: Claude <[email protected]>

Regenerated all JOOQ table and record classes to reflect current database schema
with consistent formatting and field ordering.

Changes:
- Updated all JOOQ table classes (Transaction, Block, Address, AddressUtxo, etc.)
- Updated all JOOQ record classes with consistent getter/setter ordering
- Applied consistent code formatting across all generated files

Affected tables:
- Transaction and TransactionRecord
- Block, Address, AddressUtxo
- Delegation, StakeRegistration
- PoolRegistration, PoolRetirement
- Error, InvalidTransaction
- And all other schema tables (48 files total)

Generated from database schema using JOOQ code generator.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Updated project version from 2.0.0-beta to 2.1.0-beta for new development cycle.

Changes:
- Set revision to 2.1.0-beta in root pom.xml
- Updated yaci-indexer version to 2.1.0-beta

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Reverting version back to 2.0.0-beta for continued development.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

PostgreSQL 15+ changed the default security model where the PUBLIC role
no longer has CREATE privilege on the public schema. This caused Flyway
migrations to fail during integration tests with "permission denied for
schema public" errors.

Added explicit GRANT commands to:
- Grant all privileges on the public schema to the database user
- Grant privileges on all existing tables in the schema
- Set default privileges for future tables created in the schema

This fix ensures the yaci-indexer can successfully run database migrations
during Docker container initialization.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Release version 2.0.0 with peer discovery improvements:
- Limited peer responses to 25 peers with randomization
- Disabled PEER_DISCOVERY by default for mainnet
- Enabled PEER_DISCOVERY for preprod environments only

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

PEER_DISCOVERY is now disabled by default for mainnet deployments
to reduce unnecessary peer discovery is still in beta version. It remains enabled
for preprod environments where dynamic peer discovery is less risky.

Changes:
- Set PEER_DISCOVERY=false in .env.docker-compose (mainnet)
- Preprod configurations keep PEER_DISCOVERY=true

Implements peer limiting and randomization to improve network peer distribution:
- Limits peer responses to 25 peers (configurable via MAX_PEERS constant)
- Randomizes peer selection on each load/discovery to avoid always returning the same peers
- Updates PeerSnapshotServiceImpl to shuffle and limit peers from snapshot files
- Updates PeerDiscoveryManager to shuffle and limit discovered peers from cardano-node
- Maintains deterministic in-memory cache between refreshes
- Updates tests to reflect new peer limiting and randomization behavior

This prevents excessive peer lists and naturally distributes connections across the network
without needing to track peer performance metrics.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Change the hardcoded retirement epoch from 19 to 2 to fix validation
errors on fresh devkit/testnet environments where current epoch is 0.

The Cardano protocol requires:
  current_epoch < retirement_epoch <= current_epoch + eMax (18)

With epoch 0, retirement epoch 19 exceeds the maximum allowed offset,
causing StakePoolRetirementWrongEpochPOOL validation errors.

Using epoch 2 provides a conservative offset that works on fresh chains
while still allowing successful pool retirement testing.

Changes:
- Update pool retirement epoch from 19 to 2 in PoolTransactions.java
- Update devkit genesis configuration and test data

Related error:
  StakePoolRetirementWrongEpochPOOL
  (Mismatch {mismatchSupplied = EpochNo 19, mismatchExpected = EpochNo 0})

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>