- What is arkecosystem/laravel used for?
- It is a Laravel bridge for Ark Core. It provides service provider and configuration support and exposes ARK client functionality for querying wallets, transactions, and blockchain data from a Laravel application. Use it when you want ARK Ecosystem features without writing your own Laravel integration layer.
- How do I install arkecosystem/laravel?
- Install it with Composer using composer require arkecosystem/laravel. Laravel package discovery should register the service provider automatically on supported versions; if not, add the provider to config/app.php. Publish any package configuration after installation so you can set your ARK connection values.
- Which Laravel and PHP versions does arkecosystem/laravel support?
- Supported versions depend on the package release and are defined in its composer.json constraints. Check the repository and Packagist metadata for the Laravel and PHP ranges before installing. If you are on an older Laravel version, verify compatibility rather than assuming the latest release will work.
- How do I configure the ARK Core connection?
- The package includes configuration support for connecting to ARK Core. Publish the configuration file and set the endpoint, network, and any other settings required by your ARK environment. Keep environment-specific values in your .env file and avoid committing secrets.
- Can I query wallet balances and transactions with this package?
- Yes. The bridge gives Laravel applications access to ARK client functionality for querying wallets, transactions, and blockchain data. You can call those client methods from controllers, services, jobs, or Artisan commands. Check the underlying ARK client documentation for exact method names and response shapes.
- Do I need to run my own Ark Core node to use arkecosystem/laravel?
- Not necessarily. The package is a bridge to ARK Core functionality, so you need a reachable ARK Core endpoint or API, which may be hosted by you or provided by your infrastructure. Whether a local node is required depends on your configuration and network requirements. Confirm the expected endpoint type in the package configuration.
- Is arkecosystem/laravel suitable for production?
- Evaluate it like any blockchain integration: review the repository's release history, open issues, test coverage, and Composer constraints. Since it connects to ARK Core, also consider endpoint reliability, timeouts, and error handling in production. Pin a tested version and monitor the package for maintenance updates.
- How do I test ARK integration in a Laravel app?
- Keep ARK calls behind your own service classes so you can swap in fakes during tests. If the package uses Laravel's HTTP client, use Http::fake to return controlled ARK responses. Use a separate test configuration and avoid hitting a live ARK Core node in automated tests.
- What are alternatives to arkecosystem/laravel?
- Alternatives include using the underlying ARK PHP client directly, wrapping ARK API calls in your own Laravel service, or choosing another Laravel blockchain integration that fits your use case. The bridge mainly saves setup time by providing service provider and configuration support. Compare maintenance status and feature coverage before switching.
- Can I use arkecosystem/laravel in Laravel queues and scheduled tasks?
- Yes, because the package exposes ARK client functionality that can be called from Laravel jobs, commands, and schedulers. Make sure your queue workers handle network timeouts and retries cleanly. For high-volume workloads, consider rate limits and whether calls should be batched.