- What is trustenterprises/hashgraph used for in Laravel?
- It is a Laravel/PHP SDK for adding Hedera Hashgraph functionality through Trust Enterprises hosted REST API. It provides helpers for accounts, tokens, consensus topics, and network requests, plus a Laravel service provider, facade, and config file. It is useful when you want Hedera features in a Laravel app without using the native Hedera SDK directly.
- How do I install and configure trustenterprises/hashgraph in Laravel?
- Install with composer require trustenterprises/hashgraph, then publish the package config file and set the API endpoint and API key in your .env file. Laravel auto-discovery registers the service provider, and you can inject the facade or underlying client. A basic testnet call can be wired up quickly, but confirm vendor key provisioning and endpoint details first.
- Does trustenterprises/hashgraph connect directly to Hedera Hashgraph?
- No, it is a client for Trust Enterprises hosted Hedera REST API, not a direct Hedera SDK integration. Your application calls the vendor's abstraction, which then talks to Hedera. That means transaction semantics, error handling, and supported features are bounded by the vendor's API contract.
- Who holds the private keys when using this Laravel Hedera package?
- Credential and signing custody sit with the vendor rather than your application, according to the assessment. The API key authorizes actions through the hosted service, so leakage can potentially allow token movement or message submission on the ledger. Treat API key storage and rotation as financial controls, not just normal Laravel .env hygiene.
- Which Laravel and PHP versions does trustenterprises/hashgraph support?
- The package assumes a modern PHP 8.x baseline and PSR-4 autoloading, but Laravel major-version and PHP-version compatibility after its January 2024 release is unverified. Check the repository composer constraints and test against your exact Laravel and PHP versions. Do not assume current Laravel support without validation.
- Is there a testnet or sandbox endpoint for trustenterprises/hashgraph?
- The assessment flags this as an open question: whether a sandbox or testnet endpoint exists and whether API keys can be obtained self-serve is not confirmed in the repository context. Ask the vendor for written testnet access and rate-limit details before building. Without that, integration feasibility is harder to validate.
- How should I handle retries and duplicate submissions with this package?
- The vendor's API contract defines finality, idempotency, retry safety, and error taxonomy, not Hedera's native SDK contract. You should ask for the vendor error model for partial failures and duplicate submissions, then implement idempotency keys or application-level safeguards if supported. Do not assume retries are safe by default.
- Can I use trustenterprises/hashgraph for multi-tenant apps or local signing?
- It is a poor fit for multi-tenant SaaS where each tenant needs its own on-ledger identity, and it does not provide local signing because custody is with the vendor. It fits better in a Laravel monolith or service that can use one vendor-operated credential. For per-tenant identity or local key control, use the official Hedera PHP SDK or direct mirror-node REST.
- What are the alternatives to trustenterprises/hashgraph for Hedera in PHP?
- Alternatives include the official Hedera PHP SDK for local signing and more control, direct mirror-node REST for read and verification paths, or the vendor's raw HTTP API without this Laravel wrapper. The package itself is a thin wrapper, so designing a narrow LedgerWriter interface makes it swappable. This reduces vendor lock-in.
- Is trustenterprises/hashgraph actively maintained and production-ready?
- Repository signals are weak: four stars, zero dependents, a single maintainer, and a last release in January 2024, with no visible security disclosure process or live API test coverage. There is also no visible SLA or deprecation policy for the commercial service it depends on. Treat it as a high vendor-risk integration and validate maintenance, support, and exit paths before production use.