solace 0.1.5 → 0.1.6

data/CHANGELOG

@@ -1,243 +0,0 @@
-# Change Log
-
-All notable changes to this project will be documented in this file.
-
-The format is based on [Keep a Changelog](http://keepachangelog.com/) and this project adheres to [Semantic Versioning](http://semver.org/).
-
-### Template
-
-```markdown
-## [VERSION] - yyyy-mm-dd
-
-### Added
-
-1.
-
-### Changed
-
-### Fixed
-```
-
----
-
-## 0.1.5 - 2026-06-13
-
-### Added
-
-1. Added Token-2022 program support
-2. Added integration tests for the Token-2022 composers
-
-### Changed
-
-1. Decoupled Token-2022 from the SPL composers via a shared mixin
-
-### Fixed
-
-1. Fixed `TransferChecked` instruction layout documentation
-
----
-
-## 0.1.3 - 2025-06-11
-
-### Added
-
-1. Added `Solace::Instructions::AssociatedTokenAccount::CreateIdempotentAccountInstruction`
-2. Added `Solace::Composers::AssociatedTokenAccountCreateIdempotentAccountComposer`
-
-### Changed
-
-1. Renamed `Solace::Instructions::AssociatedTokenAccount::CreateAssociatedTokenAccountInstruction` to `Solace::Instructions::AssociatedTokenAccount::CreateAccountInstruction` with backwards compatibility
-
----
-
-## [0.1.2] - 2025-05-11
-
-### Added
-
-1. Added support for closing SPL token accounts with:
-  - `Solace::Composers::SystemProgramCreateAccountComposer`
-  - `Solace::Instructions::SystemProgram::CreateAccountInstruction`
-
-## [0.1.1] - 2025-05-11
-
-### Added
-
-1. Added support to inject encoding externally to get the data with respective encoding.
-
-## [0.1.0] - 2025-18-10
-
-**NOTE (Breaking):**
-All previous `prepare_*` Program methods have been renamed to `compose_*` and now return an **unsigned composer instance**. This enables composition and extensibility that weren’t possible when methods returned a signed transaction that was only editable via low-level manipulation.
-Additionally, unless explicitly required by a composer’s instruction, the `payer:` keyword has been removed from the new `compose_*` methods and is instead only used in their execution counterparts (e.g., `compose_mint_to` → `mint_to`). This allows specifying the fee payer when building the final transaction, while keeping composition steps payer-agnostic.
-
-### Added
-
-1. **`Solace::Tokens`** — a structured registry and lookup system for Solana token metadata.
-
-   - Developers can define token details via a YAML configuration file scoped by network (e.g., `mainnet`, `devnet`).
-   - Programmatic access to token metadata:
-
-     ```ruby
-     Solace::Tokens.load(path: 'tokens.yml', network: :devnet)
-     Solace::Tokens::USDC.decimals  # => 6
-     Solace::Tokens.fetch('USDC')   # => <Solace::Tokens::Token ...>
-     Solace::Tokens.where(decimals: 6)
-     ```
-
-   - Dynamically registers constants for each token symbol (`USDC`, `SOL`, etc.).
-   - Safety improvements to preserve internal constants (`Token`) during reloads.
-
-2. **`SystemProgramCreateAccountComposer`** — composer for building account creation flows via the Solana System Program.
-
-   - Wraps `SystemProgram::CreateAccountInstruction`.
-   - Handles lamport allocation, rent exemption, and ownership assignment.
-   - Simplifies creation of system-owned and program-owned accounts.
-
-3. **`SplTokenProgramInitializeMintComposer`** — composer for initializing new SPL Token mints.
-
-   - Wraps `SplToken::InitializeMintInstruction`.
-   - Supports decimals, mint authority, and optional freeze authority.
-   - Designed to pair with `SystemProgramCreateAccountComposer` for one-transaction mint creation.
-
-4. **`SplTokenProgramMintToComposer`** — composer for minting tokens to an ATA.
-
-   - Wraps `SplToken::MintToInstruction`.
-   - Supports minting tokens to a destination ATA.
-
-5. **`SplTokenProgramTransferComposer`** — composer for transferring tokens.
-
-   - Wraps `SplToken::TransferInstruction`.
-   - Supports sending SPL tokens.
-
-6. **`Solace::Connection`** — cached blockhash accessors.
-
-   - Added `last_fetched_blockhash` and `last_fetched_block_height`.
-   - Stores the most recently retrieved blockhash and corresponding `lastValidBlockHeight`.
-   - Enables reuse without re-fetching between sequential transactions.
-   - `get_latest_blockhash` now sets these values automatically.
-
-7. **`TransactionComposer`** — instruction ordering helpers.
-
-   - Added `prepend_instruction` and `insert_instruction` for finer control of instruction order.
-
-8. **`Transaction`** — signature helper.
-
-   - Added `transaction.signature` to get the signature from a signed transaction.
-
-9. **Program method options** — higher-level control.
-
-   - Added `execute`, `sign`, and a yield block to relevant Program methods for flow control and composer access.
-
-### Changed
-
-1. `TransactionComposer#build_instructions` now flattens arrays so composers can return multiple instructions (e.g., create an account then initialize it).
-
-2. `Connection#get_latest_blockhash` now uses the connection’s expected commitment (or provided options) and returns `[blockhash, lastValidBlockheight]`.
-
-3. Default commitment level changed to `processed` in `Solace::Connection`.
-
-4. SPL Program: renamed/adjusted kwargs for `compose_create_mint` and moved signing logic to `create_mint`.
-
-5. SPL Program: `compose_mint_to` moved signing logic to `mint_to`.
-
-6. SPL Program: `compose_transfer` moved signing logic to `transfer`.
-
-7. SPL Program: `create_mint`, `compose_create_mint`, and `compose_create_associated_token_account` now accept separate `funder` and `payer` keys. Both may be the same value, but splitting them allows one account to pay transaction fees while another covers rent exemption.
-
-8. All executable Program methods now return the **Solace transaction instance** instead of an encoded signature.
-
-9. Updated `test/bootstrap.rb` to use composers for setting up test fixtures in a single transaction.
-
-### Fixed
-
-- Improved token loading safety in `Solace::Tokens` to prevent internal constant removal during reloads.
-
----
-
-## [0.0.9] - 2025-08-12
-
-### Added
-
-1. Added `get_program_accounts` to `Solace::Connection`.
-
-### Changed
-
-### Fixed
-
-1. Removed use of the `try` method for supporting non-rails environments.
-
-## [0.0.8] - 2025-08-11
-
-### Added
-
-1. Added `load` method to `Solace::Constants` to load constants from a YAML file. This method allows for loading constants from a YAML file (i.e. custom program addresses and mint accounts).
-2. Added `to_s` and `address` method to `Solace::Keypair` and `Solace::PublicKey` to return the public key as a Base58 string.
-3. Added `get_signature_status` and `get_signature_statuses` to `Solace::Connection`.
-4. Added `RPCClient` to `Solace::Utils` to handle HTTP requests to a Solana RPC node.
-5. Added `Errors` module to `Solace::Utils` to handle errors from the HTTP requests made to the Solana RPC node.
-
-### Changed
-
-1. All methods that take a `Solace::Keypair` or `Solace::Pubkey` where an address is needed now also accept a plain string address. This prevents the need of creating instances of the classes when all that is needed is the address. This is with the exception of the low-level instruction builders, which only expect the correct data and indicies with no required casting.
-2. Changed `wait_for_confirmed_signature` method to accept a `timeout`, `interval`, and `commitment` arguments.
-
-### Fixed
-
-1. Fixed `get_or_create_address` method in `Solace::Programs::AssociatedTokenAccount` to return the address of the associated token account if it already exists by checking if there is any data at the address.
-
-## [0.0.7] - 2025-08-09
-
-### Added
-
-1. Added `AssociatedTokenAccountProgramCreateAccountComposer` with tests.
-
-### Changed
-
-1. Updated `AssociatedTokenAccount` to use `AssociatedTokenAccountProgramCreateAccountComposer` and sign the transaction in the `create_associated_token_account` method instead of the `compose_create_associated_token_account` method.
-
-### Fixed
-
-## [0.0.6] - 2025-08-07
-
-### Added
-
-1. Added `from_address` method to `Solace::PublicKey`.
-2. Change docs on most methods to include an `@example` section.
-
-### Changed
-
-1. Change `private_key` method on Keypair to `pivate_key_bytes`
-2. Change README to include a practical example of using composers.
-
-### Fixed
-
-1. Fix `encode_signatures` method in `Solace::Serializers::TransactionSerializer` to correctly count the number of signatures using the `num_required_signatures` field in the message.
-
-## [0.0.3] - 2025-07-30
-
-### Added
-
-1. Moved `TransferCheckedInstruction` and `TransferInstruction` to `Solace::Instructions::SystemProgram` namespace.
-2. Added `get_token_account_balance` to `Solace::Connection`.
-3. Added `get_or_create_address` to `Solace::Programs::AssociatedTokenAccount`.
-4. Added Composer system for handling accounts and instructions in a higher level abstraction.
-5. Added `SystemProgramTransferComposer` to `Solace::Composers` namespace.
-6. Added `SplTokenProgramTransferCheckedComposer` to `Solace::Composers` namespace.
-7. Moved TransferCheckedInstruction to proper namespace `Solace::Instructions::SplToken::TransferCheckedInstruction`.
-8. Updated `get_or_create_address` to wait for confirmation before returning the address in `Solace::Programs::AssociatedTokenAccount`.
-9. Moved default options to instance variable in `Solace::Connection`.
-10. Moved test setup to `test/bootstrap.rb` and added rake task `bootstrap` to run it.
-
-### Changed
-
-THESE ARE BREAKING CHANGES FROM 0.0.2 TO 0.0.3. Solice is still in alpha and the API is subject to change.
-
-There was a bit of a refactoring of the codebase to make it more maintainable and to make it easier to add new features. Additonally, the SDK now has `Composers` for handling accounts and instructions in a higher level abstraction. These composers are used in the tests and can be used in your own code as well.
-
-Soon, YARD documentation will be added to the SDK and published to https://solace-rb.github.io/solace/.
-
-Stay tuned.
-
-### Fixed
-
-N/A

data/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2025 Sebastian Scholl
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.